MM2 of The Locust Team Strategy

1. Assign temporary roles, not permanent classes

The official listing does not publish named survivor roles or a class system. You can still coordinate by assigning temporary jobs: one player reads prompts, one watches the route, and one records what changed. Rotate those jobs so one person’s assumption does not become the team’s “official” rule.

Use plain callouts based on what everyone can see. “Red door, left side” is safer than a nickname copied from a video, especially when maps and labels may change during Pre-Alpha.

2. Keep communication short and repeatable

A good callout contains a location, an action, and a confidence label: “North corner, prompt visible, confirmed.” If you only saw the result once, say “observed” instead. This vocabulary lets teammates make decisions without mistaking a report for a universal mechanic.

Choose one person to repeat the objective at the start of each attempt. Shared wording reduces the chance that three players follow three different interpretations of the same prompt.

3. Run team tests one variable at a time

When testing a route or interaction, agree on what stays constant: the starting area, the order of actions, or the number of players nearby. Change only the variable you want to learn. Save the result with the server context and date.

If a teammate discovers something unexpected, do not immediately publish it as a trick. Repeat it in a fresh round and check the update log first. A bug can look like a powerful strategy for one session.

4. Recover when the plan breaks

When communication fails, return to the visible objective and regroup at a landmark everyone can identify. Avoid splitting into an untracked search unless the team has agreed on a time limit and a meeting point.

After the round, compare notes rather than arguing from memory. The clearest next step is usually one small change to the callout or starting position.

Frequently asked questions