How to Fix a Godot Control Not Receiving GUI Input

A Control that ignores input usually has the wrong mouse filter or is blocked by an overlay. Here is how to fix it.

How to fix it

1. Set the mouse filter

A Control with mouse filter Ignore receives no mouse input. Set it to Stop (consume) or Pass (handle and propagate) so it gets gui input events.

2. Check for blocking overlays

A Control above it in draw order with mouse filter Stop consumes the input first. Set overlapping decorative controls to Ignore so the input reaches the interactive one beneath.

3. Confirm it is within bounds

A Control outside its parent's rect, or with zero size, gets no input over its area. Make sure it has size and is positioned where the player clicks.

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.