Adapt the plan to party size
The official store supports one to four players and online co-op. A two-person squad needs each player to hold several responsibilities and should choose early retreat triggers. Three players can separate observation, action, and recovery more clearly. Four players offer another perspective and backup but can crowd lanes or voice communication. Headcount does not replace an explicit plan.
Before entering, put every player on the same build. Patch 0.05.007 fixes Steam invites, lobby searches, and other networking features, while 0.05.005 says a version mismatch prevents connection. Once the session is stable, name the observer, movement caller, environmental operator, and recovery coordinator. Combine roles in smaller groups and assign backups in larger ones.
Use callouts that change a decision
A useful call describes observed fact, location, and intended action. ‘Light changed at the last junction; hold here’ is actionable. Long theories can wait until the group is stable. Avoid narrating every visual detail, because important movement or resource information will disappear in the noise. Confirm critical calls with a short response so the caller knows the shared picture updated.
Agree on names for landmarks and directions before pressure. If two players use different terms, resolve the ambiguity immediately. During confusion, one person summarizes: current objective, known retreat, next action. Others correct only material errors. This restores a common plan without turning recovery into a debate.
- Fact: what changed or moved?
- Place: where relative to a shared landmark?
- Action: hold, move, interact, spend, or regroup?
- Owner: who acts and who watches?
- Confirm: did the squad understand the same instruction?
Sequence FAITH instead of duplicating it
Casting consumes FAITH and lower FAITH exposes the run to FEAR. When several players can answer a problem, name the first action and the signal for a follow-up. Two simultaneous casts may be intentional, but they should not happen because neither player knew the other was acting. State purpose rather than unsupported mechanical values.
After a consequential spend, one player summarizes the opening and the remaining plan. If the expected result did not appear, use the fallback before adding more effects. The shared FAITH picture can remain qualitative. What matters is that the group understands which purposes, including movement, control, information, support, and recovery, still have an answer.
Assign operator, observer, and route keeper
Physical interactions and the generator should never pull every player’s attention to the same point. The operator performs the action, the observer watches the immediate space, and the route keeper preserves orientation and retreat. A fourth player can maintain wider coordination or backup. Smaller squads combine roles but should still say which perspective is temporarily missing.
After an interaction, pause for the observer and route keeper to report before the group moves. The environment may now support a different plan. This handoff is especially important around light changes, where visibility can alter landmarks and spacing. Do not assume an interaction’s exact consequence beyond what the current build shows.
Pre-plan separation and regrouping
Choose a regroup landmark and a phrase that means stop adding new commitments. If players lose contact, the person with the clearest safe route calls the next movement; others report location facts rather than racing independently toward a guess. A backup route helps, but procedural bunkers make a fixed recovery script unreliable.
When reunited, restore role ownership and the shared resource picture before pushing. Separation can silently move important options to the wrong part of the group. Ask what changed and whether the original objective still makes sense. A clean regroup is a tactical success even when it costs forward progress.
Choose the squad plan for the official mode
The developer's Early Access launch announcement states two official game modes: B.O.S.S. Rush and Endless Bunker. That announcement establishes their names and the count, while the current public sources do not provide every rule, reward, timer, or difficulty formula. Use the game-modes hub to keep those verified boundaries visible before preparing a run.
For B.O.S.S. Rush, use the Run Checklist to confirm movement, resource purpose, and recovery ownership before the encounter sequence. For Endless Bunker, use it to define review points and preserve a sustainable retreat rule. The Squad Planner can record party size, mode, capability coverage, and handoffs without producing a fictional damage score or best-build ranking.
Review coordination, not personalities
After a run, identify the first missed call, duplicated action, lost landmark, or unclear handoff. Describe the process without blaming the player. Change one communication rule on the next attempt and retain the calls that worked. This keeps learning possible across procedural variation and different group compositions.
Record the build date when an interaction or spell outcome matters. Early Access can change the systems beneath a familiar squad routine. Use the class guide for capability language, the build guide for primary and backup coverage, and the known-issues page before treating unexpected behavior as established present status.