GRAIN ROT Outpost

The Outpost is the part of GRAIN ROT that turns a successful extraction into a longer-term plan. The Steam Store describes persistent Outpost rebuilding, interactive furniture, stat upgrades, and rescued survivors. That gives the hub a clear job: explain how to decide what the base should do for the next descent. It does not justify a made-up room order, a fabricated cost table, or a claim that every upgrade has the same value for solo and co-op crews.

What a return should accomplish

A return to the Outpost has three possible outcomes. It can repair an immediate weakness, unlock a new way to interact with the base, or improve the crew’s ability to survive a deeper run. Pick one primary outcome before spending. If the team returns with a scattered handful of materials and immediately buys the first visible upgrade, it may feel productive while leaving the real failure untouched. If everyone kept breaking vessels because the route became too crowded, more damage may not solve the problem; a room or layout change could matter more.

Start by naming the bottleneck in plain language. “We cannot move the haul safely,” “we do not know where the route ends,” and “we are losing time when a Spark is displaced” are better than “the base is weak.” Each statement points to a different test. The first suggests space and furniture. The second suggests a Maps note. The third belongs to Combat and co-op practice. This separation prevents the Outpost page from pretending that every problem is a stat problem.

Furniture is a resource with a location

The Store explicitly says that furniture can be ripped out of shifting ruins for resources and can be fed into the Grinder for gold. It also calls Outpost furniture interactive. Those statements point to a useful distinction: an object’s value is not only the number shown in an inventory. Its position, the time needed to move it, the noise created by handling it, and the space it occupies can all matter to an extraction crew.

At the Outpost, test one interaction at a time. Move an object, inspect its prompt, and note whether the base displays a repair, build, or upgrade result. Do not infer that a piece of furniture has a permanent bonus merely because it can be placed. Conversely, do not call it cosmetic until the current interface and the patch notes show no gameplay effect. A good wiki entry will state the observation date, the AppID, and the build context rather than using a screenshot as proof of a universal rule.

Prioritize the next descent, not the prettiest room

Base building is a planning surface for the extraction loop. If the crew is learning how to survive Deep Layers, prioritize anything that makes the next objective legible: a place to prepare, a place to inspect the current state, and a clear way to return to the elevator. If the crew is already extracting reliably, a stat upgrade or rescued survivor may be the better test. The correct order depends on what the game exposes and on whether the run is solo or online co-op.

Avoid a universal “best Outpost order” at launch. A four-player group may value a different improvement from a solo player, and an early patch can change the cost or the unlock condition. The public Store text does not provide a full table. The Community Hub has player observations about fixing the house and inspecting objects around the Outpost, but those posts are evidence to investigate, not permission to publish exact numbers. Link a future room guide from here once two dated observations agree or an official patch note names the system.

Survivors and persistent progression

Rescued survivors are a named feature in the official description, which means they belong in the Outpost information model even before the wiki knows every role. Record how a survivor is found, what the UI calls the action, and whether the person changes a stat, opens an interaction, or adds a cosmetic detail. Keep “the Store says survivors can be rescued” separate from “this survivor adds ten percent to a stat” unless the latter is directly verified.

Persistent progression should also be described in terms of reversibility. If an upgrade can be changed, the crew can experiment. If it consumes a scarce currency or locks a room, the decision deserves a warning. The current launch hub intentionally uses a decision framework instead of a fake tier list. A live database can be added under Systems or Outpost later without rewriting the core route.

A compact Outpost review

After each return, write down the run objective, the largest failure, the resource or gold action taken, and the next test. If the group cannot explain why an upgrade helps, save the resource. If a room change clearly reduces confusion, keep it and record the version. If the only benefit is visual, label it as cosmetic. This discipline is more valuable than a copied list because GRAIN ROT is built around shifting ruins, physics, and a progression space that can change with patches.

Use the hub boundaries

Follow Guides for the first descent and Systems for Grinder, loot, and economy questions. Send vessel, Spark, and Corrupted behavior to Combat. This keeps the Outpost page focused on what persists between runs instead of becoming a second general guide.