Procedural Changes

This campaign introduces two formal practices not found in standard AD&D: Session Zero and The Rutter. Both are new, even to experienced players. Both ask something of the table — time, preparation, and a willingness to engage before and after the session itself. That investment does not come at the expense of the gaming session; it reduces the discursion and confusion that would otherwise consume it, leaving the time at the table freer for the warmth, interaction, and collaboration that make a campaign worth playing.

Both practices exist in service of the same principle: that the most important moments of collaboration between GM and players happen outside the fiction, not inside it. The GM may run a session with considerable opacity — withholding information, maintaining uncertainty, allowing events to unfold without commentary — and that is entirely consistent with good play. But many of the decisions that shape the campaign’s health over time are not made during play — they are made before it starts and after each session ends. Session Zero and The Rutter are where those decisions live.

Session Zero ensures that a crew begins play with shared ground: the same picture of the world, the same understanding of what the campaign will ask of them, and characters that were built together rather than imported from elsewhere. The Rutter ensures that what is decided and recorded during play is accurate and available to everyone. Together they create the transparency that good collaborative play depends on — even, and especially, when the table itself is running in a less transparent mode.

Neither practice is an imposition on the GM’s authority or on the players' freedom. They are the infrastructure that makes both more meaningful.

How does a newly-assembled crew begin play? The answers most commonly reached for are the barroom brawl — strangers thrown together by circumstance and a convenient eruption of violence — or the portal variant, where the characters find themselves outside an eldritch entrance with arcane symbols on the stonework and no explanation offered. The crew was never given a reason to exist, and the GM is improvising one at the last moment. Various solutions to this problem exist, and some work well enough. Session Zero is, in this designer’s experience, consistently the best of them — because characters built together, with shared history and agreed purpose, do not need a contrived incident to explain why they are in the same place.

The problem has a sharper form when a priest is among the crew. In a traditional AD&D game, the question of why a lawfully obligated character with divine duties and institutional allegiances would travel with a band of unaligned strangers is rarely asked, because the answer everyone accepts is that the crew needed a healer. The priest becomes portable medical equipment with a personality. In Oath-Bound that answer is unavailable — a priest carries an oath, a purpose, and obligations that do not point naturally toward wandering with whoever happened to be in the same tavern. The question has to be answered honestly, at Session Zero, before play begins. Answering it produces a richer crew and a more credible priest than the portable healing machine ever could. It was, in fact, one of the catalysts for the way the priestly system in Oath-Bound was redesigned.