Your Wizard Never Runs Out of Spell Slots. That's Not a Compliment.

Your Wizard Never Runs Out of Spell Slots. That's Not a Compliment.

D&D's class balance assumes six to eight fights between long rests. Almost nobody runs that many. Here's what breaks when the attrition math never kicks in, and the one-line fix that brings it back.

Every D&D group has met the wizard who opens every single encounter with a leveled spell, because why wouldn't they -- there's a long rest coming as soon as the fight's over anyway. That's not a min-maxing failure. That's the adventuring day working exactly the way it's built to work, except backwards.

The math behind D&D's class balance assumes something specific: six to eight medium-or-harder encounters between long rests, spread across a couple of short rests along the way. That's not flavor text. It's the load-bearing assumption behind why full casters get fewer, bigger spell slots while fighters and warlocks get more frequent, smaller resources. The whole system is tuned for attrition. Spend early and you're weak later. Hold back and you're sitting on a resource that resets anyway, for nothing.

Almost nobody runs six to eight encounters a day. Most home tables get through one real fight a session, maybe two, because that's what a three-hour session actually holds once you count roleplay, travel, and the fifteen minutes someone spends deciding whether to check the door for traps. Which means the attrition math never kicks in. Every fight becomes the first fight, which means every fight becomes the only fight, which means every fight is the one worth nova-ing on. Your wizard learns, correctly, that Fireball is free. Your warlock, stuck with two slots that come back on a short rest the party might not even take, quietly starts to resent existing.

None of this is a rules problem. It's a tracking problem -- nobody's writing down what a long rest actually cost the story. The fix isn't redesigning your session around a spreadsheet of encounter budgets. It's one line, added to whatever you already use for notes: what got spent since the last long rest, and what the rest is costing the world while it happens. A used-up wand charge. Two of four spell slots. A potion nobody will admit to drinking. The fact that the search party has now had eight uninterrupted hours to close in.

That second half matters more than the tracking itself. A long rest is only free to the players if you're also treating it as free to the world. If a wandering monster check, an NPC's next move, or a ticking clock keeps running whether or not the party rests, resting stops being a reset button and starts being a decision with a cost attached, even when that cost never turns into a fight. You don't need to punish every rest. You need the table to know that one, eventually, might come with a bill.

Where this actually falls apart at most tables isn't remembering the rule. It's remembering the state: what's already been spent, what the world's been doing in the meantime, three sessions from now when nobody can recall if the warlock rested twice today or once. That's the kind of running thread GameMasterCraft's session notes are built to hold -- not a rules engine, just a place where "spent since last rest" and "what happened while they rested" sit next to each other instead of living in nobody's memory at all.

You don't need eight fights a day to make attrition mean something. You need one sentence a session that says what it actually cost.

Comments (0)

More from the Blog

Ready to create something?

Subscribe to an individual app or get the full GameMaster Studio.