Client Multiplayer Netcode

Client-side connection, prediction, correction, and diagnostics layer for multiplayer play. More...

Files
file	ClientPrediction.cpp
	Implementation of client-side local prediction, replay, and recovery helpers.
file	ClientPrediction.h
	Client-side local prediction history, correction replay, and recovery state.
file	NetClient.Connection.cpp
	Connection lifecycle and transport teardown for the client-side multiplayer connection hub.
file	NetClient.cpp
	Shared construction and common state access for the client-side multiplayer connection hub.
file	NetClient.h
	Client-side multiplayer connection lifecycle and packet endpoint.
file	NetClient.Protocol.cpp
	Authoritative message caching and protocol handlers for the client-side multiplayer connection hub.
file	NetClient.Runtime.cpp
	Network pumping and outgoing runtime messaging for the client-side multiplayer connection hub.
file	ClientDiagnostics.cpp
	Client-side multiplayer diagnostics recorder and report writer.
file	ClientDiagnostics.h
	Client-side multiplayer diagnostics data model and recorder.

Detailed Description

Client-side connection, prediction, correction, and diagnostics layer for multiplayer play.

This is the core of the client networking work.

It is the layer that turns server-driven multiplayer state into something the game can actually use:

• NetClient handles transport, handshake, message intake, and cached authoritative state
• ClientPrediction handles owner-local prediction, replay, and recovery after correction
• ClientDiagnostics records what happened so networking behaviour can be inspected and tested

The important design boundary is simple: this subsystem owns multiplayer netcode behaviour on the client, while MultiplayerLevelScene owns presentation and match scene flow.

Ownership

The client has to do three things at once:

• stay connected to an authoritative server
• feel responsive for the owning player
• stay debuggable when prediction or delivery goes wrong

That is why transport, prediction, and diagnostics are kept adjacent but distinct.

System View

The scene reads authoritative state from NetClient, while prediction and diagnostics stay in adjacent client-netcode helpers.

Code Layout

NetClient stays one class, but its implementation is split by concern: connection, runtime, and protocol/cache handling.

Relevant code:

• Net/Client/NetClient.h
• Net/Client/NetClient.cpp
• Net/Client/NetClient.Connection.cpp
• Net/Client/NetClient.Runtime.cpp
• Net/Client/NetClient.Protocol.cpp
• Net/Client/ClientPrediction.h
• Net/Client/ClientPrediction.cpp
• Net/ClientDiagnostics.h
• Net/ClientDiagnostics.cpp

Previous	Next
Authoritative Server	Multiplayer Level Scene