Treat every Corrupted encounter as a resource decision: read the room, preserve the Living Spark, and fight only when the route or reward justifies it.
What to watch
- Movement and sound cues before committing to a room.
- Escape paths back toward the elevator.
- Furniture or scrap that can be turned into useful resources.
- How much Rot pressure the crew can absorb before extraction.
Why this is one hub
The enemy roster and names are still being documented. This page groups verified encounters first instead of publishing thin pages for every rumored creature.
What the Corrupted are
The Deep Layers contain Corrupted vessels that react to sound, movement, and one another. That official description explains why a room can change quickly even when the crew has seen the same visual threat before. Enemy knowledge should reduce uncertainty—recognize a pressure pattern, protect a retreat, and choose a response—not promise that an encounter always follows one scripted sequence.
Fight, build, run, or panic
Combat is one option in an extraction economy. A fight consumes time, position, durability, and attention. Building or using furniture may control a route. Running preserves resources but can pull danger into another room. The correct decision depends on carried value, distance to the elevator, exposed Sparks, and whether the encounter blocks an objective. This hub organizes threats around those decisions.
Sound and movement discipline
- Stop adding noise when the crew does not understand the room.
- Identify one retreat path before committing to an attack.
- Keep an exposed Spark behind the most stable vessel.
- Avoid chasing a target so far that the elevator route disappears.
- Call out a new threat by direction and behavior, not an unverified community nickname.
Why we do not publish nine thin monster pages
Search demand exists for monsters and enemies as a group, but names, categories, and balance details are still being verified. A single complete overview is more useful than many pages repeating uncertain descriptions. Individual enemy pages should exist only when players consistently search a stable name and the guide can provide distinct behavior, counterplay, and evidence.
Reporting a new encounter
Capture the biome or layer context, visible appearance, sound cue, movement, what triggered aggression, and the game version. A short clip is stronger than a memory-based label. Do not post private account information with bug reports. The official Discord provides bug-report and technical-support channels for reproducible problems.
Search coverage
Related questions players ask
What are the enemies called in GRAIN ROT?
Official descriptions refer broadly to Corrupted vessels in the Deep Layers. Individual enemy names should be confirmed in the current launch build before being treated as canonical search entities.
What attracts the Corrupted?
The Steam description says Corrupted vessels react to sound, movement, and one another. Exact ranges and triggers can vary or change, so treat those three signals as the confirmed behavior categories.
Do you have to fight every enemy?
No official rule requires a full clear. Combat, building, running, and route control are all part of survival. Fight when an encounter blocks a valuable objective or safe path, not merely because a target is visible.
Where can I report an enemy bug?
Use the official Discord's Bug Report or technical ticket path. Include the version, location context, trigger, expected behavior, host or guest role, and a short clip where possible.
Evidence
Sources used on this page
Primary sources lead this page. Community discussions can surface questions, but do not override a current developer or storefront statement.
GRAIN ROT on Steam ↗Release, platforms, features, requirements, media, and live pricing.Developer launch FAQ ↗Solo, player count, lobbies, saves, controllers, support, and platform plans.