What it is
Define every action in your game (Jump / Attack / Inventory / …) and bind it per platform — keyboard key, gamepad button, touch gesture. Export a PDF cheat sheet for your manual or a contractor handing off input code.
When to use it
- Documenting the canonical input scheme before the engine team writes it.
- Producing a reference card for QA testers.
- Mapping abilities to buttons in a way that's actually printable.
- Switching layouts (e.g. left-handed mode) and seeing them side by side.
How to use it
- 1Click "+ Add Action" and pick a category.
- 2For each platform tab (Keyboard / Xbox / PlayStation / Touch), assign the binding.
- 3Click "Export PDF" to generate a printable cheat sheet.
- 4Switch the active layout dropdown to manage alternate schemes.
Tips you should know
- →Bindings are stored as opaque strings — match them to your engine's input map manually.
- →PDF export uses the active layout; switch first if you want a different one.
- →Use Categories to group bindings (Movement / Combat / UI) — the PDF respects those headers.
- →Touch bindings store as gestures (Tap / Hold / Swipe Left / etc.) — your engine's gesture recogniser does the heavy lifting.