AOS REVIVALJoin Discord
Packet ID1160x74
Input // wire record

PositionData

A position-only input shape retained for compatibility tooling. The targeted retail 1.x client does not send it in normal play.

C→SHandledProvisional7 or 13 bytes
Exact field order

Packet 116 wire layout

The first byte is the application packet ID. The rows after it appear in decode order. Sizes exclude ENet headers, the outer wrapper prefix, LZF chunk framing, and compression effects.

Packet 116 PositionData fields in byte order
#FieldEncodingBytesPurpose
0packet_idu81Always 116 (0x74).
1position3 × fixed16 LE or 3 × f32 LE6 or 12The tolerant runtime decoder selects raw floats when 12 payload bytes are available, otherwise fixed-point shorts.
Protocol convention

How to read this layout

  • LE means least-significant byte first.
  • fixed16 is two-byte sign-magnitude at 1/64 precision.
  • orientation16 uses the measured 1/8192 orientation mapping.
  • NUL strings consume their encoded byte length plus one 00 terminator.
  • Counted arrays repeat immediately in the order shown.