Unscathed RNG combat is best learned one turn at a time. Read the active Aura, available actions, target, element, displayed accuracy, and any cost or condition before confirming. Choose a dependable action, observe the enemy response, and change only one part of the team when testing an improvement.
World bosses and PvP are officially supported. Current guides describe Story and other fights as turn-based Aura battles, but exact formulas, team limits, action values, and mode rules must be confirmed in the live interface.
Prepare a legal team
Open the lineup screen and read the current slot and duplicate rules. Build with distinct jobs: a reliable lead, a different element or matchup option, and a flexible finisher or defensive answer. If the current mode uses another slot count, preserve the same role logic.
Inspect each Aura card. Record normal and critical actions, targets, accuracy, element, visible damage or effect, and conditions. Keep an accessible full-kit Aura over a rarer name that cannot fill a needed job.
Use Aura List for identities and Tier List for a provisional comparison.
Read the action panel
Before choosing, identify whose turn it is and which target is selected. Read every enabled and disabled action. A disabled control may indicate cost, cooldown, status, target, or mode rules rather than a broken input.
Use the dependable normal action to establish a baseline. Save a critical or lower-accuracy action for a situation where its expected value justifies the risk. Do not infer accuracy from animation or a single hit.
On mobile, scroll the panel and confirm the selected target before submitting. On desktop or controller, verify focus and confirmation so a navigation input does not become an unintended turn.
Use the observe, choose, verify loop
Observe the enemy element, health, visible status, and previous action. Choose the Aura and action that address the current problem. Verify the result: hit or miss, displayed damage, status, turn order, and the next available choices.
Repeat the loop. If the action failed, decide whether the cause was accuracy, element, timing, target, condition, or insufficient account support. Avoid changing the whole lineup after one unlucky result.
Record one reliable action per Aura before experimenting with a complete combo or build.
Test elements responsibly
Use the same attacker, action, defender, and account setup. Compare a claimed advantaged relationship with a neutral baseline. Read any weakness, resistance, or damage message produced by the client.
Repeat enough times to separate accuracy or critical variation from element effect. Do not publish an exact modifier from a small sample. The Element Chart records current reports and leaves unsupported relationships unknown.
Even before exact values are known, carrying multiple elements prevents one matchup from blocking the whole team.
Improve a failed encounter
If entry fails, inspect team legality and unlock state. If actions miss, review displayed accuracy and conditions. If damage is low, inspect element, equipment, skill tree, Gems, and Traits. If survival fails, improve coverage or defense before spending premium consumables.
Change one slot or account layer, then repeat the same fight. Keep the change only when it improves consistency. A high single hit does not prove the build is better.
Use routine content to fund upgrades. Preserve rare items until the route reaches the difficult phase reliably.
Move from Story to bosses and PvP
Story is the safest practice because the encounter can be repeated and compared. Build a low-cost clear before trying a world boss. For bosses, confirm current entry, phases, group rules, and rewards. Bring a lineup with sustained value and a backup element.
For PvP, expect the opponent to adapt. Avoid one-element teams and plans that depend entirely on one uncertain action. Define a lead, a response to a counter, and a second win route.
Use the Modes hub for separate preparation.
Record a useful combat result
Write the date, mode, encounter, Aura lineup, actions, elements, equipment, Gems, Traits, skill-tree focus, consumables, and outcome. Label exact facts as In-game verified only when directly observed.
Evidence status, checked 2026-08-22: bosses and PvP are Official. Turn-based Aura combat, Story, normal and critical actions, accuracy, and elements are Community corroborated. Team size, complete formulas, action values, turn order, status effects, and mode rewards need in-game testing.