parry-guard · diff
git:20260912.6fe41d5 to git:20260913.43ccc40
15 added, 12 removed. Audit A to A.
---
name: parry-guard
- description: Block and parry are data on the defense move. Ask hold-block vs tap-parry vs both. I-frames live on dodge-iframe. Do not fake a parry with juice only.
+ description: Use when blocking or parrying needs explicit input windows, guard arcs, chip/guard-break rules, and deterministic same-tick interaction with incoming attacks.
---
# Parry and guard
- Ask the column:
+ Choose the defense model:
| Column | Input |
|---|---|
- | hold-block | hold reduces or negates |
- | tap-parry | short window, punish |
- | both | block default, tap is parry |
- | none | dodge only |
+ | hold-block | held state with published damage/reaction rules |
+ | tap-parry | short authored success window |
+ | both | held guard plus an explicit parry window |
+ | none | no guard/parry mechanic |
## Rules
- 1. Windows are frames on the defense move, same clock as action-feel.
- 2. Chip, guard-break, and chip-kill are published or absent.
- 3. A successful parry is a state the attacker enters, not a screen flash.
- 4. Lost focus releases a held block.
- 5. A back attack ignores guard unless the column says so.
+ 1. Guard/parry windows use the same published logical clock as combat.
+ 2. Contact eligibility is evaluated at the contact tick before applying reaction effects; same-tick attack/defense transitions follow the project's declared priority rule.
+ 3. Chip, chip-kill, guard damage, guard break and stamina cost are explicit data or explicitly absent.
+ 4. Guard direction uses a published arc/facing rule. Do not universally make “back attacks” unblockable; the selected arc decides.
+ 5. A successful parry causes authored logical states/reactions, not only a flash or sound.
+ 6. Focus loss or device reset cannot leave a synthetic held-block input stuck.
+ Invulnerability belongs to `dodge-iframe`; persistent poise belongs to `poise-stagger`.
+
## Accept
- A tap outside the window is a late block or a hit, never a secret auto-parry.
+ Test contacts one tick before, at both parry boundaries and one tick after, including simultaneous attack/guard transitions and multiple attack classes. Reversing actor iteration order must not change the outcome. The debug view shows guard arc, window and resulting logical state without relying on juice.