Let’s Talk About the GM — Trust, Influence, and the Shape of the Game

Oath-Bound is a more demanding game than vanilla AD&D — for both players and GMs — and that is not an accident. It is a deliberate consequence of how the rules are designed.

Vanilla AD&D provides extensive procedural scaffolding: tables for most situations, formulas for advancement, mechanical resolution for most uncertainties. That scaffolding is genuinely useful. It gives a new GM something to stand on while developing judgment, and it provides players with predictable resolution they can plan around. What it also does, unavoidably, is place a ceiling on what judgment can achieve — when a table lookup produces the answer, there is limited room for the GM to do something better.

Oath-Bound removes some of that scaffolding deliberately and replaces it with the expectation of considered judgment, exercised openly. Advancement is not a formula — it is a conversation at Rutter Keeping, with reasons given. The Competency Profile is not a skill list with point thresholds — it is a qualitative record adjudicated by the GM in context. The dice resolve genuine uncertainty; they do not substitute for situational assessment. In each case, the choice to reduce mechanical procedure and increase GM judgment is the same: because judgment, exercised well and transparently, produces better play than procedure alone can.

This makes Oath-Bound more demanding. It also makes it more rewarding — for a GM prepared to do the work.

The approach is not novel. Early RuneQuest built advancement around what characters actually did — skills grew from use, not from points allocated at level. Ars Magica went further, treating the covenant as the primary unit of play and magic as something embedded in social obligation rather than a personal resource to be spent. Pendragon tracked personality traits and passions as mechanical elements, making character psychology as consequential as combat capability. Each of these systems placed qualitative judgment at the center of play and reduced the role of procedure accordingly, and each produced campaigns that players remember long after they have forgotten the rules.

Oath-Bound is working in that territory.

The reduced reliance on dice is one of the most visible expressions of this design. Options are always present, and Oath-Bound encourages players to drive their gameplay toward due consideration rather than reach for a roll. The dice resolve genuine uncertainty — whether the thief picks the lock, whether the arrow finds its mark — but they are not the primary resolution mechanism for situations where the characters' preparation, knowledge, and decisions are the more meaningful factors.

For players this means the game rewards considered engagement. A crew that thinks about what they are walking into, manages its resources, and acts on what it knows will find the world responds accordingly. That is not a prescription for how to play — it is a description of what Oath-Bound is designed to support. It is a more demanding game than hack-and-slash, and a different one.

For the GM it means that more decisions land on judgment rather than on procedure. What does this character’s Competency Profile tell us about whether they can attempt this? Has this crew earned advancement through meaningful experience, or merely survived? What consequence follows honestly from what just happened? These are not questions a table can answer. A GM who engages with them seriously, and who can defend the answers at Rutter Keeping, is doing what the game asks.

It should be acknowledged honestly: GMing Oath-Bound is more difficult than running vanilla AD&D.

Running AD&D well requires genuine mastery — of the rules, the monsters, the encounter design, the management of a table, the ability to improvise within a system — and that is not a small thing. Running Oath-Bound well requires all of that and then more: judgment that can be defended in front of the table, the ability to hold the world’s internal consistency across months of play while leaving genuine room for the players to shape what happens, and the willingness to make transparent decisions about advancement, consequence, and when to put a thumb on the scale. It requires a GM who has thought seriously about what they are doing and why. Players who understand this will extend appropriate trust and patience, and a GM who is running Oath-Bound honestly — making judgment calls in the open, occasionally getting it wrong and acknowledging it — is doing something that deserves to be met with good faith.

It is also worth being direct about something that may sound unwelcoming but is simply accurate: Oath-Bound is not well suited to a novice GM. The vanilla AD&D model gives a new GM scaffolding — procedures to follow, tables to consult, a DMG that tells you what to do in most situations — and that scaffolding is genuinely helpful when you are still developing the judgment the game calls for. Oath-Bound removes some of it deliberately and replaces it with "use your judgment," which is liberating for a GM who has played enough to have developed that judgment and quietly frustrating for one who hasn’t, in ways that can be hard to diagnose.

The PHBO and DMGO exist precisely to ease this transition for a GM who knows vanilla AD&D and wants to bring that knowledge to Oath-Bound. They are a map from the familiar to the different — section by section, with the deviations explained and the reasoning given. A GM who knows 1st Edition well has a real foundation to work from, and the overlays make that foundation usable. A GM for whom vanilla AD&D is itself new is navigating without the map, which compounds the difficulty considerably. Knowing the original system first is not a requirement, but it is a significant advantage.

A new GM who wants to run Oath-Bound is not discouraged from trying, but they are better served by knowing what they are taking on. Running with an experienced player at the table who can help, seeking out a mentor who has run this kind of campaign before, or spending time as a player before stepping behind the screen are not signs of inadequacy but sensible preparation for a job that is genuinely difficult.

There is a question worth asking directly, because players who have been around long enough will ask it anyway.

Can we actually trust the GM?

Not in the abstract but in practice. We have all played in games where the GM took sides — where a favorite NPC was inexplicably difficult to kill, where the dice behind the screen produced suspiciously convenient results, where the story went where the GM had already decided it would go regardless of what the players did. Those experiences are real, and they leave a residue. A player who has been through that is not being paranoid when they wonder whether this game will be different.

The honest answer is that Oath-Bound provides structural reasons to trust the GM, and asks the GM to demonstrate the rest.

It also helps to have the right mental model for what the GM actually is. The GM in Oath-Bound is not the troll guarding the bridge of death — the impartial obstacle, the neutral arbiter of what the rules permit, the entity whose job is to make the dice mean what they mean and nothing more. That model exists and has its uses, but it is not what Oath-Bound is asking for. The GM here is more like an editor working on a collaborative manuscript than an author controlling one. The players write the characters, make the choices, and generate the material; the GM shapes what is there — finding the through-line, cutting what doesn’t serve, holding the coherence of the whole while the individual parts are being created. The difference between a good session and a great one is often invisible: the judgment of what to emphasize, when to let a moment land, when to move on. The players are not submitting work for approval but working as co-authors alongside an editorial intelligence that is present throughout, whether or not it makes itself visible.

Oath-Bound is, by design, as collaborative as a GM-led game can reasonably be. The Session Zero ceremony establishes the characters and the world together, with the GM present as a participant rather than a hidden architect revealing their creation. The Rutter — the tangible record of the campaign, updated at the ceremony that closes every session — anchors the XP award made openly, with reasons given, in front of the table. The advancement model explicitly removes the formula that allowed GMs to hide their judgment behind arithmetic, replacing it with judgment that has to be defended.

These are structural choices that make the GM’s role visible and accountable in ways the vanilla AD&D model — for all its virtues — did not. The PHB and DMG between them provided plenty of cover for a GM who wanted to control outcomes, and Oath-Bound removes some of that cover deliberately.

Session Zero and The Rutter ask something of the table before and after play — time and preparation that does not happen inside the fiction. That investment is repaid during the session itself, which runs with less discursion and confusion precisely because the agreements and records that would otherwise be improvised mid-play have already been made. They are structurally essential for a specific reason beyond efficiency: the interactions that happen in those ceremonies are between the players, not between the player characters, which is a different dynamic with a different objective. In Session Zero, the people at the table make agreements about what they are going to do together — not through their characters, not inside the fiction, but as themselves — establishing the world, the characters, the expectations, and the tone. Trust that is built there is trust between real people, and it is the foundation on which everything that follows rests. A table that skips Session Zero is trying to build collaborative trust inside the fiction that should have been built outside it first, and finding out that the fiction is not a reliable place to do that work.

The Rutter is a tangible object — the accumulated record of the campaign, session by session, owned by the table collectively. The ceremony that closes each session adds to it: the XP award, the significant events, the decisions made and their consequences. It is the evidence that choices had weight, and it keeps the people at the table honest with each other about what the game actually was rather than what anyone remembers it as.

It would be dishonest to suggest that structure alone is sufficient. Every GM-led game, including the most scrupulously run vanilla AD&D campaign, is subject to the same question. The GM knows things the players don’t and makes decisions that shape what is possible, so structure helps without resolving the underlying relationship.

Here is the thing that needs to be said plainly: the GM is not a neutral referee but the shaping intelligence of the campaign.

They make choices about what happens, what consequences flow from which actions, and what the world emphasizes or leaves in shadow. They are working with the threads of the story — the characters, the established facts, the consequences already in motion — and occasionally doing something to one of them that changes where the whole thing is going. A skilled GM does this the way a god is understood to influence fate in Oath-Bound: not by pulling hard, but by finding the thread with some natural play in it and doing something precise, so the effect is systemic while the intervention stays subtle.

A deft GM is not above putting a thumb on the scale. The question is whether they do it in service of the story — to create the conditions for something worth playing — or in service of their own preferences, their attachment to a particular outcome, or their desire to be right. The former is craft, and the latter is the thing players rightly distrust.

GMs fudge dice. This is not a confession but an observation about how experienced GMs actually run games. A result that would produce something narratively incoherent, that would end a session on a note of pure arbitrariness rather than consequence, sometimes gets quietly managed. Oath-Bound does not eliminate this, but what it does is reduce the surface area for it. Fewer decisions hang on a specific number, fewer moments require the dice to be managed, because fewer moments are defined by what the dice produce. The GM’s discretion moves to where it belongs — to judgment calls about consequence and story — and away from arithmetic outcomes that were always a fragile foundation for meaningful events.

The point of this discretion is worth stating precisely, because it is easily confused with something else. The objective is not spectacle and it is not the rule of cool — the managed result that produces a memorable moment, the dramatic beat engineered for effect. The objective is simpler and more important: a session that was worth having for the people at the table. Whether the thief picks the lock is a question the dice answer. Whether everyone — or nearly everyone — leaves the session feeling that something real happened, that their choices mattered, that the world responded honestly to what they did — that is the GM’s responsibility, and it is what the discretion is for. A GM who manages a result to serve the shared experience is doing something different in kind from one who manages it to protect their preferred story: the former is craft in service of the table, while the latter is the table in service of the GM. From the outside they can look identical; from the inside, at the table, over time, they are not.

Oath-Bound cannot make the choice of how that discretion is used. What it can do is name the thing clearly, create the structural conditions that make the good version easier and the bad version more visible, and trust the GM to understand what they are being asked to do.

There is a corollary to everything above that is worth stating plainly.

If a table finds itself at a moment where a single dice roll is the decision-point between catastrophic failure and epic success, they may have been better off not breaking into that orc lair.

The dice resolve uncertainty but do not create meaning. A session structured so that everything hangs on one number has arrived at that structure through a series of prior choices, and those choices are where the real decisions were made — or should have been. A crew that understands what it is doing, that manages its resources and thinks about what it is walking into before it walks in, does not often produce moments with that shape. When such a moment does arrive it is usually the consequence of something the crew did or did not do earlier, which is exactly where consequences belong.

This is also why the GM’s thumb on the scale is less frequently needed in an Oath-Bound campaign that is being played well. The situation has been produced by deliberate play, the dice are resolving something real, and the structural conditions that make managed outcomes tempting — the moment that feels arbitrary, the result that would be narratively incoherent — are rarer when the play that produced the situation was itself thoughtful.

The orc lair will still be there tomorrow. Sometimes the right decision is to go and find out more before going in.

Killing a character abruptly mid-campaign works in fiction where the reader is carried by other threads simultaneously. At the table, without that density and without the craft to sustain it, it usually just disappoints — the player has been developing a real understanding of this person, and then they are gone, and the story has not built toward it.

This connects to something the open-world claim obscures. AD&D games — and Oath-Bound — present themselves as open worlds where player characters are free agents who can do anything, and this is, largely, a comfortable fiction. A good GM is quietly shepherding the players between the story’s possibilities in ways that are largely invisible — making the curated feel genuinely open, keeping the boundaries from becoming walls the players run into. The skill is not in building an open world but in building one that feels open while being shaped toward something worth experiencing.

Consider what a genuinely open world would require. A player decides to mount up, hire a competent body of men-at-arms, and march south until something happens. At some point the GM is designing topography five minutes before the character arrives at it. The world was never open in that direction — it just hadn’t been tested yet — and every GM knows this. The claim is maintained because it serves the fiction, not because it is true. The honest version is simpler and more defensible: the players have meaningful choices within a space that has been thoughtfully prepared, and a skilled GM makes that space feel larger than it is, which is not a lesser achievement than a genuinely open world but in many respects a more demanding one.

Acknowledging this honestly is not a betrayal of the fiction but the basis for the trust the earlier sections described. A GM who knows they are shaping — who makes those shepherding choices deliberately and in service of the table — is doing something different from one who pretends the world is truly open and then becomes confused when the players go somewhere the story cannot follow. The former is editing in service of the story, and the latter is hoping for the best.

Trust at the Oath-Bound table is not the absence of the question but the result of the question being answered over time, by how the game is actually run.

One practical point belongs here. If a player believes the GM has put a thumb on the scale in a way that wasn’t in service of the table — that a result was managed for the wrong reasons, that the story was steered in a direction that served the GM’s preferences rather than the shared experience — the correct venue for that concern is The Rutter, not during play where the fiction absorbs everything and a player concern gets expressed through a character’s frustration, and not in the car park afterward where it becomes a grievance without a structure to receive it. The ceremony, between sessions, where the participants are the players rather than the player characters, is built for exactly this kind of conversation.

The Rutter is the accountability mechanism — where the collaborative contract is renewed, or where the table acknowledges that something needs to be discussed — and a GM who understands this welcomes that function, because a table that uses it well is one where trust can actually be built.

The Rutter is also where the GM can offer their own transparency, not as confession but as craft. A decision that looked arbitrary or convenient during play can be explained there without breaking the fiction. The characters don’t know why the merchant betrayed them, but the players can: it was his liege lord — a relationship the GM established in session two and has been tracking quietly ever since — and the betrayal was not random but the consequence of a structure the players couldn’t see yet, now made visible in the Rutter where it belongs.

This is the bidirectional nature of the ceremony. Players bring their concerns, and the GM brings their rationale. Meta-gaming observations — things that exist at the level of the story rather than the fiction, that the characters can never know but the players benefit from understanding — belong here. A GM who offers this regularly is demonstrating that the decisions were reasoned, that the world was coherent, and that the thumb on the scale was in service of something real, and that demonstration repeated across sessions is what trust is actually built from.

All of this requires something that no structure can provide: the willingness of everyone at the table — players and GM alike — to engage with criticism and challenges directly and in good faith. A Rutter where the GM becomes defensive, or where players feel they cannot raise a concern without damaging a relationship, has the structure present but not the honesty. This is mutual and needs to be named as such. Players who raise concerns passive-aggressively, who treat every judgment call as evidence of bad faith, or who use the Rutter to relitigate results they simply did not like are not engaging with the collaborative model honestly either. The ceremony works when both sides come prepared to be honest and to hear honest responses.

For the GM, this is another dimension of the difficulty described earlier. The vanilla model provides procedural cover — a GM who followed the rules correctly is hard to challenge on a result — but Oath-Bound removes that cover. Judgment calls can be questioned, and they should be, and handling that well when it happens is part of the job. The preparation to be challenged is part of the preparation to run the game.

Session Zero is the first opportunity. A GM who runs it honestly — who builds the world with the players rather than revealing it to them, who engages with the characters as collaborators rather than variables — is demonstrating something. The first entry in the Rutter is another opportunity. A GM who awards XP transparently, who can say what they saw and why it matters, who is willing to be questioned and will respond with reasons rather than authority — that GM is building the thing that structural design can only prepare the ground for.

The game works best when the players bring their most interesting characters and their genuine engagement, and the GM brings their best judgment and their honest commitment to the story that emerges rather than the story they planned. Neither side can guarantee this, but both sides have to choose it, and that is not a weakness of the model — it is what the model is for.