If the connection type represented a world login, then an extra useless byte is read. An int is read containing the client version, followed but a second int representing the sub version, which is normally 1. The next stage in the login protocol is to decode the client version and details. So RS keeps track of the connection being processed. These connection requests will change a few things in the decoding process. 19 - Represents A login into the world via lobby.18 - Represents a re-connection login after the client has lost communication with the server.16 - Represents an initial login into the lobby.A short is read directly after, which is always 0. The connection requests veries depending on the stage of login you are at or if the client is re-connecting after a lost connection to the server. The first byte read from the login buffer is a connection request. An int is read as the encryption key, and a short is read as the padding. Opcode 4 is responsible for telling the server that there sould be an update in the encyption. This keeps the server updated on the state of the client. Opcode 2 and 3 tell the server that the client is either, 2, performing a log in. The end of the buffer should contain 0xFF as a byte. A bitwise OR mask is written as a byte, containing 0x80 as the compression type. However, if the opcode is 1, then the file request is marked as a "priority" file.Ī file is encoded by first, writing a byte as the type. Opcode 0 and 1 are responsible for telling the server that there is a new file request, the information is read by first reading a byte as the type. These packets tells the server what data to decode. Otherwise, the decoder should read an unsigned byte known as the packets. Afterwords, the client expects a satus code, and an array of 25 integers that represent the update blueprints. Then, the version and sub-version are read as integers. This byte is the buffer length, in bytes, to check if the decoder knows what to expect from the client. If the state of the protocol is to check the version, an unsigned byte is read from the buffer. 14 - Js5 Login (Stage at which the server finishes Js5 update and is ready to show the login screen).15 - Js5 Update (Stage at which the server updates the client by sending cache files).Be warned.įirst, a byte is read to indicate the type of protocol to decode. Note: ShoeOnHead doesn't know what a protocol is. In the next paragraphs, you will learn about how the basic EoC protocol works, from update server to ground items. Very little developers have participated in building the 751 or EoC era, because people either have little interest in EoC, or people don't have the required skill level to contribute. Not surprisingly, little has changed from the jump from pre-EoC to post EoC. The 751 protocol is very similar to previous Runescape revisions.
0 Comments
Leave a Reply. |