Quick answer: MultiplayerSynchronizer broadcasts to every peer by default (public_visibility = true). For area-of-interest or team-only state, set public_visibility = false and call set_visibility_for(peer_id, visible) to scope updates.

You build a multiplayer game with 32 players per match. Every player’s transform is a MultiplayerSynchronizer. Bandwidth usage is terrible, and cheaters on the other side of the map know exactly where your stealth character is hiding. The fix is a visibility filter that only sends state to players who can actually see the object.

Visibility Modes

Each synchronizer has a boolean public_visibility:

AOI Example

extends Node

@onready var sync = $MultiplayerSynchronizer
@onready var aoi_area = $Area3D

func _ready():
    sync.public_visibility = false
    aoi_area.body_entered.connect(_on_peer_entered)
    aoi_area.body_exited.connect(_on_peer_exited)
    multiplayer.peer_disconnected.connect(_on_peer_disconnected)

func _on_peer_entered(body):
    if body.is_in_group("player"):
        sync.set_visibility_for(body.get_multiplayer_authority(), true)

func _on_peer_exited(body):
    if body.is_in_group("player"):
        sync.set_visibility_for(body.get_multiplayer_authority(), false)

func _on_peer_disconnected(peer_id):
    sync.set_visibility_for(peer_id, false)

The AOI Area3D is a large sphere around the object. When a player’s body enters, they become visible for this synchronizer. When they leave, they stop receiving updates. When they disconnect, cleanup removes them from the visibility table.

MultiplayerSpawner Visibility

Spawners also have a spawn_function and visibility_changed signal. Use visibility_changed to hide the object’s visual representation on peers who can’t see it, not just stop replicating state. A client with an invisible opponent still sees a stale ghost unless you handle the signal.

Performance

Per-peer visibility has a cost: every tick checks the per-peer table. For 100 synchronizers and 32 peers, that’s 3200 checks per tick. This is still cheaper than sending 3200 pointless packets, but if you have extreme object counts, use spatial partitioning (like grid cells) instead of per-object AOI.

Verifying

Enable multiplayer.debug logging and watch per-peer bandwidth. Before the fix, every client’s download matches every other client. After, bandwidth scales with nearby activity. Stealth-focused game? Test that invisible players don’t appear in a network packet sniffer.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

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

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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.

“MultiplayerSynchronizer defaults to the simplest behavior: send to everyone. For anything larger than a 4-player lobby, you need a visibility filter.”

Related Issues

For spawner replication, see Godot MultiplayerSpawner not syncing. For RPC routing, see Godot multiplayer RPC not reaching peers.

Never ship a multiplayer game without per-peer visibility on non-public data. Bandwidth and cheat risk both explode otherwise.