JUST ONE MORE ASYM controls should be learned from the prompts in your current client. Community guides commonly document familiar Roblox movement such as WASD, Space, and Shift on PC, plus mouse buttons and lettered ability slots, but the audit found no first-party public control sheet. Treat every exact binding as community reported until you see it in the live tutorial or settings.
Verify controls before a real fight
Complete the tutorial rather than testing every button while a round is active. The official “ready for JOMA” badge confirms the tutorial exists. In a safe space, identify movement, jump, sprint, camera lock or shift lock, basic attack, defensive action, interaction, and each visible ability slot. Say the action name while pressing it so you remember function before key.
On PC, community documentation currently reports WASD movement, Space to jump, Shift to sprint, mouse buttons for core combat, and Q/E/R-style ability slots. Do not assume every character uses every input, and do not assume a community “parry” label matches the exact live action name.
Build a device-specific control card
PC keyboard and mouse
Record movement, sprint, jump, camera behavior, attack, defense, interaction, and each ability exactly as shown. Test whether shift lock changes aim or turn behavior.
Mobile
Check which buttons appear only after spawning, whether ability buttons can overlap Roblox UI, and how camera drag affects aim. Increase UI scale only if the game or Roblox client exposes it.
Controller
Confirm prompts after the controller is connected. Test trigger, bumper, face-button, stick-click, and camera sensitivity behavior; never copy a console diagram from another asym game.
Write unknown bindings as unknown rather than filling them from habit. A clean card for one current device is more useful than a “complete” table with guessed mobile and controller inputs.
Movement inputs are resource decisions
The important control is not merely how to sprint; it is when to stop. Walk while unspotted. Use sprint to cross an exposed lane, reach a teammate, clear an ability, or break line of sight. Release it after reaching the destination so stamina can recover before the next threat.
Practice camera and movement together. Look toward the threat without drifting into a wall or ledge. On Cloud Nine, uncontrolled camera turns near bridges can be as dangerous as the hunter. On District, camera awareness helps you cross a road without losing the building entrance you intend to reach.
Ability inputs need an order
Before the round, read each selected character’s visible ability text. Decide which button is for setup, which is for the main action, and which must be saved for escape or recovery. Pressing every slot at first contact leaves no answer for the second threat.
For a Survivor, a sensible sequence may be: reposition, interrupt or protect, then use recovery after line of sight breaks. For an Adversary, it may be: reveal or control the target, let the Aberrant force movement, then spend the chase tool on the exit. The exact skills differ, but the input discipline transfers.
A ten-minute practice routine
- Move around a safe area without sprinting and keep the camera on one landmark.
- Sprint between two named landmarks, releasing the input as soon as cover is reached.
- Trigger one ability at a time and watch its startup, active effect, and recovery.
- Test whether attacks or abilities change your facing.
- Reconnect your device and confirm prompts do not switch or disappear.
- Play one round where you say each ability name before pressing its button.
This routine separates “wrong input” from “right input at the wrong time.” If the action fired but failed, the problem may be range, line of sight, timing, or role rather than the binding.
Troubleshoot missing or wrong prompts
If controller icons do not appear, disconnect duplicate input devices, reconnect before joining, and verify Roblox recognizes the controller. If prompts flicker between keyboard and controller, check for stick drift or a pressed key. Avoid third-party remappers until the normal client behavior is clear.
On mobile, close overlays that cover ability buttons and rotate the device only if the experience supports that orientation. If touch targets are too close to the screen edge, check Roblox and in-game settings before installing anything. Never use an executor or script to change input behavior; the official game rules prohibit exploiting and intentional bug abuse.
If an ability appears unavailable, inspect its cooldown, resource, target, and state. A grayed button is not automatically a broken key. Some actions may require a valid target, sufficient stamina, or a particular round state.
Controls by role
Survivors should prioritize movement accuracy, camera awareness, a defensive or peel input, and the ability they need after breaking line of sight. Backliners need a quick route to teammates more than a perfect attack combo.
Adversaries should learn target selection and camera control around the AI Aberrant. A fast ability that sends you past the target is a positioning error even if the button worked. Control-focused characters should confirm aim and placement without spending all stamina during setup.
Keep the current build authoritative
Exact controls remain a live-test item because the public Roblox APIs do not expose keybinds. Record the date and device whenever you share a binding. If a patch changes an action, update the device card instead of arguing from an old screenshot.
The stamina guide turns movement inputs into a repeatable resource plan, while the beginner guide places controls in the first-match flow.
Frequently asked questions
What are the PC controls?
Community guides report standard Roblox movement with WASD, Space, and Shift, plus mouse and lettered ability inputs. Verify every action in the live tutorial because a current first-party control sheet is not public.
Can I change keybinds?
Full rebinding has not been verified. Check the current in-game and Roblox settings. Do not download a remapper from a guide comment.
Why does sprint stop working?
Check stamina and character state before assuming the key failed. Release sprint during safe movement so the bar can recover.
Are mobile and controller fully supported?
Roblox clients may expose those inputs, but exact JOMA prompts and usability require current device testing. Use live prompts, not PC labels copied onto a mobile diagram.