PacketType.hpp File Reference

Network packet type identifiers for client-server communication. More...

#include <cstdint>

Include dependency graph for PacketType.hpp:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Enumerations
enum class	PacketType : uint8_t {   INPUT , ASSIGN_CLIENT_ID , UPDATE_REGISTRY , PARTICLE_SPAWN ,   PING , PONG , MATCH_STATE , KILL_EVENT ,   UPDATE_REGISTRY_DELTA , SHOT_DEBUG_REPORT , SHOT_INTENT , JOIN_LOBBY ,   JOIN_FAILED , PLAYER_READY , PLAYER_UNREADY , LOBBY_UPDATE ,   LOBBY_STATE , HOST_READY , START_MATCH , TEXT_CHAT ,   VOICE_FRAME , VOICE_STATE , PHYSICS_DIAG_RECORDING , LOCAL_SERVER_DISCOVERY_REQUEST ,   LOCAL_SERVER_DISCOVERY_RESPONSE }
	Identifies the type of a network packet. More...

Detailed Description

Network packet type identifiers for client-server communication.

Enumeration Type Documentation

PacketType

enum class PacketType : uint8_t

strong

Identifies the type of a network packet.

Enumerator
INPUT	Client -> Server: player input snapshot.
ASSIGN_CLIENT_ID	Server -> Client: assign the connecting client its entity ID.
UPDATE_REGISTRY	Server -> Client: full ECS registry state snapshot.
PARTICLE_SPAWN	Server -> All clients: replicated particle/VFX event.
PING	Client -> Server: latency measurement (carries uint64_t timestamp).
PONG	Server -> Client: latency measurement reply (echoes timestamp).
MATCH_STATE	Server -> All clients: match phase transition update.
KILL_EVENT	Server -> All clients: player kill notification.
UPDATE_REGISTRY_DELTA	Server -> Client: delta against a previously-received full snapshot. PR-10 (server-perf): wire format of the payload is [currentTick:u32] [fromTick:u32] [baselineSize:u32] [rleDelta:bytes] where rleDelta is an RLE stream of (skipBytes:u32, copyBytes:u32, copyData:u8[copyBytes]) triples — apply over a copy of the baseline at fromTick to reconstruct the full snapshot bytes for tick currentTick. Clients drop the packet if they don't currently have the baseline; a periodic UPDATE_REGISTRY (full keyframe) recovers.
SHOT_DEBUG_REPORT	Server -> single shooter: lag-comp shot debug snapshot. PR-20: CSGO sv_showimpacts-style debug visualizer. Sent only to the shooter client (not broadcast) immediately after the server resolves a hitscan shot. Carries the rewound state the server saw when it processed the shot — origin + direction + hit point + per-target rewound capsule list — so the client can overlay "what server hit" (red) on top of "what I aimed at" (blue) and visually inspect lag-comp alignment. Wire format defined in network/ShotDebugReport.hpp.
SHOT_INTENT	Client -> Server: animation-state assertion for a single shot. PR-27 (netsync): on the rising edge of input.shooting, the client snapshots the target's animation state (5 ClipSampler slots) and sends it alongside the input. The server, when it processes the corresponding INPUT, looks up the historical AnimSnapshot for the target at the rewound tick and computes anim_snapshot::delta(client, server). When that delta is below an empirically-tuned epsilon, the server may accept the client's view of the pose (PR-27b future work — accept logic). Currently the delta is logged to server_shots.csv for telemetry only (PR-27a — instrument first, tune epsilon from data). Wire format: [type:u8] [shotInputTick:u32] [targetClientId:u16] [AnimSnapshot:20B = 5 * (clipIdRaw:u8, timeRatioQ:u16, weightQ:u8)] → 27 bytes per shot. Sent on UDP alongside INPUT (rising-edge only; ~10 Hz worst case → ~270 B/s/client).
JOIN_LOBBY	Client -> Server: request to join the lobby (carries player name).
JOIN_FAILED	Server -> Client: lobby join failed (carries error message).
PLAYER_READY	Client -> Server: player signals ready for match start.
PLAYER_UNREADY	Client -> Server: player cancels ready status.
LOBBY_UPDATE	Server -> All clients: lobby state update (player list, match start countdown).
LOBBY_STATE	Server -> single Client: full lobby snapshot on join. Format: [count:u32][LobbyPlayer*count].
HOST_READY	Client -> Server: host signals ready to start match.
START_MATCH	Client -> Server: host requests match start.
TEXT_CHAT	Client <-> Server: bounded UTF-8 all-chat message.
VOICE_FRAME	Client <-> Server: Opus voice frame for proximity chat.
VOICE_STATE	Client <-> Server: push-to-talk state hint for HUD indicators.
PHYSICS_DIAG_RECORDING	Client -> Server: start/stop authoritative physics CSV recording.
LOCAL_SERVER_DISCOVERY_REQUEST	client broadcasts to server, which responds with response below
LOCAL_SERVER_DISCOVERY_RESPONSE