MM2 of The Locust Maps

1. Name landmarks by visible features

The official description mentions upcoming maps but does not publish a map list. Start with stable visual anchors: a colored wall, a large prop, a staircase, or a distinctive doorway. Use descriptions that another player can verify without knowing your nickname.

Record two directions from each landmark instead of drawing a perfect map immediately. “Blue wall connects to the open yard” is enough to reconstruct a route after several attempts.

2. Connect prompts to locations

When an objective or interaction appears, write the exact prompt and the landmark where it appeared. Note whether the prompt stayed visible, disappeared, or changed after another action. These observations can reveal useful navigation patterns without claiming an undocumented map rule.

Keep version and date beside every note. A Pre-Alpha layout may change while the game keeps the same broad escape premise.

3. Compare routes with a simple scorecard

For each route, track orientation time, interruptions, backtracking, and whether the objective remained visible. Do not score a route by “success” alone; a failed attempt that clearly identifies a dead end is valuable evidence.

Use the same starting point where possible. If the server or player count differs, mark it so readers understand why two results may not compare directly.

4. Share maps without leaking false certainty

A useful community map includes a date, build signal, legend, and confidence label. Separate confirmed prompts from player landmarks and unknown areas. Avoid copying a screenshot from an unverified account and presenting it as an official map.

When an official map or update arrives, archive the old observation instead of silently overwriting it. This makes the wiki’s update history understandable.

Frequently asked questions