8
Mapped Biomes
Use boss relations now when planning the next route segment.
Use Saros Biomes when you need to know what overlaps in the same run segment: boss order, resource pressure, collectible cleanup and route status. Avoid fixed room assumptions while procedural layouts remain uncertain.
Mapped Biomes
Use boss relations now when planning the next route segment.
Resource Caps
Track Halcyon signals, but wait on full cap proof.
Route Depth
Use the shared biome command board until each biome has enough proof for deeper routing.
Prophet route. Halcyon finite cap has a public example signal, but avoid fixed map claims until routes are verified.
Bastion route. Use the biome link to prepare survivability and weapon comfort before the second main wall.
Rhabdom route. Resource and collectible counts need verification.
Legion route. Public sources suggest longer pathing; exact room rules need testing.
Architect route. Keep spoiler-sensitive details behind expandable cards.
Shepherd route. Relationship hub data is stronger than map data right now.
Priestess route. Exact collectible and Halcyon counts remain testing fields.
King route. Treat final-biome information as spoiler-sensitive.
| Boss | Map each biome to its Overlord. | media verified |
|---|---|---|
| Resources | Track known Halcyon/resource signals only. | mixed |
| Routes | Avoid fixed room maps until verified. | needs testing |
When release, platform or named-system facts conflict, trust PlayStation, Housemarque and PlayStation Store before any rumor.
Treat launch-week route advice as a starting read, not a permanent order. Exact values need screenshots, direct play or repeatable proof.
For procedural or randomized systems, plan around behavior. Do not bet a run on fixed maps, caps or drop tables that have not been proven.
Exact biome resource caps
Room-level route screenshots
Collectible counts by biome
Late-biome cleanup order
No. Use Saros Wiki&Tools for route decisions, risk calls and cleanup planning. Use PlayStation, Housemarque and PlayStation Store when you need official release, platform or edition facts.
Because weak certainty wastes runs. If exact node costs, collectible counts, spawn rules or boss attacks are not proven, the safer move is to mark the risk instead of pretending the number is final.
Only after each biome has enough verified depth. Thin biome pages with repeated warnings are worse than one dense command board.
That is the current working structure. Boss order and biome relation are strong enough for prep even when room layouts stay procedural.
No. Do not treat procedural spaces as fixed maps. Focus on boss relation, resource signals and route-safe notes.
Because biomes connect those systems. It is the fastest way to see which boss, resource and collectible pressure overlaps in the same run segment.