AOS REVIVALJoin Discord

Packet ID0060x06

Combat // wire record

ShootPacket

A client firearm request. The server validates cadence, origin, orientation, weapon state, and penetration before resolving authoritative hits.

C→SHandledLive-verified40 bytes

Exact field order

Packet 6 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 6 ShootPacket fields in byte order
#	Field	Encoding	Bytes	Purpose
0	`packet_id`	u8	1	Always `6` (0x06).
1	`loop_count`	i32 LE	4	Simulation-loop stamp used for ordering, prediction, or reconciliation.
2	`shooter_id`	u8	1	Player slot that initiated the action.
3	`shot_on_world_update`	i32 LE	4	WorldUpdate reference used to associate the predicted shot.
4	`origin`	3 × IEEE-754 f32 LE	12	X, Y, and Z floating-point components.
5	`orientation`	3 × IEEE-754 f32 LE	12	X, Y, and Z floating-point components.
6	`damage`	i16 LE	2	Client-reported weapon damage; never trusted without server validation.
7	`penetration`	i16 LE	2	Client-reported penetration value.
8	`shot_flags`	u8	1	Bit 0 affect_shooter; bit 1 secondary fire.
9	`seed`	u8	1	Deterministic random seed used to reproduce client effects.

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.