Fix: Godot MultiplayerSpawner Not Replicating Children

Here is how to fix Godot 4 MultiplayerSpawner that adds children on the server but never spawns them on clients. You add a player scene under the spawn_path on the server, the player appears locally, but client peers see an empty world. The fix involves understanding spawn_path strict-matching, the _spawnable_scenes whitelist, and the timing of peer registration.

The Symptom

Server starts a session. multiplayer.peer = ENetMultiplayerPeer.create_server(...) succeeds. Server adds child scenes under what should be the spawn parent. The server sees them. Connecting clients show the world without any of those children. Console shows no errors.

What Causes This

Wrong spawn_path target. MultiplayerSpawner replicates children of exactly the node referenced by spawn_path. Adding under a parent of that path or a sibling does nothing.

Scene not in spawnable list. The spawner whitelists scenes via _spawnable_scenes. Spawning a non-listed PackedScene is silently ignored.

Spawned before peer registered. If the server adds children before clients connect, those children are not retroactively replicated unless the spawner is configured for that. New clients see only future spawns.

Authority mismatch on spawn parent. The MultiplayerSpawner’s authority is the server (1) by default. Adding from a client violates the authority model and is rejected.

The Fix

Step 1: Configure the spawner correctly.

# In the editor on the MultiplayerSpawner node:
#   Spawn Path = ../World/Players
#   Spawnable Scenes = [res://player.tscn, res://npc.tscn]

Verify the spawn path resolves at runtime — if your scene tree changes, a stale path silently fails.

Step 2: Spawn from the server.

extends Node

@onready var spawner: MultiplayerSpawner = $MultiplayerSpawner
@onready var players_root: Node = $World/Players

func _on_peer_connected(id: int):
    if not multiplayer.is_server():
        return

    var player = preload("res://player.tscn").instantiate()
    player.name = str(id)              # Unique node names per client
    player.set_multiplayer_authority(id)
    players_root.add_child(player, true)

The set_multiplayer_authority(id) call assigns the client peer ownership so input from that client replicates correctly back to the server’s copy.

Step 3: Connect the peer signals before starting.

func _ready():
    multiplayer.peer_connected.connect(_on_peer_connected)
    multiplayer.peer_disconnected.connect(_on_peer_disconnected)

Step 4: Use _spawn_custom for parameterized spawns. If your spawn needs initialization data, override _spawn_custom:

func _spawn_custom(data: Variant) -> Node:
    var n = preload("res://enemy.tscn").instantiate()
    n.position = data["pos"]
    n.health  = data["hp"]
    return n

# On server
spawner.spawn({ "pos": Vector2(100, 0), "hp": 50 })

The Variant is sent to clients, which call _spawn_custom with the same data to recreate the node.

Step 5: Verify late-join replication. Without explicit handling, clients joining after a spawn will not see existing children. Enable Spawn All Existing on the MultiplayerSpawner if you want clients to receive everything on connect, or write your own catch-up code that re-spawns on peer_connected.

Debugging Tips

Add prints on both server and client around spawn time:

print("Server: adding child ", player.name, " under ", players_root.get_path())
print("Client: children of players_root: ", players_root.get_children())

If the server log shows the child but the client log does not, the spawn message did not replicate. Common causes: spawn_path mismatch, missing scene in spawnable list, peer not registered.

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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Spawn path. Spawnable list. Authority on the parent. Three checks for replicated worlds.”

Related Issues

For multiplayer signaling failures, see Multiplayer Signaling Connection Failed. For autoload visibility issues, see Autoload Not Accessible.

Path matches. Scene listed. Authority set. The world appears for everyone.