Why doesn't my MultiplayerSynchronizer replicate position?

The Replication Config asset starts empty. Open the synchronizer's Replication panel and add each property (e.g. position, rotation, animation_state). Each entry can be flagged Spawn (initial value), Sync (continuous), or both.

What's the difference between Spawn and Sync?

Spawn: replicates once when the spawned scene appears via MultiplayerSpawner. Sync: replicates continuously thereafter. Most properties want both. Use Spawn-only for things that don't change post-spawn.

Why is root_path important?

Root Path on the synchronizer points at the node whose properties to replicate. Default is the parent. If your synchronizer is on a child node and the synchronized properties are on a sibling, set root_path explicitly.

Fix: Godot 4 MultiplayerSynchronizer Replication Config Empty

Quick answer: Open MultiplayerSynchronizer’s Replication panel. Add each property you want to sync (e.g. :position, :rotation). Tick Sync (continuous). Save the Replication Config resource.

Spawned via MultiplayerSpawner. Clients see the spawn but movement doesn’t replicate. The synchronizer exists; its Replication Config is empty.

The Symptom

Network spawn works. Position freezes on clients while moving on the server. Adding more properties to the actor doesn’t change the symptom.

The Fix

Step 1: Open the synchronizer. Select the MultiplayerSynchronizer node. In the dock at the bottom, find the Replication tab.

Step 2: Add properties.

Replication panel:
  + .position           Sync: true   Spawn: true
  + .rotation           Sync: true   Spawn: true
  + AnimationPlayer:current_animation
                        Sync: true   Spawn: false
  + health              Sync: true   Spawn: true

Format: NodePath:property for child nodes; :property for the synchronizer’s root.

Step 3: root_path. Default is the parent. If the synchronizer needs to replicate a sibling’s state, set root_path explicitly.

Authority

By default, the multiplayer authority of the parent owns the data. For player-controlled actors, set authority to the owning peer with set_multiplayer_authority(peer_id) on spawn. The synchronizer reads from the authority and pushes to others.

Visibility

For per-peer visibility (only show to teammates), set the Visibility list. add_visibility_filter callback determines who sees this synchronizer.

Verifying

Run a host + client. Move on the host. Client sees position update. Open Remote → Network in the debugger to confirm packets are flowing for this synchronizer.

Understanding the issue

Multiplayer code has a different correctness model than single-player code. It must tolerate latency, packet loss, and out-of-order delivery while preserving game-state consistency. Each tolerance is engineering work; you choose which network conditions to handle.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Add properties to Replication Config. Sync flag. Authority right. Clients see updates.”

Related Issues

For MultiplayerSpawner replication, see spawner. For RPC not firing, see RPC.

Add properties. Sync ticked. State propagates.