MM2 of The Locust Beginner Guide

Before you join: know the reliable starting point

MM2 of The Locust is listed on Roblox as a Survival / 1 vs All experience by THE STALKERS OG. The official description places you in the Locust’s nest and asks whether you can escape. That is the useful, confirmed brief for a first session. It also carries a Pre-Alpha notice and tells players to expect bugs, which changes how you should interpret early gameplay.

Do not begin by looking for an “optimal” loadout, a map route, or a code video. None of those are documented by an official source in the material currently available. Start with the official Roblox page, check that the game is available, and open this site’s status page if you want to see the latest verified listing signal. This keeps the first decision simple: you are joining to observe and learn, not to follow an unverified script.

If you are playing with friends, agree on one practical rule before joining: separate what you directly saw from what you heard. A player can report that something happened in their session; that does not automatically make it a universal mechanic. This distinction is especially useful while maps, equipment, and powers are still described as upcoming.

Your first session: prioritize orientation over speed

When the session starts, give yourself time to understand the visible interface, any objective text, and the immediate environment. The official page confirms survival and escape themes, but it does not publish a step-by-step escape condition. Treat the game’s in-session instructions as the authority for that current build. Read them before committing to a route or a role.

For the first few attempts, your target should be a clean baseline rather than a successful escape at any cost. Note roughly how long you were active, what ended the attempt, whether other players changed the situation, and which instructions were visible. You do not need a complicated spreadsheet: a few honest observations are more useful than a copied guide with no source. The Escape Planner is designed around this principle. You supply your own observed attempt time and reset time; it never pretends to know a hidden in-game timer.

In a server that supports up to 30 players, the number of people around you can affect how easy it is to read the scene and repeat an observation. If a test is unclear, repeat it in another session rather than declaring a conclusion from one crowded round. This is not a claim about a specific game mechanic; it is a practical way to reduce noise when learning any multiplayer survival game.

What to observe without inventing a mechanic

Focus on information you can check directly. Record the date, the game version or visible update note if one is shown, the server context, the instruction you followed, and the result. If there is an item, map, or power, use the exact name shown by the game. Do not rename it from a video title or assume two similarly named things work the same way.

Use three labels for your notes. Confirmed means it appears in an official source or in a repeatable in-game instruction. Observed means you saw it in one or more sessions but have not confirmed its general rule. Unknown means you have a question but no evidence yet. This small system protects you from a common Pre-Alpha problem: a temporary bug or unfinished feature looks consistent enough to become a rumor.

When you encounter a claim about equipment powers, rankings, rewards, codes, or secret maps, first check the matching page on this wiki. The tier-list status explains why rankings are currently withheld; the codes page does the same for redemption claims. A page that says “not verified” can save you more time than a confident but invented answer.

Playing a Pre-Alpha safely and usefully

Pre-Alpha does not mean every session will fail, but it does mean that bugs, balance changes, and incomplete features are part of the expected experience. Keep expectations flexible. If an on-screen instruction conflicts with an older community tip, follow the current in-game instruction and record the difference. If a menu or feature disappears, avoid treating it as a permanent removal until an official update says so.

Use only the normal Roblox game link to enter the experience. A “code generator,” free Robux offer, or external account-verification page is not part of an ordinary game guide. Never give a password, browser cookie, or recovery code to a fan site. Official links collected by this wiki are listed on the Trello & Wiki page; no unverified Discord, Trello, or wiki link is promoted as official.

Finally, keep the game’s content label in mind. The listing carries a Mild maturity label and mentions repeated mild horror and violence along with non-realistic heavy blood. If you are coordinating a group, make sure everyone is comfortable with that tone before the session starts.

After the session: turn one attempt into better next steps

End each session with one useful question: what would make the next attempt more informative? Maybe you need to read the objective text earlier, try a less crowded server, compare a different visible route, or confirm whether a change persists after rejoining. Pick one change, then use the next attempt to test it. This creates a repeatable learning loop without claiming knowledge the game has not published.

For scheduling, add your observed attempt length and reset time to the Escape Planner. It will show how many attempts fit into your available time and where the waiting overhead goes. That result is about your personal session, not a prediction of the game. When the developers publish systems, item details, maps, or power rules, those pages can evolve from status references into more tactical guides with sourced steps.

Beginner questions