godot-input-handling

Godot 4.3 input handling routes hardware events through InputEvents to game logic. You define actions in the Input Map and process keyboard, mouse, gamepad, or touch inputs using either event-driven callbacks like _unhandled_input() or polling methods.

Event-driven input in Godot processes discrete hardware actions through callback functions like _unhandled_input(), while polling checks the current input state continuously via Input. Your game logic requirements determine whether you need immediate event responses or ongoing state checks.

Dynamic input action rebinding in Godot modifies the InputMap at runtime, allowing players to customize controls. You update action mappings by clearing existing assigned events and adding new InputEvent resources to the target action.

Godot supports gamepad detection and input handling alongside dedicated touch event processing. For mobile testing on desktop, Godot provides an option to emulate touch input from mouse events to streamline multi-platform input architecture development.

Input handling stops during pause because Godot restricts input event propagation to paused nodes. You must explicitly configure your input architecture to process paused input, ensuring specific UI or menu nodes receive events while the game tree is paused.

You can stop input event propagation in Godot by consuming the InputEvent within a node's handler. Calling event methods or setting specific properties prevents the event from continuing down the scene tree to other nodes.