Quick answer: Set the layer and mask so the detector's mask includes the other object's layer, enable monitoring on Areas, and confirm both objects have a non-empty CollisionShape.

Collision detection in Godot is gated by layers and masks, and it is easy to set them so two objects never test against each other. Add a missing shape and the problem is usually one of three things. Here they are.

How to fix it

1. Make layers and masks overlap

An object detects another only if its mask includes the other's layer. For an Area2D to sense the player, the Area's mask must include the player's layer. Mismatched bits mean silence.

2. Enable monitoring on Areas

An Area only reports body_entered and area_entered when Monitoring is on. If it was disabled (or monitorable is off on the target), the signals never fire.

3. Give both objects a real collision shape

A CollisionShape with no shape resource, or a zero-size shape, collides with nothing. Confirm each object has a shape assigned and sized to the sprite.

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.