Most DMs skip overland travel because it feels like dead time. "You travel for three days and arrive at the dungeon." The problem is not that travel is boring; it is that nothing is happening during it. Weather changes that.
When a blizzard hits on day two of a five-day journey, the party has to make decisions. Do they push through and risk exhaustion? Do they find shelter and lose a day? Do they burn spell slots to mitigate the cold? These are not combat encounters, but they are real gameplay with resource management and narrative stakes.
How to use a 7-day forecast
Generate the forecast before the session and write it on an index card or drop it in your VTT notes. At the start of each travel day, read the weather aloud. Keep it brief. "Day three. Heavy rain since dawn, the road is mud. Travel will be slow." Then ask what the party does.
The best weather is not extreme. A light drizzle on day one and clearing skies on day two sets a rhythm. It makes the world feel like it has its own calendar. When the storm does arrive on day four, the contrast makes it feel significant.
Climate and season pairings
Each climate behaves differently across seasons. Arctic winters are brutal with blizzards, extreme cold, and near-zero visibility. Arctic summers are surprisingly mild, with long days and cool temperatures. Desert seasons swing between scorching days and cold nights, with sandstorms more likely in spring and autumn. Coastal weather is unpredictable year-round, with fog and squalls regardless of season.
Mountain weather deserves special attention. Altitude compresses seasons. A mountain in summer can produce conditions that feel like autumn in the valleys below. Wind is almost always a factor, and precipitation tends to be heavier and more sudden.
Travel pace and encumbrance
The travel impact column gives a plain-language effect. "Difficult terrain, -25% pace" means the party covers three-quarters of their normal distance. "Halved pace" means they cover half. "No effect" means normal travel. These are guidelines, not physics simulations. Adjust based on whether the party has cold weather gear, mounts, or magical transport.
If you track rations, weather is a natural pressure valve. Rain spoils food if it is not covered. Extreme cold requires more calories. Heat demands more water. You do not need complex survival rules. Just ask "do you have the right gear for this?" and impose disadvantage or resource costs if the answer is no.
Integrating weather with random encounter tables
Weather and random encounters pair naturally because they both represent the world happening to the party rather than the party happening to the world. If a blizzard hits on day two and you have a random encounter on day three, the encounter takes place in blizzard conditions. The bandits who ambush the party are cold, visibility is low, the ground is slippery. These details cost nothing to add and make every encounter distinct.
A practical method: after generating the 7-day forecast, mark the two or three days with significant weather. Then, when a random encounter happens on one of those days, describe the conditions first and let the party react to them before the encounter develops. You might find they use the fog for cover, or the storm as a reason to approach a roadside shelter where trouble is waiting.
Weather also modulates encounter difficulty without changing the stat blocks. Fighting four bandits on a clear day is a different problem from fighting four bandits on an ice-covered mountain path in howling wind. Action economy is unchanged, but positioning, movement, and tactics shift. Use severe weather as a difficulty dial when you want a fight to feel harder without increasing monster CR.
Sharing forecasts in Roll20, Foundry, and at the table
In Roll20, paste the forecast as a handout visible to players at the start of the travel segment. In Foundry VTT, a journal entry with the 7-day table shared to players serves the same purpose. Either way, having the forecast as a player-facing document changes the dynamic: players start planning rather than reacting. They buy cold weather gear before leaving town. They pick their marching route to avoid the worst terrain. These decisions make the travel feel consequential before a single die is rolled.
For physical tables, print the forecast on a half-sheet of paper and pass it around after the party leaves the last settlement. It reads like a newspaper weather report, which is exactly the right vibe. Describe it diegetically if your setting has such things: a harbour master's tide chart, a druid's reading of the omens, a caravan driver's hard-won experience with this stretch of road.
MakeMythic battlemaps include wilderness and travel scenes (forest roads, mountain passes, river crossings, moorland) designed for precisely this kind of overland encounter. Pair the weather forecast with a matching battlemap from the shop and the random encounter becomes a scene, not just a dice roll.