Overview
Numerical balance fails when it's treated as art. The designer adjusts a weapon's damage from 45 to 50 because it "feels" too weak, without calculating what that 11% increase does to the time-to-kill against every enemy type, how it shifts the weapon's rank in the DPS hierarchy, or whether it makes the weapon's tradeoff (slow attack speed) irrelevant because the damage per hit now exceeds the threshold where speed matters. The change fixes the symptom (the weapon feels weak) while creating second-order problems (the weapon is now the only viable choice, enemies designed for the old damage curve are trivialized, the weapon's intended role as a slow-but-powerful option is lost because the power increase wasn't offset by a speed decrease).
The Numerical Balance Framework prompt builds a tuning system with three properties: (1) impact prediction — every stat change comes with a calculated prediction of its downstream effects on related systems, (2) measurable balance metrics — the game's balance state is represented by specific metrics (DPS variance across weapon types, time-to-kill range per enemy tier, win rate per strategy) that can be measured and compared against target values, and (3) rollback readiness — every change is documented with its pre-change state and the metrics that justified it, enabling rapid reversal when the change produces unintended consequences.
What you get: - Stat change impact prediction template with downstream effect mapping - Balance metric definitions with target values and tolerance ranges - Change documentation and rollback protocol - Second-order effect detection method - Balance regression testing specification - Numerical balance audit checklist
Built for: systems designers, balance designers, and gameplay programmers who need numbers that produce the intended gameplay — not numbers that feel right in isolation but break the game in combination.