Networked games

How SDF breaks props in multiplayer with nothing to turn on - the server decides, a small state per altered prop replicates, recent and late breaks, dedicated servers, World Partition, loot and what is not replicated.

Two players in the same crypt: one strikes a pot, and both see it break, the same pieces starting the same way, with the same sound. A third player who joins a minute later finds the pot already broken, without hearing it break.

SDF breaks props in multiplayer games with nothing to turn on. As soon as the game runs as a listen server, a dedicated server or a client, the server decides every break and every machine shows it. In single player (NM_Standalone) none of this exists and nothing changes.

The server decides

Damage, health, power, locks, breaks, fire, explosions, Break What Rests On It and propagation are judged on the server only.

  • On a client, a hit, ForceDestroy, Ignite, Extinguish or ResetDestruction changes nothing. A hit’s result says Server Decides (ESDFRejectionReason::ServerDecides).
  • The server’s own hits reach the prop on the server: an animation notify, a projectile or a collision runs there too.
  • A game that sends a client’s hit to the server does it through its own server RPC, as for Unreal damage.
  • There is no prediction: a client sees its hit break the prop about half its ping later.

What travels

The server makes one ASDFNetworkRelay per world, always relevant, the first time one of its props changes. SDF makes it; it is never placed.

For each prop the server altered, it replicates a small state: broken or not, its damage stage, its fire, the pieces Partial Break took off, and the hit and seed of its last break. It never replicates the debris.

  • Each broken prop costs a few dozen bytes, once. Nothing travels while nothing breaks.
  • Lost packets are sent again until they arrive.

The same break everywhere

Each machine breaks the prop itself, with the server’s hit and seed:

  • Swap And Scatter pieces start at the same places with the same pushes;
  • a Chaos break gives its pieces the same starting speeds;
  • glass cracks into the same shards;
  • an Animated Break plays the same animation, from where the server’s has reached.

Physics then runs on each machine: the debris end up close, not identical.

Recent or late breaks

A break that reaches a machine less than 2 s after the server made it is seen and heard there.

A break older than that, for a player who joins after it or a part of the world that loads again, is set at once and silent:

  • with Remember Debris Layout, its debris are set down where they lay on the server, sent once they have settled, 10 s after the break;
  • without it, they drop from the seed, unseen and unheard;
  • an Animated Break shows its last pose.

See Broken props remembered.

On the server only, and on every machine

On the server onlyOn every client
LootThe debris
The break’s noise for the AIThe sounds
Explosion damage to charactersThe effects and decals
Burn and crush damageThe damage stages
Break What Rests On It, propagationThe fire
The persistence records and savesHiding the intact prop and turning its collision off
OnDestructibleBroken
The navigation changes

Resets

A zone reset, a death or a rest at a checkpoint called on the server, through NotifyRestAtCheckpoint, NotifyPlayerDeath, ResetZone or ResetDestruction, makes the props whole on every machine. Permanent props stay broken everywhere. The cheat commands SDF.ResetAll, SDF.ResetZone and SDF.ListBroken are typed on the server.

Dedicated server

A dedicated server judges every break, hides the intact prop and turns its collision off, and spawns no debris, sound or effect: nobody is there to see them.

  • Debris Affects Navigation therefore has no effect on a dedicated server.
  • An Animated Break still plays there: its pieces carry and crush the characters.
  • With Remember Debris Layout, the dedicated server has no debris to send: the machines that arrive later drop theirs from the seed.

Which props are networked

  • Props placed in the level, and props the server spawns from a replicated actor. A prop a client spawns on its own is never networked.
  • Each prop is found on every machine by its persistent key (see Its key), so a prop of a World Partition cell keeps its state when its cell unloads and loads again, on the server and on the clients.
  • In a World Partition cell, the persistent key uses the world’s map rather than the cell’s level: the same key in the editor, PIE and a packaged game.

Loot

The server spawns it. Reaching the clients is the loot class’s own replication. In a networked game, SDF writes a warning in the log when the loot class does not replicate.

Fire, explosions and partial breaks

  • Fire. The server lights and puts out every fire; every machine shows it. Burn damage is dealt on the server. See Fire and burning props.
  • Explosions. Only the machine with authority sets the explosion off. The other machines see the break, and the props it breaks reach them as their own breaks. See Explosions, break point and cover.
  • Partial breaks. Each hit that breaks pieces off travels with its hit and seed: recent, it is replayed on each machine; late, the fallen pieces are set at once, silent.

Diagnostics

A hit on a client returns the rejection reason Server Decides. Cannot Show Break, which on a single machine means the break was rolled back because nothing could show it, behaves differently in a networked game: the break commits instead, because the server decided it. See Diagnostics.

Not replicated

A Simulated prop pushed about before it breaks moves on each machine on its own; its break starts where it stands on each. There is no client prediction. Validate your integration, including networked play and World Partition, before relying on it.

Last updated: 2026-10-27

Type to search titles, sections and keywords.