Region, biome, and condition are different layers
A region entry contains a name, dominant races, a biome, and a condition-like tag. The executable condition roll does not read that tag. Instead, it starts from the region's biome and selects among dungeon conditions whose own data lists that biome. The “Rolls” row on each card is derived from that relationship. This distinction matters because a label that sounds hazardous may be flavour only, while the biome determines the real environmental pool.
Two region tags in the current table do not correspond to any condition record. The page marks them as “not a condition” rather than inventing an effect. Other tags may share a name with a condition but still are not the mechanism used by the roll. Always follow the Rolls value to the dungeon conditions page before planning a counter.
How to plan a delve from this page
- Find the destination region and read its biome.
- Use the Rolls row as the possible environmental pool.
- Open each listed condition to compare its penalty and counter requirements.
- Check the proposed party's attributes, traits, and equipment against those risks.
- Treat the region tag as descriptive unless executable evidence shows otherwise.
This process does not predict which condition a particular delve will draw. It narrows the possibilities and prevents preparation for a hazard that cannot occur in that biome. When several conditions share the pool, build for the most damaging uncovered failure or choose a balanced party that can tolerate more than one result.
What a region's dominant race means for recruiting
The Races row records the region's dominant races. It does not mean only those races can join the guild, nor does it prove that a resident race is mechanically best for the region's dungeon. Race–class efficiency comes from attribute tendencies and class weights, which are analysed on the race pages. Treat regional race data as part of the world table unless a separate mechanic explicitly uses it.
The same caution applies to theme-based assumptions. A frozen-sounding place does not automatically apply a cold penalty, and a cursed-sounding tag does not create a curse roll. The current bundle relationship shown on this page is biome to condition. If the game adds a second region-specific effect in a future patch, it needs separate evidence.
Use conditions and equipment together
Environmental preparation is a roster-and-inventory problem. The condition page explains what a hazard penalises and the counter the data exposes. Theequipment reference explains the available item system, while class and trait pages help identify heroes who can absorb or avoid the remaining risk. Do not buy an attractive item first and then search for a condition it might solve; start from the region's actual roll pool.
Evidence and version limits
The Rolls rows are derived from the current condition records, not hand-maintained prose. That keeps them aligned when a biome or condition list changes. The explanatory sections state the interpretation found in the current executable bundle, but no extracted table can guarantee the outcome of a future patch or every random delve.
Check the version shown in the header before applying the table to a saved game. Archived region pages preserve older snapshots, while current advice remains on the unprefixed URL. Use the changelog when another guide, screenshot, or memory reports a different region or condition relationship. If you can reproduce a mismatch, send the version and evidence through Contact.