Two build sites claim the same tiles, or a failed claim leaves ghost tiles behind

A builder game must decide who owns each tile the moment a site is placed. The classic bug is a rejected placement that still blocks half of its tiles forever, or a moved building that collides with itself. Here is the claim logic that avoids both.

Why this works

A claim on several tiles is either complete or not made at all. Checking everything first and only then writing keeps a failed attempt from leaving half-owned ground behind, and treating a building's own tiles as free lets it move.

When not to use it

Skip it when buildings are allowed to overlap or to share a tile, as with items lying on a floor, or when the map is so small that a simple list works. This all-or-nothing rule is meant for solid, exclusive ground.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 35 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Two build sites claim the same tiles, or a failed claim leaves ghost tiles behind" (read_entry building-footprint-claims-without-leaks) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP