GRAIN ROT Vessels

GRAIN ROT vessels wiki: understand fragile wooden bodies, what happens when one breaks, how Spark re-hosting fits the run, and which body details remain TBA.

See the wooden-body loop in context.

~7 min read

Spark guide Enemies

At A Glance

This GRAIN ROT Vessels wiki page separates the confirmed loop from details that still need a current-build check. GRAIN ROT sends one to four players into cursed Deep Layers. Break furniture for scrap, use the Grinder for gold, extract by Elevator before the Corrupted overwhelm the run, then use the haul to rebuild the Outpost. Use it as a run-side reference, not as a promise that an unverified symbol, price, spawn rule, or named variant works the same in every seed.

The practical goal is simple: make one safer decision at a time, keep a return route, and turn a completed extraction into useful persistent progress. When a result is uncertain, preserve the haul and compare notes after the run.

Fact	Detail
Platform	Steam PC
Mode	Solo or up to 4-player co-op
Core setting	Cursed, procedurally shifting Deep Layers
Topic	Vessels Wiki
Body type	Fragile wooden Vessel
Pilot	Living Spark
Full named roster	TBA — intentionally not invented
Source boundary	Steam listing and current player-observed guidance; unconfirmed details are marked TBA

What are Vessels in GRAIN ROT?

Vessels are the fragile wooden bodies possessed by Living Sparks. They are central to the game’s extraction loop because a body break changes the team’s mobility and recovery problem before it changes the loot plan.

The reliable foundation is the same whether you are solo or in a group: a Living Spark uses a wooden Vessel in a procedurally shifting Deep Layer, valuable items must survive long enough to reach the Elevator, and the Outpost only benefits from what actually comes home. That is why vessels wiki advice should start with position, team condition, and an exit rather than with a supposed optimal trick.

GRAIN ROT wooden Vessel and Spark possession

Do01Treat the current Vessel as worth protecting
Do02Keep a retreat route before testing a threat
Do03Tell the group when a Vessel is damaged or broken
Do04Do not assume a named alternative is available
Do05Use the Spark guide to plan a safe recovery

Treat the first observation as information, not a command

A useful observation tells you what changed: a sound, a symbol, an unsafe route, a damaged Vessel, or a possible resource. It does not automatically tell you to push deeper. Pause long enough to name the change, identify who can act on it, and decide whether acting would leave the Elevator route exposed.

This avoids a common early-run failure: the team notices something important, everyone moves toward it, and nobody retains a shared plan for regrouping. If the current floor becomes noisy or confusing, backing out with a small haul is a successful run rather than a wasted attempt.

Use short calls that change behaviour

In co-op, say the location, the pressure, and the intended action: “Elevator side, Vessel broken, regroup,” is more useful than a long description. Solo players can apply the same discipline as a mental checklist. The game rewards decisions that leave you a second option when the first path becomes unsafe.

With that baseline in place, the next question is not “can we continue?” but “what does continuing cost if the situation worsens?”

What should I decide during a Vessels Wiki run?

The important Vessel decision is not a tier ranking; it is whether the current body and route can still support a safe extraction.

Use the table as a decision aid, not a hidden-stat calculator. GRAIN ROT has changing layouts and evolving community knowledge, so a precise number without an in-game check is less useful than a conservative threshold: protect value when recovery is uncertain, and test risky ideas only when the team can afford the result.

GRAIN ROT switching between Vessels during a run

Situation	Action	Why it is safer
Your Vessel is intact	Use it to keep the group mobile and oriented	Preservation retains options
Your Vessel breaks	Switch to a Spark recovery plan	The player is not automatically removed
You hear of an alternative body	Check it in the live build	Names and stats are not yet authoritative
The group is carrying value	Avoid body-risking experiments	Secure the haul before testing

Make the irreversible choice last

Breaking an object, spending a resource, taking a deeper route, or splitting the group can remove options. Before doing any of those, confirm what the team keeps if the attempt fails. If the answer is “nothing useful,” choose the reversible option first: regroup, scout, mark the route, or extract.

That same habit makes progress steadier. One secure extraction can improve the Outpost and make the next attempt more informed; a speculative loss often repeats the same first minutes with no new advantage.

Are there different Vessel types?

The official core premise confirms wooden Vessels and re-hosting, but it does not provide a complete official catalogue of named bodies, stats, or unlocks. This wiki therefore does not turn isolated reports into a full roster.

Avoid turning player reports into universal rules. A report can be valuable evidence of an interaction, yet it may come from a particular layer, patch, item state, or group setup. Record the context before copying it: where it happened, what the Elevator offered, what the team carried, and whether the result was repeated.

GRAIN ROT Vessel movement through a Deep Layer

What belongs in a future database

A named Vessel needs a clear current-build visual, source, availability, and observable effect before it earns a row.

The useful follow-up is to connect this observation to the broader run: does it make extraction easier, reduce the danger to a Spark or Vessel, change the value of scrap, or simply create a new risk? If it does not answer one of those questions, do not let it pull the team away from its plan.

What remains TBA

Exact alternative-body names, attributes, locations, and upgrade interactions remain TBA until consistently verified.

How do Vessels change extraction choices?

A fragile Vessel raises the cost of a deep extension. If the body is threatened, the group may lose the ability to carry value, guide a Spark, or reach the Elevator together. That makes an earlier extract a practical body-management choice.

A conservative guide is especially important while the live knowledge base is still growing. The Steam description confirms the broad systems—Sparks, Vessels, Deep Layers, the Elevator, Corrupted pressure, the Grinder, and the Outpost—but it does not publish a complete numerical database. Tables on this site therefore distinguish a confirmed loop from TBA details instead of filling gaps with invented stats.

Plan around recovery, not ranks

Use position, team condition, and exit access instead of unverified tier labels.

If the observed result matters to your next run, verify it again after a patch or compare it with a concise report in the community. Keep the claim narrow: “this happened in this setup” is more useful and more durable than a broad claim about every seed.

Keep observations narrow

Report the body, context, and observed interaction; do not infer a universal stat from one run.

What should I verify before trusting Vessels Wiki advice?

Check the current build before treating a named effect, numerical cost, channel name, exact spawn condition, or complete roster as settled. The official Steam page is the source for the game’s core premise and player count; the verified Discord is the best route for patch-sensitive questions. Do not use copied invite links or anonymous “full databases” as authority.

Do01Confirm the claim is about GRAIN ROT, not another game with a similar name
Do02Check whether the report identifies a current patch or a specific Deep Layer context
Do03Separate a confirmed system from a proposed strategy or personal preference
Do04Keep an Elevator route and a recovery plan before testing a risky claim
Do05Use Spark guide when the next decision concerns the wider run loop
Do06Use the verified Steam listing or the verified community for details marked TBA