You Slept Eight Hours. You're Still Exhausted. That's Not a Bug.

Under the 2024 rules, a long rest only knocks off one level of exhaustion, not the whole thing. Here's the math nobody re-reads and the one-line fix that keeps it from getting lost between sessions.

Your party just crawled out of a three-day trek through a blizzard, fought off a pack of frost-touched wolves running on no sleep, and finally made it to an inn. Everyone narrates the hot bath, the real bed, the eight hours of actual sleep. Next morning you ask for a Perception check and someone rolls a 3 on what should've been a decent roll. "Wait, why am I still at disadvantage — I mean, minus four?" Because they are. A long rest didn't fix it. It just knocked one level off.

That surprises a lot of tables, and it's worth saying plainly: under the 2024 rules, exhaustion doesn't reset when you sleep. It decays, one level at a time, the same way a debt gets paid down instead of forgiven.

How the math actually works

Exhaustion still tops out at level 6 (that one kills the character), but the 2024 Player's Handbook changed what each level does. There's no more chart of unique effects per level — no more "level 3 drops your speed by half, level 4 gives disadvantage on saves," each one different from the last. Now it's one clean rule: each level of exhaustion gives a cumulative −2 to every d20 test (ability checks, attack rolls, saving throws) and −5 feet of speed, and it stacks. Level 3 is −6 to everything and −15 feet. Level 6 is dead.

The part that trips people up is recovery. A long rest doesn't zero it out — it removes exactly one level, and only if the character also ate and drank and didn't sleep in medium or heavy armor. Get hit with exhaustion 3 from that blizzard trek, and you're not back to normal after one good night. You're at exhaustion 2, still hauling a −4 penalty and moving 10 feet slower, and you'll be feeling it for two more nights unless somebody's got Greater Restoration on tap.

Why it's the condition everyone forgets is still there

Every other condition on a character sheet lives inside a scene. You get poisoned in a fight, you track it through that fight, it resolves. Exhaustion doesn't work like that — it's the one condition explicitly built to outlast the encounter that caused it, sitting on the sheet for real-world sessions at a time while nothing about the token, the map, or the current scene reminds anyone it's there. The wolves that caused it are long dead. The blizzard's over. There's no visual cue left pointing back at the number quietly sitting under "conditions." So it gets applied in the moment everyone's paying attention to it, and then it gets forgotten the second the scene that caused it ends — right up until someone whiffs a roll that shouldn't have been whiffed and the table has to stop and reconstruct who's at what level and since when.

The fix is to stop treating it like a combat condition

Combat conditions belong on the initiative tracker because they live and die with the fight. Exhaustion belongs somewhere that survives a scene change — the same place you're already tracking HP between sessions, written as a running number next to the character's name, not a box you check and forget. Every long rest, the whole table updates that number together out loud, the same beat as everyone marking off rations: "minus one exhaustion, everybody." That's it. It turns recovery from a thing someone has to remember into a thing that happens automatically because it's part of the ritual.

If you're running fights in Virtual Combat Simulator, the same logic applies to why exhaustion needs to be a persistent condition on the token rather than something that gets cleared with the rest of the combat state — a fresh encounter shouldn't wipe a number that's supposed to survive three real sessions. Set it once when the exhaustion hits, and it rides on the character sheet across every combat until somebody actually rests it down.

Either way, the lesson's the same: the condition that outlasts the fight needs to live somewhere that outlasts the fight, too.

#dnd #exhaustion #combat tracking #virtual combat simulator #2024 rules #homebrew

You Slept Eight Hours. You're Still Exhausted. That's Not a Bug.