SpeedRunners 2 Controls: Keyboard, Controller and Remapping

Controls are the quiet make-or-break of a competitive platformer — and SpeedRunners 2’s launch week came with one genuinely important remapping caveat that every player should know before touching the settings screen. This page covers what is verified about keyboards, controllers and rebinding, and links the practice routines that make the inputs automatic.

The One Fact That Matters: Gameplay Remaps, Menus Don’t

The developer confirmed on September 4 (Steam community discussion):

• Gameplay actions are remappable — jump, grapple, slide, items and friends can all move to your preferred keys.
• Menu controls currently are not remappable — a limitation, with a future change “being discussed, not promised.”

Practical consequence: plan your layout assuming menu bindings stay exactly where they are.

The Numpad Trap

The most-reported binding issue of launch week: gameplay actions bound to the numpad can also fire training-menu shortcuts — so your carefully-bound grapple opens a menu mid-race. This is the collision of the two facts above: your gameplay bind moved to the numpad; the menu shortcut sitting on that key didn’t move and can’t be moved.

The fix pattern:

1. Screenshot your current bindings before changing anything — with menus unremappable, you want a record of what you moved.
2. Keep gameplay actions on letter keys near your movement hand.
3. Change one bind at a time and test in training or a bot race — an action should move your runner and only move your runner.

The Confirmed Action Set

What the game asks your hands to do, per official sources:

Controller Notes

On console, controllers are the native input, period. On PC, the store listing carries no explicit controller tag in what we have verified, so test before a party. Two launch-window notes worth knowing: some players report missing button prompts in places (a polish item, patch-likely), and mixed keyboard/controller households should test everyone’s setup in a bot race before the party starts. The friends guide has the full session-checklist.

When Controls Feel Wrong: The Debug Order

1. Test inputs in free play or a bot race — if jump and grapple are reliable outside the lesson, your bindings are fine (this is step one of the tutorials guide’s stuck-on-Reverse-Grapple checklist too).
2. Check for the numpad conflict above.
3. Rule out hardware — a flaky key or a controller with drift imitates a game bug perfectly.
4. Only then suspect the game — and if it reproduces, report it through the official channels in the troubleshooting guide.

Related Pages

• Tutorials guide — the input checks before lesson retries
• Movement techniques — what good inputs become
• Troubleshooting — when the problem isn’t the bindings