Dungeon World's "16 HP Dragon" Is Cope

St. George fights a 10 HD dragon.

When Dungeon World was first released, it was a massive hit in the RPGsphere, creating a bridge between traditional RPGs and storygames, introducing a more narrative "D&D" experience to those who wanted the familiar and time-tested trappings of D&D sans the mechanical cruft. The RPG community was enthralled, but a question of power scale arose.

This issue arose because Dungeon World has one foot in the narrative world and one foot in the traditional RPG world. Its engine (Powered by the Apocalypse) does not handle traditional "D&Disms" (vertical advancement) very well. The PbtA system doesn't "do" things like characters gaining a bunch of Hit Points and adding a dozen incremental +1s to their attacks and saving throws. It's not designed to support that style of gameplay.

Despite this, the designers (Sage LaTorra and Adaem Koebel) married this engine to D&D, which brings us to the problem of dragons. The 16 HP dragon, as it were.

In Dungeon World, a dragon has 16 HP and 4 armor. A fighter does 1d10 damage on a hit (+1d6 on a strong hit). While insufficient to slay a dragon outright, a first-level fighter has the power to seriously injure a dragon--and, given the probabilities involved in the system, he was likely to do so. Questions arose from GMs asking how to make fights more difficult or threatening, and from this came the 16 HP Dragon article.

This article was lauded and passed about the community as great wisdom for how to run Dungeon World, but to anyone with a critical eye, it's clearly an incoherent mess coping at Dungeon World's limitations.

Right away, the author starts off with some nonsense:

Think of these fights more in terms of literature and pacing instead of the classic ‘they have X hp and we have to swing Y times with Q hits to drop it’. The problem in this context is that there is no accounting for fiction, this is a mechanical solution (a simulation) of a sword doing consistent damage, and scaling monster HP to allow for the same tool (swing) to be applied to every problem (monster).

This is entirely nonsense because the mechanics in a game should approximate the media or literature from which it draws inspiration. Very simply: Call of Cthulhu has sanity rules because Lovecraft's stories oft ended with characters going mad. The One Ring has rules for weariness and despair because those featured heavily in Tolkien's writing. Pendragon has rules about chivalry and honor because Arthurian knights were honorable.

If Dungeon World is a heroic fantasy game where you fight dragons, why don't the rules create the desired pacing? D&D does this by giving dragons high AC and HP, meaning that dragons are mechanically fearsome and difficult to kill. Dungeon World does this via...bullshit, apparently:

The group starts to help the townsfolk (this is not a magical node, so the wizard can’t just ritual up some rain) when a building shatters with the landing of a 4-5 ton creature, and it opens up its pipes, it’s golden eyes burning and it’s metal hide resonates with a roar (terrifying Their charges scatter, the PC’s have to defy their own terror to attack the thing.

I've cut out a previous section wherein the author describes how the dragon is burning down a village. In the above section, I've underlined the mechanical bits to expound upon them.

First and foremost, the "defy their own danger to attack" is not part of the Dungeon World rules as-is. It's entirely fabricated by the GM in an attempt to compensate for the mechanics. The GM arbitrarily throwing in a "saving throw or you can't attack :3" mechanic because he's trying to make an encounter harder is poor form--but I suppose that mechanizing this the way D&D does with a save vs. fear too deprotagonizing and icky.

They do negligible damage (yay 4 armor) for those that DO anything, and realize that the only person who has a shot at killing this is the armor-penetrating wizard spells. Unfortunately, so does the dragon. What ensues is horrific. One fighter takes up defensive position, when the dragon strikes it doesn’t just do 1d10+5 damage, it rips off his arm (messy remember?) and shreds mail like tissue paper. It does breath weapon attacks that cause ALL of them to defy danger or burn. The party breaks and runs. The dragon laughs and settles to ash the village and eat any survivors.

Next, the author goes on to note that the dragon has 4 armor and inflicts 1d10+5 damage (both of these are implied to be impressive), despite spending the previous eight paragraphs establishing why Dungeon World doesn't, like, need mechanics. These statements directly contradict his core premise, which is that you need to be thinking less in terms of mechanics and more in terms of "literature and pacing."

Moreover, the party's "negligible damage" to the dragon is entirely based upon the luck of the dice; as mentioned previously, a baseline fighter whacking the dragon for maximum damage could have done (net) 12 damage to the dragon, depleting 75% of its hit points in a single sword stroke.

The limb-ripping from the messy tag is arbitrary. The rules state:

Messy: It does damage in a particularly destructive way, ripping people and things apart.

But there's no actual notes on when this comes into play. (GM fiat, and I suspect that the GM in this story is a bit stricter about when this applies on the PCs' end). I will give the GM a pass on the Defy Danger for fire breath (this seems entirely reasonable).

The Dragon had 16 hit points. The party did 9 to it before they left. And when I said left, I mean they ran like rabbits into the night with few provisions, no easy means of recovering them, and no thoughts in their heads other than survival.

The author notes the dragon has a paltry 5/16 HP remaining after the fight, which indicates to me they realized the GM was going to continue to tear off their limbs like a cruel child with a spider if they dared to press their luck against the dragon. A single good roll would have ended this creature, but I suppose you don't want to stick around when the GM is forcing you to roll the dice specifically to prevent you from killing the dragon too quickly. (It's not like in my fantasy novels! You can't kill the monster too fast because that's lame!)

Finally, the author goes on to say:

The moral of the story is it’s not about the hitpoints. In my 4e game the party had a dozen dragon kills under their belt. The dragons were mechanically threatening, they were tricksy, they were tactical, but their claws and teeth didn’t do damage, they did numbers. After this session they explained that they had never been so scared of a monster. Make the fights epic. Use the fiction. Describe their skin curling black from fire. The bones shattering from the unyielding stone grasp of the earth elemental. Most fights clean up the fiction by saying you take 5 damage. Make it stick, make it hard to heal, make them scarred and battle hardened having earned every mark, and every wound a story.

Yes, the author's 4e game had a dozen dragon kills under their belt because he designed the encounters to let the PCs win, in the exact same way he designed this abysmal dragon encounter to force them to lose. They also didn't care because 4e was designed in such a way that there were no lasting consequences, unlike this scenario where the GM ruled--quite arbitrarily--that they were losing arms. There's nothing in the D&D 4e rules that precludes this from happening, but somehow Dungeon World makes this happen because you're not thinking in numbers (about the 4 armor and 1d10+5 damage).

It's clear that the author of this anecdote is excited about Dungeon World and enjoys running it, but he's likewise coping about the severe shortcomings of the system. The 16 HP dragon just isn't scary unless the GM fights the system tooth-and-nail to make it scary.