The
Delvers of Dàrkmesa campaign rules represent the culmination of my ten years exploring the theory and spirit of tabletop roleplaying games in the vein of Dungeons & Dragons.
This project began in 2008 in the wake of D&D 4th Edition. But that inflection point needs some context.
I had been playing D&D since 2003, when a new friend gave me a copy of the 3rd Edition D&D Player's Handbook, having recently upgraded to 3.5 himself. I read every word in that handbook one thousand times over. I was running games of 3.5 for my friends soon after, and quickly settled into a nice groove: each campaign I tried to run would last three to four sessions, only to spiral out of control due to my lack of experience.
In my heart, I usually blamed the players for how things would fall apart. I had played the epic campaigns through in my head, and tried to run them all to that end. Didn't they know that Tolkien-level excitement and wonder awaited them, if they could just go along with the story? They never seemed to march to the tune, despite their best efforts. Luckily, we were young, and all still in school in our home town. Starting a new game every month was never an issue. I had a million tired fantasy tropes that I yearned to emulate at the table, and a good handful of friends more than willing to indulge me.
I never admitted that I blamed them, and that was good, because it was my fault and I didn't know it. I didn't know that the stories I liked to read and write were not the ones I liked to play in or run. I couldn't see that my campaigns as conceived were little more than setting and stage direction. It was truly the bliss (or perhaps, frustration) of ignorance.
You see, the friend that introduced me to D&D was the first person I ever met who played. That made me the second person I ever knew who played. Each of my other friends who I invited to play then became the third, fourth, fifth, and so on. We were making it up as we went. Sure, we were using the rules. But the rules don't tell you how to play. Not really. And back then, it was faster to walk to the library and check-out a Dragonlance novel than to look up anything online. How other people played was a complete mystery to all of us.
Around 2007, the older cousin of a friend of mine came to town. His name was (is) Nick, and besides being a math genius, he was also an avid player of 2nd edition D&D. Once he found out his little cousin and co were all playing D&D on the weekends, he offered to run a (3.5 converted) game of Ravenloft for seven or eight of us.
That was good D&D. I played a monk, which was a terrible class in 3.5. But the D&D was good, so I had fun.
Then we went back to playing our own games (which I ran), and they sucked again. I would often pine away in my memory for the details of that game, searching for its secret sauce.
In 2008, 4th edition D&D is released, and for the first time, the veil of design is peeled back for me. The deliberate ways that the game was laid out and organized, the brutal crackdown on the numbers, the every inch regulated and standardized.
D&D it was not. My friends all lamented the
something that was lost in translation. I maintained always that I loved 4th edition, but found it rather hard to express precisely
why in the language of fun. In my eyes, 4th edition was designed to a very specific end: tactical combat play. In that, it succeeded. It was designed to be learned quickly. Again, it succeeded there. It was designed to look modern and aesthetically consistent. A+ again. It was the right product, but for the wrong market.
So my theory crafting and homebrewing began. "There must be a way," I thought, "to bring the principles of design from 4th edition
into 3.5 such that we can play a superior hybrid game."
It should be said: 3.5 was universally regarded as broken by 2008. How broken exactly was up for debate, but the sheer lack of direction for the design of the game and its splat books was becoming a malignant issue. There was too much game, and no central idea to measure each component's worth and validity against. One of the primary draws to a new game from the player's perspective was the chance to try out new classes and options. But from the other side of the table, every new feature was a chance to break the game.
Notebook after notebook did I fill with my Frankenstein D&D hacks. If I recall correctly, the first things I ever scribbled house rules about were skills and feats. Did we really need over 36 skills? And who knows how many hundred feats? Do those options really enrich
play, or do they just tickle the fancy of min/maxers?
By 2009, my family had DSL and I had my own laptop for school. So I decided to start Googling these questions and delving for answers in the dark halls of the interweb.
What I discovered was called the Old School Renaissance. It had begun around 2006 or 2007, as best I can tell, with some bloggers connecting on various forums and posts. They shared ideas from their history with the game, which stretched back to its very beginnings, and even before. They knew the old rulesets weren't perfect, and offered their solutions to the age-old problems. There was debate and proselytism among great grognard philosophers, and countless quiet members of the community, like me, just trying to absorb it all.
These champions of the old school tore my fragile conceptions about D&D apart, like the Twelve prophets of the Hebrew Bible chastising Israel. What was this game I had been playing all these years? Where had it come from, and what great pillars of its history had been lost to its many transmutations? Had we taken the wisdom of its forefathers for granted? Nowhere else have I seen such thoughtful effort by people to justify their ideas about a hobby and its function. While everyone else spent three years learning Pathfinder, I was mesmerized by the mysteries of OSR games.
If this era (c. 2006-2011) was indeed the Old School "Renaissance," then what happened in 2012 was the Old School "Industrial Revolution." In January, Wizards of the Coast announced that the short-lived 4th edition would soon be replaced by a new D&D, "D&D Next." In May, they began a massive open playtest of the rules they were working on.
The forums that existed on the old WotC website containing all of the playtest feedback and discussion were truly a treasure of knowledge and design theory. I was well into my obsession with writing a better ruleset by 2012, and I consider myself extremely lucky to have had the chance to explore those million musings before they were archived later that year.
For two years, there seemed to be no word of the next D&D, but my mind never stopped swirling around the problems the OSR had illuminated. As I got further into college, time for playing the game became scarce, but my interest in thinking about it only grew. The homebrews I made became smaller and simpler. There were fewer and fewer rules each time I would revise or start again. I was getting better at the design, but deep down I still didn't understand what I wanted. I was designing for better design's sake, but not for the sake of better play. Indeed, most of my homebrews never saw the light of day. The ones I did test largely felt like playing any other ruleset.
It doesn't matter much what font you write the stage directions in, turns out.
In 2014, D&D 5 came out, and my friends loved it. It was the greatest thing since sliced bread, fixing all the problems with 3.5, but still holding onto that
something that 4 had abandoned.
But when I looked at it, I was disappointed. Sure, advantage/disadvantage is a great mechanic. And yeah, the monk is way better now. And oh hey, they are consciously keeping the official splat books and feats and skills and classes under control. All good things, no doubt, for those of us content with the quality of play we had achieved throughout the years. But D&D 5 didn't do what I desperately wanted it to do.
It didn't show me how to design toward something. D&D 5 is the everyman's game. It's a story game, it's a tactical combat game, it's epic high fantasy, it's gritty low fantasy. It's everything, and nothing. At the table, it feels just like 3.5 did when my friends and I couldn't yet afford the extra books.
Fast-forward another year, and Critical Role is D&D's technological revolution. D&D is sexy now, and it rivals the best TV shows for hours of content and number of dedicated fans. Like all instances of celebrity art, Critical Role is at first inspiring, and then soul crushing. Inspiring because it shows you what tabletop RPGs can deliver, and soul crushing because I am not friends with a cadre of professional voice actors who want nothing more than to practice their acting around my narrative, with some combat thrown in to spice things up. It isn't just an unattainable ideal, it may actually be an un-approachable ideal depending on the friends you have.
A cursory scan of D&D subreddits these days will show you the Critical Role heartbreak phenomenon writ large. DMs are afraid to let their players fail. They're afraid to change the plans they have for their narrative in response to what the players do. They hand their players stage directions, and instead of amazing voice actors and improv artists, it turns out their players are just regular people. The story-based D&D facade all comes crashing down when you try to fit it into the real context that the game has in our lives. A weekly hobby for a handful of non-writers and non-actors with shifting schedules and more important things to remember than the evil motivations of the Demon Vicar of Nowheresville in your tabletop soap opera guest-starring the player characters.
But even a few years into playing and DMing 5e, I still maintained that top-down DM fiat narrative was a viable play strategy. And it wasn't until a little later, when one of my close friends ran a short-lived game in which I played, that the final trigger for my OSR metamorphosis would occur.
The setup was this: the party (which had several new members) were asked to convene at an inn to receive a quest from an NPC. We did, and the NPC told us how to get to a mythic dungeon full of (literally) civilizations worth of treasure. If we do it, the NPC gets to keep whatever scrolls and spellbooks we find in the loot. My guy is a fighter, so that is fine with me.
The party leaves for the dungeon, which is in the center of a crazy necrotic swamp that has emerged around it because the dungeon is the fossilized remains of an ancient dragon god (cool) which is causing the land to transform as it decays (super cool). When we arrive, there is a crew of evil dudes camping around the dungeon entrance, which we battle and defeat in a fight (sweet). Then, upon entering the dungeon, we find out that all of the treasure has already been looted and thrown through a portal into the plane of Limbo (...what?).
Now, from my friend's perspective, he was offering the potential for a sweet adventure on a rarely-explored plane of existence. And had that been the hook for the adventure from the beginning, I would have been more than excited.
But from my perspective, my character's motivation to adventure had been flushed down the drain. That might not be so bad (hey, things don't always turn out the way your character wants), but my poor dwarf was also
trapped by the swamp. I tried to make a choice about what adventure my character would pursue, and then when that was turned on its head, I was denied a second choice. Not only was the original intent of the adventure no longer an option, but if my character jumped through that portal, there was literally no way for me to control whether I could turn back. No way for me to make an actual
choice.
I was outraged after the fact, and it surprised me! This was no different than a hundred other times that one of my friends or I had weaved a D&D web around our players to get them to do what we wanted. The difference this time was how obvious it was to me given the mindset that I was in. I didn't blame my friend, I blamed our collective understanding of the game.
The swamp was not an obstacle to the treasure, because the treasure wasn't there anymore. The swamp was an obstacle to beginning the adventure, or any other adventure for that matter, if the party had changed its mind. The dungeon was the single source of player-DM agreement ahead of time, and it was thrown out. The foundational structure of the game, that there was a treasure to be had if some obstacles were overcome, was abandoned for the sake of an unsure reward (the treasure was in
Limbo, after all) after an indeterminate amount of time and obstacles.
The contract of the game was broken, I was mad, and that was the answer I had always been looking for. What was the contract that my games should make between the DM and the players? Whatever that contract, design the game toward it.
D&D 5 makes no contracts. All forms of play are equally valid, and therefore there can be no measure of what games succeed or fail except on the scale of fun. This makes DMing, and DM prep especially, a nightmare of guesswork no matter how many books or tips or tools you have. What type of game will be fulfilling? What type of game will last? How do I get the
players to ask about
my availability to play rather than trying to chase them?
Well what if, given the wealth of OSR knowledge that I had absorbed, I made the contract of my campaign specific in the way that is time tested:
In this campaign, the player characters will explore a megadungeon for treasure. They will frequently return to the outlying town or towns to restock and rest, and may occasionally pursue non-dungeon adventures when the desire strikes them. New players and characters can come in or be swapped in at any point while the party is in town. No individual player needs to attend every session because no individual character needs to be on any given delve.
I, the DM, promise to prepare for that. The players promise to bring characters that will eagerly pursue that cadence of play. It doesn't create any unspoken requirements to attend every session for the sake of keeping in the loop of the plot. It doesn't mislead players as to what they will be doing. And most importantly, it takes a hard line on the boundaries of the play area, but within that play area, there is real choice with real consequence. No Quantum Ogre, no DM fiat.
And so, if I designed a ruleset around that contract, and DMed the game around that contract, I would be able to actually improve the game from session to session because I and the players would be pursuing the same goal. Which finally brings me to Delvers of Dàrkmesa.
Once I landed on the idea of the megadungeon as a distillation of the time-tested campaign promise, I thought about making my own take on Dwimmermount (if only for the supremely euphonic nature of the name), but decided instead to go completely homebrew. That's how Dàrkmesa came to be. I was struck by the double meaning of
mesa (a huge rock formation that could easily fit a megadungeon inside, as well as the Spanish/Latin root for
table), and what would a dungeon be without darkness? The Delvers part is just to drive the point home. Both in the sense that the characters will be primarily engaged in exploring a dungeon, and in the sense that the game is
about them and
about their exploration, not some arbitrary story I have concocted.
The rules and classes and example spells to include all fell into place now that I had a gameplay goal in mind other than "have fun." Many of the strangest parts of old school games that I could never understand before started to make sense and became incredibly attractive aspects of the experience for me.
Of course the game should be deadly, because that is a large part of what creates drama in a campaign with no forced plot. Of course random encounters were necessary, to keep the players and the DM honest as they all pursued the campaign goal: random chance is what keeps a non-narrative game alive. Of course two hundred pig-faced orcs appearing in a dungeon cavern is a good encounter, because it forces the players to bring to the table what makes them good players, not well-statted characters. And finally, of course the dungeon is the primordial soup from which all good games emerge, because it is the most apt compromise between what the DM needs to do, and what the players need to do. It creates strict boundaries that allow the DM to prepare more of the right thing, but when done right it forces no specific action on the players other than to engage. They want the treasure, and however they get it is by definition a fine way to play. That's why we all play this game, to get the treasure that exists hidden in the forgotten halls of our collective imagination and good company. So why hide the ball? Why not be clear about how agency works in the game right from the beginning? Why not embrace the canvas that was originally conceived for the game, and was so important that it became the first word in its name?
Luckily, it only took me ten years of searching to figure that out. Now I have the rest of my time to play.
