What causes Godot UI not navigable by controller or keyboard?

The Control nodes have no focus configuration, so the engine cannot move focus with the D-pad or arrow keys and players without a mouse cannot use the menus.

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 Godot UI Not Navigable by Controller or Keyboard

Quick answer: Set focus modes and focus neighbors on Controls, grab focus on the first item when a screen opens, and ensure the UI theme shows a visible focus highlight.

A mouse-only menu locks out controller and keyboard players, including many with disabilities. Focus navigation fixes it. Here is how.

How to fix it

1. Enable focus and neighbors

Set each Control's focus mode to All and configure focus_neighbor_* links (or use the automatic neighbor setup) so D-pad and arrows move predictably.

2. Grab focus on open

Call grab_focus() on the first logical control when a menu becomes visible so there is always a starting point for non-mouse input.

3. Show a visible highlight

Give focused controls a clear focus style in the theme so players can always see where they are, which also helps low-vision players.

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.