WEATHER PATTERNS
Weather as a changing system over time — fronts rolling through on schedules or simulations, seasonal tendencies, forecast-able patterns that gameplay can plan against, the sky as a slow machine rather than a random skybox.
- SOLO-DEV COST MEDIUM
- TIMING REAL-TIME
- COMMON IN SIM · LIFE-SIM · SURVIVAL · RACING
Simulation-forward games run genuine meteorology (Microsoft Flight Simulator streams real-world weather; sailing games like Sailwind model wind systems worth studying), farming and life sims cycle seasonal probabilities (Stardew's rain rolls against the season's odds — and the forecast channel makes tomorrow plannable), survival games schedule weather as threat cadence (The Long Dark's blizzard rhythms; Death Stranding's timefall zones as mapped weather geography), strategy layers modify whole campaigns by season (mud seasons halting offensives in war games), and racing sims make dynamic weather mid-race the strategic wildcard (the rain that repaves the track). Designers pattern their weather — rather than purely randomizing it — because pattern is what converts weather from event into system: random rain is something that happens to the player, but patterned weather (seasonal tendencies, visible fronts, forecast mechanics) is something the player plans against, which promotes weather from atmosphere to strategy layer — the harvest scheduled before the storm season, the assault timed to the fog, the route chosen around the timefall — and planning-against-weather is a distinct gameplay pleasure (reading the sky as an opponent whose moves are probabilistic but legible). Forecasting is the mechanic's keystone: a forecast converts future weather into present information with a reliability dial (the perfect forecast makes weather a schedule; the rough one makes it risk management — the choice of forecast accuracy is really the choice of how much weather is strategy versus gamble), and diegetic forecasting (the TV channel, the sailor's warnings, the aching knee) delivers it in-world. Weather's interaction depth then determines whether patterns matter: weather that touches many systems (visibility, movement, crops, NPC behavior, combat) makes each front a game-state change worth anticipating. Key decisions: pattern legibility (seasonal structure, visible approaching fronts, forecast access — the player's planning horizon is a design parameter), simulation versus schedule versus weighted-random (simulated fronts are expensive and emergent; scheduled weather is authored pacing; weighted dice are cheap and usually enough), interaction breadth across systems, and duration/frequency tuning — weather states long enough to adapt to, varied enough that adaptation isn't a solved routine. Pitfall: weather as mood-only randomness — patterns without gameplay teeth (the rain that changes nothing but the shader) train players to ignore the sky entirely, wasting both the simulation budget and the strategic layer it could have been; the test is whether players ever check the forecast, because weather nobody plans around is a screensaver with a probability table.
SEEN IN
- MICROSOFT FLIGHT SIMULATOR
- STARDEW VALLEY
- THE LONG DARK