In the cold mountains of Vermont, the great wyrm Zaskettr met its fate.
Let’s back up. Last weekend was Carnage, the annual northern New England tabletop gaming convention that currently takes place at the Killington Ski Mountain Resort. It is a great con, with hundreds of attendees playing all manner of games. This year, I ran a long form game called The High Guard which you can read about here. For the purposes of this discussion, only one detail of that adventure matters: the fight against, and victory over, Zaskettr, the great wyrm responsible for the death of the High King and following chaos.
Dragon fights are notoriously difficult in D&D. As very powerful singular monsters, dragons can be both overwhelming for a party and at the same time anti-climactic. This is due to the nature of threats, combat and so-called “challenge ratings” in D&D. As what can be referred to as “boss” or “solo” monsters, dragons have tons of hit points and the potential to deal a lot of damage. As such, they can be very deadly, even for level appropriate PCs. Despite this, they can also seem somewhat weak. As singular monsters, they are inherently the focus of a heroic party’s energies and all those arrows, swords and spells stack up quickly. This is doubly true when, such as at a convention, the party is larger than usual.
Zaskettr began as an indistinct concept. I wanted to create a setting defined by a central monster, one that would always be present but not necessarily involved. This being D&D, the obvious choice was a dragon. Not any dragon, mind you, but an ancient red wyrm, the most powerful evil dragon in any edition of the game (barring deities and the like). The dragon would have destroyed not just the king and his castle, but the very stability of the kingdom. It would be the ultimate boss monster for a party that started out as zero level nothings trying to survive giant rats in the inn cellar.
Of course the idea evolved over time. Eventually when I was deciding what sort of long form game to run this year, I remembered the idea and created a world around the creature, which I called Zaskettr based on some random googling. Despite whatever details changed, the core idea remained the same: the dragon was the monster that had brought down the apocalypse and whatever else the heroes accomplished, destroying it would be the ultimate test. That said, I did not actually go into the con game expecting the PCs would tackle the dragon. I thought they might so I prepared, but it was just one of a few threads. It became clear early on in actual play though that if you put a dragon at the center of a game, the players are going to want to kill it.
Many adventures led up to the direct conflict with Zaskettr. One of the things I believe I am really good at from a Dungeon Mastering perspective is working on the fly. I create a realized setting and I prepare some expected encounters and Non-Player Characters. So armed, I am confident in letting the players go whatever direction and dealing with it as they go. Truth be told, I prefer this method of DMing simply because I get to be surprised, too. Who knows what a random group of players are going to do at a convention game, let alone one that stretches over 5 or more slots? I certainly don’t, and I like it that way.
Eventually, the PCs did come into direct conflict with Zaskettr. Twice, actually. Once the party had acquired the weapon with which to defeat the dragon, they went looking for it in its domain. That location proved very challenging and when they retreated to lick their wounds, the dragon, drawn by the very weapon designed to defeat it, attacked. The party barely survived and managed to escape through sheer luck. (Aside: that luck happened to be in the form of a helm of teleportation that one player rolled as a random starting item at the beginning of the first session. I believe in random input into the game. I can’t think of everything, and sometimes a random die roll, whether for an item or an encounter or even just a name, can completely change the course of an adventure. As I said, I like to be surprised.)
After the party fled, they chose to seek aid from the lords, churches and common folk of the land. With such aid, they drew the dragon away from a populated area and used magic to create a battleground of their devising. Zaskettr met them and this time the wyrm and the party were far more evenly matched. Even so, there were tense moments where only lucky die rolls on the part of the PCs or unlucky die rolls on my part spared their lives. It was glorious — everything a tabletop D&D fight with a dragon should be. I guess that an outside observer inexperienced with the nature of play would probably have been bored to death as we worked through a single battle for 2 or more hours. But for us at the time, it was thrilling. By the way, in my opinion that, in a nutshell, is tabletop gaming.
In the end, the PCs managed to whittle Zaskettr down. I had the dragon all set to flee the battle and force the PCs to come to its lair for the final round. Sadly, I did not leave the poor beast enough hit points. I did not expect the last round of luck the PCs had and before Zaskettr could fly off, the party cut the dragon down and impaled it with the magic spear that would keep it in torpor so long as the spear remained in Zaskettr’s heart. They whooped and hollered on their victory and, to be honest, so did I. I talk a good “killer DM” game but in the end I want them to succeed just as much as they want to. After all, what we are all really looking forward to is a good tale to tell afterwards.
I gleaned a lot more from that extended game at Carnage this year than the fun of the party defeating Zaskettr. I will go into that in a future post. But for now, the joy of a well fought battle that mattered to the players, even at a convention without any of the weight of a home game, is enough to make me smile. This is why I run games and why I run games at conventions the way I do. Success after 20 hours, even if you as a player was not there for every single moment of it, is still far sweater than after just four.
I.E. 