Introduction
To play The One Ring Roleplaying Game Second Edition, the Loremaster presents a situation, the players say what their Player-heroes do, and everyone follows the consequences. Dice enter when uncertainty is meaningful, not when the table needs proof that a door can be opened or a friendly innkeeper can answer a reasonable question.
That procedure sounds simple because it is. The useful part is learning where the game's attention goes: scenes with a decision, journeys that change what the Company can risk, councils that make relationships matter, and Fellowship time that turns a completed adventure into a new priority. You do not need to perform Middle-earth correctly. You need to make choices as people for whom the road, home, and one another matter.

Hot Take
The One Ring runs better when players announce a goal, not a rule they hope will solve it.
"I roll Awareness" leaves the Loremaster with a number and no scene. "I want to know whether anyone has used this road since the rain began" gives the table an intention, a possible cost, and room for a consequence that changes the adventure. It also lets the Loremaster say yes without rolling when the answer is obvious.
The caveat is that players should not have to guess the one acceptable sentence. The Loremaster can ask, "What are you trying to learn?" or "What will you do if this goes badly?" Those questions are an invitation to build the scene together, and any phrasing of the answer will do. The reader action is simple: begin every significant attempt with what your hero wants and how they are pursuing it.
The Table Conversation
The Core Rules describe a session as an ongoing conversation rather than a sequence of turns. The Loremaster and players create scenes together, with Player-heroes as the protagonists.
| Step | The Loremaster does | The players do |
|---|---|---|
| Frame the scene | Describe the location, who is present, and the immediate challenge. | Listen for what the heroes can perceive and what needs a decision. |
| State an intention | Answer questions and clarify stakes. | Say what the Player-heroes want to do and how they approach it. |
| Decide on resolution | Grant an outcome when it is clear, or call for a roll when uncertainty matters. | Choose the hero best suited to act and explain support or a different approach. |
| Apply the consequence | Describe how the world reacts. | Decide what the Company now does with the new information, success, cost, or danger. |
That last step is where play lives. A roll changes the situation, and the Company chooses its next move from there.
Example: A Roadside Warning
The Loremaster says: "Rain has washed soil across the old road. Ahead, you see a broken cart and hear a horse struggling somewhere beyond the bend. Dusk is close."
The Company might respond in several valid ways:
- One hero approaches carefully, looking for signs that the cart is a trap.
- Another calls out to the unseen traveller before moving closer.
- The group leaves the road and looks for a safer approach through the trees.
- The Company decides the risk is too high and makes camp well away from the bend.
None of those choices requires a roll by default. The Loremaster first decides what is clear from the description and what each approach changes. A roll becomes useful when a hero takes a real risk, seeks information that is not available, or tries to influence someone who does not want to cooperate.
When to Roll
The core book's basic test is practical: do not roll unless an action might fail and the outcome can matter. Its common triggers give new Loremasters a dependable decision tree.
Does the hero's stated approach have a clear outcome? Yes -> Say what happens. No roll. No -> Is failure meaningful? No -> Say what happens. No roll. Yes -> Is this danger, unavailable knowledge, or an unwilling person? Yes -> Call for the relevant roll. No -> Use judgment: resolve it or call for a roll if the uncertainty changes play.
Three Reliable Triggers
| Trigger | Example | Good Loremaster question |
|---|---|---|
| Danger | A hero crosses a rotten bridge while enemies close in. | "What do you risk if this goes wrong?" |
| Unavailable knowledge | The Company tries to read a warning in old tracks after rain. | "What exactly are you hoping to learn?" |
| Manipulation | A suspicious local does not want to reveal what they saw. | "What could make this person listen or refuse?" |
The rules are not telling a Loremaster to withhold ordinary information until somebody rolls. If the Company asks a friendly guide where the road goes, answer it. If it asks an unwilling witness about something dangerous and secret, that is a scene with pressure. The difference is not whether the information is interesting; it is whether getting it involves an obstacle the Company must engage.
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.
How to Read a Result
When a roll is called for, choose the Player-hero best suited to act, determine the relevant ability, roll, and compare the result to the appropriate Target Number. A success achieves the stated goal; a failure means the goal is not achieved and the situation changes. Some procedures, such as combat and journeys, define their own results. Elsewhere, the table uses the scene's stakes to give the outcome a clear consequence.
As a rule, the Core Rules give a hero one attempt at anything resolved with a roll. For a Skill roll, the Loremaster can allow the same hero to try again with a different Skill, representing a different approach, and the hero still deals with the consequence of the first failure. That prevents the table from turning a locked question into an endless queue of identical dice rolls.
| Result | Player takeaway | Loremaster responsibility |
|---|---|---|
| Clear success | Your hero gets the intended basic result. | Show what changes and let the Company act on it. |
| Superior success | Your hero may gain a better-quality outcome under the applicable rules. | Make the added benefit concrete in the fiction. |
| Failure | The goal is not achieved as attempted. | Apply a meaningful change: time, exposure, risk, lost position, or a new complication. |
| Different approach | The Company tries another method after the first consequence. | Confirm the new Skill and approach before allowing a new roll. |
For the exact Feat Die, Success Dice, Target Number, degree-of-success, Favoured, and Ill-favoured procedures, use the Core Rules and The One Ring RPG 2e Dice Mechanics Guide. The key lesson for now is that dice resolve a meaningful question; they do not replace the question.
From Scenes to a Campaign
Individual scenes connect into the Adventuring Phase, the part of the game in which the Company follows a significant chain of events through to a resolution. The Loremaster frames scenes, and the players make detailed decisions while time is close and danger is immediate.
When that adventure concludes, the Fellowship Phase begins. Players describe where their heroes rest, what they want to do there, and which undertakings they pursue. The Loremaster listens, applies the rules, and uses the resulting choices as material for what comes next.
| Phase | Put the spotlight on | Avoid |
|---|---|---|
| Adventuring | The current challenge, immediate choices, and scenes where a result changes the Company's position. | Making every safe moment a roll or every journey day an identical scene. |
| Fellowship | Rest, recovery, undertakings, and the people or places that now matter to the Company. | Treating all downtime as a sentence that says "you recover" before the next quest arrives. |
The two phases work because they answer different questions. The Adventuring Phase asks, "What will the Company do now?" The Fellowship Phase asks, "What did that cost, and what will the Company choose to carry forward?" A good campaign lets the second answer complicate the first.
A First Session in Practice
Use this modest structure for a first session. It is not an adventure outline; it is a way to practice the loop without needing a rules lecture beforehand.
- Give the Company a local problem. Someone is late, an old route feels unsafe, a familiar place has changed, or a rumour needs checking.
- Ask why each Player-hero cares. A personal connection, duty, curiosity, or concern for a community is enough.
- Frame the first scene clearly. Name the location, who is present, and the immediate question.
- Let the players state approaches. Answer what is obvious before choosing whether a roll is needed.
- Make one meaningful consequence visible. A success opens a route; a failure costs time, alerts someone, creates risk, or changes what the Company knows.
- End with a decision. The Company chooses a route, an ally, a warning it cannot ignore, or a place to rest and return from.
This procedure teaches the game more honestly than an isolated mock combat. It shows that the Player-heroes have agency, the Loremaster has a responsive world to play, and every procedure points back to a human decision.
Where To Go From Here
Read What Is The One Ring RPG 2e? for the system's premise and group fit, use The One Ring RPG 2e Dice Mechanics Guide for exact roll procedures, and use What You Need to Play The One Ring RPG 2e to gather the first-session table kit. Return to the Getting Started hub for the published starter library, and use the Core Rules for character-sheet values and edge cases.
Source Scope
This guide uses Chapters 1 and 2 of the Third Printing of The One Ring Core Rules. It explains the table conversation, scene procedure, common reasons to roll, and campaign phases without reproducing the book's rules text, complete mechanical tables, character options, or adventure material. Refer to the Core Rules for exact roll procedures and all formal subsystems.


