MM2 of The Locust remains labeled PRE-ALPHA on its official Roblox page as of August 27, 2026. The creator warns players to expect bugs and says the next update is intended to bring game improvements, upcoming maps, and new equipment powers. No numbered version, release time, item list, map names, or detailed patch notes are stated there, so this tracker separates the official promise from changes that still need a live in-game check.
Latest verified status
2026-08-27 - Official description and PRE-ALPHA status checked
Type: Official status
The official experience listing identifies MM2 of The Locust as PRE-ALPHA, warns that bugs are expected, and previews game improvements, upcoming maps, and new equipment powers for the next update. The listing does not provide a release date or complete patch list.
- Status remains PRE-ALPHA on the checked date.
- Future map additions are promised without public names or a final count.
- New equipment powers are promised without confirmed item names, values, or controls.
- General game improvements are promised without a version number or detailed change log.
Source: Official MM2 of The Locust Roblox experience
What the official promise means
“Game improvements” is broad language. It may cover stability, interface behavior, matchmaking, round flow, map geometry, controls, or balance, but none of those individual areas should be marked changed until the live client or a creator note confirms it. If a bug disappears in one server, repeat the same action in another current server before calling it fixed.
“Upcoming maps” confirms that the current environment selection is not final. It does not establish how many maps will arrive, whether an existing map will be replaced, or whether map voting will change with them. A newly visible vote panel can be a useful clue, but the round must load the candidate before it becomes a confirmed playable map.
“New equipment powers” confirms planned equipment-related change while leaving the implementation open. It may refer to a new item, a new action on an existing item, a role-specific power, or a revised interface. Check the live label, item card, cooldown feedback, effect, and who can use it. Do not transfer taser values or monster abilities from a community video into a future build without testing.
What to inspect when a server changes
Begin in the lobby. Note the official page’s updated time, then join a fresh public server and wait for the whole interface to load. Check the map-vote area, role selection or assignment message, equipment panels, settings, and any new announcement banner. If a button appears, read its label before pressing it and capture the result rather than relying on its icon alone.
During a survivor round, compare objective prompts, key labels, item locations, interaction range, downed-state options, and the escape trigger. Use stable landmarks when checking a route. If a key moved, the map may have changed even when the room looks familiar. If an exit fails, verify that the correct objective was completed before calling it a bug.
During a Locust round, compare the normal attack, special action, button labels, input response, target feedback, and recovery between actions. Current public reporting suggests a player-controlled threat with regular and special actions, but the official page does not publish a complete ability sheet. A changed animation does not always mean a changed effect, and a changed keybind does not always mean the ability itself is new.
A clean before-and-after record
Keep the record ordinary and reproducible. Do not use exploit executors, ESP, altered movement, teleports, or hidden-property tools to “prove” an update. Those methods change what can be seen or reached and do not describe the experience available to normal players.
PRE-ALPHA bug or intentional change?
An intentional change should repeat in fresh servers, affect players using normal controls, and fit either a creator statement or consistent new interface. A bug is more likely when only one player sees it, the interface is partly missing, an interaction stops after lag, or the result disappears after rejoining. PRE-ALPHA can contain both at the same time.
When a control fails, first check whether chat, a text field, a Roblox system menu, or a role transition owns the input. When an item fails, check whether it is equipped, available for the current role, waiting on feedback, or already spent. When a door fails, check the prompt and objective state. These checks avoid turning an ordinary condition into false patch notes.
If the behavior repeats, record it as Community observed until a creator message confirms intent. The distinction matters: players can still use a reliable observation while understanding that it may be repaired or reversed without notice.
Map changes to recheck
Future maps are the clearest announced content area. On a changed build, compare the lobby candidates and the environment that actually loads. Give a map a neutral working identity based on distinctive landmarks until the live UI displays its official name. Record its central anchor, vertical layers, main loops, dead ends, hiding interactions, objective surfaces, and escape route.
Recheck the Key Locations guide before treating old spawn notes as permanent. Search order remains useful even when the pickup moves. Recheck Hiding Spots when a locker, vent, window, or lower route changes access. Recheck Secret Rooms when geometry moves, and distinguish a new intended route from a collision gap.
Map voting also needs a separate check. Candidate panels, vote confirmation, ties, late joins, and the final loaded result can change independently. The Map Voting guide uses visible confirmation instead of assuming a fixed rule.
Equipment and power changes to recheck
For survivor equipment, record who can obtain it, where the prompt appears, how it is equipped, what the normal action does, what feedback confirms a hit or use, and what happens afterward. Avoid publishing exact range, duration, charges, cost, or cooldown from a single server. Repeat at least the visible effect under normal play.
For Locust powers, read the role-specific control shown in the live client. Test the regular action and special action separately in open space before a chase. Mobile, controller, and keyboard layouts may expose different labels or focus behavior, so a working PC input is not a complete control update. The Monster Controls guide keeps the platform verification separate from the ability description.
For revive behavior, record the state shown after elimination, the visible button or prompt, any clearly disclosed cost, the return location, and whether the same round continues. Never infer a permanent price from a dated recording. The Revive guide explains how to decide using the current prompt.
Codes and rewards after an update
The checked official listing does not announce a working reward code or a redemption menu. An update could add one, but the new button, exact string, result, and reward must all be verified for this Place before it is called active. Strings copied from normal Murder Mystery 2 or another Locust experience do not become valid because the names resemble each other.
Use the Codes page for the dated redemption status and safe verification routine. A real code should work through the normal game interface or another method the creator clearly documents. It should never require a password, account cookie, recovery code, downloaded executor, or external “generator.”
How this tracker labels evidence
Official means the fact appears on the target Roblox experience page or in a creator channel clearly attached to it. Community observed means current players or gameplay show a repeatable action that first-party text does not document. Needs in-game testing means evidence is missing, version-sensitive, platform-specific, or too narrow to state as a stable rule.
The labels are intentionally conservative. An official promise can still lack implementation details. A strong community observation can still change in PRE-ALPHA. A question needing a live test is not an invitation to fill the gap with a guide from another game.
Before trusting new patch notes
Confirm the exact Place ID, follow the source link, compare the publication time with the Roblox update activity, and look for a reproducible in-game result. Reject lists that merge multiple games, supply detailed numbers without a visible test, or convert a creator’s broad promise into named content that was never announced.
For a normal play plan that survives small changes, start at Guides, use Survival for role decisions, and rebuild your route from Maps after any environment change. This tracker will stay focused on dated, attributable changes rather than guesses about the next build.