Monster controls in MM2 of The Locust depend on the current role and platform UI. Public gameplay reporting shows a regular attack and a special action and associates the special with Q on PC, but there is no complete official binding chart. Follow the live labels instead of treating one recorded key as permanent.
Confirm that the role is active
Wait for the role message and round transition. Look for a monster HUD, attack icon, ability slot, or changed objective. A missing button in the lobby does not prove the control is broken; the actions may appear only after the monster round begins or after the role is equipped.
Move in open space and check the camera. If ordinary Roblox movement fails, fix device focus or connection before diagnosing the monster action. Close chat and menus so keyboard input returns to the game.
PC setup
Use normal Roblox movement and camera as the baseline. Find the regular attack through the visible HUD or control hint. A current game-specific walkthrough reports Q for a special action and Left Control for sprint-like movement, but both are Community reported and may change.
Test the regular attack once while facing open space. Then test the special with its icon ready. Watch which button changes. If both activate together, check whether the chosen input is overlapping a Roblox or device setting. Do not remap external software until you establish the default behavior.
Mobile and tablet setup
Touch players should inspect the entire action side of the screen before moving into a chase. Rotate the device to the supported orientation, close chat and the player list, and identify the largest attack or ability icons. Public coverage notes that mobile players may have difficulty finding monster attacks, so this setup step is essential.
Tap one action in open space and watch its icon. If the button is near a display cutout or system gesture area, avoid swiping from the edge. If it never appears, capture the role message and HUD; the issue may be a missing layout rather than an unknown gesture.
Console setup
No official controller map was confirmed for this target experience. Follow the glyph beside the attack or ability icon. Standard Roblox stick movement does not establish the monster’s face-button, trigger, bumper, or stick-click assignment.
If keyboard prompts appear, reconnect the controller before launch and navigate the lobby without touching another input device. Reopen the round UI. Record the controller type and platform if the wrong prompts remain.
Camera and chase control
Keep the camera pointed through the next doorway rather than centered only on the nearest survivor. In an uneven chase, route prediction matters more than constant turning. Use wider camera movement in open areas and smaller corrections in narrow rooms so you do not lose the target at a corner.
Do not attack while the camera is still catching up unless the hit area is clear. A missed action can create recovery time and let the survivor reach a second sight break. Learn the attack cue and the movement that remains available during recovery.
Troubleshooting sequence
Avoid accidental input problems
Do not use macros, exploit scripts, hitbox extensions, or automated attacks. Apart from violating fair play, they create behavior that normal players cannot reproduce and make control advice useless. Test with the standard Roblox client and one input device at a time.
If the game appears stuck, retry the action once after moving away from geometry. Rejoin only when the normal UI stays broken. The official page warns about PRE-ALPHA bugs, so include the update time and platform in any report.
Practice order
- Confirm role and HUD.
- Move and turn through an open loop.
- Test one regular attack and observe recovery.
- Test one special action and observe the icon state.
- Start a short chase while preserving camera control.
- Review which input or route caused the miss.
Continue with Locust Abilities for action cues and Maps for efficient search routes. Use the broader Controls guide for device problems affecting both roles.
Confidence
Player-controlled monster actions are Community reported. Specific PC keys are dated community observations. Mobile, console, cooldown, and action-slot details remain Needs in-game testing.