AOS REVIVALJoin Discord
Packet ID0000x00
Timing // wire record

ClockSync

Round-trip clock synchronization. The server returns its loop count while keeping the retail client one simulation tick ahead.

BothHandled + sentImplementation-backed9 bytes
Exact field order

Packet 0 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 0 ClockSync fields in byte order
#FieldEncodingBytesPurpose
0packet_idu81Always 0 (0x00).
1client_timei32 LE4Client clock value echoed through the synchronization exchange.
2server_loop_counti32 LE4Authoritative server simulation loop.
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.