Armor vs health

Damage is absorbed by a separate armor or shield pool before it touches the underlying health total, with the two pools often behaving differently — armor regenerates, health doesn't; armor blocks certain damage types, health doesn't. Halo's recharging shield-over-health popularized the split, turning combat into a rhythm of poke, retreat to regen, and re-engage. Designers use the two-layer system to create a soft, forgiving buffer (shields absorb chip damage) layered over hard, meaningful consequences (health loss matters more and heals slower), and to enable distinct counters (armor-piercing weapons that skip the buffer). Key decisions: regeneration rules and delay, whether armor and health share resistances or differ, visual feedback distinguishing which pool is being hit, and headshot or bypass mechanics. Pitfall: if armor absorbs everything with no meaningful downside, health becomes irrelevant — the two pools need distinct enough behavior that players make different decisions depending on which is depleted.

• Dev effort: Small
• Timing: Real-time
• Common in: shooter

View “Armor vs health” in the interactive map →