World Packet: Difference between revisions
Jump to navigation
Jump to search
(Change header to CMSG_Header template) |
(Add World Packets category and info about header encryption) |
||
| Line 10: | Line 10: | ||
{{CMSG_Header}} | {{CMSG_Header}} | ||
All world packet headers are encrypted using the session key negotiated during login, except for [[SMSG_AUTH_CHALLENGE]] and [[CMSG_AUTH_SESSION]]. | |||
[[Category:Packet]] | [[Category:Packet]] | ||
[[Category:World_Packets]] | |||
Revision as of 18:56, 23 May 2021
World Packets are the majority of communication between the client and the world server.
World packets consist of a packet size, an Opcode and a body.
For server messages (SMSG) the headers look like:
| Offset | Size / Endianness | Type | Name | Description |
|---|---|---|---|---|
| 0x0 | 2 / Big | uint16 | size | Size of the packet including the opcode field. |
| 0x2 | 2 / Little | uint16 | opcode | Opcode for the packet. Determines the structure of the body. |
For client messages (CMSG) the headers look like:
| Offset | Size / Endianness | Type | Name | Description |
|---|---|---|---|---|
| 0x0 | 2 / Big | uint16 | size | Size of the packet including the opcode field. |
| 0x2 | 4 / Little | uint32 | opcode | Opcode for the packet. Determines the structure of the body. |
All world packet headers are encrypted using the session key negotiated during login, except for SMSG_AUTH_CHALLENGE and CMSG_AUTH_SESSION.