(Edit: I did some changes to the original version to account for feedback I received that pointed out some inaccuracies.)
I ran The One Ring (2e) for nine sessions as Loremaster, so this is neither a first impression nor a reading review. It is an assessment of what the game actually did at the table. I wanted to like it. The books are beautiful, I bought and read all of them, the respect for Tolkien is obvious, and the ambition behind the design is real. But after sustained play, I have come to a difficult conclusion: The One Ring consistently puts mechanics before situations, and repeatedly asks the table to justify outcomes rather than discover them.
The central problem of The One Ring is that it abstracts play without simplifying it. Abstraction in a roleplaying game should reduce cognitive load while preserving meaning. Here, abstraction replaces concrete situations with layered procedures, but still leaves the GM responsible for inventing much of the meaningful fiction afterward. The result is not elegance. It is more work for less payoff.
This problem is especially visible in the Journey and Council subsystems. Journeys are presented as one of the game’s signature mechanics, but in practice they often function as a dice-driven attrition engine. You roll dice, receive fatigue, hazards, or shadow, and then invent a narrative to explain the results. There is no meaningful exploration in the sense that a hexcrawl provides it, no real discovery driven by player choice, and little sense that the road is being encountered as a place of decisions and surprises. The dice decide first, and the fiction comes afterward as explanation. If one removes the Journey subsystem and narrates travel or runs actual encounters along the road, perhaps even using an old-fashioned encounter table, the game immediately improves. That is not a minor weakness. It is a serious problem in a subsystem that should have been one of the game’s strengths.
Councils fare similarly. Instead of interaction and roleplay shaping the outcome, the system determines the structure of the scene in advance. You roll Courtesy to find out how many attempts you are allowed to make, and then speeches, songs, courtesies, or riddles become mechanical units spent to accumulate success. There is little emergence and very little organic process. The players are not persuading through force of argument or emotion so much as filling procedural slots. Because the possible outcome space is effectively defined before anyone has actually spoken, roleplay becomes ornamental. The fiction is not causing the mechanics. It is decorating them. Again, the common advice online is simply to ignore the subsystem and roleplay the scene more freely, which is not a defense of the design. It is an admission that the design does not support the experience it is trying to create as well as it should.
Combat is not as problematic as Journeys and Councils, but it is still not very satisfying. It abandons many familiar structures of traditional roleplaying combat. It does not use initiative order, it does not have a straightforward movement-plus-action structure, and it avoids concrete positioning. In principle, that should make combat simpler and faster. In practice, it does not, unless the comparison point is something like modern D&D, which is aiming low. Combat in The One Ring is more abstract than in games like Call of Cthulhu or Pendragon, but it is not easier to run. It is harder to run and harder to visualize. Players and GM alike often have a less immediate sense of what is happening in the fight, even while they are spending significant time resolving the mechanics.
One of the strangest things about this combat system is that it abandons more concrete traditional structures without gaining simplicity. In Call of Cthulhu or Pendragon, one can generally picture the fight more clearly and resolve it more quickly. In The One Ring, each exchange involves building and interpreting dice pools, remembering symbol meanings, accounting for details like the fact that an 11 on the Feat die counts as a 0 whereas a 12 is an automatic success for players, while monsters reverse that logic, checking weapon damage, interpreting special results such as Tengwar (a roll of 6 on a d6), and choosing effects from a table. The system introduces both Endurance and Wounds and layers conditional effects on top of that. Armour must be rolled to negate the effects of wounds against a target which is defined differently for player characters and monsters. All of this produces outcomes that are, in the end, fairly simple. Someone gains fatigue or suffers a wound. The procedure is elaborate, but the result is not.Much of this goes moves in the opposite direction of what I believe a combat system should provide.
It would at least be easier to defend if this complexity produced richer tactical play. But it does not, at least not enough to justify the overhead. Combat does contain tactical choices, mainly in the selection of stances and the decision to use a stance-specific action or simply attack. Yet these options are narrower, more repetitive, and more abstract than in a typical roleplaying game. There are fewer meaningful choices than in many more traditional systems, and still combat takes longer. For a game that does not want to be a D&D-style tactical combat exercise, this is a significant weakness. It takes on the burdens of abstraction and the burdens of complexity at the same time, while delivering neither speed nor clarity.
The combat system also introduces asymmetries that add complexity without adding much value. Player-heroes and adversaries do not operate through exactly the same procedures, and even small details, such as the different automatic success thresholds on the Feat die, vary depending on whether one is dealing with a hero or an adversary. These distinctions may be intended as flavour, but they are flavour that exists mainly at the mechanical level. They do not meaningfully enrich the fiction, and they do not create enough tactical or dramatic interest to justify the extra cognitive load. What they do create is more work for the GM, who has to juggle related but non-identical procedures instead of learning a single clean model of combat and applying it consistently.
This asymmetry also creates confusion in edge cases. The combat rules are clearly written for player-heroes fighting adversaries, and once one moves outside that configuration, the system has no answers. What to do if two player characters fight each other? No idea. What to do if an ally fights on the side of the player characters? This is not the largest problem in the game, but it contributes to the sense that the system is more cumbersome than it needs to be.
Another major issue is the general difficulty of rolls and the experience of incompetence that this creates. Over several sessions, it became increasingly clear that the game’s basic skill checks are often so punishing that even competent characters regularly feel ineffective. They fail often, even in situations where one would expect them to perform reasonably well. I routinely give bonus success dice to players just to manage the level of frustration.
(Update) My son pointed out to me this little paragraph in the core book:
And moreover, in The One Ring, failure too often produces only attrition: another point of fatigue, another point of shadow, a failed council, another explanation the GM has to invent to justify what the dice have decided. The game does not make characters feel challenged so much as persistently ineffective.
This ties into a broader issue, which is that The One Ring asks everyone at the table to think too much about dice. In a well-functioning RPG, dice should resolve uncertainty and then get out of the way. Here, they dominate attention. Even because given that the characters are nor particularly proficient, players will be encouraged to try to gain advantages in the roll - bonus dice from the GM, being "helped" bonuses, being "inspired" bonuses. And thus play is often drawn toward the construction of dice pools, the interpretation of symbols, the handling of exceptions, and the tracking of mechanical states. Instead of asking, “What is happening?” and “What do you do?”, the game repeatedly pushes everyone toward asking, “What do we roll now?” and “How do these results translate?” Dice are no longer servants of uncertainty. They become the object of attention. That inversion works against immersive roleplaying. In fact, my first reaction to reading the rules was that The One Ring system is what a board game designer would think an RPG is, without ever having played one. I afterwards realised that the authors' background is indeed in designing board games (some of them truly excellent classics, btw).
The usual defence from the community is to advise the Loremaster not to use the parts of the game that do not work. If you dislike Journeys, you should simplify them or skip them. If Councils feel mechanical, you should just roleplay them. If Combat feels static, you should handle it more flexibly. But this is not really a good defence. It is a concession. These are not marginal rules. They are some of the game’s signature subsystems, the very things that are supposed to distinguish it from a generic fantasy RPG. If the solution to dissatisfaction is to bypass the core mechanics, then what remains is little more than a skill-based system with Tolkien terminology attached to it. That is not flexibility. That is a tacit admission that the defining mechanics are not worth using as written.
Leaving the system aside, the game is much stronger at the level of content. The scenarios are generally good to very good. None has struck me as truly excellent, but they are consistently well made, respectful of Tolkien’s world, and often very engaging. The game’s expansions of Tolkien’s writings are usually tasteful and fitting. There is a clear affection for the source material, and when the line adds detail to Middle-earth it usually does so in a way that feels coherent. I do think there are occasional missteps. The excessive profusion of spear- and shield- maidens, for example, risks turning Éowyn from an exceptional figure into a more commonplace archetype. That feels less like worldbuilding and more like a concession to contemporary expectations. But compared to the larger strengths of the setting material, that is a secondary complaint.
The books themselves are beautiful, but beautiful in a stern way. What fails at this level is not craftsmanship, but tone. The One Ring presents Middle-earth as overwhelmingly gloomy, austere, melancholic, and weary. All of those qualities belong in Tolkien, certainly. But Tolkien’s world also contains warmth, vitality, humor, renewal, and beauty. In this game, those counterweights are largely absent. Even a map of a fertile valley in spring is rendered with taste, but in shades that feel muted and joyless.
This is what a fertile hidden valley looks like:
Character portraits almost invariably show people who look old, tired, dirty, worn, and/or ugly. An example from the same scenario:
There should absolutely be room for those things in Middle-earth, but there should not be only those things. The visual and tonal direction of the line creates a world that feels consistently diminished, as if beauty has already retreated almost everywhere.
The Hobbit starter set is an obvious exception. It lightens the tone, introduces charm and warmth, and reminds one that Middle-earth can still be a place of delight. But it does so in a way that almost feels disconnected from the rest of the line.
Outside the Shire, the game returns quickly to its habitual gloom. Even books that should have offered tonal contrast, such as material centered on the realms of the Three Rings and the Elven kingdoms, do little to challenge this mood. At times it genuinely feels like a wonder that so many Elves have not already sailed to Valinor.
And yet, despite all of this, we keep playing, and on balance we are enjoying it. One of my groups has completed four scenarios in roughly nine sessions, and we are still going. None of us likes the system very much, but we all care about Middle-earth, and that has been enough to carry the game. The setting, the scenarios, the sourcebooks, and the opportunity to explore Tolkien’s world have kept us engaged in spite of the mechanics rather than because of them.
More tellingly, the experience improved once I began working around the system. The game became better when I started forgetting the Journey and Council rules (as widely advised even by system fans in internet fora), and when I became more inventive about interpreting movement and positioning during combat while still trying to fit those interpretations loosely within the written rules. In other words, the game improved when I stopped relying on the system to do its own job.
That, in the end, is my problem with The One Ring. Middle-earth should not require this much compensation from the GM. A good roleplaying system should help bring the setting to life. It should reduce burdens, support the fiction, and make sustained play easier and richer. The One Ring too often does the opposite. It burdens the GM with interpretation, repair, and omission, while offering a great deal of thematic sincerity and relatively little practical support.
I do not think The One Ring is an incompetent game. It is clearly designed by people who care deeply about Tolkien and who understand games in a broad sense. But as a roleplaying game, it repeatedly fails to trust the actual practice of roleplaying. It feels like a system more interested in mechanically expressing themes than in helping the table generate living situations. And yet we are still playing it, and enjoying enough of it to continue. That says a great deal about the strength of Middle-earth, the quality of the scenarios, and the appeal of the line as a whole. It also says, unfortunately, that the game succeeds most when the system stops getting in the way.
TL;DR: After nine sessions, The One Ring RPG proves atmospheric and faithful to Tolkien, but its core mechanics (Journeys, Councils, and even Combat) are overly abstract, cumbersome, and often get in the way of natural roleplay—so the game works best when the GM hacks them.
Pluses
- Strong thematic fidelity to Tolkien
The setting, scenarios, and expansions show clear respect and affection for Middle-earth, creating an engaging narrative foundation. - High-quality presentation and source material
The books are beautifully produced, and the scenarios are consistently good and enjoyable to run. - Enjoyable despite its flaws
The game can still deliver a good experience, especially when the GM adapts or works around weaker systems.
Minuses
- Mechanics override fiction
Core systems (Journeys, Councils, Combat) often determine outcomes first, forcing the narrative to justify results afterward. - Complexity without payoff
The game introduces layered procedures and cognitive load without delivering corresponding depth, clarity, or speed. - Subsystems fail at their intended purpose
Signature mechanics like Journeys and Councils feel artificial and are often better ignored or replaced, undermining the game’s identity.
This was my experience as well, and likewise I dearly wanted to like the game. I even like complex games, and am not averse to heavy closed systems which dictate outcomes. But sadly, I shared your experience.
ReplyDeleteI have been going again and again through the rules, asking in dedicated fora for best practices. I do think that with a bit of work you can improve the experience. But it is far from plug and play.
Delete