Thread: Hyperion downgrading?

Results 1 to 6 of 6
  1. #1 Hyperion downgrading? 
    Registered Member Kandarin's Avatar
    Join Date
    Jan 2011
    Posts
    157
    Thanks given
    0
    Thanks received
    9
    Rep Power
    0
    Lets say there was awesome Hyperion based 459 source available for download but I'm stictly 317 programmer, what features would I lose as result of downgrading it to work with 317 client?

    1. I'd have to change the packets to 317 ones
    2. Update Server format
    3. 594+(?) Lobby implemention
    4. ?
    5. ?

    I'm not making this thread to figure out how to leech someone's awesome Hyperion server... but I'm rather trying to find out how easily convertable Hyperion actually is?

    Like if I start out 317, then I get bored of transforming my 317 client into 600 or even 700 revisions, will I be just able to change the packets and roll out with up-to-date revision client?
    Reply With Quote  
     

  2. #2  
    Registered Member
    Ant-Man's Avatar
    Join Date
    Aug 2010
    Posts
    1,018
    Thanks given
    277
    Thanks received
    177
    Rep Power
    452
    Why not go download the original Hyperion? it was 319, or 377...

    Reply With Quote  
     

  3. #3  
    Registered Member thiefmn6092's Avatar
    Join Date
    Dec 2006
    Age
    24
    Posts
    2
    Thanks given
    26
    Thanks received
    389
    Rep Power
    0
    you won't be able to move to one of the 600+ unless you implement the several other components that Jagex has since added into the mix such as the "lobby" server
    Reply With Quote  
     

  4. #4  
    Member
    Join Date
    Nov 2010
    Posts
    62
    Thanks given
    0
    Thanks received
    13
    Rep Power
    0
    Quote Originally Posted by thiefmn6092 View Post
    you won't be able to move to one of the 600+ unless you implement the several other components that Jagex has since added into the mix such as the "lobby" server
    no shit.

    It doesn't take much to convert Hyperion to work with another revision given that you have everything you need to make a smooth transition. To fully implement Grahams cache loader though you will have to work out the format of the cache that belongs to the engine that you are porting to as every time they update their engine, they update their cache (I.E; 194-377 will be fine with Hyperion as the cache format is the same, 420-499 you will have to read up on the format, and newer engine revisions also have a different cache format... but I don't know how much documentation there is for the newer engine cache(s) so you might have to work that out yourself.).
    Quote Originally Posted by The MisJudged View Post
    I am god so i can answer both of ur fucking questions....... revision is scratch and base is 317.
    Reply With Quote  
     

  5. #5  
    Community Veteran


    Join Date
    Jan 2008
    Posts
    2,659
    Thanks given
    494
    Thanks received
    627
    Rep Power
    980
    Quote Originally Posted by deimos_ View Post
    no shit.

    It doesn't take much to convert Hyperion to work with another revision given that you have everything you need to make a smooth transition. To fully implement Grahams cache loader though you will have to work out the format of the cache that belongs to the engine that you are porting to as every time they update their engine, they update their cache (I.E; 194-377 will be fine with Hyperion as the cache format is the same, 420-499 you will have to read up on the format, and newer engine revisions also have a different cache format... but I don't know how much documentation there is for the newer engine cache(s) so you might have to work that out yourself.).
    They don't necessarily change formats after every new-engine update. All JS5 clients (~400-Current) pretty much follow the same format. (There have been slight changes, but not after a new-engine update.) In fact, the format before then is mostly the same as well.
    ~iKilem
    Reply With Quote  
     

  6. #6  
    Registered Member Kandarin's Avatar
    Join Date
    Jan 2011
    Posts
    157
    Thanks given
    0
    Thanks received
    9
    Rep Power
    0
    Antguy didn't even read what I wrote above...

    Quote Originally Posted by deimos_ View Post
    no shit.

    It doesn't take much to convert Hyperion to work with another revision given that you have everything you need to make a smooth transition. To fully implement Grahams cache loader though you will have to work out the format of the cache that belongs to the engine that you are porting to as every time they update their engine, they update their cache (I.E; 194-377 will be fine with Hyperion as the cache format is the same, 420-499 you will have to read up on the format, and newer engine revisions also have a different cache format... but I don't know how much documentation there is for the newer engine cache(s) so you might have to work that out yourself.).
    Knew this, quite easy to do, too.

    Quote Originally Posted by thiefmn6092 View Post
    you won't be able to move to one of the 600+ unless you implement the several other components that Jagex has since added into the mix such as the "lobby" server
    Yep.
    Reply With Quote  
     


Thread Information
Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)


User Tag List

Similar Threads

  1. [PJA/Hyperion] Custom Object Loading [PJA/Hyperion]
    By helloevery1 in forum Snippets
    Replies: 20
    Last Post: 11-06-2012, 12:25 AM
  2. Replies: 6
    Last Post: 06-16-2010, 01:45 PM
Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •