MM2 of The Locust is built for multiplayer rounds. Roblox lists a maximum server size of 30 and classifies the experience as Survival / 1 vs All. The useful team skill is not packing everyone into one corridor; it is sharing map information while keeping enough spacing that one Locust chase does not disable the whole survivor side.
Join the same server
Open the official Place ID 113385977463481 and use Roblox’s friend join flow when the friend’s privacy and server settings allow it. Confirm the experience title and creator before joining. If the target server is full, leave together and choose another public instance rather than repeatedly splitting the group across servers.
The official maximum is not a guaranteed player count, party size, or private-server feature. No current first-party source confirms a dedicated in-game party queue. Treat Roblox’s standard join tools as the reliable path and check the live experience page for any server options added later.
Agree on map language
Before the round, choose short names for visible anchors. Good calls combine a place and direction: “upper stairs,” “lower hall,” “room beside courtyard,” or “vent exit.” Avoid “over here” because the listener may face another direction. If the map resembles a familiar Murder Mystery 2 location, use the name only if everyone understands it and do not assume the original map’s doors or hiding rules remain identical.
Keep calls short while chased. Say where the Locust is heading, not only where it was. Add an objective status when it changes: “key found, leaving lower room.” That tells the team which area no longer needs searching and which route may need protection.
Divide survivor jobs
Route scout
Checks one branch, announces dead ends and open connections, then returns to a shared landmark.
Objective searcher
Searches interactable surfaces and reports the nearest landmark for keys or doors.
Threat caller
Tracks the Locust's direction from safe distance without following it into every room.
Support carrier
Holds a defensive item and uses it to open an escape route, not to start an unnecessary fight.
These are temporary jobs, not locked classes. Swap when a player is chased or finds an objective. The point is to prevent four people from checking the same table while another part of the map remains untouched.
Handle a chase without collapsing the team
The chased player should call the Locust’s route and move away from active objectives when possible. Other players should not form a train behind the monster. Use the chase window to search, open a route, or position near a junction that offers a safe assist. If you carry a taser-like item, wait until the intervention creates real distance for both players.
Do not body-block a doorway unless the current game explicitly supports a safe mechanic. Collision, hitboxes, and monster abilities can change in PRE-ALPHA. A crowded doorway can trap survivors and hide attack cues. Leave one lane open and plan the next corner before the threat arrives.
Share keys and escape progress
Current public coverage reports keys as part of progression, but the holder rules and spawn order are not officially documented. When a key is found, say its visible label or color, the pickup landmark, and whether the inventory or objective UI changed. If the key cannot be dropped or transferred, keep the carrier away from unnecessary searches and guide them toward the likely route.
When a door or objective reacts, announce the result. “Blue key did nothing at upper door” prevents repeated trips. “Door opened to lower route” gives the team a new loop. Avoid publishing the observation as a universal fixed route until it repeats in the same current build.
Decide on revive together
A community walkthrough shows a revive option after elimination. The current cost, limits, and return state are not first-party confirmed. Before spending, the eliminated player should ask whether the round is active, whether the team has meaningful progress, and whether the return position is survivable. Teammates can give a quick state call rather than pressuring every player to revive.
If revive is declined, the eliminated player can spectate and call safe information permitted by the game. Avoid revealing information that the current spectator system is designed to hide or using external tools. A clean group run should work with the experience’s normal interface.
Playing when a friend becomes the Locust
Role assignment can put friends on opposite sides. Treat the round competitively without using private voice information to reveal hidden survivors. The monster player should learn attacks from the current HUD, while survivors continue normal calls. Agree before the session whether you want serious rounds or experimentation so nobody mistakes testing for griefing.
After the round, compare observations: which route broke sight, which hiding place was checked, and what the monster UI showed. This is the fastest way for a group to learn both sides without turning unverified values into rules.
Recover from disconnects and bugs
The official page warns that the PRE-ALPHA build may contain bugs. If one player disconnects, finish the round unless the whole group intended a private test. Rejoin through a friend after the match. If a role action disappears, capture platform, role, round state, and HUD before rejoining; a screenshot can show whether the problem is layout, cooldown, or missing input.
Use Beginner Guide for the basic round loop, How to Escape for survivor progression, and Monster Controls for the opposing side. All team tactics here avoid fixed player counts and prices because those remain update-sensitive.
Sources and confidence
- Official: Roblox game identity, maximum server size, Survival / 1 vs All classification, and PRE-ALPHA warning.
- Community reported: keys, map voting, taser support, revive UI, and platform-specific monster-control differences in the August 27 build.