Guide

Game hold parry and drive parry systems explained

Harbor Siege’s rushdown roster dominated the first month of ranked play. Blockstrings chipped posture down, throws beat hold-block, and just-guard timing was too tight for the median player to learn in week one. Defenders described neutral as “pick your poison: eat chip or guess reversal.” Engineers prototyped a hold parry — hold a dedicated parry button to enter a sustained absorption state that negated chip and posture drain on each absorbed hit while draining a shared tension bar. Rushdown win rate against mid-tier defenders fell from 61% to 48%; average round length rose 8 seconds as attackers learned to reset with throws and delayed overheads instead of mashing lights into the parry box.

Hold parry (often branded drive parry, faultless defense, or sustained guard) is a defensive mode toggled by holding an input, not a single-frame timing read. It differs from impact-timed just guard, blockstun red parry, and one-shot reflect parry windows. The defender commits to a visible state with resource cost, movement options, and a punishable release. This guide covers the hold-parry state machine, per-hit absorption rules, meter and burnout economics, walk-through pressure, counterplay taxonomy, the Harbor Siege refactor, a technique decision table versus other defensive layers, pitfalls, and a production checklist.

What hold parry adds to block and timing parry

Ordinary block is passive: hold back, absorb blockstun, take chip, lose posture. Timing parries reward a narrow input window with frame advantage or reversal. Hold parry sits between them — active defense you can sustain across multiple hits if you pay the resource price.

Typical properties of a hold-parry state:

Chip and posture immunity on successfully absorbed strikes (not throws or command grabs).
Per-hit resource drain from a tension, drive, or guard meter shared with offense.
Reduced or zero pushback so the defender can walk forward through the attacker during blockstrings.
Startup and release recovery that attackers can frame-trap if the defender holds too long.
Distinct VFX and SFX so offense knows when to stop pressing and switch to throw or shimmy.

The design goal is giving defenders a readable tool against blockstring chip wars without making hold-parry the dominant neutral option. If holding parry is always optimal, rushdown dies; if it is free, turtling dominates. The meter curve and release punish windows carry that balance.

Hold-parry state machine

Implement hold parry as an explicit combat state with guarded transitions, not a flag bolted onto block. A minimal pipeline:

Idle — parry input not held; normal movement and attacks.
Startup — 2–6 frames where parry is not yet active (prevents instant reaction to visible attacks).
Active hold — absorption box enabled; per-hit handler runs; tension drains on each qualifying strike.
Hit absorbed — apply brief hitstop, optional spark VFX, optional forward walk speed bonus; do not enter blockstun.
Burnout / break — tension hits zero or a heavy hit breaks the state; enter long recovery or stagger.
Release — button up triggers recovery animation; frame-trappable by meaties and throws.

Multi-hit moves should call the per-hit handler once per active frame cluster, not once per move ID, or single specials drain the entire tension bar unfairly. Beam and multi-tick projectiles need a drain cap per move documented in frame data.

What hold parry should not absorb

Clear exclusions prevent degenerate defense:

Throws and command grabs — answered by throw techs and spacing, not parry hold.
Unblockable lows/overheads if your game tags them explicitly (optional design knob).
Guard-break and crush moves designed to pierce defensive layers.
Chip-only environmental hazards unless you want parry to work on stage traps (usually no).

Resource economics and burnout

Hold parry without cost becomes passive invincibility. Common cost models:

Cost model	Behavior	Risk
Flat drain per absorbed hit	Predictable; scales with blockstring length	Light mash strings bankrupt defenders fast
Drain scaled by attack strength	Heavies and supers threaten burnout	Requires per-move drain table maintenance
Continuous drain while holding	Punishes infinite hold in neutral	Feels bad if drain rate is opaque
Separate offense meter tax	Parrying spends the same bar as EX moves	Skilled players may never parry if offense is stronger

Burnout is the fail state: tension empty, parry shatters, defender enters 20–30 frames of stagger or full guard break. Burnout must be telegraphed — audio pitch rise, bar color shift — so attackers can confirm into supers. Without burnout threat, walk-through parry into throw range becomes oppressive.

Walk-through pressure and offensive counterplay

The signature skill expression of hold parry is walking forward while absorbing, closing distance on a blockstring and threatening throw or short-range normal. That only works if:

Pushback on absorbed hits is near zero or inward.
Parry walk speed is tuned per character weight class.
Attackers have answer tools: empty jump, delayed overhead, shimmy, tick throw, and frame traps on parry release.

Offensive counterplay taxonomy:

Stop pressing — backdash or reset neutral when parry VFX appears; avoids tension drain race.
Throw / command grab — beats hold parry if throws are not parry-able.
Frame trap release — leave a gap long enough that a human releases parry, then meaty the recovery.
Burnout fishing — EX special or multi-hit super to empty tension in one interaction.
Shimmy — walk backward out of throw range when defender walks forward out of parry.

If your game also has fuzzy guard or low-high mix, hold parry should not auto-defend both heights unless that is an explicit design choice — otherwise mixups remain the answer to parry hold.

Harbor Siege hold-parry refactor

The ranked patch added Drive Guard (internal name) with these constants after two weeks of lab tuning:

4-frame startup; active while parry button held.
8 tension per light absorbed, 14 per medium, 22 per heavy; cap 3 drains per multi-hit special.
2 tension per frame continuous hold after 15 frames (anti-infinite neutral hold).
+25% forward walk speed during active; zero pushback on absorbed strikes.
Burnout at 0 tension: 24-frame stagger, no block option.
12-frame recovery on voluntary release; throw-invulnerable only frames 1–3 of release (throws still beat greedy hold).

Results after 9,800 ranked duels: rushdown vs mid-tier defender win rate 61% to 48%; throw attempts per round +0.6; parry burnout punishes per round +0.3. Complaints about “unreactable pressure” dropped 37% in post-match surveys. Experts still favored rushdown (+3% win rate) via shimmy and delayed overhead reads.

Technique decision table

Goal	Prefer hold parry	Prefer alternative
Teach defense without frame-perfect timing	Hold parry with visible bar and 4+ frame startup	Generous hold-block with low chip only
Answer long blockstring chip	Sustained absorption + walk-forward threat	Just guard per hit for skilled players
High-risk high-reward defensive read	Short-window reflect or full parry	Hold parry (lower peak, higher floor)
Punish predictable projectile spam	Reflect parry with ownership flip	Hold parry (absorbs but does not return fire)
Break defensive blockstrings from inside	Hold parry walk-through into throw	Red parry during blockstun gaps
Rollback online determinism	Hold parry with discrete per-hit drain events	Continuous physics-based pushback parry

Common pitfalls

Zero startup hold parry. Reacts to reaction tests; removes offense identity. Minimum 2–4 frames startup is standard.
Parry absorbs throws. Collapses mixup triangle unless throws are a deliberate parry answer.
No release punish. Defenders hold forever in neutral; add continuous drain or shimmy/throw answers.
Opaque tension bar. Players cannot learn burnout thresholds; show per-hit drain ticks in training mode.
Same drain for lights and supers. One super empties bar unfairly or not at all; scale drain by move class.
Rollback desync on hold state. Predicted parry on one client only; replicate hold state and drain on confirmed hit flags per rollback rules.
Invisible parry box. Attackers cannot tell parry is active; use persistent aura or guard-point sparks on each absorption.

Production checklist

Document hold-parry FSM: startup, active, burnout, release recovery frame counts.
Publish per-move tension drain table alongside frame data.
Cap multi-hit drain per move ID; test beams and rapid-fire jabs.
Exclude throws, command grabs, and guard-break moves from absorption.
Tune forward walk speed and pushback per weight class.
Telegraph burnout with audio, UI, and stagger recovery length.
Author offensive answers: throw, shimmy, delayed overhead, frame trap release.
Expose parry tension, drain events, and hold duration in training overlays.
Validate rollback reproduces hold state and tension identically on both clients.
Telemetry: hold frequency, avg hold duration, burnout rate, walk-through throw rate.
A/B test startup length with intermediate skill cohort before ranked ship.
Cross-link movelist tags: moves that break parry vs moves that drain extra.

Key takeaways

Hold parry is a sustained defensive state with resource cost — not a single-frame timing parry.
Per-hit absorption plus walk-through movement answers chip blockstrings if burnout and throws remain real threats.
Harbor Siege cut rushdown win rate from 61% to 48% with tension drain, walk speed, and release recovery.
Pair hold parry with just guard and reflect layers so skill expression scales from beginner to expert.
Offensive counterplay is throw, shimmy, and frame-trap release — not bigger blockstrings into parry.