Weather in games is usually cosmetic. Rain that doesn't affect gameplay. Snow that looks pretty. Fog that's atmospheric. Some games make weather load-bearing, and when they do, the design work is specific. This piece from the team at Tyrian Games covers how weather-as-difficulty works in games, and how HAWKER's blightstorm mechanic uses weather as a three-day escalation loop.
TL;DR
- Weather in most games is cosmetic. A small number of games make it mechanical.
- Don't Starve, Rain World, The Long Dark, and Dredge use weather as meaningful difficulty modifier.
- HAWKER uses blightstorms that recur every three days, reshaping the map and intensifying enemy behaviour.
- The three-day cadence is deliberate; it creates a rhythmic pressure beat that the player can anticipate but can't avoid.
- Weather-as-difficulty pairs well with deadline-based run structures like HAWKER's thirty-day clock.
The two kinds of weather in games
Cosmetic weather is the default. Rain falls, fog rolls in, snow accumulates. The player sees it. Nothing meaningful changes. Most open-world games use cosmetic weather, and it's fine for atmosphere.
Mechanical weather affects gameplay directly. Visibility changes. Stamina drains. Enemy behaviour shifts. Resources deplete. Specific actions become possible or impossible. The player has to plan around it.
The gap between the two is substantial. Cosmetic weather is decoration. Mechanical weather is a mechanic. Games that commit to mechanical weather tend to feel distinctly different from games that don't, and the design work required is proportionately higher.
Games that use weather mechanically
Don't Starve (Klei, 2013) has one of the most developed weather systems in indie gaming. Seasons shift the threat profile entirely. Summer brings overheating. Winter brings freezing. Rain damages items. Each season requires different preparation. Weather is the difficulty system, not an overlay on it.
Rain World (Videocult, 2017) uses rainfall cycles as a direct gameplay threat. Every cycle ends with a punishing rain that kills the player if they aren't sheltered. The player's whole day-planning revolves around timing food-gathering to end before rain.
The Long Dark (Hinterland Studio, 2017) weaponises winter weather. Blizzards obscure vision, cold drains stamina, wind chills through layers of clothing. The Canadian wilderness feels hostile partly because the weather is hostile, not just the wolves.
Dredge (Black Salt Games, 2023) uses fog and specific weather events to shape the fishing loop. Some catches only appear in certain weather. Others are dangerous in specific fog conditions. The weather is a constant strategic consideration.
Subnautica (Unknown Worlds, 2018) has less weather but uses day-night and depth-based pressure as environmental difficulty escalators. Similar design principle, different axis.
Pacific Drive (Ironwood Studios, 2024) uses anomalous weather events that escalate as the player goes deeper into the Olympic Exclusion Zone. The storms aren't just dangerous; they're plot beats.
Project Zomboid (The Indie Stone, 2013, ongoing) uses weather for survival-mechanical effect across multi-season runs.
HAWKER (Tyrian Games, September 2026) uses blightstorms that recur every three days across the thirty-day run. Details below.
What HAWKER's blightstorm actually is
The specific mechanic, for readers who want the design beats.
Recurrence. Blightstorms arrive at regular intervals: at the end of Day 3 and every third day after. Day 6, Day 9, Day 12, and so on. The player knows when they're coming.
Effect on map. The landscape reshapes after each storm. Scavenging locations that were accessible before may be buried. New locations may open. The Gwiravon players thought they knew by Day 4 isn't quite the Gwiravon they're navigating by Day 5 and beyond.
Effect on enemies. The Fallen become more dangerous after blightstorms. Existing enemies grow more aggressive. New variants may appear. The akhlotic spores released by each storm feed the blight directly.
Effect on the caravan. Caravans caught outside during a storm take wear damage. Goods exposed to the storm can be lost or damaged. Smart players return to the caravan before a storm hits, even if it costs them scavenging time.
Effect on NPCs. Some NPCs behave differently after storms. Gossip shifts. Specific characters may be absent or present depending on how the storm affected them.
The blightstorm isn't one mechanic. It's a bundle of effects that all fire on the same trigger, creating a coordinated pressure event that reshapes several game systems simultaneously.
Why three-day cadence
HAWKER's blightstorms arrive at a specific rhythm for reasons worth unpacking.
Three days is learnable. Players figure out the cadence within the first two storms. By Day 9 they're planning around it. This predictability is the thing that makes the mechanic work. An unpredictable storm would be unfair. A fully predictable storm becomes routine. Three days sits in the sweet spot.
Three days creates mini-arcs within the run. Ten three-day cycles across the thirty-day run gives the game a natural rhythmic structure. Each three-day window is a mini-mission: prepare, execute, survive. The thirty-day run becomes ten linked three-day arcs rather than one long continuous experience.
Three days matches the debt payment cadence. Ankou's first formal appearance is on Day 3, and his debt installment cycles match the three-day rhythm. The blightstorm and the debt clock reinforce each other, creating a double-beat every three days that the player can't ignore.
Three days is tunable. Longer cycles (five days, seven days) would be easier but less present. Shorter cycles (two days, every day) would be overwhelming. Three is the length we landed on through playtest iteration, and it's been stable since mid-2024.
Why weather-as-difficulty pairs with deadlines
HAWKER's thirty-day clock and blightstorm mechanic work in combination. Each reinforces the other. This is a design pattern worth flagging because it's underused outside a few specific games.
The deadline provides the primary pressure. You have thirty days to pay Ankou. That's the spine of the run.
The weather provides the secondary pressure. Every three days, the world gets harder. That's the rhythm of the run.
Together they produce specific decisions. The player can't just minmax for the thirty-day clock; they have to account for the storm cadence. They can't just ride out storms; the clock doesn't wait. The combination creates a decision-space richer than either mechanic alone.
This is why HAWKER's blightstorms recur every three days rather than randomly. The predictability lets the storm rhythm compound with the deadline rhythm. The player plans around both in combination, and the combination is what makes the game's strategic texture specific.
Common mistakes in weather-as-difficulty design
Four failure modes across the pattern.
Weather that's too random. If the player can't predict when storms will hit, they can't plan. The mechanic becomes frustrating rather than strategic. Don't Starve's seasons are predictable. Rain World's rain cycles are predictable. HAWKER's blightstorms are predictable. Predictability is part of the contract.
Weather with no effect on the shop or hub. If the weather only affects exploration, the player can hide in the hub and wait it out. HAWKER's blightstorms affect the caravan and the shop, not just the scavenging zones. The weather has to reach everywhere the player might go.
Weather that's too easy to ignore. A storm that costs 5% damage and is otherwise cosmetic isn't really difficulty weather. The effects have to be substantial enough that the player actually plans around them. HAWKER's blightstorms can genuinely compromise a run if the player ignores them.
Weather without visual signature. The player needs to see storms coming. HAWKER's blightstorms have specific sky effects, dust plumes, audio cues, and UI warnings. Weather that's only visible in the numbers doesn't feel like weather; it feels like a system.
A first-hand Hawker design note
One of the specific playtest moments that validated the blightstorm design came in mid-2025. A tester was playing defensively, rushing back to the caravan before each storm and sitting out the weather. Her approach was efficient but felt cautious.
On Day 18 she got caught outside during a storm for the first time. She was about a kilometre of in-game ground from the caravan, the storm rolled faster than she expected, and she had to make the choice: keep running and lose goods, or shelter in a ruin and lose time. She chose the ruin. The storm passed, she emerged with her cart intact, and she found a specific rare item that only spawns after blightstorms in sheltered locations.
Her post-session feedback was that the blightstorm had gone from being an inconvenience to being a mechanic she'd actively seek. Getting caught outside wasn't the failure state we'd worried it would be; it was a different mode of play with different rewards. Players who always shelter miss the post-storm scavenging window. Players who know how to survive a storm outdoors have access to content the cautious players don't.
This is the thing weather-as-difficulty can do when it's designed right. It doesn't just make the game harder. It creates alternative playstyles that reward different skills. The cautious player finishes the run on the clock. The bold player finishes the run with rare items. Both are valid. The mechanic has space for both. That's the difference between weather that adds difficulty and weather that adds design depth. We landed on the latter through playtest iteration, not theory.
How to add weather-as-difficulty to your game
Four principles for studios considering the pattern.
Design predictability into the weather. Random storms are frustrating. Scheduled storms are strategic. Tell the player when the weather is coming, even if the specific effects vary.
Make the weather affect multiple systems. Storms that only affect combat feel flat. Storms that affect shop economy, NPC behaviour, map state, and combat all at once feel significant.
Give the weather a visual and audio signature. Players should see and hear storms coming. Good audio cues are particularly important; visual cues can be missed.
Tune for compounding effects. A storm that just adds 10% damage is a multiplier. A storm that changes the map, increases enemy aggression, damages goods, shifts NPC presence, and requires specific preparation is a mechanic. The second produces more interesting play.
FAQ
What's a blightstorm in HAWKER?
A recurring weather event in HAWKER that arrives every three days, reshapes the Gwiravon landscape, intensifies enemy behaviour, damages caravans caught outside, and releases akhlotic spores that feed the blight.
How often do blightstorms happen?
Every three days. Day 3, Day 6, Day 9, and so on. The player can anticipate them.
Can you hide from a blightstorm?
Yes, in the caravan or in specific sheltered ruins. But hiding costs time, and time is the game's scarcest resource.
What games use weather mechanically?
Don't Starve, Rain World, The Long Dark, Dredge, and Pacific Drive all use weather as meaningful difficulty modifier.
Is there a reward for being out during a blightstorm?
Yes. Specific rare items spawn in sheltered locations after storms. Bold players can access content cautious players can't.
Does the weather affect the shop?
Yes. Blightstorms affect NPC behaviour and gossip in ways that ripple into the shop economy. The weather isn't just an exploration mechanic.
Spoiler wall
Everything above keeps to the demo-line weather for Hawker. Blightstorms at Day 3 and Day 6 are shown in the first seven days. Specific late-game storm variants and the post-Day 20 storm effects sit behind this wall.
Closing
Weather in games doesn't have to be cosmetic. When weather is mechanical, it creates strategic texture that pure difficulty scaling can't match. HAWKER's blightstorms are our version of the pattern, running on a three-day cadence that compounds with the thirty-day debt clock. Studios considering weather-as-difficulty have a rich design space to work in.
Next read: The light and shadow mechanic, or Night-escalation in roguelites.
Further reading
For related context see light and shadow mechanic.