godot-input-handling

Input buffering stores a jump press in a timed window (typically 100-150ms) and consumes it when the character lands. Use a buffer that decays in _physics_process so the window matches CharacterBody consumption rather than render frame rate.

Runtime rebinding uses InputMap.action_add_event and action_erase_events with conflict detection, then persists mappings via ConfigFile to user://. This lets players remap controls in a settings menu without hardcoded keys.

Gameplay actions belong in _unhandled_input, which only fires after UI controls have consumed events. Using _input causes gameplay logic like shooting to trigger while the player clicks menus.

Stick drift is fixed with a radial deadzone, preferably via Input.get_vector which applies a circular deadzone and clamps magnitude to 1.0. Manually subtracting axes creates square deadzones with uneven diagonal behavior.

Detect the last active device by checking for InputEventJoypadButton or InputEventJoypadMotion in a singleton, then broadcast a device_changed signal. All UI prompt elements listen to that signal and swap their glyph textures.

Polling gameplay input in _process is frame-rate dependent, so presses can be missed at low FPS. Poll actions in _physics_process or handle them in _unhandled_input, and add a timed input buffer for fast-paced actions.