Introduction
The Journey rules in The One Ring RPG 2e turn a route into a sequence of choices instead of a background sentence. The Company sets a path to a known destination, assigns practical roles, and lets the Guide's Marching Tests establish where the road interrupts the plan. Journey events then target the people doing the work of travel, build Fatigue, and create short scenes that should matter when the Company finally arrives. Keep the procedure visible enough to be fair, then let the fiction do the talking.
This page is the procedure. The One Ring RPG 2e Journeys and Travel Guide explains the parts it calls on: when to use the full procedure, the travel roles, journey hazards and event results, and Fatigue rules through Load and Weariness. Use The One Ring RPG 2e Skills Guide for reading the relevant Skill from the fiction and The One Ring RPG 2e Injury and Endurance Guide for the related Load and Weariness pressure that remaining Fatigue can create.
Hot Take
The Journey Sequence works because it distributes travel spotlight without pretending the whole Company is doing the same job.
| Consequence | Caveat | Reader action |
|---|---|---|
| The Guide, Scout, Look-out, and Hunter each have a reason to matter before the destination scene begins | A single hero can hold multiple roles in a small Company, so share narration even when one sheet supplies several rolls | Before the next trip, have every player say one concrete thing their travel role is watching, carrying, finding, or planning |
If a journey feels like one person rolling TRAVEL until the map ends, the procedure has been followed but the Company has been left behind.
The Journey Sequence at a Glance
The Core Rules has three stages: set the Journey Path, make Marching Tests, and end the journey. This sequence is deliberately compact. It tells the table what must be known before travel starts, when the road has a chance to intrude, and how to turn arrival into the next scene rather than the end of the procedure.
- Set Journey Path Choose destination, route, and roles | v
- Make Marching Tests Guide places events or reaches the destination | v
- End the Journey Resolve remaining Fatigue and begin the arrival scene
For a very long itinerary (the book's threshold is more than 20 hexes), the Core Rules has the Loremaster split it into separate legs. A trip with several destinations is also a series of journeys, one per destination. That lets the Company reach a meaningful intermediate place, change the plan, and begin the next section with a new question instead of treating an entire region as one enormous roll.
Set a Path the Company Can Explain
The Company begins with a destination it can locate at least approximately. The players trace the intended route on their map; the Loremaster checks the terrain and records the corresponding path on the Journey Log. The route does not travel in a straight line just because the destination sits in that direction. Passes, bridges, fords, roads, woods, marshes, and landmarks are the reasons one path is safer, faster, or more costly than another.
| Path question | What players provide | What the Loremaster provides |
|---|---|---|
| Where are we going? | A specific destination and reason to reach it | What is known, uncertain, or urgent about it |
| How do we get there? | A route using visible landmarks and plausible crossings | Terrain facts and practical consequences before the choice is locked |
| What might change our plan? | A priority such as speed, safety, secrecy, or a needed stop | A route decision that creates a real tradeoff, not a hidden trap |
| Does the trip need a leg break? | An interest in stopping, resupplying, or changing approach | A meaningful intermediate scene or place |
The Journey Log is useful because it records the path, roles, events, and Fatigue in one place. It is not a second board game. A clear note about the route and what has happened is enough to keep the next event connected to the last one.
Assign Travel Roles Before the First Roll
Once the path is set, the Company covers the four roles: one Guide, plus at least one Hunter, Look-out, and Scout. The Guide rolls the Marching Tests; events later target the Scouts, Look-outs, or Hunters and test EXPLORE, AWARENESS, or HUNTING. Small Companies double up, and large ones can share every role except Guide. Record the assignments on the Journey Log before the first roll so responsibility is settled before an event picks a target. The hub's travel roles section covers what each role does and how to assign them well.
Use Marching Tests to Place Events
The Guide makes a Marching Test using TRAVEL as the Company sets out and after each resolved event. The Loremaster counts hexes along the Journey Path from the Company's position: on a failure, the next event is 2 hexes away in Spring or Summer and 1 hex away in Autumn or Winter; on a success, it is 3 hexes away plus 1 for each Success icon. If the count reaches or passes the destination, the Company arrives instead.
Guide makes a TRAVEL Marching Test | +-- Result reaches the destination: end the journey | +-- Result stops along the route: mark an event there | v Resolve the event, then march again
This makes the Guide important without making the Guide responsible for every travel problem. A good Marching Test can cover distance; the event procedure then turns attention to the Scout, Look-out, or Hunter who is carrying a different part of the journey.
Running a Game This Week?
The GM Session Kit - a Session Zero template, a recap format, and a pricing cheat sheet. Free, and yours the moment you ask.
No spam, unsubscribe anytime.
Resolve Events as Short Scenes
Once a Marching Test places an event, the Loremaster selects a target role with a Success Die, determines the event with a Feat die roll that depends on the region type, and has one targeted hero resolve it with the role's Skill. Up to one other hero covering the same role may support the roll. An event on a road grants the roller a bonus die, and one in hard terrain costs a die. Most event results also give every hero Fatigue. The hub's journey hazards section summarizes what each event result does and how region types and Perilous Areas change the odds.
| Event step | What it establishes | Scene question |
|---|---|---|
| Select target | Which travel responsibility is under pressure | What has put this Scout, Look-out, or Hunter in the middle of the problem? |
| Determine event | The kind of opportunity or trouble the region produces | How does this terrain make the result feel specific? |
| Resolve Skill | Whether the target handles the immediate challenge | What changes if the roll succeeds or fails? |
| Record Fatigue | The cost the whole Company carries | What will this pressure change after arrival? |
Keep an event focused. A washed-out path can ask the Scout to find a route. A distant fire can test the Look-out's warning. Scarce tracks can put the Hunter under pressure. The result should be a compact scene with a consequence that still points back at why the Company was travelling.
End the Journey and Carry Its Cost Forward
The journey ends when the Guide's Marching Test reaches the destination, or when an unexpected occurrence engages the Company in another significant activity. At arrival, heroes with a mount subtract its Vigour from their Fatigue, and then every hero can roll TRAVEL to reduce it further. Any remaining Fatigue moves from the Journey Log to the character sheets and drops by 1 point for each later Prolonged Rest in a sheltered, safe refuge. The hub's Fatigue rules section explains how that leftover Fatigue interacts with Load and Weariness.
Arrival is therefore a handoff, not a reset. If the Company arrives with remaining Fatigue, the next council, exploration, or confrontation begins with a reason to seek shelter, conserve effort, or accept a risk knowingly. If it arrives without it, the road may still have changed the Company through a discovery, a local contact, or a new worry.
Journey Length and Forced Marches
If the table wants to know how long the trip took, count the hexes on the path and add 1 day for each hard-terrain hex. A Company travelling entirely on horseback halves that total, rounding up, though riding normally needs roads or good paths. A Company can also force-march, counting one day per two hexes, at the price of 1 extra Fatigue per hero for each day of forced march.
Worked Example: The Ford Before Dusk
This is an original example. It shows the sequence without copying a Core Rules event table or using a published route.
The Company must reach a ford before dusk to warn a ferryman that riders have been seen on the north road. The players trace a route that follows a road for part of the way, then cuts through wet woodland to save time. They choose a Guide who knows the area, a Hunter to keep food available, a Look-out watching the ridge, and a Scout opening the woodland trail.
- Set the path. The players tell the Loremaster they value speed over the safer road. The Loremaster marks the woodland section and confirms that it is hard terrain. Everyone understands why the route may cost more even if it saves time.
- Make the first Marching Test. The Guide rolls TRAVEL. The result places an event in the woods rather than reaching the ford, so the Loremaster marks the point on the log.
- Select and frame the event. The event targets the Scout. The Loremaster describes floodwater hiding the old trail and asks how the Scout recognizes a crossing that will not bog down the whole Company.
- Resolve the roll. The Scout makes the required Skill roll with the one-die hard-terrain penalty. Another Scout could support if the Company had one. On a success, the Company finds a workable crossing and keeps the warning urgent; on a failure, the printed result and Fatigue apply, and the fictional cost might be lost time or waterlogged gear.
- March again. The Guide makes the next Marching Test. If the destination is reached, the group handles the arrival procedure and begins the ford scene. If another event occurs, it should follow from the changed route and the approaching dusk rather than restarting the journey from zero.
The example matters because the roles lead to different kinds of spotlight. The Guide sets progress, the Scout confronts terrain, and the whole Company decides whether saving time is still worth the fatigue and uncertainty. The road changes the warning scene before the ferryman ever appears.
Player and Loremaster Advice
Players
- State the route priority before the path is drawn: speed, safety, secrecy, supplies, or a landmark worth visiting.
- Treat a journey role as a repeated contribution you can describe out loud each time the road tests it.
- When an event selects your role, ask what the Company stands to lose or gain before rolling.
- Record the result and Fatigue promptly so the arrival scene begins from the actual journey.
Loremasters
- Let the Company see enough terrain and route information to choose deliberately.
- Frame events around the current mission, season, terrain, and preceding result.
- Use the Journey Log to preserve continuity, not to demand minute-by-minute narration.
- Start the arrival scene with a question affected by the road: who is waiting, what has changed, or whether the Company can act before resting.
Where To Go From Here
Return to the Journeys and Travel hub for the wider approach to the road. The maps guide turns a procedure into an actual route, and the Shadow and Hope hub covers what a hard road costs a hero.
Source Scope
This guide uses Chapter 6 of the Third Printing of The One Ring Core Rules. It summarizes the Journey Sequence, Marching Tests, event procedure, arrival, journey length, and forced marches without reproducing the Journey Log, maps, or event tables. The worked example is original. Consult the Core Rules for every exact result and requirement.
Return to Journeys and Travel, continue with The One Ring RPG 2e Skills Guide, or browse The One Ring RPG 2e Guide Hub.
