Skip to article

AneeMate joint attacks: when your awakened companion joins in

QORPO Studio · 18 November 2026 · 4 min read

Ginbu poised on an island trail with frost sparks curling beside its crystals
Concept illustration created for this article, not a gameplay screenshot.

In AneeMate’s 0.1.5-ce release, breaking a robot or landing a perfect dodge can bring your awakened AneeMate into a joint attack. The companion appears beside the enemy in a burst of its element, with a comic-style panel framing the shared moment.

These are the triggers described in the 6 November weekly report. The report does not provide a universal timing window, damage formula or complete progression checklist. This guide explains what to look for without inventing those details.

Begin with the companion state

The documented description refers to an awakened AneeMate. Check the state and information displayed by your current game before expecting a joint attack from every companion.

If you are still learning progression, the evolution readiness guide is a useful related read. Do not assume that similar words in different systems establish identical requirements.

A clear starting state makes practice easier to interpret. If the expected companion state is uncertain, a missing joint attack cannot yet be attributed to dodge timing or the enemy’s behaviour.

Two documented opportunities

The release describes a robot break and a perfect dodge as opportunities for the awakened companion to join. Practise one sequence at a time so you can identify which event happened.

For a dodge-focused attempt, observe the incoming attack and the game’s response to your timing. A roll that avoids damage is not automatically proof that the game classified the action as a perfect dodge.

For a robot-break attempt, watch for the break event and the companion’s arrival. Keep the sequence distinct from a normal hit or an enemy defeat, unless the game itself clearly identifies the relevant state.

Watch the sequence as a whole

The useful observation is the connection between the triggering moment, the companion appearing beside the enemy and the framed shared attack. A single still image may show the panel while hiding what caused it.

If you record practice, start before the incoming attack or break. Continue until the companion response finishes. That makes it possible to discuss the whole sequence rather than infer it from a dramatic frame.

The elemental burst is part of the release description. It is not a basis for claiming that all companions have identical damage, range or additional status effects.

A model practice session

Imagine a hypothetical player who checks an awakened companion and chooses a manageable robot encounter. The player focuses first on recognizing the robot’s incoming attack, then attempts a dodge and watches the resulting feedback.

After an attempt that the game identifies as perfect, the player looks for the companion arrival and shared panel. If the sequence occurs, they have one observed example of that interaction.

If it does not occur, the next useful step is to record the starting state and full sequence. Changing companion, equipment, enemy and session role all at once would make the result harder to interpret.

Keep staff handling separate

The same update improves turning after attacks and animation blending. It also fixes a dodge roll accidentally cancelling a charged staff attack. Those are related combat changes, but they are not a complete definition of the joint-attack trigger.

Our staff mastery guide covers the broader weapon context. The staff blink guide addresses another distinct mechanic.

Learning those systems may help you plan an encounter, but this article does not combine their requirements or promise that a particular equipment sequence guarantees a joint attack.

Choose practice that leaves room to observe

A crowded fight can make it difficult to tell whether a break, dodge or companion arrival happened first. Use a manageable situation when learning the sequence, then apply that understanding to busier encounters.

Avoid judging the mechanic only by whether the enemy loses a large amount of health. The first question is whether the documented event and response occur. Damage comparisons require a controlled setup and more information than the release note supplies.

This approach also keeps practice useful after equipment changes. You can recognize the intended sequence without assuming that one damage number is the definition of success.

Common questions

Does every dodge trigger a joint attack?

The report names a perfect dodge, not every dodge. It does not publish an exact timing window. Use the current game’s feedback and avoid relying on an invented number of frames.

Does the companion need to be awakened?

That is the state explicitly named in the release description. The note does not establish that every companion in every state can perform the same sequence.

What if the sequence seems inconsistent?

Record the build, companion state, trigger you observed and the full action sequence. Include whether you hosted or joined if the attempt was in co-op. These details describe the case without guessing at a hidden cause.

Is the article image an actual joint attack?

No. The hero is labelled concept artwork. Use the game itself and official gameplay material to judge the actual animation, panel and effects.

Explore AneeMate gameplay for the wider adventure, and use the tester feedback guide when a specific sequence needs investigation. A clear description of the moment is more useful than a broad claim that combat did not work.

Sources