The Locust of MM2 Sources — the Full Register

The Roblox game page and its linked creator community are the only official surfaces, and they carry the premise, credits, dates, and snapshot stats this site quotes.

Atlas's Roblox discovery tracker follows the title's visits and concurrency. Roblox's own public API reports the universe as content-restricted (re-confirmed November 1, 2026), which limits the stat field to outside trackers.

Villains Wiki documents The Locust's origin in Doctor Nowhere's T.O.E. series. It is a source about the character, not about this game's systems.

RoHorizon's guide cluster is the main public gameplay write-up. It is an AI-assisted fan publisher, prints no place ID, and uses both title orders for one game — every borrowed claim carries that warning and its date.

Destructoid, GameRant, Pro Game Guides, and Beebom have no code page for this exact title (first checked October 3, re-checked November 1, 2026). Their Locust coverage — Destructoid's included, whose look-alike codes page was updated October 15, 2026 — tracks the look-alike place 113385977463481, which is documented as such, never imported.

No announcements channel, board, or patch-note page is linked from the official page or findable for this place. The storefront page itself is the news feed.

September 2026 playthroughs of the exact title document the round format in public footage. Videos are evidence for the loop, not for numbers.

September 6–30, 2026

Snapshot of the launch-week page (stats, stamps, genre label), in-person verification of the September 6 updated stamp on September 9, and three observation passes confirming the title and credits stayed unchanged.

October 3, 2026

Site-wide recheck: the games API reports universe 10764415270 as content-restricted, the title-matched code tracker still lists zero verified codes, and the tracker sweep found no publisher code page for this title.

October 8, 2026

Register re-verification: the content-restricted API state and the place 113447904853223 → universe 10764415270 mapping were re-confirmed, and both RoHorizon code trackers re-checked unchanged — zero verified codes for this title, the same five unverified look-alike reports.

October 16, 2026

Register re-verification: the mapping and content-restricted API state re-confirmed, the storefront observed redirecting to Roblox's Title-Unavailable placeholder in this environment (its stamp stays unverifiable here), the title-matched tracker re-fetched at zero verified codes, the look-alike tracker unchanged at five unverified reports, and Destructoid's look-alike codes page (updated October 15, 2026) read as reporting no active codes.

October 25, 2026

Register re-verification: the mapping and content-restricted API state re-confirmed, the storefront still serving Roblox's Title-Unavailable placeholder state in this environment (the /store/ deep link now returns 404), the title-matched tracker re-fetched at zero verified codes, the look-alike tracker unchanged at five unverified reports, and Destructoid's look-alike codes page re-read in a rendered browser still showing its October 15 no-active-codes state. The guide-site schedule article re-checked at its October 23 stamp with the tracked event now rendering “[ Content Deleted ]”, and the outlet’s former events-schedule URL for this game now redirecting to an unrelated game’s page.

November 1, 2026

Register re-verification: the mapping and content-restricted API state re-confirmed, the storefront still serving Roblox's Title-Unavailable placeholder state in this environment (the fetched page URL now redirects to the /Title-Unavailable slug; the /store/ deep link still 404), the title-matched tracker re-fetched at zero verified codes, the look-alike tracker unchanged at five unverified reports, and Destructoid's look-alike codes page re-read in a rendered browser still showing its October 15 no-active-codes state. The guide-site schedule article re-checked at its October 30 stamp projecting Saturday, October 31 at 4:24 AM ET — a fourth straight Saturday projection, already passed at this check — and the article itself now renamed: its former update-schedule URL redirects to a “content-deleted-update-schedule” slug named after the deleted tracked event, while the companion events URL still lands on the unrelated yard-cleanup game's article.

Why do some claims on this site come from only one outlet?

Because for a two-month-old game with no changelog, one outlet is often all that exists. The rule applied here is that single-source claims are labeled single-source with their date (like the camera-flash report), rather than laundered into a consensus that does not exist.

How do you handle the look-alike game's sources?

By labeling them. Publisher code trackers do cover the reversed-title game, and their reports are genuinely useful — as documentation of the other place. Any string, link, or number from those sources is marked with the look-alike's place ID wherever it appears on this site.

What triggers a re-check of a source?

A storefront change (new stamp, title, or description) re-opens everything economy- and code-related; a new creator video can re-open a mechanic claim; and every claim carries its checked date so stale ones identify themselves.

Can I suggest a source?

Yes — the contact page takes a URL plus the claim it supports. Sources that bind to place 113447904853223 are exactly what this site lacks most.