The One Ring RPG 2e Loremaster Guide: Session Zero to Encounters

Introduction

The Loremaster does not compete with the Company. The job is to make Middle-earth clear enough for Player-heroes to make meaningful choices, then let the world answer those choices honestly. In practice that means presenting a concrete situation, portraying people with understandable motives, applying procedures when the outcome is uncertain, and keeping consequences around long enough for the Company to care about them.

This guide follows the order a Loremaster actually works in. It starts with session zero, where the table builds a Company and agrees on tone. Campaign design comes next, turning that Company into a local, seasonal campaign. Then it covers running sessions at the table, building the non-player characters who make places feel inhabited, and using encounter prompts, journey events, councils, and Eye Awareness to put pressure on the road.

Use The One Ring RPG 2e Guide Hub for the whole game rhythm, The One Ring RPG 2e Character Creation Guide for individual Player-heroes, The One Ring RPG 2e Fellowship Phase Guide for carrying one adventure into the next, and The One Ring RPG Council of the Wise Guide for the formal social procedure in depth.

Hot Take

Most of what makes a Loremaster good at The One Ring happens before anyone rolls: a Company with one shared reason to travel, one village that remembers them, and one Scheme that moves when they look away. Hiding a vast plot does not make Middle-earth feel large. What works is making the Company feel small in a large world and then proving, session after session, that its choices can change one corner of it. If you only adopt one rule from this guide, make it this: every adventure opens from something the Company did in the last one.

The Loremaster Is the Interface to Middle-earth

The Core Rules says the most important task of a Loremaster is to act as the interface between the players and Middle-earth. The job is to evoke the right mood, present the facts the heroes can act on, and adjudicate how people, places, danger, and consequences respond. Protecting a preferred plot from player decisions is not part of it.

The book splits the job into three roles:

The split also shows who owns what:

The Loremaster is not a neutral camera, and the role is not an author with a captive cast either. Present a world worth engaging with and let the Company show what matters inside it. The Core Rules puts it plainly: the Player-heroes are the protagonists, and their choices must always produce tangible effects in the game world.

Session Zero

A useful session zero for The One Ring makes one promise: the campaign will belong to a Company, not to a stack of unrelated character sheets or to a Loremaster plot that arrives fully armored. Build heroes, decide why they travel together, agree on the kind of pressure the table wants to face, and give the Loremaster a first situation the players can answer in more than one way.

What Session Zero Does Here

The Core Rules does not name session zero as a distinct procedure. It does ask the group to create Player-heroes, form a Company around a common cause, and set up key Company features before the first Adventuring Phase. A session zero is a practical way to make those choices on purpose and to agree on how the table will handle tone and collaboration.

Keep it grounded. The game is about people who choose to face a perilous world, often because someone or somewhere is worth protecting. You do not need a dozen pages of family trees before the first journey. You need enough common ground that the group understands why it stays together when the weather turns and the easy road ends.

Create a Company With a Reason to Travel

Chapter 3 treats Company creation as a way to wrap up a character creation session, or as a step taken right before the first Adventuring Phase. Players introduce their adventurers and decide what brought them together, and the book suggests assuming the Company has already been together for some time, united by a common cause. The formal sequence is short: choose a Patron, choose a safe haven, determine the Company's Fellowship rating, and choose Fellowship focuses. The Loremaster helps with suggestions.

Do not make the cause a contract that decides every adventure. "We keep a dangerous road open," "we seek what was lost," or "we answer threats to people who cannot answer alone" is broad enough to create choices. The Company can change its mind, take on a new responsibility, or disagree about the best response. A shared cause gives direction. It should not work like handcuffs with a tasteful crest.

Align Tone, Boundaries, and Spotlight

The One Ring can put ordinary people near danger, weariness, loss, moral pressure, and the Shadow. Decide in advance what the table wants shown closely, handled briefly, or left off-screen. This is ordinary table practice, and it leaves the game every bit as serious. It gives players what they need to take risks in good faith.

Write the answers down plainly and respect later changes. This does not need to become a committee meeting with inferior snacks. A campaign can be melancholy and still be considerate, and a player engages more honestly with a hard decision when they know the table will listen if the subject needs to change.

Choose a Starting Base and First Pressure

The Core Rules describes the safe haven as the Company's starting base of operations and its refuge for Fellowship Phases, usually the place where the Player-heroes first gathered. For Eriador it names Bree as the ideal starting choice, since the village sits where the East Road meets the North Road, and it notes that a Company can add new safe havens as it explores.

Choose a starting base that is close enough to understand and rich enough to produce a first problem: a road, a settlement, a family, a market, a local custom, or a route that matters to someone.

A good opening situation is concrete enough to understand and unfinished enough to invite action. A missing person, a dangerous road, a worried community, a disputed claim, or a strange rumor can all work if they carry a human cost and allow more than one response.

Avoid opening with a continent-spanning secret war the Company is expected to solve at once. Prepare the situation and leave the solution open. If the opening concerns a damaged bridge, the Company might investigate, seek help, take another route, protect travelers, wait for better weather, or make a new plan. Session zero has done its job when players can see the kind of choice the campaign will honor.

Agree on Table Responsibilities

The Core Rules gives players full control over what their heroes do, while the Loremaster decides how every part of the world reacts. Say that division out loud before the first scene so no one feels they need permission to pursue a reasonable idea.

This is also where you tell the players that nobody is expected to solve the Loremaster's puzzle. The Loremaster brings pressure and follows through, and the Company chooses what matters. Once both sides understand that, the first unexpected plan feels like the campaign working, and your notes survive the experience.

A 45-Minute Session Zero Agenda

This agenda is original table advice built from the Core Rules' character, Company, and Loremaster guidance.

0-10 minutes: Tone, boundaries, and desired play 10-20 minutes: Player-hero concepts and shared Company cause 20-30 minutes: Patron, safe haven, Fellowship connections 30-40 minutes: Local starting pressure and first meaningful choice 40-45 minutes: Confirm expectations and name what each player wants next

If character creation needs more time, stop before the pressure discussion and come back to it once the sheets are ready. Finishing on schedule matters less than leaving with a Company, a shared understanding, and a first question nobody has already answered for the players.

Questions to Take to the Table

Use these prompts directly or adapt them.

1. What makes your hero willing to leave a safe place and face a dangerous road?
2. What does the Company hope to protect, recover, understand, or oppose together?
3. Which scenes do you want more of, and which should be lighter or off-screen?
4. What boundary or check-in practice will help everyone stay comfortable and engaged?
5. Where does the Company begin, and why does that place matter to at least one hero?
6. Who or what in that area could ask for help, create tension, or reveal a troubling change?
7. What choice do you want the Company to face first?

The last answer need not be a grand mission. A family waiting for a traveler, a road becoming unsafe, or a rumor that makes a familiar place feel strange is enough. Start there and let the campaign earn its larger shape. Ask every player for one thing their hero protects, and use only one of those answers in the first local pressure, so the rest stay available for later.

Campaign Design

A good The One Ring campaign is a Company-centered chain of Adventuring Phases and Fellowship Phases in which a small part of Middle-earth remembers what the heroes did. Start local, make the Company care, let pressure develop, and use each return to safety to reveal the next road worth taking.

Start With the Company, Not the Plot

The Core Rules presents the Company as more than a group of hired problem-solvers: its members share a cause and a reason to carry burdens together. That is the campaign's most useful foundation. Before preparing a villain, a mystery, or a distant ruin, learn what each Player-hero is trying to protect, understand, restore, or prove.

You do not need every answer in the first session. One honest connection per Player-hero is enough. When the Company chooses a direction, note why it mattered. That note is better campaign material than a dramatic secret nobody has run into yet.

Choose a Local Campaign Frame

The Core Rules sets play in Eriador, a broad region of roads, ruins, settlements, old histories, and long empty stretches between safe places. It also says the map does not show every settlement: even sparsely populated Eriador has dozens of unmarked villages and isolated homesteads. That leaves room to create original communities and problems of your own.

Pick one frame the Company can understand before expanding outward.

Start within a journey or two of a place the Company knows. Keeping the frame local gives distance a cost, a destination a meaning, and a return home a reason to matter, and Eriador stays as wide as it ever was.

Build Pressures, Not a Script

Chapter 8 tells Loremasters not to prepare too much in advance or force a prewritten plot, and to treat each session as an episode that builds on the consequences of the ones before. It also says each Adventuring Phase should feature one or more overarching Schemes: the objectives of the Company's enemies, which give opposition a direction. The book is direct about choice as well. When the Loremaster develops options for where a situation may lead, they must be presented as viable choices, and "the last thing" a Loremaster should do is railroad the players.

The difference shows up clearly in how you write a hook:

The Core Rules does allow some scripted events, tied to a chronology or a Loremaster character's agenda. Use them to put pressure on the Company, and leave the response to the players. If the heroes take an unexpected route, let the existing motives answer their decision. The campaign stays coherent because the world has its own logic, even though no scene was written in advance.

Use the Two-Phase Campaign Rhythm

Play alternates between an Adventuring Phase and a Fellowship Phase. The Core Rules says an Adventuring Phase usually takes the largest part of a session, or even several sessions, and is followed by a Fellowship Phase in which the players narrate how their heroes rest and follow up. The Loremaster uses that handoff to make events feel connected instead of episodic.

Local pressure appears | v Adventuring Phase: pursue, travel, investigate, seek counsel, confront | v Show what changed in people, places, and routes | v Fellowship Phase: recover, grow, choose undertakings | v Turn those choices into the next local pressure

The next adventure does not have to be a direct sequel to the last. It should remember what the Company protected, ignored, promised, learned, or made worse. A rumor, a request, a new ally, a damaged route, or a worried community can carry that memory forward. Not every Fellowship choice needs to launch an expedition, either. A training effort, a renewed relationship, or a quiet recovery still tells you what deserves attention later. The table is handing you a map of its interests, so read it before drawing another ominous arrow across yours.

Make Seasons and Safe Havens Matter

The Core Rules treats time as flexible. One evening of play might cover a single day or skim over a month. Adventuring Phase scenes track time closely, a Fellowship Phase moves faster, weeks or months may pass before the next adventure, and the Yule Fellowship Phase advances the Tale of Years. Use that range so the campaign feels lived in instead of stuck in one anxious Tuesday.

Keep the record brief: a season, a place, what the Company did, and what changed. A few lines after each Fellowship Phase do more for continuity than pages of private chronology. If the players cannot see why the past matters, the record is only a filing system with nicer weather.

Keep Canon Useful Rather Than Confining

Middle-earth gives The One Ring its atmosphere: old places, long memories, ordinary people under pressure, beauty worth protecting, and danger felt before it is understood. The Core Rules offers two tools for handling canon. The first treats the stories as the accounts of an "unreliable narrator," witnesses who can be mistaken, which lets a Loremaster adjust a date or a detail. The second is "filling in the blanks": the sagas leave many places and events barely touched, and the Loremaster is free to create stories there.

The book also names consistency as the key to directing the game, and a good grasp of the source material helps with that. Consistency matters more than trivia. If a famous figure appears, give them limits, priorities, and a reason to need the Company. If an established fact needs a small change for your campaign, keep the feeling and motivation that made it matter. When unsure, ask whether a new situation respects the setting's mood and gives the Company a credible reason to act. If it does, the table can make it its own.

A Four-Arc Original Campaign Framework

Use this framework to build an original campaign. It does not reproduce a Core Rules scenario or require any particular canon character, location, or ending.

Example: a settlement's failing ferry starts as a local concern. Investigation might point to neglected repairs, a frightened ferryman, a rival toll collector, or something unnatural along the river. The Company may fix one part, promise help elsewhere, or find that safe travel has become a wider problem. At every stage, feed the result the players created into the next pressure. The ferry does not need to be part of the Dark Lord's master plan to be worth crossing a cold river for.

Campaign Preparation Checklist

Before the first Adventuring Phase, write down:

1. The Company's shared reason to travel and one personal connection for each hero.
2. One safe haven or familiar community the heroes can return to.
3. One local pressure with visible stakes and at least two viable first responses.
4. Two groups or people with different motives inside that pressure, and the Scheme that moves if nobody stops it.
5. A likely consequence for action, delay, success, and failure.
6. A short season-and-consequence record to update after each Fellowship Phase.
7. The question to ask at the end of the session: "What does the Company do next?"

That is enough to begin. Expand only when the table gives you a reason. After each Fellowship Phase, add one changed person, route, or obligation to the next adventure's opening situation, and keep returns from turning into identical comfort food.

Running Sessions at the Table

Running The One Ring means making Middle-earth clear enough for the Company to choose what it cares about, then letting those choices carry weight. The loop is simple: frame a situation, listen to the players, use the rules when uncertainty matters, show the consequence, and move to the next meaningful question.

The Core Scene Loop

The Core Rules gives a running pattern for Adventuring Phase scenes. The Loremaster frames a scene, the players decide how their heroes approach it, the table uses Action Resolution and the Loremaster describes the consequences, and the Loremaster then advances play by developing several options for where the situation could lead. Keep that order visible so a prepared idea never turns into a conclusion the players are merely asked to act out.

Frame a situation with a visible pressure | v Ask what the Company does | v Resolve only meaningful uncertainty | v Show a consequence that changes the situation | v Develop, close, or cut to the next scene

Frame from the heroes' point of view. The book suggests keeping it simple: a location, a time of day, who is present, and some detail like the weather, with more added once players start asking questions. "Rain has washed out the ford; a trader and her child are stranded on the far bank; daylight is leaving" is ready for play. "You must rescue the trader by climbing the old bridge" hands the players a solution and calls it a scene.

Choose the Right Pace

The Core Rules says a new scene can jump forward in time or move somewhere far away. If a long stretch passes, describe it as a montage. If the action moves a long way, consider the journey rules. Spend table time on the details that change choices, and players will see what matters without a speech about the campaign's theme.

When distance is dangerous or meaningful, let the road take its due through the Journey Rules Guide. When an important audience deserves formal social pressure, use the council procedure described below and the Council Rules Guide.

Make Consequences Move Play Forward

Fairness does not mean going easy. The Core Rules asks the Loremaster to give every consequence, success or failure, appropriate narrative weight. A hard result can cost time, create a new danger, change an ally's attitude, reveal inconvenient information, or force the Company to decide what it will give up. It should never quietly restore the original situation because the prepared scene needed a different answer.

The Core Rules gives the Loremaster three Risk levels for Skill rolls: Standard, Hazardous, and Foolish. A Standard failure can be a simple failure or, at the Loremaster's discretion, a success with woe, while failing a Hazardous or Foolish action brings serious or grievous consequences. When setting a risk above Standard, the book says the Loremaster should always warn the players and describe what makes the action dangerous. That warning gives players what they need to choose bravely, cautiously, or differently. Consult the Core Rules for the full action-resolution and risk-level rules.

A Practical Preparation Loop

Before each session, prepare the situation and leave its conclusion open.

1. Name one local pressure that cannot be ignored forever.
2. Identify two or three people or groups with understandable, different priorities.
3. Decide what the Company can learn right away and what stays uncertain.
4. Prepare a few likely consequences for action, delay, failure, or unexpected help.
5. End the session by noting what changed and which question the Company now owns.

That is enough structure to improvise fairly. If players take a route you did not expect, go back to motives, geography, and consequences, and resist forcing the prepared scene to reappear in a different costume.

A First-Session Checklist

Use this before introducing the first pressure.

1. Confirm the Company's shared reason to be together and one thing it wants to protect.
2. Restate the tone, the boundaries, and the role of player choice from session zero.
3. Prepare one local problem with visible human stakes.
4. Name two or three viable responses without ranking them.
5. Decide what failure, delay, or success will change.
6. Keep one relevant procedure ready, but do not force it into a scene that does not need it.
7. End by asking what the Company will do next, and use that answer to prepare the following situation.

The last item is the whole campaign in miniature. The Company tells you what matters, you make the world answer, and then it tells you what matters next.

A Worked Opening Scene

This original example uses the scene loop without recreating a published adventure.

The Company reaches a small settlement before a hard rain. A local healer asks for help: a messenger carrying medicine has not come back from the nearby ford, and a worried family wants to search before nightfall. The Loremaster describes what the heroes can see and hear, then offers no preferred route.

If the heroes find the messenger, the medicine arrives, but the flood may have damaged the road. If they are slow, the messenger might still be alive but stranded somewhere else, which creates a new decision instead of a closed door. If they uncover another cause for the disappearance, that becomes the next pressure. The Loremaster prepared people, weather, and consequences, and left the answer to the table.

NPC Creation for Loremaster Characters

A useful non-player character makes the present scene clearer. The Core Rules calls Loremaster characters the best tool for a believable setting: the crowd of extras in a village, the people met more than once, and the famous figures of the stories. Most of them need a practical role, a recognizable detail, a reason to care, and a limit that leaves the Company with real work to do.

Build the Character for the Scene

The Core Rules says a Loremaster character usually needs just a name, a short description, and an idea of the purpose they serve in the current scene. Begin with the scene's question, then give the person a role that sharpens it.

Do not decide the character's final effect on the story before the conversation begins. Decide what they know, want, fear, and can reasonably offer. The Player-heroes decide whether it becomes an alliance, a misunderstanding, a bargain, or a problem for another day.

Use an Occupation and Distinctive Features

When a character needs more depth, the Core Rules has the Loremaster choose an occupation or field of expertise and add one or two Distinctive Features, picked from the heroes' list or invented on the spot. The book's own examples are short phrases, such as a "grim-faced, keen-eyed guard." A precise practical detail is easier to remember and play than a long private history. The book also suggests keeping a list of culture-appropriate names ready, drawn from the Heroic Cultures chapter, so you are not caught out when a player asks who someone is.

Choose details that can change the fiction. "Kind" gives a direction, but "kind to every hungry traveler and ashamed that the storehouse is running low" gives the table something to discover. A detail should suggest how the person speaks, what they notice, or where their help ends.

Give Every Character a Useful Pressure

A character becomes active when they want something the current situation complicates. That does not require a secret betrayal. Ordinary obligations often pull harder: protect a household, keep a promise, avoid public shame, save a livelihood, or stop someone else from taking a dangerous risk.

Avoid making every stranger a hidden servant of the Shadow. A worried host, a stubborn local leader, or a cautious guide can push back hard without being a villain. Save darker explanations for when the evidence and the Company's choices make them worth revealing.

Know When Rules Matter

The Core Rules says most interactions with Loremaster characters need no dice: natural conversation and knowledge of the setting are enough. When they are not, use the normal Action Resolution rules and treat the character as either an obstacle or a source of help.

This keeps the focus on the Company's choices, and conversations stay conversations. If a person's cooperation follows naturally from their motive, let it happen. If the action carries real cost or uncertainty, let the rules make that pressure visible. Before violence starts, give the table one last clear chance to change course.

Build Recurring Characters From Consequences

Recurring characters should remember what happened. They do not need a bigger backstory each time they return. They need a changed attitude, a new need, or a different bargaining position because the Company mattered to them.

Feed these changes into the campaign rhythm. A familiar face should not return on a schedule. Bring them back because the world and the relationship have changed.

A Worked Original NPC

Use this example as a method. It is not a profile to drop into a published setting.

Mara is ready because she gives the first scene something to act on. You do not need to decide whether the lights are bandits, a natural hazard, or something stranger until the Company gives that question weight. If Mara returns, start from the result: does she trust the heroes, regret the warning, owe them a favor, or fear what their inquiry uncovered?

A Fast NPC Checklist

Before play, write one line for each answer.

1. What is this person's role in the current scene?
2. What occupation or expertise makes them credible here?
3. Which one or two details will the table remember?
4. What do they want from the Company or the situation?
5. What do they fear, protect, or refuse to risk?
6. What help, resistance, or information can they provide?
7. Why must the Player-heroes still make the consequential decision or take the risk?

That is enough. Add a name when the character enters play, and make a note after the scene only if the Company changed the relationship. A good target before a session is three people, each with an occupation, two details, a current want, and one limit.

Encounter Tables and Journey Events

An encounter prompt should do more than drop random trouble on the Company. Its job is to ask a useful question: what does this place demand of these travelers now, and how will their answer change the road ahead? The Core Rules supplies one real table for this, the journey events procedure, and two related tools, councils and Eye Awareness. Everything else here is original preparation built around them.

What an Encounter Framework Is For

Chapter 6 gives journeys a procedure for placing and resolving events. Chapter 8 asks the Loremaster to frame scenes from clear ingredients and let the Company make real decisions. An original encounter framework can support both jobs as long as it produces a situation and leaves the conclusion open.

The framework supplies pressure and an opening image, and the Company supplies the direction. If a prompt cannot change what the heroes know, value, risk, or choose, it is probably scenery.

How the Core Journey Event Procedure Works

The Core Rules places events along the route with Marching Tests. The Guide rolls TRAVEL, and the result says how many hexes ahead the next event occurs: on a failure, 2 hexes in spring and summer or 1 in autumn and winter; on a success, 3 hexes plus 1 for each Success icon. After each event, the Guide rolls again.

Each event then follows three steps:

The table's results run from Terrible Misfortune (a failed roll leaves the target Wounded) through Despair, Ill Choices, and Mishap, to Short Cut, Chance-meeting, and Joyful Sight (a success restores 1 Hope to everyone). Every event also gives each member of the Company some Fatigue, from none on Joyful Sight to 3 on Terrible Misfortune. A Chance-meeting is the one entry that asks the Loremaster to improvise an encounter that helps the Company, and the book suggests it can be a bigger moment, such as meeting a Patron.

The Core Rules also asks the Loremaster to describe each event as a short scene that fits the current situation and links the road to the wider story. That is where original prompts help. Consult the Core Rules and the Journey Rules Guide for the full table and consequences.

Start With Place and Pressure

Begin with the part of the world the Company is actually crossing or visiting. A similar event means different things on an open road, at a settled crossing, beside a ruin, or near a safe haven.

Name the immediate pressure before choosing a procedure. A blocked road might call for a conversation, practical problem-solving, a journey event, or just a hard decision. Let the rules settle the uncertain part and leave the fiction to explain why it matters.

Use Roles Without Reducing People to Rolls

Because journey events target the Scouts, Look-outs, or Hunters, each event gives one role a moment in the spotlight. Treat that as an invitation, and avoid turning every encounter into a single-skill gate. Let the targeted hero lead, and let the rest of the Company ask questions, support, try another approach, or accept a different cost.

When someone helps, make their contribution visible in the description. An encounter sticks when the Company sees its roles working together, and players stay engaged when they are not watching one person roll.

Four Original Encounter Frameworks

Choose one that suits the current place, or roll a d4 if surprise would help. These are original prompts. They do not replace the Journey Events table.

When one of these needs a person to carry the pressure into later sessions, build them with the NPC checklist. Do not prewrite the answer. Note only what changes if the Company investigates, delays, helps, or walks away.

Turn a Result Into a Scene

Whether an event comes from the journey table, a prepared prompt, or a spontaneous idea, turn it into play with a short sequence.

1. Show the physical sign first: smoke, a broken wheel, silence in a village, a light where none should be, or tracks in rain-soft ground.
2. State enough pressure that the Company can ask useful questions and choose an approach.
3. Put the targeted role or a relevant person in the first spotlight, then ask what the others do.
4. Use Action Resolution only when the outcome is uncertain and the difference will matter.
5. Describe the cost, discovery, delay, help, or danger that follows, then ask the next meaningful question.

The sequence keeps a random result from feeling arbitrary. A hard event can still feel fair when players understand what they are responding to and what is at stake.

When to Choose Instead of Roll

Rolls create surprise, but outside the journey procedure a Loremaster can simply choose an encounter when it follows from earlier play. Choosing works best when the Company has ignored a warning, made a promise, built a relationship, or entered a place where a specific pressure already makes sense.

Never use randomness to erase a meaningful choice the players already made. Use it to discover how the world pushes back, offers help, or reveals a new cost.

Councils: When a Conversation Becomes a Procedure

The Core Rules reserves the council rules for social events of extraordinary importance: formal gatherings with high stakes, where the Company can win or lose something valuable. Everyday exchanges with Loremaster characters use ordinary Skill rolls instead.

As an encounter tool, a council works best when earlier play has set it up: a Patron's request, a community the Company helped or offended, or a promise that needs honoring. A disaster can make the heroes look like a threat to their hosts, which makes a strong opening for the next pressure.

Eye Awareness and Revelation Episodes

Eye Awareness is how the Core Rules tracks the Enemy's attention on the Company during an Adventuring Phase. The book suggests it suits groups that have already played for a few years of game time, since it adds complexity not every table wants.

A Revelation episode should make the Company's situation worse in a way that grows out of what is already happening. The book rules out attacks from nowhere, and it asks for a hint of something dark at work: a malicious misfortune, strange behavior from people or beasts, or a faint trace of sorcery. Its examples include spoiled provisions, a companion getting separated, a contact who fails to show, and a council whose request suddenly counts as one step harder. If the current scene offers nothing that fits, the Loremaster can hold the episode for a better moment, even the next session. Used that way, Eye Awareness produces the same kind of encounter this section has been describing, only with the Shadow behind it.

A Fast Encounter Preparation Checklist

Before a journey or exploration scene, prepare three short prompts: one road pressure, one human pressure, and one discovery pressure.

1. Write down the current place and one visible physical sign.
2. Tie each prompt to time, safety, trust, resources, or a promise.
3. Choose one person, Company role, or local fact that can matter first.
4. Note two plausible directions the Company might take.
5. Decide how action, delay, and refusal each change the situation.
6. Check the region type and the Company's Eye Awareness if you use those rules.
7. Cut any prompt that exists only to force a fight or deliver a prewritten answer.

You may never use all three, and that is fine. Good preparation gives you material to respond with. The players should never feel they have to get through it.

Where To Go From Here

Build the trouble waiting at the end of the road with the Combat and Adversaries hub, get the Company there using the Journeys and Travel hub, and ground it all in the Setting and Lore hub.

Source Scope

This guide uses Chapters 1, 3, 6, 7, 8, and 9 of the Third Printing of The One Ring Core Rules: the Prologue's summary of the two phases, Company creation (Patron, safe haven, Fellowship), the Adventuring Phases chapter's council and journey procedures, Fellowship timing, the Loremaster chapter (scene framing, the Director, Referee, and Narrator roles, canon, Risk levels, Loremaster characters, Eye Awareness, and Revelation episodes), and Eriador's playable scope. It summarizes these rules without reproducing rule text, full tables, setting entries, maps, or scenarios. The Core Rules has no separate session zero subsystem. The session zero agenda, campaign framework, encounter frameworks, worked examples, and checklists are original.

Return to The One Ring RPG 2e Guide Hub or browse The One Ring RPG Guides.