1. Notes

Cold Weather Checks (GFN)

Cold Weather Rules (Reisa Synthesis)

1. Core Principle

Cold is not damage.
Cold is attrition plus decision pressure.

Exposure:

  • penalizes performance

  • escalates quickly

  • kills only if ignored

This keeps winter dangerous without turning every hour into a saving throw slog.


2. Hypothermia (GFN Core, OSE-Friendly)

Trigger:
The referee calls for a hypothermia save when:

  • traveling without adequate gear

  • resting without shelter or heat

  • during storms or severe wind

  • after getting wet in cold conditions

Save: Save vs. Paralysis
Failure moves the character one step down the hypothermia track.

Hypothermia Track (unchanged, GFN)

StageConditionMechanical Effect
1Mild–1 to attack rolls and saves
2Moderate–2 to attack rolls and saves
3Severe–3 to attack rolls and saves, confusion
4Apparent DeathComatose; death imminent

Severe Hypothermia Confusion (GFN)

Roll 1d6 each hour:

  1. Burrows into snow or debris

  2. Begins undressing

  3. Incoherent, cannot communicate or cast
    4–6. Acts normally

Apparent Death

If not warmed:

  • Death occurs in 6 turns minus temperature level

  • Severe cold kills fast

This is excellent as-is. Keep it.


3. Temperature Levels (Simplified Use)

You already have five temperature levels. The key improvement is how often saves are called, not tracking every hour obsessively.

Temperature Levels

LevelDescriptorSave Frequency (No Proper Gear)
1MildNone
2Cold1 per day
3Very Cold1 per watch
4Severe Cold1 per hour
5Extreme Cold1 per turn

Proper gear pushes the save frequency one step slower.
Extreme gear may negate saves entirely unless worsened by weather.


4. Getting Wet (Keep This Rule)

This is one of the most important rules in GFN.

  • If a character gets wet in Cold or worse:

    • cold gear becomes ineffective

    • treat temperature as one level worse

  • Drying requires:

    • shelter + heat

    • or a full watch in a protected location

This rule makes rivers, snowmelt, storms, and falling through ice terrifying without adding math.


5. Climate Zones (Use as Modifiers, Not Maps)

Rather than track zones constantly, use them as background pressure.

ZoneEffect
BorealNo modifier
Tundra–1 temperature level; –2 to hypothermia saves
Polar–2 temperature levels; –4 to hypothermia saves

This stacks cleanly with weather and time of day.


6. Weather Conditions (Streamlined)

Use weather to change visibility, navigation, and risk, not damage.

Common Effects

  • Fog / Snow: visibility to encounter range

  • Storm / Blizzard: half visibility, navigation checks worsen

  • Wind / Gale: missile penalties, shelter stress

Blizzards are where:

  • sled teams matter

  • retainers matter

  • bad decisions become lethal


7. Weather Generation (Referee-Light)

Instead of rolling every sub-table every day, use this:

Daily Winter Weather (1d6)

RollResult
1–2Clear or Clouded
3Snow
4Wind + Snow
5Storm
6Blizzard

Then apply:

  • Day/Night temperature shift from your seasonal tables

  • Zone modifiers

  • Wind level only if it matters tactically

This keeps the feel of GFN without bogging play.


8. How This Integrates with Your Stages

  • Stage 1 parties fear every night

  • Stage 2 parties manage exposure and fatigue

  • Stage 3 parties can operate through storms

  • Stage 4 parties treat weather as timing pressure, not a stop sign

Cold never stops being relevant.
It just stops being the main antagonist.


9. Referee Rule of Thumb

If players ask:

“Do we need to roll for hypothermia?”

Ask instead:

  • Are they wet?

  • Are they exposed?

  • Are they pushing time?

  • Did they cheap out on gear?

If yes → roll.
If no → let the cold loom quietly.


10. Why This Works

  • Keeps GFN’s brutality

  • Respects OSE pacing

  • Rewards logistics, sled teams, and retainers

  • Makes winter a system, not a tax

If you want next, I can:

  • condense this into a one-page referee winter sheet

  • build a storm escalation table

  • or write a player-facing “Winter Kills the Careless” sidebar