Player-input comparison lab
Which build actually improves output?
Enter numbers from the same Showcase or Sandbox test. The calculator exposes its formula and downgrades confidence when conditions differ.
Build B versus Build A
+15.00%
Single-target attack-rate change
Directional
5/5 controls · min n=1
Single-target rate
200 → 230
Wave throughput index
200 → 230 (+15.00%)
Effective SPA
5s → 5s
Entered-window output
12,000 (60s) → 13,800 (60s)
Interpretation warnings
- !Time-window output assumes constant uptime and target density for the entire entered duration.
- !Fewer than three observations per build cannot earn a Controlled label.
The setup link contains numeric fields and comparison controls only.
Transparent formula
What the calculator measures
Single-target attack rate
Adjusted damage × expected crit × hits × placements ÷ effective SPA × uptime
This normalizes the entered attack cycle into a per-second comparison. Leave optional modifiers at zero when the live Damage or SPA panel already includes them.
Entered-window output
Single-target rate × seconds
This estimates output across a chosen boss or ability window. It assumes uptime stays constant, so it is a scenario model rather than a combat log.
Wave throughput index
Single-target rate × average targets hit
This exposes the value of AoE coverage, but remains an index because target density, overkill and time inside the attack area change throughout a stage.
Run a reproducible Anime Expeditions damage test
- 1. Freeze the baseline. Record the unit, level, evolution, in-match upgrade, Potential grades, trait, equipment, supports, placements and test target.
- 2. Change one thing. Swap only the trait, equipment item, Potential field or team support you are evaluating. Several simultaneous changes cannot identify a cause.
- 3. Repeat both builds. Use at least three observations per build before calling the comparison controlled. More runs matter when crits, targeting or spawn timing add variance.
- 4. Record the losing result too. A failed hypothesis is still useful evidence. Copy the generated record with its conditions and limitations instead of publishing only the largest number.
What the output deliberately excludes
- • Enemy defense, resistance and elemental interactions
- • Random critical-hit outcomes around the expected average
- • Damage-over-time tick intervals and status caps
- • Summon travel, spawn and targeting behavior
- • Active-ability cooldowns and changing buff windows
- • Animation delay, projectile travel and missed attacks
- • Overkill and enemies leaving range
- • Economy cost and the wave when a build becomes affordable
Those exclusions are why the output is called an attack-rate estimate and throughput index—not a claim about exact stage DPS. Critical chance produces an expected average; it cannot predict the result of a short run.
Use it with the rest of the decision stack
Choose a documented kit in the unit finder, expose missing roles in the team builder, use the Stat Potential advisor to select one field to test, and compare the observed before/after build here. When the real objective is rewards per hour rather than combat output, switch to the failure-adjusted farming calculator.
Sources and evidence boundary
The verified Roblox listing by Expeditions Entertainment confirms the broad wave-defense, unit-upgrade and boss loop, but does not publish a complete stat database or universal damage formula. Current community coverage describes a Showcase or Sandbox environment for observing units, including the Sandbox guide and beginner walkthrough. Trait vocabulary and SPA direction were checked against the illustrated All Things How trait guide. The formulas, confidence rules and record format are original and regression-tested; they are not official game mechanics.
Frequently asked questions
How do I calculate Anime Expeditions DPS?+
For a transparent baseline, multiply displayed damage by landed hits and placements, divide by SPA, then multiply by target uptime. Optional damage, SPA and crit fields can model modifiers that are not already reflected in the live panel. Treat the result as an attack-rate estimate because many game mechanics remain outside the formula.
Should I enter a buff when displayed Damage already changed?+
No. If the live Damage or SPA value already reflects a buff, enter that displayed value and leave the matching optional modifier at zero. Adding it again would double count the effect.
Is lower SPA better in Anime Expeditions?+
Current illustrated trait reporting describes a lower SPA as faster attack timing. Verify the live unit panel after balance changes.
Why does the calculator ask for average targets?+
A single-target comparison ignores AoE coverage. Average targets creates a wave-throughput index, but it is not exact total stage damage because enemy density changes.
What is included in a shared setup link?+
Only the two builds' numeric calculator fields and five comparison-control choices. Unit names, scenarios, dates, patch notes and other free-text test notes are not placed in the URL.
Does this tool save my unit data?+
No. Inputs and calculations stay in the current browser page. Clipboard buttons run only when pressed; the setup-link button creates a URL from numeric fields and the test-record button creates a plain-text evidence record.