Use dated combat changes to refine a team, rather than building around a universal tier list or an assumed co-op combo rule. This page covers Just Dodge, hero-specific fixes, acquisition information and Hunt or Raid coordination, with clear boundaries between released behavior and version 1.1 previews.
- Start a team comparison with a question
- Build around observed skill conditions, not a guessed formula
- Include Just Dodge in your practice
- Separate control changes from hero balance changes
- Use the latest fix when testing Astria
- Choose heroes with acquisition and preview information
- Coordinate the activity, not an invented co-op rule
- Revisit advice when version 1.1 actually lands
1. Start a team comparison with a question
Decide what you want to improve: recognizing a Signal opportunity, staying oriented during a target switch or understanding one hero skill. Use heroes and abilities you can inspect in the current game. The store explains status-ailment tag-team action, but it does not prove a single best party or a fixed role assigned to every slot. Keep most of a familiar team unchanged while testing a new hero, so the result gives you useful information rather than several unexplained changes at once.
Sources: Steam store
2. Build around observed skill conditions, not a guessed formula
Read each Active and Signal Skill description and compare it with the prompts you see on the target. Applying ailments is part of the advertised combat system; claiming that attacks exist only to apply them, or that all damage scales identically with stacked conditions, goes beyond that description. If a combination seems unreliable, note which skill and target were involved. A specific failed interaction is more useful for learning or reporting a bug than deciding that an entire team archetype is automatically wrong.
Sources: Steam store
3. Include Just Dodge in your practice
The released 1.0.11 mechanic rewards a perfect dodge with one second of invincibility, three seconds of guaranteed critical hits, 10 percent Active Skill Rage recovery and half of the spent dodge stamina restored. Read the dedicated in-game Help entry and learn the trigger on a recognizable attack. The published effects make it a concrete practice target; they do not disclose an exact input window or guarantee that every delayed enemy hit can be ignored. Check later balance notes before treating these values as permanent.
Sources: Update Notes 1.0.11
4. Separate control changes from hero balance changes
The 1.0.11 lock-on redesign changes how you retain and select a target, while the same update also changes several hero actions. Aria moves from a five-hit basic attack to three hits and throws Air Bomb immediately when switching; Tarte can finish Lightning Shock when switched; Dana immediately summons Chako when switching during that action. Those details explain why an older video can feel different. Test the named skill on the installed build rather than attributing every difference to your equipment.
Sources: Update Notes 1.0.11
5. Use the latest fix when testing Astria
Update 1.0.12 fixes an unexpected Slide cooldown when the Blazing Lightning Master Skill is learned and fixes rotation during Slide. That is a narrow, hero-specific correction, not a buff statement for the whole roster. If an old discussion reports the cooldown behavior, compare its version with this applied note. A useful report includes whether the Master Skill is learned, the action attempted and the build. Avoid recreating a full team just to work around a fault already addressed by the patch.
Sources: Update Notes 1.0.12
6. Choose heroes with acquisition and preview information
The Hero Codex combat-style preview from 1.0.11 provides a way to inspect a character before deciding how to experiment. The 1.0.10 notes mention both quest and Exchange Shop acquisition, so progression involves more than an assumption that all 19 characters arrive in one automatic story sequence. Compare what is available to your account, read the source and try a role you can actually test. Paid cosmetic ownership should not be confused with a claim that the no-gacha game requires random character purchases.
Sources: Update Notes 1.0.10 / Update Notes 1.0.11
7. Coordinate the activity, not an invented co-op rule
Current multiplayer notes name Hunt and Raid, with a party-leader Retry after a clear or wipe and warnings when versions differ. Agree on the activity and difficulty, keep builds compatible and let the leader handle retries. These are verifiable coordination points. The notes do not establish that two players using Signal Skills cancel one another, nor that the entire story can be explored together. Describe a specific interaction if you encounter one, instead of enforcing a supposed universal builder-and-finisher split on every group.
Sources: Update Notes 1.0.11
8. Revisit advice when version 1.1 actually lands
The October preview announces changes to critical-hit calculations, Sub-Options and hero balance, plus new Hunt features and Training Ground. Until the October 15 release, those are future changes, not instructions for a menu or damage formula available today. Keep a note of which build a team comparison used. When the patch is released, read the applied notes before importing old conclusions; a reproducible test on one balance version may need another test after the formula changes.
Sources: [Video] Version 1.1 Update Preview Video Now Available
| Change | What it helps you identify |
|---|---|
| One hero slot | The effect of that hero on a known encounter |
| Control bindings | Differences caused by lock-on input changes |
| Same build across a party | Version mismatch before a co-op attempt |
A useful team recommendation names its game build, skill conditions and activity. Without those details, a confident combo claim is difficult to verify.
Related guides
Use observed skill conditions, current Just Dodge and hero-specific patch notes to refine combat. Coordinate Hunt or Raid retries and versions, and retest balance conclusions after an update rather than presenting previewed formulas as live behavior.
Sources checked October 11, 2026. Published facts are linked beside their explanations; testing and teamwork suggestions are editorial advice, not verified optimal builds.
Comment
No comments yet. Be the first to post one.