Parry and Deflect are two of the defensive techniques officially named for Onimusha: Way of the Sword. The safest way to learn them is to treat the current prompt, input device and enemy cue as the authority. Public announcements establish that both belong to the combat vocabulary; they do not publish universal frame windows, keyboard bindings or a final rule for every enemy. This guide gives you a repeatable test rather than invented data.
Identify the incoming action
Choose a single enemy in an open enough space that a second attacker cannot hide off-screen. Watch the wind-up, weapon line, sound and distance. Your first goal is not to defend; it is to predict when contact would happen. If you press a response before the cue is visible, you are testing a guess rather than the mechanic.
Use a short recording or written note if the platform permits it. Describe the cue in player language: overhead swing, horizontal cut, lunge, projectile, grab or area effect. Do not assume all blue, red or glowing effects represent the same response. A guide becomes reliable when another player can recognise the same action without a screenshot from a different build.
Test Parry without adding damage
Once the cue is familiar, press the current Parry input once and observe the result. Did the blades meet, did Musashi lose health, did the enemy stagger, or did the action fail because the attack was outside the expected range? Repeat the same exchange several times before adding an attack. This isolates timing from damage and prevents a lucky punish from hiding a late input.
If the Parry result changes with distance or angle, record that as part of the observation. If a prompt appears, write whether it is a tutorial reminder or a contextual action. Never call a response “perfect” merely because the animation looks dramatic; the player-facing effect is the important field.
Test Deflect as a separate answer
Repeat the experiment with Deflect when the build teaches or displays it. Compare the practical outcome with Parry: contact, enemy position, opening size, Musashi’s recovery and the next safe choice. The guide should explain what a player can decide after the action, not collapse both names into “press defence.”
Deflect may be more useful against a different type of pressure, but that must be established by the current game. Do not transfer a rule from a previous Onimusha or a Soulslike. If the demo presents only one training case, say that the evidence covers that case and leave the rest pending.
Choose evade when the answer is unsafe
An accurate Parry or Deflect is not always the right answer. A late cue, crowd, projectile, grab or poor camera angle can make an escape safer. Practice moving to a visible recovery point, then return to the defensive timing once the arena is controlled. A player who refuses to evade can lose to the second attack even after winning the first exchange.
If an input feels ignored, stop changing combat technique and record the technical context. Test a default layout, a second input device and a stable frame-rate scene before declaring the window impossible. Send a prompt or latency problem to Technical with the AppID and driver; keep the combat page focused on the decision.
Convert the defence into Issen or damage
After a successful response, wait for the opening the build actually gives you. Use a short strike if the enemy is close, an announced Issen opportunity if its cue appears, or a reset if another threat approaches. The best timing note says “after this action, watch for this opening,” not “always press this attack.”
Sources and check date
Source: Official Steam Community combat announcement
Source: PlayStation Blog: Parry, Deflect and Issen
Source: GamesRadar hands-on combat report
Checked 2026-08-09 UTC. Exact buttons and frame windows remain build-specific.