Know the B.O.S.S. evidence boundary
Official material establishes B.O.S.S. encounters as part of the run, but the current checked sources do not justify a published roster with exact mechanics. A dramatic clip can show an example without establishing every phase, value, or counter in the current build. Early Access raises the risk of stale detail further. Read the encounter in front of you and treat this page as preparation doctrine rather than a hidden-stat database.
- Record the date or build context, party size, visible cue, response, and outcome.
- Separate what happened from why you think it happened.
- Treat repeated observations as an editorial hypothesis until official evidence confirms a claim.
- Do not present this site’s preparation framework as a measured encounter solution.
Run the readiness check before commitment
Confirm the retreat or regroup direction, current team spacing, remaining resource purposes, and the player who will call movement. Ask whether each critical responsibility has a backup. A squad can possess many options and still be unprepared if nobody knows the order in which they will act. Solo players should choose simpler triggers because observation, movement, resource management, and recovery all compete for one person’s attention.
Do not delay forever in pursuit of perfect preparation. The check should reveal whether the group can explain its plan and survive the plan being incomplete. If the answer is no, use the bunker to restore clarity where possible. If the answer is yes, enter with one initial hypothesis and a clear signal for abandoning it.
- Movement caller and regroup landmark are named.
- FAITH reserve has a purpose, not an invented percentage.
- Players know primary and backup responsibilities.
- The first observation goal is explicit.
- The retreat signal describes an action everyone understands.
Use first contact to gather information
During the opening, prioritize visible cues, spatial constraints, safe movement, and the timing of obvious changes. Avoid spending every answer before the group understands the problem. Equally, do not preserve resources while the plan collapses. The FAITH decision loop covers the problem, alternative, purpose, fallback, and reassessment. It keeps the opening focused without relying on unsupported numerical thresholds.
In co-op, assign observations so the voice channel does not become several competing narrations. One player calls movement, another reports the encounter, and others confirm position or resource intent. Transfer those roles when information changes. Solo players can slow the analysis by concentrating on one cue per attempt and choosing reversible positioning whenever the current state allows it.
Adapt one assumption at a time
When the first plan fails, identify the earliest assumption that became unreliable. Was the movement lane narrower than expected, a cue misunderstood, the group too tightly spaced, or a resource sequence duplicated? Change one answer while preserving the parts that still worked. Simultaneous revisions create confusion and make the next outcome impossible to interpret.
Use neutral calls while learning: observed change, location, proposed response. Avoid converting a guess into a command unless urgency requires a temporary choice. After the attempt, label the guess as a hypothesis. Procedural bunker conditions and team resources may alter the context around an encounter, so a successful adjustment is still not a universal script.
Build recovery into the encounter plan
Recovery starts before the mistake. Keep a route or spacing rule that lets the squad simplify, identify who restates the objective, and protect an option whose purpose is restoring control. If confusion rises, stop layering new interactions and effects. Return to a known formation or landmark if possible, then rebuild the shared picture from observable facts.
A solo recovery threshold may need to be earlier because there is no backup observer or caller. Leaving a bad position is not proof the build failed; it may be the action that keeps the run alive. If the encounter ends the run, review the first loss of control rather than only the final hit. That point usually offers a more transferable lesson.
Write encounter notes that survive updates
Useful notes include current build context, visible cue, location, response, result, and confidence. Avoid exact values unless the current game clearly provides them and the publication can source them. Never import demo balance into the Early Access build without confirmation. If an official announcement changes an encounter, recheck the note against that source before presenting it as guidance.
Continue to the builds guide to pressure-test capability coverage, the spell guide to plan FAITH sequences, or the known-issues page when behavior appears unexpected. A surprising event belongs first in observation notes. It becomes a present official issue only when a current official source establishes that status.