How to Fix a Stale Shared Blackboard Value Across AI Agents in Godot

Two guards both chase the same player even though only one saw you, or a value set by one NPC mysteriously appears on another. They are reading and writing the same blackboard object. Scoping it per-agent fixes the cross-talk. Here is how.

How to fix it

1. Make the blackboard local to scene

If the blackboard is a Resource, enable Local To Scene (or call duplicate() on ready) so each instanced agent gets its own copy instead of sharing the cached resource.

2. Separate per-agent from global data

Keep target, last-known-position, and state on the agent's own blackboard. Put squad-wide facts (alarm raised, shared objective) on a distinct global blackboard that is intentionally shared.

3. Initialize on _ready

Populate per-agent keys in _ready() rather than as exported defaults, so the values cannot leak from an editor-shared resource into runtime instances.

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.