What causes Godot TileMap collision not working?

The tiles have no physics collision shape assigned in the TileSet, the TileMap's physics layer does not match the body's mask, or you painted tiles on a layer without collision.

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 TileMap Collision Not Working in Godot

Quick answer: Add a physics layer to the TileSet and draw collision shapes on the tiles, make sure the TileMap's collision layer is in the body's mask, and confirm you painted the collidable tiles.

A TileMap the player walks straight through is missing collision data on the tiles themselves, or has a layer mismatch. Collision is authored per-tile in the TileSet. Here is how to set it up.

How to fix it

1. Add collision shapes to the TileSet

In the TileSet editor, add a Physics Layer, then paint a collision polygon on each solid tile. Tiles without a shape have no collision no matter what the TileMap settings say.

2. Match layers and masks

The TileMap's physics collision_layer must be included in the moving body's collision_mask. If they do not overlap, the body ignores the tiles.

3. Confirm the right tiles are painted

Collision belongs to specific tiles; if you painted decorative variants without shapes, they will not block. Re-paint with the collidable tiles, or add shapes to the ones you used.

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.