GAME MECHANICS HOARD

FLOODS

Rising water as a dynamic hazard — rivers bursting banks, storms surging coastlines, dam failures — that submerges terrain, destroys structures, and reroutes play.

Cities: Skylines models water flow well enough that players build dams and accidentally drown districts, Frostpunk 2 and colony sims use floods as periodic disasters testing infrastructure, and Timberborn makes water management the entire game — droughts and floods alternate as the core threat pair. Designers use floods because water is the most legible disaster: players intuitively understand elevation, drainage, and barriers, so flood defense becomes real spatial problem-solving (build high, build walls, build overflow channels) rather than stat mitigation. Floods also audit city layout retroactively — the cheap riverside district was a loan the flood collects. Key decisions: simulated fluid flow versus scripted water levels (simulation enables creative engineering but costs performance and QA), warning time and seasonality (predictable floods reward planning; surprise floods punish), and whether floodwater recedes, leaving repairable damage, or permanently reshapes the map. Pitfall: floods in games without elevation-aware building tools — if players can't see drainage and height clearly while constructing, flood damage feels arbitrary rather than earned.

SEEN IN

VIEW “FLOODS” IN THE MAP ▶