About This Journey Tool
Travel in a heroic tale should feel uncertain. A party may begin with hope, yet weather, fear, hunger, and bad choices change the road. This calculator helps a Loremaster plan that pressure without stopping the story.
It does not replace judgment. It turns distance, terrain, season, threat, and company skill into a clear event estimate. The result gives a hazard score, likely events, travel days, and a fatigue warning. You can adjust values until the journey feels right for the table.
Why Events Matter
Journey events create drama between safe places. They may reveal a lost track, a hard climb, a hostile watcher, or a moment of wonder. Good events do more than punish. They show the land, test roles, and give players choices.
Long routes should not always be worse than short routes. A safe road with inns may be kinder than a short pass in winter. For that reason, the calculator uses both distance and danger. It also rewards preparation, mounts, and strong role coverage.
Reading The Result
The hazard score is the main guide. Low scores suggest a calm road. Medium scores suggest one problem. High scores suggest several hard scenes. Very high scores warn that the route may deserve extra planning or a safer alternative.
Expected events are rounded for table use. Use the exact value for planning. Use the suggested count during play. A value near two means the road can carry two meaningful incidents. A value under one may only need a short complication.
Design Notes
The tool is intentionally adjustable. Every table handles travel differently. You can raise the region threat for darker lands. You can lower it when the company uses known roads. You can increase preparation after good scouting, maps, songs, or local help.
The fatigue estimate is also a guide. It combines event pressure with harsh conditions. It is useful for pacing. It tells you when the journey should feel heavy, even before combat begins.
Use the export buttons after calculating. The CSV file helps compare routes. The PDF note helps keep a quick planning record for the session.
Share both files between sessions. Keep hidden notes for later review. Update values when the story changes.