Weather

Owns a current weather state, and sometimes a forecast, drawn each day or interval from season-dependent probabilities or evolved as a Markov chain or noise field across the map. The state sets modifiers other systems read: rain waters crops or puts out fire, storms bring lightning that damages things, cold lowers body temperature, wind changes travel or spread, and fog cuts visibility. Stardew Valley picks daily weather, shows tomorrow's forecast on the TV, never rains in winter without a Rain Totem, and lets lightning destroy crops unless lightning rods intercept it; The Long Dark's blizzards and cold nights drive its survival loop; Microsoft Flight Simulator 2020 can stream real-world weather. Inputs are season, location, and random draws; outputs are condition flags and values such as temperature and wind.

Adapting plans to conditions outside the player's control. The player checks the forecast, moves tasks indoors on stormy days, waits out a blizzard, or takes advantage of rain. Weather makes days feel different and gives the world a mood.

• set of weather states and their transition probabilities by season and region
• duration and spatial extent of weather events
• which systems each state modifies and by how much
• forecast availability and accuracy
• protection tools: shelter, lightning rods, clothing, irrigation

• Purely cosmetic weather costs effects budget without changing decisions.
• Severe weather with no forecast or counterplay feels like an unfair random penalty.
• Weather rolled independently each day can flip implausibly between extremes.

• Weather couples many systems at once: crops, fire, travel, mood, and body temperature.
• Forecasts turn weather from noise into a planning input, rewarding flexible schedules.
• Rare extreme weather becomes a memorable event that players prepare for.

• Can learned global weather models supply spatially coherent, plausible weather for procedural worlds at low runtime cost?