How Arab Wuwa Tests

1. Live game, current patch. Results are measured in the live game on the current patch.
2. Visible assumptions. Every ranking and comparison states the assumptions behind it.
3. Reproducible rotations. Damage results are tied to a written rotation anyone can repeat.
4. Version labels. When balance changes, affected results are re-tested and re-dated.

Each team is measured using defined rotations under the same calculation assumptions for everyone. The full calculation contract is published on the Team DPS page; this is the summary.

• Test target: a level 100 boss with 20% resistance and no Tower buffs; the only buffs applied are the ones the team's own characters provide.
• Build standard: every character receives the same standardized stat budget, using the best applicable Cost-4, Cost-3, and Cost-1 Echo assumptions: three Echoes each carry 8.1% Crit Rate, 16.2% Crit DMG, 8.6% in the character's relevant scaling stat, and 8.6% in the relevant damage bonus; the other two Echoes each carry 8.1% Crit Rate and 16.2% Crit DMG. The exact sequences (S0–S6), weapons, and refinements (R0–R5) are shown on every team.
• Measurement: every team is tested across three rotations. DPS is total damage divided by time, averaged across the three rotations, and each team also publishes its average damage, average time, and average difficulty.
• Playable rotations and Energy: rotations are designed to work in real fights, not only in theory. Energy requirements are checked, Liberation-dependent characters receive enough Energy Regen in the calculation to use their Liberation as intended, and adjustments are explained in each Team Note.
• Timing and execution: timing comes from actual gameplay testing. Clean runs assume no dodges, boss interruptions, or execution mistakes; animation cancels may be used where Concerto and Energy Regen requirements allow.
• Difficulty rating: each team carries a difficulty rating (Easy, Mid, Hard, or Extreme) reflecting execution demands.

Because conditions are equal for every team, performance differences come from composition, rotation, and kit synergy.

Rotations are submitted by the community, then reviewed and approved before publication. Published rotations include bilingual step-by-step actions and are the same rotations used for Team DPS measurements.

Studies answer focused questions, such as weapon options for one exact team. A weapon study locks one team and one rotation, tests the weapon combinations, and ranks every audited result by total damage while preserving its global rank. Weapons are compared at Rank 1 unless the study states a different rank.

Study numbers are scoped to their own question: they show differences between weapons inside one rotation, and they are not comparable with Team DPS page results. Each study documents its own setup, scope, and assumptions on its page.

Damage numbers are computed from in-game character multipliers and stats. The calculation data is maintained in a large spreadsheet and imported into the website format, and teams can change when a better rotation or strategy is found.

From Version 3.0, Tune Break damage is counted for the character who triggers it, while Tune Rupture damage belongs to the character whose kit supplies it. The full attribution rules are documented on the Team DPS page.

Player builds shown in leaderboards and community statistics require in-game proof and pass verification before they appear. Unverified submissions are not published.

In-game damage varies with execution, RNG (crits, Echo procs), and enemy behavior. Published assumptions exist so readers can judge results and reproduce them. When a result cannot be tested cleanly, the page says so.

Arab Wuwa is also built and tested by one person, so small mistakes can slip through, especially in character calculations and Team DPS. Feedback on anything is appreciated.

Questions about a specific result? Use the Feedback page or see the Corrections Policy.