Resource budgets
01The same number, four different names
A wizard's spell slots, a lantern's oil, a paladin's lay-on-hands charges, a thief's pool of "luck points" — these look like distinct fictional things. Mechanically they are identical: a counter that depletes during a session and refills at a defined interval. Every resource budget in a tabletop RPG is just that structure. Understanding it means tracking two variables: how much the counter holds, and when it resets.
The two numbers that define a resource
- 01Counter size — the raw capacity; meaningless without knowing drain rate
- 02Refresh interval — short rest, long rest, resupply; this controls session cadence more than counter size does
The size of the counter governs what the resource feels like in the moment. A budget of twelve hit points in a dangerous system demands different play than a budget of twelve hit points in one where foes deal a single point per hit. Raw size is meaningless without knowing the rate of spend. Designers who publish a resource without also specifying the typical drain rate per encounter have described only half the machine.
The refresh interval is the part that actually controls session structure. A resource that refills on a short rest — after ten quiet minutes — behaves like a different tool than one that refills only after sleeping. The wizard who recovers spell slots on a long rest is tuned for about four major encounters per day; force eight encounters through before the party sleeps and the budget shreds. The system's encounter cadence is not a separate design decision from its resource cadence. They are the same decision, stated twice.
02What the interval is really a claim about
When a designer sets the refresh interval, they are making a bet about how many resource-draining events will happen between refreshes. Call that number the expected drain cycle. If the drain cycle matches the budget — the party burns through roughly all their resources just as the rest arrives — the design is in balance. The resource feels meaningful without becoming paralyzing.
What a fight costs is partly a question of absolute numbers; it is equally a question of where in the drain cycle the fight sits.
Short intervals push toward attrition-light play. A fighter who recovers a chunk of hit points after every fight can absorb punishment and keep moving; individual fights feel lower-stakes because the clock resets quickly. Long intervals push toward careful husbandry: every fireball is a decision, every torch matters, because recovery is far away. Old-school dungeon designs borrowed directly from this logic — the torch lasted roughly an hour (six turns) for exactly the reason the dungeon was measured in exploration turns of ten minutes each. Resource and procedure were calibrated together.
Calibration signals
- 01In-balance signal: party arrives at the rest point roughly spent; no single resource type has been left entirely full
- 02Short-interval mismatch: full casters feel overpowered in one-fight sessions; martial classes with flat resources feel fine
- 03Long-interval mismatch: marathon sessions punish burst-power characters; husbandry stops feeling like a choice
The trouble appears when the interval and the actual play pattern diverge. A system balanced for four fights between long rests starts to buckle when the referee runs one-fight sessions: full casters roll into every encounter loaded, martial classes with simpler resource profiles never notice the gap. Conversely, marathon sessions with no rests punish classes whose power spikes are short-interval and reward anyone whose budget is flat. What a fight costs is partly a question of absolute numbers; it is equally a question of where in the drain cycle the fight sits.
03Refreshing mid-cycle and why it matters
Many systems allow partial recovery — a short rest, a Second Wind, a single spell slot back — that sits between the two main intervals. These exist to smooth the curve. Without mid-cycle recovery, a party approaching their second-to-last encounter on fumes either retreats (breaking narrative momentum) or grinds through at greatly elevated risk. A small injection of resources gives the designer control over the tension shape without resetting everything.
The injection has to be sized carefully. Too generous and it collapses the distinction between short and long rest — players learn to treat every short rest like a full reset and the long interval becomes administrative fiction. Too stingy and it might as well not exist. The test is behavioral: after a short rest, does a player change the kind of resource they are willing to spend in the next encounter? If yes, the mid-cycle top-up is doing work. If the calculus is identical, it is noise.
Non-violent drains — light sources, rations, spell components, vehicle fuel — run on the same logic but against a different clock. They usually reset on resupply rather than rest, making their interval a function of distance to town or a dungeon's supply cache. A dungeon that is three torches deep with no resupply is not a flavor choice; it is a budget constraint that shapes every decision before the first roll. Call them logistics resources rather than combat resources if you need the distinction, but the arithmetic is the same: finite pool, defined drain rate, meaningful moment of replenishment.