Skip to content

Step 09: Multiplayer

Jump to bottom
BavGames edited this page Jul 11, 2026 · 4 revisions

Works in Listen Server and Dedicated Server. Single player needs nothing from this page.

The model: server-authoritative

  • Only the server saves and loads. Save/Load called on a client is refused with a clean error. Gate your UI with Has Save Authority.
  • The save file lives on the server. Clients have no save files.
  • A client can ask the server by adding a Save Request Component to its PlayerController and calling Request Save / Request Load - the server decides.

What clients receive automatically

After a server load, the restored state is mirrored to every client - no setup:

  • Actor and component positions (including physics meshes)
  • SaveGame variable values at the moment of the load
  • Destroyed actors are destroyed on clients too
  • On Loaded fires on clients as well - update text renders, materials, visuals there
  • Late joiners receive the last loaded state when they connect

Delivery is bandwidth-safe: only changed entries are sent, in paced batches, with quantized transforms, and the sync actor costs zero network time between loads.

"Load finished" event on clients

Clients cannot bind to the Save Subsystem's load events (loads run on the server). For client UI ("Game Loaded" popup, fade-in), bind to On Load Complete Replicated on the USS Replication Controller actor (find it with Get Actor Of Class after joining). It fires on every machine once the loaded state has been delivered.

What still needs YOUR replication

The sync mirrors the moment of the load - it is a snapshot, not live replication. A variable that changes during play reaches clients only if you mark it Replicated (with RepNotify if you drive visuals from it). This is the standard Unreal rule; the save system does not change it.

Rule of thumb: loaded state = handled by the plugin; live gameplay state = your replication.

Two safety rules built in

  • Clients never locally move a replicated actor's root (server movement replication owns it).
  • Clients never touch player-controlled pawns (their movement is client-predicted).

Testing checklist

  1. PIE settings: Net Mode = Play As Listen Server, Number of Players = 2. (Play Standalone starts two separate offline games - nothing can replicate.)
  2. Save and load in the server window.
  3. Both windows must show identical restored state.

Log lines to look for:

Server: Load 'Slot': syncing 12 actor transform(s) to 1 connected client(s).
Client: Replication controller ready on client (12 sync item(s) present).
Client: applied restored transforms for 12 of 12 actor(s).

If the "controller ready" line never appears in the client log, there is no replication in the session - check the PIE Net Mode first.

Next: Step 10: Persistent & Custom Objects

Clone this wiki locally