Anime Vanguards trait pity is tracked on the individual unit copy, not as one account-wide bar. Current community documentation lists Mythic-trait pity at Monarch 1,500, Ethereal 858, Deadeye 400, and Solar 300 rerolls on the same unit. Open the live Trait Index before spending: thresholds and preservation rules are update-sensitive, and the counter shown for your selected copy is more important than an old chart.
Identify the exact unit counter
Lock the unit and note its displayed form, Shiny status, level, trait, and stat ranks. If you own duplicates, rename or favorite the target if the interface allows it. Select the unit at Mandra, open the Trait Index, and screenshot the pity display before the first reroll.
Rerolling another copy does not advance the original unit’s pity. This is the most expensive misunderstanding in the system. A total of 1,500 rerolls scattered over five units is not the same as 1,500 on one selected unit.
These are Community corroborated values checked October 21, 2026. They are not a promise that every future update keeps the same thresholds.
Understand chance versus guarantee
Pity is a ceiling for the named result, not a schedule saying you cannot roll it earlier. Each reroll still resolves independently under the current pool. Reaching a lower Mythic checkpoint can produce a useful stopping result before Monarch pity, depending on how the interface applies overlapping counters.
Do not calculate expected cost by multiplying only the displayed percentage. Your real budget includes the rerolls already stored on this exact copy, the trait you would overwrite, and the opportunity cost of not improving another role. A good Deadeye or Ethereal can be worth keeping when the account lacks the reserve to continue safely.
Make a reroll budget
Choose the target trait, a minimum acceptable stop, a reserve, and a maximum session spend. Count every reroll currency source currently available to you, but do not include a code or event reward until it is claimed. Leave enough resources to build the unit after the trait lands.
For an early account, spread functional traits across a farm unit, main carry, and support before forcing one prestige result. For a mature account, concentrate pity on the copy whose role and long-term availability are already secure. Never chase a trait on a unit you may replace before its evolution is finished.
Preserve pity through other systems
The community Wiki reports that evolving, Normalizing, and Stat Transfers do not reset a unit’s trait pity. Treat that as a current system rule, then verify the live confirmation screen whenever an action changes the unit. Trading is different: current trading documentation warns that traits and pities reset when a limited unit is traded.
Before evolution, normalization, transfer, or trade, screenshot the unit and its Trait Index. After the action, reopen the same copy and compare. Stop if the counter is missing or the interface selects another duplicate.
Reroll without losing the target
Confirm the selected portrait and current trait before every large batch. Do not click through a rare result because an auto-reroll filter was configured for another goal. If the interface provides stop conditions, test them with a small session first.
The pity bar should advance by the number of eligible rerolls you actually spend on that copy. If it does not, recheck the selected unit and server version. Do not continue hundreds of rolls while assuming a hidden counter is working.
Trait pity mistakes
- Splitting rerolls between duplicates while expecting one shared counter.
- Rerolling a useful trait without enough reserve to reach the next acceptable stop.
- Treating the 0.1% community rate as proof that Monarch must arrive near 1,000 rolls.
- Trading a unit without reading the trait-and-pity reset warning.
- Copying an old 2,500 Monarch threshold after the community documentation changed to 1,500.
- Counting unclaimed codes, shop stock, or future event rewards as available currency.
Trait pity FAQ
Is trait pity global?
No. Current documentation and player reports agree that pity belongs to each individual unit copy.
Does evolution reset trait pity?
Current community documentation says it does not, but confirm the live evolution preview and compare the counter afterward.
Should I always continue to Monarch?
No. Stop when the current trait solves the unit’s role and continuing would consume resources needed elsewhere. Read Monarch Trait for the placement tradeoff.