What causes disconnected rooms in a Godot TileMap procedural dungeon?

Rooms placed independently with no connection step leave isolated rooms the player cannot walk between, because nothing carves corridors linking them.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Disconnected Rooms in a Godot TileMap Procedural Dungeon

Quick answer: Build a graph of room centers, compute a minimum spanning tree to choose which rooms to connect, and carve corridors along those edges into the TileMapLayer.

Isolated rooms in a Godot dungeon mean the connection pass is missing. An MST over room centers guarantees every room is reachable with minimal corridors.

How to fix it

1. Collect room center cells

After placing rooms, gather each room's center cell. These are the nodes of the connection graph you will build corridors over.

2. Connect with a minimum spanning tree

Build an MST over the room centers (Prim's or Kruskal's on Euclidean distances). Its edges connect every room with no cycles, so the whole dungeon is reachable using the fewest corridors.

3. Carve corridors with set_cell

For each MST edge, carve an L-shaped corridor between the two centers by writing floor tiles with set_cell on your TileMapLayer. Optionally add a few extra non-MST edges back for loops and replayability.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.