Plan for variation, not a fixed map
The official store describes procedural bunkers. That means a route from a video or previous run can offer ideas but cannot replace observation. Begin each new area by identifying the entrance, usable lanes, notable landmarks, interactions, and a retreat direction. Share those facts before the team divides attention. A mental map built from confirmed transitions is more dependable than one built from visual similarity.
Use names the squad can reproduce: a visible object, shape, light state, or junction. Avoid long improvised labels that become confusing under pressure. Solo players should pause at junctions and deliberately look back; the return view may be different enough to matter. The goal is not perfect mapping. It is maintaining enough orientation to make the next decision recoverable.
Use a repeatable room-reading loop
At the threshold, observe before interacting. Identify where movement could compress, what remains behind the group, and which objects appear physically relevant. Choose who crosses or acts first, then reassess after the action. An interaction can change the tactical meaning of a room even if the geometry appears familiar. Treat the post-interaction state as new information rather than continuing automatically.
The loop is observe, orient, assign, act, and update. It applies in solo play with the assignment step becoming a statement of personal intent. If danger interrupts it, return to the last completed step when control is restored. This structure prevents several half-finished plans from competing and makes a failed attempt easier to review.
- Observe entrances, exits, lanes, and interactable objects.
- Orient the group around one shared landmark.
- Assign the next action and the person watching retreat.
- Act without adding unrelated commitments.
- Update the shared map after the environment changes.
Treat physical interactions as commitments
Physical interaction is an official feature, so the environment belongs in the plan. Before using an object or mechanism, say what outcome is expected and what the team will do if access, visibility, or pressure changes. Keep other players clear enough to observe rather than crowding the interaction. One player acts; another preserves awareness. In solo, position so the interaction does not erase the only understood route.
Do not assume every available interaction should be used immediately. Information can raise or lower its value. Nor should old demo notes become current rules for doors, machinery, or enemies. When behavior differs from memory, verify the present build and official notices. An unexpected result is first an observation, not automatically a defect.
Make generator and light choices locally
The official description presents generators and lighting as tradeoffs. Avoid a universal always-on or always-off rule. Ask what visibility enables now, what the interaction changes, how the squad will hold the space, and whether a fallback remains. A useful decision is local to the route, resources, and group state. Announce it so everyone updates the same environmental picture.
After the light state changes, stop and scan again. New visibility can reveal useful information, but it may also change how players move and where they focus. The generator guide expands this decision without inventing exact noise radii, timers, or guaranteed reactions. Those values are not established by the checked current sources.
Preserve and rehearse the retreat
A retreat plan should identify direction, trigger, order, and regroup point. ‘Go back’ is weak if half the team has a different understanding of back. Before a consequential room or interaction, name the landmark and who calls withdrawal. Keep enough spacing to turn and move. A plan that exists only after pressure begins is usually a collection of individual guesses.
Solo players should choose retreat triggers earlier because no teammate can cover a missed angle or restore shared orientation. Retreat does not have to mean abandoning the run. It can create space to rebuild the map, reassess FAITH, and choose a different interaction. The ability to simplify is a survival resource.
Turn each bunker into transferable learning
After the run, sketch decisions rather than pretending to preserve an exact procedural map. Record which landmark system worked, where the group lost the retreat, which interaction changed the plan, and whether communication remained clear. These lessons transfer across layouts. Exact room orders often do not. If sharing notes, include the build date and separate direct observation from interpretation.
Use the beginner guide to practice the loop, the generator briefing for light decisions, and the solo or co-op guide for the relevant information burden. Recheck official sources after Early Access updates. Procedural generation creates natural variation; build changes add another reason to avoid presenting one run as a permanent rule.