*** ON THE PACKET AND OPCODE NAMING CONVENTIONS ***


- Packets which are sent by the server should be called SMSG_XXX
	Example: SMSG_MOVE

- Packets which are sent by the client should be called CMSG_XXX
	Example: CMSG_MOVE


- Optionally, when referring to a packet, a number after the packet name can be used, especifying the runescape version.
	Example: CMSG_MOVE_V458	(RS version 458).

- Optionally too, the opcode can be specified:
	Example: CMSG_MOVE_OP206

- Both preffixes can be used: Example: CMSG_MOVE_V458_OP206



*** ON THE PACKET DATA DESCRIPTION CONVENTIONS ***

- The variables in packets can be of different lengths. These should be described in the following way:

# bits: [#xBITS] (# is a number)
One byte: [BYTE]
Two bytes: [WORD]
Four bytes: [DWORD]
Eight bytes: [QWORD]
# bytes: [#xBYTES]

Null-Terminated string: [char*]
Unicode string: [UniStr]


- The variables can have their bytes ordered in different ways. These should be described in the following way:

Standard byte order: 0xAABBCCDD : BIG_ENDIAN
Reverse byte order: 0xDDCCBBAA : LITTLE_ENDIAN
Strange byte order: Use letters. Example: 0xDDBBCCAA