Quick answer: Re-enable the relevant processing flag, or read input from the global Input singleton in _process, which does not depend on the per-node input callbacks.

If your node's _input stopped running while the rest of the game still responds, input processing was switched off on that node. Turning it back on fixes it. Here is how.

How to fix it

1. Re-enable the callback

Call set_process_input(true) (or set_process_unhandled_input(true)) in _ready. These flags are sometimes flipped off when a node is pooled or pausing logic ran.

2. Check pause mode

If the tree is paused, only nodes with process_mode set to Always or When Paused receive input. A node in Inherit under a paused parent goes silent.

3. Fall back to the Input singleton

For polling-style reads use Input.is_action_pressed inside _process; the singleton works regardless of the node's input callback flags.

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 bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.