AOS REVIVALJoin Discord

Packet ID0100x0A

Combat // wire record

UseOrientedItem

Uses an oriented item such as a legacy grenade-family object. The server validates the active tool, cadence, and stock before accepting or relaying it.

BothHandled + sentImplementation-backed21 bytes

Exact field order

Packet 10 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 10 UseOrientedItem fields in byte order
#	Field	Encoding	Bytes	Purpose
0	`packet_id`	u8	1	Always `10` (0x0A).
1	`loop_count`	i32 LE	4	Simulation-loop stamp used for ordering, prediction, or reconciliation.
2	`player_id`	u8	1	Compact player-slot identifier.
3	`tool`	u8	1	Tool/object identifier.
4	`value`	sign-magnitude fixed16 LE (1/64)	2	Item-specific scalar, commonly fuse or charge.
5	`position`	3 × fixed16 LE	6	X, Y, and Z components at 1/64-unit precision.
6	`velocity`	3 × fixed16 LE	6	X, Y, and Z components at 1/64-unit precision.

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.