Quick answer: Spawn nodes through the MultiplayerSpawner's spawn path on the authority, configure the spawnable scenes, and set multiplayer authority correctly.
A MultiplayerSpawner not syncing is spawning outside its path or wrong authority. Here is how to fix it.
How to fix it
1. Spawn through the spawner path
Add spawned nodes under the spawner's configured spawn path (or via its spawn function) on the server. Nodes added elsewhere are not tracked by the spawner and never replicate to clients.
2. Configure spawnable scenes
Register the scenes the spawner is allowed to spawn. If a scene is not in the spawnable list, the spawner cannot replicate it. Add it so clients can instantiate the right scene.
3. Set authority correctly
Spawn on the multiplayer authority (usually the server) and ensure authority is assigned so replication flows to clients. Spawning on a client, or with wrong authority, does not propagate as expected.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.