Skip to article

AneeMate charged staff attacks: what the dodge-roll fix changes

QORPO Studio · 21 November 2026 · 5 min read

Ginbu watching a practice staff with a restrained luminous arc in an island clearing
Concept illustration created for this article, not a gameplay screenshot.

AneeMate’s 0.1.5-ce release report says a dodge roll no longer accidentally cancels a charged staff attack. The fix addresses continuity between those actions. It does not promise invulnerability, a guaranteed hit or identical timing for every encounter, so practise the sequence against a familiar situation before relying on it under pressure.

The report was published on 6 November 2026 and identifies its changes as live in build 0.1.5-ce. This guide, checked on 21 November, focuses on that one combat adjustment rather than treating every movement change as a new ability.

What was the interruption?

The useful distinction is between choosing a defensive movement and losing a charge unexpectedly. The release report places the fix alongside smoother turning and animation blending after staff attacks.

That is a narrow claim. It establishes the reported cancellation fix, not a complete description of every input window or every possible interruption. It does not say that enemy attacks cannot interrupt you, that a charge lasts indefinitely or that a roll guarantees a perfect dodge.

Approach it as a chance to make an existing sequence more dependable. Keep the exact controls tied to your current bindings rather than memorising a key from someone else’s recording.

Check the actions before combining them

Start with a familiar place where you can observe the staff without also navigating an unfamiliar encounter. Review your current attack and dodge bindings in Settings.

Perform a charged staff attack on its own, then a dodge roll on its own. Notice the cues you use to recognise each action. This gives you a baseline before the combined sequence introduces movement and a changed camera view.

The controls guide explains how to check bindings and conflicts. If a key triggers the wrong action, resolve that first. A binding problem can look like a charge problem when several inputs happen close together.

Practise one transition at a time

Begin the charge, use the roll at a deliberate moment and observe what happens when you return to the attack sequence. Repeat slowly enough that you can describe your order of inputs.

Change only the point at which you roll. Avoid mixing in a creature switch, a menu or a different ability while learning this transition. If the result changes, you want to know which action changed with it.

This is a suggested practice routine, not an instruction to use a fixed timing window. The public report does not provide a universal number of milliseconds for this sequence. The important observation is whether the charge disappears because of the roll itself.

A model practice note

Imagine a player who knows the charge cue but repeatedly rolls as soon as an enemy begins moving. They finish the roll unsure whether the charge remains, then release an attack without checking the target’s position.

A useful note separates three observations: the charge state, the defensive movement and the eventual attack. The roll can behave correctly while the attack still misses because the target moved. Likewise, an unsuccessful defensive choice does not automatically show that the cancellation fix failed.

This is a labelled example, not a report of our own play session. It describes how to make the result understandable instead of collapsing several events into “the combo did not work.”

Keep perfect dodges separate

The same release report mentions perfect dodges recognising close enemy-attack timing. That does not make every dodge roll a perfect dodge, and it does not make the charged-staff fix depend on a guaranteed joint attack.

Our awakened companion joint-attack guide explains that separate relationship. Learn the staff sequence first; then observe how it fits the particular encounter and companion state you are using.

The staff mastery guide provides the wider combat context. A narrow continuity fix is easier to appreciate when it supports a sequence you already understand.

What should a useful bug report contain?

If a charged attack still appears to cancel unexpectedly, record the installed build and your input order. Say whether the action worked without a roll and whether you were hit during the combined attempt.

A short clip should begin before the charge. Keep enough of the screen visible to show the character, target and relevant action cues. A recording that starts after the roll can hide the event that explains the result.

Describe what you observed before proposing a cause. “The charge cue disappeared immediately after the roll with no visible hit” is more actionable than “staff combat is broken.” If it happened only once, say that instead of presenting it as a repeatable failure. The testing feedback guide helps structure the rest.

What should you avoid assuming?

Do not turn charge continuity into a damage or survival guarantee. Position, enemy action and your chosen timing still matter. Nor does this note establish changes to an unmentioned ability, weapon or mode.

If the installed build is older than the documented fix, update through the official distribution route before comparing behaviour. If it is newer and behaves differently, include that version in feedback. A dated release report explains its own build, not every future balance decision.

FAQ

Does the roll now guarantee that the attack lands?

No. The fix concerns accidental cancellation, not target position or hit confirmation.

Is this the staff throw-and-blink unlock?

No. That is a separate ability described in the blink guide.

Did this article verify a new gameplay test?

No. It translates the released report into a bounded practice and reporting routine.

Sources and next step

The primary source is the 6 November report for build 0.1.5-ce. Check the gameplay guide, confirm your bindings and practise the transition before adding more actions.