GRAIN ROT is easiest to understand as a loop with a visible consequence: prepare in the Outpost, descend through a cursed elevator, take useful things from shifting ruins, and return before the run turns into a total loss. The official Steam description calls it a co-op extraction builder in a scorched wasteland, but that label does not tell a new player what to do with the first five minutes. This hub turns the broad description into a safe learning route without inventing a control map, a loot table, or a fixed dungeon layout.
Start with a repeatable first session
Do not treat the first descent as a race to the deepest possible room. The useful first objective is to learn what your crew can carry, what breaks a vessel, and which actions make the return trip safer. Confirm that everyone has the same Steam game and can hear the group before entering the elevator. If you are playing alone, expect a different risk profile: there is no partner to rescue a Spark, distract a threat, or carry the run while you learn the room.
Use a short pre-run callout. One player says who is watching the route, another watches the group’s condition, and everyone agrees on a retreat signal. GRAIN ROT encourages physics-driven chaos and even friendly trolling, so a boundary is part of the strategy. Decide whether dropped furniture is being destroyed for resources, moved as cover, or left alone until the room is safe. These are small choices, but they prevent a funny accident from becoming an expensive wipe.
Check the Outpost, the available equipment, and the route goal before the elevator starts.
Move deliberately, learn how sound and physics affect threats, and keep a way back in mind.
Leave with a useful haul rather than proving that a damaged vessel can survive one more room.
Use the result to improve the next decision, then record what changed for the crew.
Make the elevator a decision point
The cursed elevator is not just a loading screen. It is the moment to define the run. A first run can be about learning the Deep Layers, checking how furniture behaves, or bringing back enough material to improve the Outpost. A later run might focus on a particular kind of loot or on reaching a deeper section, but the objective should stay narrow enough that the team recognizes when it has succeeded.
Before descending, separate facts from assumptions. The Store confirms that the ruins shift, so a route remembered from one session may not map perfectly onto the next. It also confirms that the Corrupted respond to sound, movement, and each other, which means a loud shortcut can be worse than a slower detour. Do not call a room “safe” because it was empty once. Call it safe only for the current state of the run, current build, and current team position.
Protect the run while you loot
Furniture is both scenery and a resource question. The Store says players can smash furniture for resources or feed it into the Grinder for gold. That does not mean every object should be processed immediately. Break only what the team can recover, watch whether the noise changes the room, and keep enough space to move around a damaged vessel. The practical rule is to turn a room into a better exit route before turning it into a bigger pile of loot.
If the group finds a high-value object, name the carrier and the retreat condition. A carrier who is isolated may be richer for ten seconds and less likely to extract. A player who is still learning should not be shamed for leaving a marginal item behind. The Store’s full-wipe warning makes the tradeoff clear: if everyone breaks, the loot is lost. A modest return is a successful run when it teaches the group a safer boundary.
Keep the Spark problem visible
When a wooden vessel breaks, the player remains in the run as a Living Spark and must search for another host. This is a different job from ordinary movement. A Spark can guide attention, look for a new vessel, and help the group understand what is happening, but it should not disappear into a side corridor without saying where it is going. The team should know whether it is escorting the Spark, holding a room, or retreating with the current haul.
The exact controls and host rules are not published in the Store text, so this page deliberately avoids a fake button sequence. During the first sessions, record the action that releases a Spark, the distance at which a new host can be used, and what happens if the team extracts while one player is displaced. Those notes belong in a later verified guide rather than in a launch hub presented as universal truth.
Use this hub without turning it into a promise
The most reliable launch advice is procedural: choose a goal, communicate the retreat rule, treat sound and movement as variables, and spend the return on the Outpost. The least reliable advice is a precise tier list assembled from screenshots, a guessed player cap, or a claim that one room order always wins. Current Steam Community discussions already contain questions about performance, co-op size, and what to inspect around the Outpost; they are useful demand signals, not official manuals. See the AppID 4450620 Community Hub for dated observations, and label them as community reports when they are used.
Three questions to ask after a run
- Which decision caused the most risk: the route, the noise, the object we carried, or the moment we stayed too long?
- Did the Outpost change in a way that improves the next descent, or did we spend the return without a clear purpose?
- If a vessel breaks again, does every player know where the Spark is expected to regroup?
Answering these questions creates useful progression even before the wiki has a complete database. It also gives later pages a stable boundary: Outpost owns persistent upgrades, Combat owns vessel and Corrupted tactics, Maps owns procedural route language, Systems owns the Grinder and resource loop, and Support owns hardware and connection checks.