|
|
| Line 10: |
Line 10: |
| | k | | k |
| | | | |
| − | == Game Protocol ==
| + | fo teh winnn |
| − | | |
| − | The Game Protocol is the protocol in which game action information is transmitted. The game protocol is encrypted using ISAAC ciphers in order to prevent third party programs from tampering with the stream. The game protocol is made up of packets that are structured like so:
| |
| − | | |
| − | | |
| − | For fixed-size packets:
| |
| − | | |
| − | <tt>opcode, payload[size]</tt>
| |
| − | | |
| − | For variable-sized packets:
| |
| − | | |
| − | <tt>opcode, size, payload[size]</tt>
| |
| − | | |
| − | | |
| − | The ''opcode'' of a game packet is basically an identifier for the type of game action that the packet represents. The ''size'' of the packet is the amount of bytes that the payload of the packet carries, and the ''payload'' is an array of bytes that holds the actual data (information) of the packet.
| |
| − | | |
| − | A ''fixed-size'' packet is a packet whose payload size does never change, and the size for the specified opcode is already known between both client and server. A ''variable-sized'' packet is a packet whose payload size changes according to the situation of the game session.
| |
| | | | |
| | ==Documented Protocols== | | ==Documented Protocols== |
Revision as of 20:11, 13 August 2009
Introduction
The RuneScape Protocol is the language in which the RuneScape client and server communicate. The protocol changes for every version.
The entire protocol is generally separated into two different categories:
- Login Protocol
- Game Protocol
k
fo teh winnn
Documented Protocols
Below is a list of the different protocols that have been documented:
