Nobody loses a build fight because they are slow at thinking. They lose because the wall is on a key their hand has to leave the mouse to reach, or because the ramp goes down half a beat after the wall instead of with it. Keybinds are not a preference — they are the ceiling on how fast you can physically play.
Here is what this build actually ships with, read off the game's own Settings → Keyboard screen, and what to change it to.
The defaults
| Action | Default | Change it to |
|---|---|---|
| Move | W A S D | Leave it |
| Jump | Space | Space |
| Crouch / slide | Left Shift | Left Ctrl if Shift is your sprint muscle memory |
| Fire / aim | Left Click / Right Click | Mouse |
| Wall | Z | Mouse Button 4 |
| Floor | X | Mouse Button 5 |
| Ramp / stairs | C | C, or Q if you came from the old layout |
| Roof / cone | V | V |
| Edit | E | E, with Edit on release left ON |
| Reset / rotate edit | R | R |
| Pickaxe | F | F or Middle Click |
| Weapons | 1 – 5 | 1–5 or the scroll wheel |
| Emote | B | B |
| Free the cursor | Left Alt | Left Alt |
Rule one: the wall never lives on the keyboard
The wall is the panic button. It is the piece you place when someone is already shooting at you, and it has to happen without your left hand travelling anywhere. If your mouse has side buttons, the wall goes on the one your thumb rests against — that is the single largest speed gain available to a mid-level player, and it costs nothing to try.
No side buttons? Then the wall belongs on a key your ring or little finger already covers while WASD is held: Q or Shift-adjacent, never Z or C, which both require the whole hand to shift down a row.
Rule two: wall and ramp should be neighbours
Ramp-then-wall is the most-repeated two-piece combination in the game. If those two inputs live on opposite sides of your hand, every ramp rush costs you a hand movement. Put them adjacent — thumb and index, or two side buttons — and the combination becomes one motion instead of two decisions.
Rule three: edit on release, always
With Edit on release enabled, you hold the edit key, drag the selection, and let go to confirm. Without it you press to open, click to select and press again to confirm — three inputs where one will do, and the extra press is exactly where fights get lost. It is on by default; the only reason to turn it off is if you have never played with it and mistake the confirm-on-release for a misfire.
Sensitivity: lower than you think, then leave it alone
There is no correct DPI, but there is a correct test. Set a sensitivity where a comfortable single sweep of the mouse — no re-gripping, no wrist strain — turns you exactly 180 degrees. If a full turn needs two sweeps you are too low; if a flick overshoots the target every time you are too high.
Then stop changing it. Aim is a motor pattern that takes days to settle, and a player who adjusts sensitivity every session is permanently re-learning the same skill. Build sensitivity can sit higher than combat sensitivity if the game exposes it separately — the pieces are large targets and speed matters more than precision.
Three settings worth changing before the keys
- Fullscreen, not a tab. A browser tab shares the compositor with the rest of the page; fullscreen hands the GPU to the game. This is worth more frames than any graphics slider.
- Turn off anything you do not look at. Shadows and effects cost frames and hide nothing useful in a 1v1 box.
- Hardware acceleration on, in the browser itself. Without it the whole WebGL client renders on the CPU, and no keybind saves you from that.
Practising a new layout without losing rank
Changing keybinds makes you worse for about a day. Do it in Free Build, not in a match: empty map, unlimited materials, nobody shooting. Drill the two combinations that matter — wall to ramp, ramp to 90 — until your hand stops looking for the old key. Then take it into a real game.
Most players change binds mid-session, lose three fights, and change them back. The layout was not the problem; a day of muscle memory was.