Guide

Game hyper armor and super armor explained

Harbor Ruins' stone brutes were supposed to be skill checks, not damage sponges. Players learned the wrong lesson: mash light attacks during the brute's wind-up and watch every hit bounce off with a dull metallic thunk. Infinite juggles on fodder enemies trained muscle memory that failed on elites. Average time-to-kill on brutes was 94 seconds with 41% of players abandoning the encounter. The fix was not lowering HP. Combat designers tagged each attack phase with explicit super armor (one heavy hit will not interrupt) and hyper armor (nothing short of an armor-break launcher interrupts) windows, added a glowing pauldron telegraph during hyper frames, and gave the player a single guard-break heavy that pierces hyper armor on a 12-second cooldown. TTK dropped to 38 seconds; abandon rate fell to 14%. Armor frames are how action games communicate “this swing is committed” without hiding the rules. This guide covers the armor taxonomy, attack-phase state machines, armor-break tooling, player-enemy asymmetry, the Harbor Ruins refactor, a technique decision table vs poise and invincibility frames, pitfalls, and a production checklist — building on stagger and poise, charge attacks, and hitstop.

Armor taxonomy: five ways hits get ignored

Designers reuse terms loosely. Separate these five mechanisms so tuning stays legible across disciplines:

Invincibility frames (i-frames) — the entity cannot be hit at all. Dodges, respawn grace, and cutscene invuln use i-frames. Damage, poise, and CC all miss.
Super armor — the entity can be hit (damage applies, hitstop may fire) but the current action is not canceled. One light attack will not flinch a super-armored wind-up; a heavy or launcher might.
Hyper armor — a stronger super armor tier. Normal attacks and many heavies bounce without interrupting the action. Only dedicated armor-break moves, grab supers, or posture-break ripostes pierce it.
Poise-based armor — not a boolean flag but a numeric pool (see our poise guide). Each hit drains poise; at zero, stagger occurs regardless of phase tags.
Guard armor — blocking absorbs hits without breaking guard until stamina or a guard-break attack depletes the shield — covered in parry and block systems.

Fighting games popularized frame-based super armor on command grabs and reversal supers. Action RPGs and soulslikes often blend phase tags with poise pools. Beat ’em ups lean on hyper armor for elite wind-ups so juggle loops cannot trivialize every encounter. Pick one primary model per enemy archetype; mixing all five on the same boss without UI telegraphs reads as random immunity.

Attack phases and when armor activates

Armor is almost always bound to an attack phase finite-state machine, not a permanent character flag. Typical phases:

Startup — vulnerable. Whiff punishes land here. Most player light attacks have no armor on startup.
Active / weapon frames — hitboxes are live. Elites often grant super armor here so trades favor the committed attacker.
Recovery — vulnerable again unless a follow-up cancels recovery (combo system) or hyper armor extends through a chain link.

Implementation pattern: each montage or animation notify carries an ArmorTier enum (None, Super, Hyper) and an InterruptPriority on incoming attacks. When a hit lands, compare attacker interrupt priority against defender armor tier. If priority is insufficient, apply damage and optional hitstop but skip transition to flinch/stagger state. Log mismatches in debug builds — silent immunity is the top player complaint in playtests.

Charge attacks commonly grant escalating armor: partial charge gets super armor on release frames; full charge gets hyper armor until recovery. Pair with audio ticks and VFX intensity so players feel the commitment window closing. See our charge attack guide for tier curves.

Armor break, trades, and priority rules

Hyper armor without a counterplay is a pacing wall. Give players explicit armor-break tools:

Launchers and guard-break heavies — tagged with InterruptPriority: ArmorBreak that pierces hyper armor once per cooldown or resource spend.
Grabs — often ignore armor because they use a separate hit reaction channel (throw state, not flinch).
Posture or stagger ripostes — after filling a posture meter, a riposte enters a guaranteed interrupt even against hyper armor.
Environmental hazards — trap damage or ledge shoves that bypass armor for encounter puzzle beats.

Trade rules matter in PvP and co-op: if both fighters have super armor on active frames, both take damage and neither cancels — classic fighting-game trade. If only one has hyper armor, the unarmored attacker still eats damage but their attack is discarded. Document trade outcomes in a matrix; QA should verify every move pair at least once per tier.

Pair armor hits with hitstop so blocked-feeling attacks still have impact feedback even when they do not interrupt. A hyper-armored thunk needs longer defender hitstop and camera shake than a normal hit to sell weight.

Player vs enemy asymmetry

Players and enemies rarely share identical armor rules — and that is intentional:

Player offense — lights are interruptible to reward spacing; heavies and charges buy super armor as risk payment. Never give the player permanent hyper armor on basics — it removes enemy threat.
Player defense — dodge i-frames are the primary escape, not hyper armor while standing. Some soulslikes grant hyper armor during slow heavies; telegraph it with stance glow.
Enemy fodder — no armor on lights; super armor only on clearly telegraphed heavies so juggles feel rewarding early.
Enemy elites — hyper armor on signature attacks; vulnerability windows only in recovery or after posture break.
Bosses — phase-gated armor: hyper armor during phase-one AOEs, stripped during stagger windows so DPS checks land.

Asymmetry creates readable loops: learn telegraph, avoid hyper window, punish recovery, or spend an armor-break cooldown. When players and elites share the same hyper armor on comparable attacks, fights become HP races.

Harbor Ruins brute refactor (worked example)

Before refactor, brutes used a flat poise stat of 999 during all attack animations — functionally permanent hyper armor. Players had no vocabulary for “wait for opening.”

Changes shipped:

Split the overhead slam into three notifies: startup 18f (no armor), active 12f (hyper armor, pauldron glow VFX), recovery 22f (no armor, +20% damage taken).
Replaced poise 999 with poise 45 on active frames only — two player heavies still stagger if you mis-time, but lights bounce as intended.
Added player guard-break heavy (InterruptPriority: ArmorBreak, 12s cooldown) with a distinct wind-up silhouette.
Tutorial ping on first brute: “Armored attack — dodge or Guard Break” when hyper frames begin.
Synced telegraph audio: low brass swell 400ms before hyper active frames.

Playtest metrics: first-attempt clear 34% to 61%; average hits taken per kill unchanged (skill expression shifted from face-tanking to timing). No HP values changed.

Technique decision table

Approach	Best when	Skip when
Frame-based super/hyper tags	Fighting games, action brawlers, frame-precise bosses	Turn-based or slow tactical combat
Poise pool only	Soulslikes with stat-building and equipment weight	You need binary “this move is uninterruptible” telegraphs
Hybrid phase tags + poise	Elites with armor phases and breakable posture	Small team without tooling to debug two systems
Full i-frames on dodge	Skill-based avoidance as primary defense	You want trades and facetank builds to matter
Permanent boss hyper armor	Never — always pair with break windows	Always skip unless cinematic set-piece
CC instead of armor	Support roles, PvP lockdown	Single-player action where armor sells weight

Common pitfalls

Invisible immunity — hyper armor without VFX or audio telegraphs feels like a bug. Glow affected limbs, weapon trails, or UI icons.
Armor on recovery — extending hyper armor through recovery removes punish windows. Recovery should be the reward for patience.
No armor-break outlet — hyper-heavy spam with no counter forces DPS checks or quit. Every hyper pattern needs a documented counter.
Priority table gaps — new moves ship without interrupt tags; defaults fall through to “always interrupt” or “never interrupt.” Automate lint on animation notifies.
Hitstop without damage — bouncing off hyper armor should still deal chip or posture damage or players think attacks whiffed.
Multiplayer desync — armor state must be server-authoritative; client-only flags cause ghost interrupts online.
Teaching juggles then hard-countering — if fodder juggles endlessly, brutes need a tutorial moment explaining armor tiers.

Production checklist

Define armor tier enum and interrupt priority schema shared by player and AI.
Tag every attack montage notify with armor tier and phase name.
Build debug overlay showing active armor tier on all combatants.
Author at least one armor-break move per player kit or party role.
Pair hyper armor with telegraph VFX, SFX, and optional UI callout.
Document trade matrix for simultaneous active frames.
Verify hitstop and damage apply even when interrupt fails.
Playtest fodder-to-elite progression so armor tiers escalate clearly.
Server-replicate armor state for multiplayer encounters.
Log armor-blocked hits in analytics to find overtuned enemies.

Key takeaways

Super armor lets hits land without canceling the action; hyper armor blocks all but dedicated armor-break tools.
Bind armor to attack phases (startup, active, recovery) — not permanent character flags — so punish windows stay readable.
Harbor Ruins fixed brute encounters with phase-tagged hyper armor, pauldron telegraphs, and a cooldown guard-break heavy — no HP changes.
Every hyper armor pattern needs a counter: dodge i-frames, posture riposte, grab, or armor-break heavy.
Hybrid frame tags plus poise pools work for elites, but telegraphs and debug tooling are mandatory.