Messages Connection

Every message in the Connection area: its opcode, direction, how far it is verified, and its fields.

Note

Generated from the message declarations at bootstrap 5aae370 by Tools/NexusTomorrow.ProtocolReference. Don't edit it by hand: change the declaration's documentation and regenerate.

Client to server

0x023C Client023C

Opcode	Direction	Verified to
0x023C	client to server	unverified

Field	Bits	Encoding
Unknown0	64	unsigned
Unknown1	64	unsigned
Unknown2	32	unsigned
Unknown3	32	float
Unknown4	32	float
Unknown5	32	float
Unknown6	32	unsigned

0x023D Client023D

Opcode	Direction	Verified to
0x023D	client to server	unverified

Field	Bits	Encoding
Unknown0	6	unsigned
Unknown1	10	unsigned
Unknown2	64	unsigned
Unknown3	64	unsigned
Unknown4	64	unsigned
Unknown5	64	unsigned
Unknown6	64	unsigned
Unknown7	64	unsigned
Unknown8	varies	wide string

0x023E Client023E

Opcode	Direction	Verified to
0x023E	client to server	unverified

Field	Bits	Encoding
Unknown0	32	float
Unknown1	32	float
Unknown2	32	float
Unknown3	32	float
Unknown4	32	float
Unknown5	32	float
Unknown6	32	float
Unknown7	32	float

0x023F Client023F

Opcode	Direction	Verified to
0x023F	client to server	unverified

Field	Bits	Encoding
Unknown0	32	unsigned
Unknown1	32	unsigned
Unknown2	32	unsigned
Unknown3	1	unsigned
Unknown4	31	unsigned

0x0240 FrameTimeReport

Reports how long the client's frames take, in milliseconds.

Opcode	Direction	Verified to
0x0240	client to server	purpose

Field	Bits	Encoding
Unknown0	1	unsigned
Unknown1	31	unsigned
Unknown2	1	unsigned
Unknown3	31	unsigned
Unknown4		the fields below
Unknown4.Unknown0.X	32	float
Unknown4.Unknown0.Y	32	float
Unknown4.Unknown0.Z	32	float
Unknown5	32	float
Unknown6	1	unsigned
Unknown7	31	unsigned

0x038C TaggedMessage

One whole client message, under a tag that depends on which message it is.

Opcode	Direction	Verified to
0x038C	client to server	fields

Field	Bits	Encoding	Meaning
Tag	5	unsigned	The tag: 0x03, 0x0B or 0x13. A message of a given opcode always travels under the same tag.
Payload	varies	byte block, 32-bit length, byte-aligned, the length counts itself	One whole message, from the next byte boundary: its own 32-bit length (counting those four bytes), then its 16-bit opcode and its body.

The client sends it before the world as well as in it: at character select, a Client082D goes out inside one under tag 0x13.

Where the code lives

Piece	Path
Message declarations	Source/NexusTomorrow.Network.World/Message/Model/Connection/
This page's generator	Tools/NexusTomorrow.ProtocolReference/