Quick answer: Set up input handling in the new scene, ensure the handling node is in the tree and processing, and give UI controls focus.

Input not working after a scene change is input handling tied to the old scene. Here is how to fix it.

How to fix it

1. Set up input in the new scene

Input handling tied to the old scene's nodes is gone after the change. Ensure the new scene sets up its own input handling, since connections and handlers from the previous scene do not carry over.

2. Ensure the node is processing

The node handling input must be in the tree and have input processing enabled (not paused by its process mode). A handler whose node is not processing receives no input after the scene change.

3. Give UI controls focus

For UI input after a scene change, set focus to a control in the new scene, since focus does not transfer. Without a focused control, keyboard and gamepad UI input has nowhere to go.

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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.