MM2 of The Locust does not currently publish a complete official control chart. Use Roblox’s normal movement and camera behavior as your starting point, then follow the action labels and touch buttons displayed by the current game build. Equipment and monster actions are the most likely to differ by role, platform, and update.
Safe control setup before a chase
Open the Roblox menu and confirm camera sensitivity, movement mode, graphics, volume, and any device-specific options. Return to the lobby and move through an open area. Test movement, camera, jump if available, and the interaction prompt without carrying an objective. A stable baseline helps you distinguish a missing game action from a general device problem.
For PC, standard Roblox movement commonly uses WASD and the mouse, while Space is normally jump. These are Roblox platform defaults, not a guarantee that every action is enabled or useful in this experience. A current game-specific walkthrough reports Left Control for sprint. Treat that sprint key as Community reported and check whether the current UI or settings panel shows the same binding.
Survivor actions to identify
Find the action used to interact with keys, doors, hiding places, and equipment. Roblox experiences often show a contextual prompt near the object rather than assigning every action permanently. Stand close enough for the label to appear, center the camera on the interactable area, and wait for the progress indicator or inventory change before moving away.
If you have a taser or another defensive item, identify four states: selected, aimed, activated, and unavailable. The public walkthrough confirms a taser-like tool but does not establish universal range, charges, stun time, or cooldown. Test the selection and aim controls in a safe space. Save the actual activation for a meaningful chase so you do not waste a limited use.
Monster controls
When the game assigns or grants a monster role, stop briefly and inspect the screen. Look for a regular attack, one or more ability slots, sprint, and any resource or cooldown indicator. A current walkthrough reports a normal attack and a special action and shows a PC special input associated with Q. This is a dated community report, not an official cross-platform binding.
Press an ability only where you can observe the result without losing the round immediately. Watch the button dim, fill, or change state. If it does nothing, confirm that you are in the active round, the ability is equipped, and the target condition is met. Do not repeatedly press every button; that can spend multiple abilities or hide which input worked.
Mobile and tablet controls
Touch players should expect movement and camera controls on opposite sides of the screen plus contextual action buttons supplied by the experience. Public gameplay reporting specifically notes confusion around monster attacks on mobile. Before chasing, rotate the device if needed, close overlays, and identify every visible action icon. Tap once in open space and observe which icon changes.
If a button is hidden behind chat, the player list, a display cutout, or another overlay, close the overlay and recheck. If the icon is present but unresponsive, move away from walls and try once more. Capture the screen orientation and role before rejoining; that evidence is more useful than simply reporting that “mobile is broken.”
Console controls
No target-game console binding chart was confirmed on August 27. Roblox maps ordinary movement and camera to controller sticks, but interaction, equipment, sprint, attacks, and abilities depend on the experience. Follow the button glyph shown by the game. Do not translate a PC letter directly to a controller face button.
If the interface shows keyboard prompts while using a controller, reconnect the device before launching, move only with the controller, and reopen the round UI. Avoid running multiple input devices during the test. If the prompt remains wrong, use the action location in the HUD as a clue and record the controller model for a bug report.
Troubleshoot a control that does not work
Build a useful control note
Record platform, device, role, map, action label, displayed binding, expected result, actual result, and check time. PRE-ALPHA bugs can make one server behave differently, so repeat the test once after a new round before declaring a permanent control. Never publish guessed keybinds for a platform you did not see.
Continue with the Monster Controls guide for chase-specific inputs or the Taser guide for equipment timing. Use Updates when an official description change mentions new equipment powers or game improvements.
Confidence note
Experience identity and PRE-ALPHA status are Official. The reported sprint and special-action keys are Community reported from the August 27 build and need a current in-game check on each platform.