Game chip damage and guard damage systems explained

What chip damage and guard damage are

Chip damage (also called block damage or guard damage) is health lost when an attack is successfully blocked. The defender avoids hitstun and combo routes, but life still decreases. In fighting games, chip answers a simple design question: if blocking negates 100% of damage forever, why would anyone risk offense when ahead on life?

Guard damage sometimes refers to the same concept, but in action RPGs and soulslikes it often means damage to a separate guard meter, poise bar, or stamina pool rather than life. Sekiro-style posture is guard damage without life chip; Street Fighter-style chip drains life directly. Many modern games use both: life chip for round pressure and posture for break-state payoffs. Keep the vocabulary explicit in your design docs so engineers do not wire chip into the wrong stat.

Chip is distinct from blockstun: stun controls who acts next; chip controls who wins on life if the defender never drops guard. A blocked string can be frame-advantage negative for the attacker while still dealing meaningful chip — the defender eats life but keeps initiative to press a faster button after blockstun ends.

Chip damage taxonomy

Production games mix several chip models. Tag each move with the rules it uses:

• Flat chip ratio — blocked damage equals raw_damage × chip_ratio. Ratios of 0.10–0.25 on normals and 0.20–0.40 on specials are common in fighters. Lights often chip at 0% to reward tight blockstrings without free damage.
• Fixed chip per hit — every blocked hit deals 6 or 12 life regardless of scaling. Simpler for designers but harder to balance across characters with different health totals.
• Chip-only moves — attacks that deal zero damage on hit but significant chip on block (rare; used for shield-pressure tools in platform fighters).
• No-chip moves — throws, command grabs, and some unblockables bypass block entirely; they should be flagged chip_immune on the defender side only when the attack type is grab, not when the defender holds a perfect guard with chip immunity buffs.
• Chip lethal — chip can kill on the last life point. When disabled, blocked attacks leave defenders at 1 HP (common in casual modes). Competitive fighters usually allow chip lethal so blocking cannot deny a deserved round win.
• Special chip rules — supers may use higher ratios; projectiles might chip at half normal rate; armor moves might chip through block in action games. Document exceptions per move ID.

Overheads and lows blocked incorrectly still use the chip ratio for the block type that actually occurred — important for high/low mixups where a stand block against a low might whiff instead of chip.

Chip vs posture, stamina, and perfect guard

Layer chip with other anti-turtle systems instead of replacing them:

• Posture / poise drain on block — each blocked hit depletes a break meter; at zero, a guard break punish opens. Chip taxes life; posture taxes structure. If only posture exists, defenders with full life can still turtle; if only chip exists, break-state spectacle disappears.
• Stamina while blocking — holding guard drains stamina per frame or per hit; at zero, guard drops. Chip and stamina stack well in soulslikes where blocking is hold-to-guard.
• Perfect guard / parry — timed blocks often negate chip entirely and may reflect projectiles. Chip should apply on normal block only; flag chip_on_parry = false unless you deliberately want failed parries to chip (usually they instead become counter-hit state).
• Chip immunity windows — supers, install modes, or guard-cancel mechanics that grant temporary chip immunity must show a clear UI icon; hidden immunity frustrates attackers.

Throws remain the hard counter to blocking: chip pressures life, throws punish hold-guard. Our grab and throw guide covers strike-throw mixups that become lethal when chip has already softened life totals.

Chip lethal and round economy

Chip lethal means blocked damage can reduce life to zero. Without it, a defender at 1 HP can block forever unless guard break or throws connect — producing awkward timeouts and reverse comebacks that feel undeserved. Most tournament fighters enable chip lethal on all chip-dealing moves.

Design implications when chip lethal is on:

• Life leads matter more: being up 15% after a successful escape encourages the leader to block cautiously — chip closes the gap even without opens.
• Supers and chip-heavy specials become legitimate finishers on low life; telegraph chip-lethal range in training mode (e.g. highlight health bar red below chip-kill threshold).
• Chip denial tools (perfect guard, backdash out of blockstring) gain value in endgame scenarios.

When chip lethal is off, clamp post-chip life to a minimum of 1 and surface “CHIPLESS” or shield icon feedback so attackers know they must break guard or throw to finish.

Implementation: formulas, display, and netcode

A typical chip application on block:

chip = floor(raw_damage × chip_ratio × defender_chip_multiplier)

Apply chip after block confirmation, on the same frame you apply blockstun. Order matters for rollback: chip events must be deterministic from attack ID + defender state (blocking standing/crouching, perfect guard flag, chip immunity).

• Rounding — floor vs round changes lethal thresholds. Pick one rule globally; log chip in combat replays for dispute resolution.
• Damage scaling in combos — decide whether chip uses the same combo-scaling table as hit damage. Most fighters scale chip with combo count so infinite blockstrings do not drain life; others keep full chip on specials only.
• UI feedback — flash health bar segment, play distinct SFX from normal hit, show floating “CHIP” damage number in a muted color. Players should instantly know life dropped without a full hit reaction.
• Networking — chip is part of the same hit confirm packet as blockstun. Do not apply chip client-side before server confirmation in online modes.
• Accessibility — optional higher-contrast chip numbers; screen-reader announcements for significant chip (e.g. >8% life).

Harbor Siege chip refactor

Harbor Siege's chip pass treated block damage as a first-class balance surface:

• Normals: lights 0% chip, mediums 12%, heavies 20% of raw damage on block.
• Specials: 25% chip default; chip-lethal enabled on all specials and supers.
• Posture drain unchanged — chip and posture now pressure different resources; duels end by life, break, or throw instead of timer.
• Training overlay showed cumulative chip in a blockstring and highlighted chip-kill range when defender life fell below the next special's chip total.
• Perfect parry still negated chip; failed parry into block used normal chip ratios.

Post-patch: timeout rate 38% to 9%; average life differential at round end tightened; survey respondents rated blocking “risky but fair” up 31 points. The key lesson: chip ratios on heavies and specials matter more than sprinkling 4% chip on every move.

Technique decision table

Common pitfalls

• Cosmetic chip — ratios so low that attackers ignore block damage; telemetry shows blocked specials deal less than 2% life per round.
• Chip on everything — lights that chip encourage mindless blockstring mashing without frame-risk; neuters defense identity.
• Hidden chip immunity — armor states or perks that negate chip without UI telegraph; feels like a bug.
• Chip without throw threat — chip softens life but defenders never fear grabs; strike-throw balance collapses.
• Mismatched chip lethal rules — some moves chip-lethal, others not, with no movelist indication; tournament disputes follow.
• Scaling bugs — chip uses unscaled damage in combos and deletes 40% life on blocked infinite strings; or scaled chip never threatens finishers.
• Confusing chip with guard meter — UI shows one bar draining but code deducts from another stat; players cannot learn cause and effect.

Production checklist

• Define chip ratio (or fixed chip) per move in data; default 0% for lights unless genre demands otherwise.
• Specify chip lethal policy globally and per game mode (ranked vs casual).
• Layer posture/stamina drain separately from life chip; document both in movelists.
• Perfect parry and chip immunity flags tested per character perk.
• Chip uses same scaling rules as hit damage or document explicit exceptions.
• Training mode shows per-move chip, blockstring chip total, and chip-kill threshold.
• Distinct VFX/SFX and health-bar flash on chip connect.
• Chip events logged in combat replay for rollback verification.
• Balance pass: timeout rate, average life at round end, throw success when ahead on chip.
• Accessibility pass on chip damage numbers and color contrast.

Key takeaways

• Chip damage taxes life on blocked hits so blocking is a trade, not a bunker — especially when the defender leads on life.
• Guard damage may mean life chip, posture drain, or stamina; name which stat each system modifies.
• Chip lethal lets deserved round wins land through block; disabling it invites timeout camping at 1 HP.
• Layer chip with guard break and throws: chip softens life, posture opens punishes, throws punish hold-guard.
• Harbor Siege cut timeout wins from 38% to 9% by raising heavy/special chip to 18–25% while keeping lights at 0% chip.

Related reading

• Game parry and block systems explained — hold block, timing parries, and ripostes
• Game guard break systems explained — posture collapse and break punishes
• Game hitstun and blockstun systems explained — frame advantage after blocked strings
• Game grab and throw systems explained — strike-throw mixups against blockers