Boss HP is a window into the CPU.

The numbers in console RPGs aren’t arbitrary. They never were. Every era of hardware left its fingerprints on how damage was calculated, how high HP could go, and what the math was even allowed to do. And if you know what to look for, you can read the CPU in the numbers.

Start at the beginning. Early console CPUs, like the 6502 in the NES and the Z80 in the Sega Master System, couldn’t multiply or divide. Not natively. Those operations had to be faked in software using addition, subtraction, and bit shifting, and doing it every frame on every enemy in a battle was expensive. So early RPGs didn’t bother with complex formulas. Damage in Dragon Quest, Final Fantasy, and Phantasy Star was essentially Attack - Defense + noise, sometimes with constants chosen specifically because multiplying or dividing by a power of two is just a bit shift. Fast, cheap, and correct enough.

The numbers stayed small for the same reason. The 6502 and Z80 worked natively in 8 bits, meaning values topped out at 255 without extra work. Final Fantasy on the NES implemented 16-bit math in software to let Chaos reach 2,000 HP, which was notable enough to be a selling point. That number felt enormous in 1987. Dragon Quest’s Dragonlord had 100 HP in his first form and 130 in his second, numbers that fit comfortably in a single byte with room to spare. Phantasy Star’s Dark Falz, the final boss of the Master System original, was technically two separate 255 HP monsters. You know when the first one dies because he abruptly drops from attacking twice per round to once.

The SNES changed the math. It had native 16-bit registers and, crucially, actual hardware multiplication and division support. It was slow by modern standards, but the hardware supported it. This opened up larger numbers and slightly more sophisticated scaling. Final Fantasy IV’s Zeromus weighs in at 65,498 HP, which is not a coincidence: it’s just short of the maximum value of an unsigned 16-bit integer (65,535).

The PlayStation generation brought 32-bit integers and hardware multiply/divide as standard, and that’s where RPG damage formulas finally got room to breathe. Final Fantasy VII’s damage reduction stopped being a flat subtraction and became multiplicative:

Damage = Base Damage × (512 - Defense) / 512

That formula does something the earlier ones couldn’t: it produces a smooth curve. At 256 Defense, you always take half damage, regardless of the base. At 512, you’d theoretically take none. The behavior is more consistent, and it’s only practical because the hardware can do the division without it costing you three frames per enemy.

HP ceilings moved too. With 32-bit integers, the hard technical limits mostly disappeared for enemy HP. A signed 32-bit integer can hold numbers up to about two billion, which is more than anyone needed. So the ceilings became stylistic rather than structural. FFVII kept player characters capped at 9,999 HP (a deliberate choice, not a hardware constraint), but let enemies go much higher. Emerald Weapon has 1,000,000 HP. Ruby Weapon has 800,000.

Hardware limits didn’t vanish entirely. A quarter century after Sega basically duct taped two Dark Falzes together to double his HP, World of Warcraft’s Garrosh Hellscream (in the Siege of Orgrimmar raid on Heroic difficulty) healed to full twice during the encounter because his total health exceeded the ~2.1 billion cap of a signed 32-bit integer. Blizzard had to split him across multiple health pools the same way Sega split Dark Falz across two monsters. Different decade, same problem, same solution.

The constraints evolved, but they never fully went away. What changed is where they show up and how deliberately designers work around them. Early RPGs built their entire numerical vocabulary around what the CPU could do cheaply. Modern games occasionally still find the edges of what the hardware can hold. The math got more powerful, but it never stopped being math.