AOS REVIVALJoin Discord
Packet ID0030x03
Entities // wire record

EntityUpdates

A separate moving-entity delta stream retained in the retail protocol surface. BattleSpades currently carries entity changes through other active paths.

InactivePlannedProvisional7 + ΣE bytes
Exact field order

Packet 3 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 3 EntityUpdates fields in byte order
#FieldEncodingBytesPurpose
0packet_idu81Always 3 (0x03).
1loop_counti32 LE4Simulation-loop stamp used for ordering, prediction, or reconciliation.
2entity_countu16 LE2entity count value.
3entities[]Entity record33 + 4I + 2FRepeated packet-21 Entity records without nested packet IDs.
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.