GRAIN ROT’s systems are tied together by the value of a successful return. The Steam Store says players can rip out furniture for resources, feed furniture into the Grinder for gold, rebuild a persistent Outpost, unlock interactive furniture and stat upgrades, rescue survivors, and find stranger ways to survive the next descent. That is enough to explain the economy loop. It is not enough to publish exact prices, drop rates, item rarity, or a permanent best spending order.
Separate value from convenience
An object in a ruin has at least three kinds of value. It can be a resource for immediate use, a candidate for the Grinder and gold, or a physical object that changes how the room can be crossed. A fourth value is information: the crew may learn what the object does and decide whether it is worth carrying in the future. The highest number is not always the best choice when the carrier becomes slow, the route becomes noisy, or the exit is uncertain.
Before processing furniture, name the desired result. If the Outpost needs a repair, carry what supports the repair. If the next upgrade needs gold, compare the Grinder option with the risk of staying. If the object only helps the crew learn the room, take a note and leave when the extraction boundary is reached. This keeps Systems connected to Maps and Outpost without letting one page pretend to own every decision.
Resource
Something the game exposes for rebuilding, crafting, repair, or another persistent purpose. Record the UI name and current source.
Grinder
A conversion choice described by Steam as a way to turn furniture into gold. Verify the prompt, result, and loss before publishing a table.
Risk
The chance that processing, carrying, or exploring longer causes a vessel break or a full-team loot loss.
The Grinder is not a free conversion
The official description makes the Grinder memorable because it creates a clear trade: feed furniture into it for gold, or use the object as a resource or physical tool. The right question is not simply “what gives the most gold?” It is “what can the crew safely convert on this run, and what persistent objective is the gold serving?” A launch guide should teach this question until the current interface supplies a verified table.
When testing the Grinder, record the object name as shown in the game, the result, the time or animation involved, and whether the action makes noise or changes the room. Repeat the observation on the same public version before calling the value stable. Do not transfer a price from a demo, a bundle, a screenshot, or a player comment into the base game. Keep the date next to every volatile number.
Loot loss changes the economy
Steam warns that if everyone breaks, the loot is lost. This rule means a resource page must include the cost of overextending. A crew can be technically “profitable” in a room and still lose the entire haul by taking one more fight with no retreat. It is often correct to extract with a modest return, use that return in the Outpost, and learn whether the new state makes the next run safer.
Track the reason for a loss. If the cause was a missing route, Systems should not prescribe more gold. If the cause was an object conversion that attracted pressure, the note belongs with the map and combat context. If the cause was a weak persistent upgrade, Outpost may own the follow-up. This classification prevents a universal economy tip from becoming a misleading answer to a spatial or combat problem.
Progression has more than a number
The Store names stat upgrades, interactive furniture, rescued survivors, and persistent Outpost rebuilding. Treat each as a separate progression layer until the live game shows how they connect. A stat may change what a vessel can survive. Furniture may add a menu interaction or a practical station. A survivor may unlock a service or a story element. The public description confirms the concepts but not their exact implementation.
For each verified progression record, capture its source, requirement, cost, result, whether it is permanent, and whether it affects solo or co-op play. If any field is unknown, leave it unknown. “The game has upgrades” is a safe overview fact; “buy room three before room two because it adds 20% stamina” is a live-data claim that must be tested before it appears in a recommendation.
Mutations and cosmetics need careful labels
Body corruption and mutation systems, plus questionable cosmetics, are official feature language. They are useful search topics, but the words alone do not describe the exact effect or unlock path. Put visual presentation, mechanics, and acquisition in separate fields. A mutation observed in one run may be tied to a layer, a host, a patch, or a temporary event. A cosmetic may be a reward, a store item, or a joke with no gameplay effect.
Do not use a tier-list voice when the evidence only establishes that a system exists. Use “currently documented,” “community reported,” or “needs live/version testing” as appropriate. The goal is to help a player decide what to check, not to turn a launch snapshot into a permanent database.
Choose the next system page
Go to Outpost for persistent spending, Maps for room and retreat context, and Combat when a vessel or Corrupted threat changes the value of an object. Use Updates for dated economy changes rather than silently rewriting an old number.