Define the build by the problem it solves
The official scope includes four classes, more than thirty spells, ten weapons, physical interactions, procedural bunkers, and one-to-four-player support. Those facts imply many combinations, but they do not establish a universal ordering. Begin with the run problem: maintaining information, preserving movement, handling environmental decisions, coordinating resources, and recovering when the plan breaks. Then select current in-game options that support those outcomes.
Write the plan in capability language so it remains useful across updates. ‘Keep a retreat lane visible’ is clearer and safer than a claim that an undocumented item guarantees safety. ‘Protect a recovery option’ tells the player how to think even when balance changes. Specific current selections can be added in personal notes with version context, while this published guide stays inside verified evidence.
Build coverage with primary and backup owners
For each important responsibility, name who acts first and who can cover if that player is occupied or separated. A backup does not need to duplicate the entire plan; it needs a workable response. If only one player understands the generator decision, the squad has fragile environmental coverage. If everybody expects somebody else to preserve the retreat, the build has no movement ownership despite having several strong individual choices.
Solo planning uses the same table with one owner. The gaps become explicit, which is valuable. A solo build can answer missing coverage with slower scouting, a larger reserve, more reversible interactions, or an earlier retreat. The aim is not to make one player imitate four people simultaneously. It is to recognize which situations need a different risk threshold.
- Information owner and backup observer.
- Movement owner and agreed retreat signal.
- Environment owner and interaction confirmation.
- Resource owner and FAITH-spend callout.
- Recovery owner and regroup location.
Attach a resource plan to the composition
Spell choices cannot be evaluated apart from FAITH and FEAR. If the composition expects several players to use spells for the same type of pressure, decide how those decisions are sequenced and when another option is preferred. A build that looks broad on paper can become narrow if all its answers consume the same reserve. Protect at least one fallback that does not depend on the original sequence working perfectly.
Do not invent numerical budgets. Use purpose and urgency: planned information spend, movement protection, control, support, and emergency recovery. Reassess after each consequential use. In co-op, one short summary can keep everyone aligned on what the group is protecting. In solo, a written or mental threshold prevents urgency from turning every problem into the same response.
Include the environment in the build
Physical interactions and generator-light tradeoffs are officially presented parts of the game. A composition therefore includes how the group notices, communicates, and uses the environment. Decide who announces an interaction and who watches the space while it happens. The build should not assume machinery is always helpful or always dangerous; it should make the decision deliberate and preserve a way to respond to the changed state.
Procedural bunkers make a fixed route brittle. Build for reading rather than memorization: identify landmarks, confirm retreat directions, and update the plan after a door, generator, or other interaction changes access or visibility. A flexible composition can transfer leadership to the player with the relevant view. That handoff is a capability in its own right.
Pressure-test the plan before relying on it
Ask what happens if the information owner is separated, a planned spell is not appropriate, the retreat direction becomes unusable, or the group reaches B.O.S.S. preparation with less flexibility than expected. These are scenario questions, not predictions about exact mechanics. A useful build has a simple answer or acknowledges that the squad should disengage earlier under that condition.
Change one element at a time after a failed run. If the group changes roles, spell purposes, communication, and movement rules together, it cannot tell which revision helped. Record the problem and the chosen adjustment. Procedural variation prevents perfect comparison, but disciplined notes still reveal repeated coordination failures more reliably than unsupported rankings.
Use presets as prompts, not prescriptions
A Balanced plan spreads attention across information, environment, movement, and recovery. A Stealth-oriented editorial preset emphasizes observation, spacing, and avoiding unnecessary commitments. An Environment-oriented preset makes physical interactions and machinery communication central. These labels belong to the guide’s planner, not the official class system, and they do not claim hidden bonuses or exact loadouts.
Choose a preset to start a conversation, then adapt it to party size and current in-game descriptions. Revisit it when the bunker exposes a gap. The squad planner can store strategy tags and notes without producing a fictional damage score. For detailed role reasoning, continue to the class guide; for the resource consequences of spell-heavy planning, use the FAITH and FEAR briefing.