Trait categories
| Trait type | Best use case |
|---|---|
| Damage traits | Best for boss DPS and units that stay on the field long enough to scale. |
| Speed traits | Useful when lane pressure or cooldown timing is the main failure point. |
| Range traits | Strong when a unit can cover more lane space or hit safer targets. |
| Economy traits | Good only if the mode gives enough time for the value to matter. |
| Special traits | Evaluate by unit role; a rare trait can still be wrong on the wrong unit. |
Trait Shard rule
Trait Shards should not be scattered across every unit you summon. Use them after a unit has a stable squad role and after you understand which mode you are trying to improve. Early accounts usually gain more from basic unit coverage than from gambling for a perfect trait.
Perfect Cubes are not normal reroll currency
Perfect Cubes sound tempting because they imply optimization, but the safest launch-week approach is to save them for units that remain useful after more banners, codes, and balance updates arrive.
How to match traits to roles
A damage trait belongs on a unit that regularly handles boss damage or high-health enemies. A speed or range trait can be stronger on wave-clear units because it helps them cover lanes before pressure builds. Economy traits should be tested only in modes where the extra value has enough time to matter.
When a rare trait lands on the wrong unit, do not assume it is optimal. Anime Squadron trait planning works best when the trait, unit role, and current game mode all point toward the same problem.