run.inputMap — the madcap's controls. The five controls the loop slice drives, each carrying keyboard, gamepad and touch (the `.inputBinding` folders beside this file). The on-screen touch layout IS these bindings: the overlay draws a stick for `move` and a button for every `touchButton` declared here, so nothing else has to author a phone UI. move axis2 WASD / left stick / left thumb stick jump button Space / south / a large button, priority 10 dash button Shift / west or right trigger / a large button, priority 20 shove button E or left mouse / east / a button, priority 30 sprint button the control `CharacterController` reads for its speed multiplier. `dash` carries the capability a player reaches for, so this one is left inert (sprintMultiplier = 1) and declares `touch = false` rather than putting a second, silent button on a phone. `group = "run"` is what the pause and menu schemes stand down: while a card is up, `uimenu` / `uipause` suppress this group and no press reaches the runner. `suppresses = { "player" }` is the other direction — the engine's default scheme carries look, zoom, crouch, interact and pointer lock, none of which this game has; standing it down keeps the touch overlay to the four controls above and leaves the browser cursor free.