Parry Windows That Shrink After Three Successful Blocks
Infinite perfect parries turn defense into a free offense engine. Parry windows that shrink after three successful blocks keep reads sharp. The first clean blocks feel generous, then the timing tightens so mashers cannot farm forever without adapting.
Pair this with combo meters that reset if you buffer too early and cover zones that expand when teammates call flanks so offense and defense both punish autopilot.
Count successful blocks, not raw attempts
Increment the shrink counter only on successful parries or blocks inside the window. Missed inputs should not punish learners who are still finding the beat of the exchange. Reset the counter after a clean hit lands on you, or after a short idle gap, so one good exchange does not lock you into hard mode for the whole round.
Shrink the window in clear steps
After three successes, cut a few frames. After six, cut again. Publish the steps in training mode with a frame meter. Hidden shrinks feel like lag. Visible steps teach players to mix throws, feints, and disengages instead of looping the same parry.
Show the heat on the fighter
Tint the guard flash or add a short spark trail as the window tightens. Silent difficulty spikes breed “the game is broken” clips. Readable heat tells both players the defender is on a clock. Related readability ideas live in the stealth game visibility test.
Give a fair recovery path
Landing a punish combo, forcing a knockdown, or spending a meter burst should restore a wider window. Pure attrition without recovery makes turtle characters unplayable. Recovery should be earned, not a free timer tick while you hold block.
Tune per character and ranked rules
Heavy armor fighters can start with wider windows and steeper shrink. Fast duelists start tighter with gentler steps. Casual modes can freeze shrink after three for teaching. Ranked should keep the full curve. Netcode must agree on the counter before damage resolves so rollback does not invent phantom shrinks.
Teach it in the lab first
Put a dummy that loops the same mid string. Show the window meter drop after the third clean parry. One lab drill beats a long patch essay. Keep the rule identical across stages so tournament players stop arguing about stage-specific frames.
Log average successful parries per round and win rate by character. If everyone still farms parries, shrink steps are too soft. If defense collapses after two blocks, steps are too hard. Adjust frames before you touch chip damage.
Online input delay should not double-count shrink. Apply the counter on confirmed successful blocks after rollback settles. Clients may predict the tint, then reconcile.
Assist characters and tag fighters need shared or per-body counters written in the patch notes. Ambiguous team rules create endless forum fights. Pick one and keep it boring.
Voice chat does not change windows. Only the combat state machine does. Keep social features out of the frame-data path.
FAQ
When does the window shrink?
After a set number of successful blocks or parries, shown in clear steps.
Do misses shrink the window?
No. Only successful defensive hits should advance the counter.
How do I recover a wider window?
Through earned recovery such as a punish, knockdown, or meter spend, per design.
Can players see the heat?
Yes. Guard flash or spark trails should telegraph the tighter timing.
Does netcode own the counter?
Yes. Server or rollback-confirmed state should own the shrink count.


