What are the TTK Testing controls?
Use M1 to fire, M2 to aim, C to crouch, Q and E to lean left and right, number keys to swap weapons, and P to activate helmetcam. These are the controls listed by the official game description.
Confirmed control list
The table below sticks to actions documented on the official Roblox listing. It does not assign undocumented controller buttons or mobile screen positions. TTK Testing has a compatibility focus that includes PC, mobile, Xbox, and PS5, but the public description gives the clearest named inputs for keyboard and mouse.
| Action | Input | How to check it |
|---|---|---|
| Fire | M1 | Press once while your weapon is ready |
| Aim | M2 | Check that the sight view appears |
| Crouch | C | Watch for the camera and stance change |
| Lean left | Q | Test beside the left edge of cover |
| Lean right | E | Test beside the right edge of cover |
| Swap weapon | Number keys | Select a different available slot |
| Helmetcam | P | Press separately from the aim input |
PC, mobile and console controls
Sable Digital lists PC, mobile, Xbox, and PS5 as compatibility targets. The public description only spells out keyboard and mouse inputs, so the safest answer for touch and controller players is to follow the labels shown by the current client instead of copying an invented button map.
PC
Use the confirmed M1, M2, C, Q/E, number-key, and P inputs listed above.
Mobile
Check the live touch controls and test aim, crouch, lean, swap, and camera actions before entering a busy angle.
Xbox / PS5
Use the current on-screen prompts. The official page confirms compatibility focus, not a permanent controller layout.
Build a usable control rhythm
Knowing a key is different from reaching it during a fight. Practice short combinations that match real decisions: aim and fire, crouch behind cover, lean to check an angle, then move away. Keep the sequence slow until you stop searching for each key.
This is editorial practice advice rather than an official tutorial. It avoids assumptions about recoil, movement speed, or weapon statistics. The goal is simply to make the confirmed actions available when you need them.
- Place your hand naturally, then press C, Q, and E without looking down.
- Aim with M2 before firing with M1 so each input has a clear purpose.
- Practice one left-side lean and one right-side lean from solid cover.
- Swap to another available slot with a number key and return to the first slot.
- Use P outside an active fight until helmetcam no longer surprises you.
If a control does not respond
First check the simple causes. The game window may not have focus, a menu may be open, or the action may not make sense in your current state. Repeat the input once in a quiet part of the match rather than rapidly pressing several keys.
If you are playing on mobile or console, use the controls shown by the live client. Do not assume the keyboard letters translate to a particular button. Platform support is an official focus, but this page will not invent layouts that the developer has not documented publicly.
- Click or select the game window so it receives input.
- Close any open menu before testing an action.
- Check that an available weapon slot is selected before testing fire or swap.
- Rejoin once if several unrelated inputs stop responding.
- Check the official listing or update notes if the live interface has changed.
What the official control list does not confirm
The official description confirms the action names and PC inputs above. It does not publish a complete sensitivity recommendation, a best keybind layout, or a fixed controller map. Treat any such recommendation as a player's preference unless Sable Digital documents it.
The current format is a public FFA test with up to eight players. Planned co-op PVE, story missions, team PVP, Survival, Missions, Quick Play, and Ground War may create different control needs later, but planned modes should not be used as proof of current bindings.