Quick Answer
- Patch 1.09 adds new skills for Oongka and Damiane.
- The input follows the same idea as Kliff’s Blinding Flash Finisher: heavy attack while using Blinding Flash.
- Test the timing in small encounters before using the new skills in boss rematches.
The most interesting combat note in Patch 1.09 is not just that Oongka and Damiane received new skills. It is that their input is tied to the same timing concept as Kliff’s Blinding Flash Finisher.
How to test the new skills
- Start with a low-pressure enemy group.
- Trigger Blinding Flash and use heavy attack during the window.
- Watch whether the skill changes positioning, stagger pressure, or recovery time.
- Repeat with a heavier enemy before trying a boss.
- Only then bring the skill into a Resonate rematch.
What to watch for
- Startup: how long the move takes before it becomes active.
- Recovery: whether the character is exposed afterward.
- Stagger value: whether the skill meaningfully pushes enemy posture.
- Camera behavior: whether the animation disorients you around large enemies.
- Spirit or resource cost: whether repeated attempts leave you dry.
Boss rematch use
Oongka and Damiane are especially worth testing in boss rematches because the mode lets you repeat familiar fights. Start with Reminisce if you only want to learn the input. Move to Resonate when you want to know whether the skill survives real pressure.
A clean test for a new character skill
Separate input discovery from balance conclusions. First reproduce the skill in a low-pressure encounter, then compare only one thing at a time such as range, recovery, positioning, or stagger. Keep the build and enemy type stable. If the move does not appear, note the character, ability state, distance, control method, and game version before drawing a conclusion. Repeat the successful input once after a save or area transition, because a one-off result is not yet a dependable route tip.
Patch advice stays useful when it separates a confirmed change from a player habit. Check the current game version and platform first, then test the feature in a normal activity rather than rebuilding an entire setup around one patch note. A small, repeatable test reveals whether the change matters to your own route.
Keep historical update pages dated. A feature may change again, arrive differently on another platform, or be described more broadly than it works in practice. The safest reading order is current official notes first, then this page for the practical way to try the system without wasting time.
When you find a difference, capture the useful context: platform, version, control method, area, and the action you tested. That turns a comment such as 鈥渋t does not work for me鈥?into information another player can verify. It also gives this page a clear path for correction when later patch notes change the original answer.
Before you move on
- Practice the input away from story-critical fights.
- Keep the build stable while comparing actions.
- Judge recovery and position before assuming a damage change.
- Check current official notes when input rules are updated.
