Read the run before committing
Procedural bunkers mean a memorized route cannot be the whole strategy. Begin by identifying what the current space allows: light, movement lanes, interactable objects, retreat paths, and whatever information the team can safely gather. A useful first decision is rarely ‘push immediately.’ It is ‘what would make the next room less uncertain?’ That question keeps attention on evidence instead of habit.
The official description emphasizes physical interaction with the environment, so objects and machinery are part of the tactical vocabulary rather than scenery. Pause long enough to understand an interaction before spending a scarce resource around it. If a choice changes visibility, access, or noise, tell the group what changed. In solo play, say the same decision to yourself in plain language; deliberate play prevents accidental commitments.
- Mark a retreat direction before entering a new space.
- Separate observed facts from guesses about the layout.
- Recheck the environment after any major interaction.
- Leave room for the bunker to invalidate a preferred route.
Manage FAITH and FEAR as one decision
The official store connects spell casting to FAITH and lower FAITH to greater exposure to FEAR. That makes a spell more than an isolated effect: it changes the state in which later decisions will be made. Before casting, identify the immediate problem, the value of solving it now, and the options that remain afterward. Saving everything is not automatically disciplined, but spending without a follow-up plan is avoidable risk.
Use a simple callout pattern in a group: problem, proposed spend, expected opening, and fallback. The pattern works without inventing cooldowns, damage values, or a preferred spell list. Solo players can use the same checklist during a pause. The aim is to make resource decisions legible. If conditions change, abandon the old plan without treating the change as failure; adaptation is the point of a flexible reserve.
Build a role plan, not a ranking
Four official classes create different possibilities, but the checked sources do not support a complete current class database or universal ordering. Start with capabilities the run needs: gathering information, controlling space, preserving recovery options, using the environment, and keeping the group coordinated. A class choice is useful when everyone understands what responsibility it is meant to cover, not when it wins an unsupported tier list.
In co-op, describe each player’s first responsibility and backup responsibility before the run becomes noisy. Avoid assigning one person every critical job. In solo, the same exercise reveals which situations need a conservative answer because nobody else can cover them. Revisit the plan when new resources appear or the bunker presents a different problem. A role plan is a living agreement, not a character verdict.
Preserve options inside the bunker
Survival improves when the team protects choices. Keep enough space to move, avoid clustering around a single interaction, and notice which direction remains usable if the current approach fails. The generator and lighting decisions described officially imply tradeoffs rather than a permanently correct switch position. Visibility can help, but the action and its consequences still need to fit the moment. Treat machinery as a decision point.
A failed approach should produce information. Ask what was observed, what assumption proved wrong, and what will change on the next attempt. Do not turn an uncertain event into a precise rule unless an official current source establishes it. Early Access makes that discipline especially important: an old clip or remembered demo behavior may not describe the build being played now. Record the version context when sharing advice.
Prepare for B.O.S.S. without invented formulas
The official material frames B.O.S.S. encounters as a destination of bunker preparation, but the checked current sources do not justify publishing a complete boss catalog, exact health values, or guaranteed counters. Prepare around universal readiness instead: can the group communicate, move without colliding, explain its remaining resources, and recover from a broken formation? Those questions stay useful when specific balance changes.
Before crossing a point that feels consequential, stop for a short readiness check. Confirm who calls movement, which lane stays open, what signals a retreat, and which resources are being protected for an emergency. After an attempt, describe observed mechanics separately from interpretation. This guide’s boss briefing uses that evidence-first method so a reader can learn without mistaking speculation for a current rule.
Use the manual as a route, not a database
Begin with the beginner briefing, then open the system page that matches the problem actually ending runs. The class and spell hubs explain safe planning boundaries; the bunker and generator briefings focus on environmental decisions; co-op and solo pages translate the same systems into different communication needs. Known issues and release pages are deliberately separated so historical demo notes cannot masquerade as current Early Access facts.
Every article shows a verification time, central game state, official sources, and contextual next steps. Recheck those signals after an update. If an official source does not establish a specific name, number, or rule, the guide will use a decision framework rather than fill the gap. That restraint is part of the product: a smaller reliable answer is more useful than a large fictional database.