What's inside
As an Amazon Associate I earn from qualifying purchases. This post may contain affiliate links at no extra cost to you.
To parry in Broken Blade, tap the guard input (L1 on PlayStation, LB on Xbox by default) so the parry’s active frames overlap the exact moment an enemy attack connects — a window of roughly 200 milliseconds, or about 12 frames at 60 fps. A successful parry spends stamina instead of health and staggers the attacker, opening a short riposte opportunity. Miss the window and you take full damage, which is why parrying is a timing skill, not a button you hold.
The practical version: parry is a tap, not a block. Blocking is the safe default and costs stamina; parrying is the risky, higher-reward read that converts an incoming hit into your turn. Everything below is about making that read repeatable.
Sections
The parry window, broken down by press timing
The parry input has a short set of active frames at the start of the animation, followed by recovery frames where you cannot act. What matters is whether those active frames overlap the contact frame of the enemy’s attack. In practice, that gives you five outcomes:
| Your press, relative to impact | What the game registers | Result |
|---|---|---|
| More than ~350 ms early | Active frames expire, you’re stuck in recovery | Whiffed parry — full damage |
| ~250–350 ms early | Recovery frames overlap contact, guard not held | Full damage — the worst outcome |
| ~120–250 ms early | Active parry frames overlap contact | Clean parry — stagger plus riposte window |
| ~0–120 ms early | Active frames still running at contact | Parry, but tighter; heavier weapons may downgrade to a block |
| Any time after contact | Hit already resolved | Full damage plus hitstun |
That middle band is where you want to live. Note that pressing early is punished harder than pressing slightly late while holding guard — if you’re unsure, hold block and eat the chip damage rather than gamble on a parry. Exact frame counts shift between patches, so treat these as the shape of the window and confirm the current numbers in your build’s training area.
Reading enemy cues before you commit
Human visual reaction time averages about 250 ms, which means you cannot see a blade start moving and parry it in time. You are not reacting to the attack — you are reacting to the wind-up, and the wind-up is long enough to fit your reaction plus your input.
Wind-up length is the real difficulty dial
| Attack class | Typical wind-up | Parry difficulty | Approach |
|---|---|---|---|
| Quick jab / thrust | 0.25–0.40 s | Hard | Pre-input on prediction, or just block it |
| Standard slash | 0.50–0.70 s | Moderate | Press when the weapon clears the shoulder line |
| Heavy overhead | 0.80–1.10 s | Easiest | Wait for the drop, then tap — generous window |
| Delayed / feinted swing | 0.6 s feint + 0.4 s hold | Hard | Watch the shoulder and hip, not the weapon |
| Multi-hit combo | Varies per hit | Moderate | Block the string, parry only the final hit |
Audio and posture cues
Most attack animations telegraph through three channels at once, and you should train on all of them because they fail in different situations. The posture shift — shoulder drop, hip rotation, weight moving to the front foot — is the earliest and most reliable cue, and it’s the one that still works when a feint freezes the weapon. The audio cue (a grunt, a weapon hum, a foot scrape) is the fastest to process but the easiest to drown out during multi-enemy fights. The visual glint or color flash is the most obvious but usually appears late in the wind-up, which makes it a good confirmation cue rather than a timing cue. If an attack flashes a distinct color, treat it as a separate, non-parryable class and dodge instead.
The stamina math behind a parry
Parrying is not free. Every attempt costs stamina whether or not it lands, and a failed parry leaves you with no guard and no stamina — the single fastest way to die in Broken Blade.
| Action | Typical stamina cost | Notes |
|---|---|---|
| Successful parry | ~18 | Cheaper than blocking a heavy hit |
| Blocked hit | 22–26 | Scales up with attack weight |
| Whiffed parry | ~18 plus damage taken | The cost is the hit, not the stamina |
| Dodge roll | ~20 | Often the cheaper answer to fast attacks |
| Riposte follow-up | ~12 | Budget for it before you commit |
| Guard break | At 0 stamina | Any hit staggers you wide open |
A worked example
Say your stamina bar is 120 and regeneration kicks in at about 20 per second after a 1.5-second delay. A boss throws a five-hit combo over roughly six seconds. If you parry the first three hits (54 stamina) and block the last two (50 stamina), you’ve spent 104 — you’re sitting at 16 stamina with regeneration still locked out, and one more hit breaks your guard. The correct play is to parry the first two, block the third, then disengage during the recovery gap so regeneration restarts. That’s the trade-off in one line: parries are cheaper than blocks per hit, but a chain of them leaves you with no reserve.
Controller and keyboard inputs
| Platform | Default parry input | Notes |
|---|---|---|
| PlayStation | L1 (tap) | Holding the same input blocks; tap to parry |
| Xbox | LB (tap) | Same tap-versus-hold distinction |
| Keyboard / mouse | Right mouse button or Shift | Check your control settings — the bind varies by build |
| Steam Deck / handheld | L1 | Consider raising the dead zone on the shoulder button |
One setup change is worth more than an hour of practice: move parry off a trigger and onto a bumper, or off a face button onto a shoulder input. Trigger travel adds roughly 40–80 ms of dead zone before the input registers, which is a meaningful chunk of a 200 ms window. Test it by tapping the input as fast as you can and watching how the character responds — if the animation starts noticeably after your finger moves, the travel is costing you parries.
A 20-minute low-risk practice routine
- Five minutes against the slowest enemy you can find. You’re not trying to win; you’re trying to make the parry animation start on command. Reason: the first failure mode is input hesitation, not timing.
- Five minutes parrying only heavy overheads. These have the longest wind-ups (0.8–1.1 s), so they’re the only attacks where you can genuinely react. Reason: this calibrates your internal sense of “how long before impact do I press.”
- Five minutes on one specific attack from one specific enemy. Pick a single move and parry nothing else. Reason: pattern recognition beats general reflexes, and most players improve faster by memorizing one telegraph than by improving their raw reaction speed.
- Five minutes with the guard held, parrying only the last hit of combos. Reason: this teaches the stamina discipline from the worked example — you learn to spend stamina on the one hit that matters instead of every hit.
Track one number: how many of your ten attempts landed. If you’re under three, you’re pressing early — deliberately delay by roughly a quarter second. If you’re over seven but still taking hits, you’re pressing late and the parry is downgrading to a block.
Mistakes that make parrying feel random
- Mashing the input. Repeated presses put you in a loop of recovery frames, so a mash guarantees the parry window never aligns with contact.
- Parrying multi-hit strings from the front. Each parry has recovery frames, and a fast second hit will land during them.
- Ignoring the audio channel. Visual feints are designed to break visual timing; audio usually isn’t feinted.
- Parrying on low stamina. A whiff at 20 stamina isn’t just a missed read, it’s a guard break.
- Changing weapon and expecting the same timing. Heavier weapons typically have slower parry start-up and shorter active frames.
Frequently Asked Questions
How long is the parry window in Broken Blade?
Roughly 200 milliseconds of active frames at the start of the parry animation, which is about 12 frames at 60 fps. The window has to overlap the contact frame of the enemy attack, so your press needs to land somewhere between about 250 ms and 0 ms before impact. Heavier weapons tend to have a slower start-up, which effectively shortens the usable portion of the window.
Can you parry every attack?
No. Attacks that flash a distinct warning color, grab-type moves, and most area-of-effect strikes are typically non-parryable and must be dodged or blocked. Fast jabs with 0.25–0.4 second wind-ups are technically parryable but sit at the edge of human reaction time, so most players pre-input or block them instead.
Is parrying better than blocking?
Per hit, yes — a parry costs around 18 stamina and creates a stagger, while a blocked heavy hit costs 22–26 and leaves the enemy in control. But blocking never fails, and parrying fails hard. The efficient pattern is to block multi-hit strings and parry the single heavy hit at the end of them.
Why do my parries work in practice but not in boss fights?
Two reasons. Boss attacks often include delayed swings and feints, where the weapon pauses mid-animation to bait an early press — the fix is watching the shoulder and hip instead of the blade. Boss fights also drain stamina faster, so you’re attempting parries at low stamina where a whiff means a guard break rather than a simple missed read.
Should I rebind the parry button?
Yes, if you’re on a controller and parry is on a trigger. Trigger travel adds roughly 40–80 ms before the input registers, which eats a large fraction of a 200 ms window. Moving parry to a bumper or shoulder input is the single highest-value setup change for most players.
How do I practice parrying without dying repeatedly?
Use the training area or the weakest early-game enemies and give yourself a fixed 20-minute block split into four five-minute drills: input timing, heavy attacks only, one specific telegraph, and last-hit-only parries with guard held. Score each block out of ten attempts and adjust by a quarter second in the direction your misses suggest.