Elements, BREAK and safe testing
Element advantage and BREAK are related combat decisions, but they are not the same measurement. Test them separately before claiming a team is stronger.
Create a clean comparison
Use the same target, level range, form and teammates. Change only the candidate or element being tested.
- Record time to first BREAK.
- Record damage during the punish window.
- Record whether the rotation survives a missed dodge.
Read the result
A quick BREAK can be more valuable than a larger isolated hit if it creates a repeatable team window.
- Bosses: prioritize predictable openings.
- Exploration: prioritize low setup cost.
- PvPvE: value control and escape alongside damage.
Patch-safe conclusions
Write “in this encounter, on this build” rather than turning one test into a universal tier claim.
- Keep the date beside the result.
- Retest after official balance notes.
- Move uncertain records to WATCH rather than forcing a rank.
Field note template
✓
Keep observations reproducible
Write down your region, test build, Aniimo form, level, teammates, target and result. A useful beta note explains its conditions.