Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Add remappable [keyboard, mouse, and gamepad] controls to [PC game]. Inspect the current input system and define named actions for [essential actions]. Keep gameplay rules connected to actions rather than hard-coded physical keys.
Update the settings interface and on-screen prompts to reflect current mappings. Define conflict handling, reset-to-default behavior, and persistence. Handle focus loss, mouse capture when relevant, and controller disconnection without leaving stale actions active.
Verify the main journey using each supported input method, then change a binding and restart the game. Check menu navigation and a safe recovery from invalid configuration. Report supported devices, checks performed, and remaining gaps.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Godot — creating and changing input action mappings
- Godot — controllers, dead zones, and input differences
- Godot — storing and loading local configuration
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original remapping template. Input-map and configuration APIs support its premises; labels, conflicts, recovery, and persistence require implementation and checks.