Shelter Progression

How Shelter Progression Helps

The shelter or Outpost is where extracted value becomes lasting preparation. Repairs, room improvements, constructs, and shop progress can increase the margin for future expeditions. The purpose is not to finish every room as quickly as possible; it is to build a base that solves the failures your current runs actually produce.

Shelter progression works best as a feedback loop. Descend with one clear goal, extract, invest in a relevant milestone, and observe whether the next runs improve. This approach turns every upgrade into a testable decision instead of an automatic purchase.

Connecting Rooms to Run Failures

Start with evidence from play. Review several extractions and failures, then name the limiting problem. Fragile vessels point toward health or durability support. Failed retreats point toward stamina. Threats that consume too much time may justify attack-related progress. Missing basic tools may make the shop a higher priority.

Separate mechanical weakness from planning error. No room upgrade can mark the elevator, prevent greed, or make a player communicate. If the team repeatedly becomes lost with unused resources, improve navigation habits before spending on combat power.

Write a one-sentence upgrade hypothesis: “Improving this room should let us survive the return route with enough health,” or “Improving the shop should make basic navigation gear replaceable.” A clear hypothesis tells you what to watch on the next run.

Planning Upgrade Milestones

Choose milestones rather than spreading Scrap across every available option. A milestone is a meaningful improvement you can complete without emptying the resources needed to equip and recover. Finish one, test it, then choose the next.

A practical progression rhythm is:

1. Stabilize the most common early failure.
2. Preserve access to basic salvage and navigation tools.
3. Improve the second-most common weakness.
4. Add specialized strength for deeper or more dangerous goals.
5. Reassess whenever the expedition pattern changes.

The supplied evidence does not publish a complete official table of exact room costs or level bonuses. Use the current interface as the authority and treat this sequence as a planning framework rather than a fixed build.

Balancing Core Stats

Health-related progress creates room for damage and imperfect routes. Stamina supports longer movement and final escapes. Attack can shorten unavoidable threats. Each can be valuable, but none should be maximized in isolation while another weakness repeatedly ends runs.

When two upgrades seem equally useful, choose the one that affects more common situations. Health and stamina often provide broad reliability, while specialized attack becomes stronger when the team consistently reaches encounters where damage is the true bottleneck.

After upgrading, run comparable expeditions. If the same failure happens at the same point, reconsider the diagnosis. More levels in the wrong system only make the investment harder to question.

Balancing the Shop and Core Stats

Shop improvement matters when equipment access limits preparation. If the team cannot reliably replace mallets, navigation tools, repair gear, or other supported items used on normal runs, shop progress may create more value than another narrow stat increase.

Do not spend every resource on the shop and leave nothing to purchase from it. Maintain an equipment reserve after the upgrade. Also avoid assuming one exact “upgrade the shop” procedure applies across all builds; the existing evidence confirms Outpost and shop improvement but not every version-specific requirement.

Using Constructs and Furnishings

Constructs and room furnishings should support a known benefit. Before placing or improving one, identify the stat, preparation service, or progression function it provides in the current game. Decorative completion is optional; reliable expeditions come first.

Avoid copying an exact layout without understanding why it works. The collected material supports placing constructs and rebuilding rooms, but not a universal best arrangement. Favor clear movement, easy access to preparation systems, and improvements tied to the team’s current milestone.

When the effect of a construct is uncertain, test it separately. Note the state before and after, avoid changing several systems at once, and use current in-game feedback. This prevents community guesses from becoming false rules.

Building a Reliable Preparation Loop

Every expedition should begin and end at the shelter with a short routine. Store equipment that is not needed, check the next upgrade target, reserve enough for essential tools, choose the run objective, and set an extraction threshold.

After returning, process the result in the same order: secure rare items, measure progress toward the milestone, purchase only the planned improvement, and verify the next run remains affordable. Repetition makes the shelter a decision center rather than a place where resources disappear between descents.

This routine also protects against emotional spending after a failure. A frustrating death may suggest a dramatic attack upgrade, but the log may show that the real cause was a lost route or late extraction.

Solo Shelter Priorities

Solo players benefit from broad, dependable support. Health, stamina, tool access, and navigation preparation reduce the number of systems one person must execute perfectly. Specialized upgrades are worthwhile when a repeated solo objective clearly requires them.

Maintain a larger recovery reserve because no teammate can carry spare gear or protect a failed route. Test new systems with inexpensive loadouts before committing rare equipment.

Co-op Shelter Priorities

Teams should choose upgrades from shared evidence rather than the loudest preference. Review where the group loses time, vessels, or equipment. An improvement that supports several roles may outperform one narrow benefit for a single player.

Coordinate purchases and loadouts so the same capability is not overfunded. If shop progress makes a tool more accessible, assign who carries it and how the team protects it. Shared progression becomes useful only when it changes shared behavior.

Shelter Progression Checklist

• Review multiple runs before choosing an upgrade.
• Name the failure the upgrade should solve.
• Complete one meaningful milestone at a time.
• Keep reserves for tools and recovery.
• Verify construct and room effects in the current build.
• Test whether the targeted failure becomes less common.
• Change priorities when the expedition pattern changes.

Shelter Progression FAQ

Which room should I improve first?

Improve the system tied to your most common preventable failure. Broad health or stamina support is often useful, but the correct choice depends on actual runs.

Should I upgrade everything evenly?

Usually not. Focused milestones produce useful changes sooner and make it easier to judge whether an investment worked.

When is the shop a priority?

Prioritize it when access to replaceable basic equipment is limiting otherwise viable expeditions. Keep enough resources to buy tools after improving it.

Is there a verified universal shelter build?

No. The supplied evidence supports shelter and room progression but does not establish one exact layout, level order, or cost table for every version.