The Anime Vanguards Summon screen is the only reliable snapshot of the banner you are about to use. Pools, rates, featured units, pity, prices, and timers can change. Read every live panel before spending Gems or tickets, then pull for a team job your account needs rather than for rarity alone.
Banner inspection checklist
Screenshot the banner and balance before a large session. If any pity or guarantee text is unclear, stop rather than testing it with the entire wallet.
Choose a target by role
List what blocks progress: affordable opening, scalable carry, support, control, economy, element, or mode mechanic. Compare the current pool with that list. A highly ranked damage unit may add little to an account with several carries and no support.
Check the target’s final form and acquisition chain. A base unit whose useful evolution requires a closed event item is not equivalent to the finished tier-list form. Review Unit List and the live Evolve panel before committing.
Set a Gem reserve
Choose a hard balance floor that remains after the session. It should cover foreseeable account needs and protect against variance. Do not count future login rewards, quests, codes, refunds, or event claims until they are in the wallet.
Probability does not create a schedule. Even a displayed rate cannot promise the target within your preferred number of pulls unless the live pity text explicitly guarantees it. Stop at the reserve or after the intended target; excitement is not a reason to move the cap.
Process new units safely
Lock valuable pulls immediately. Match exact forms and Shiny status before selling, feeding, normalizing, transferring, or using duplicates. Read current collection and Codex benefits. Do not sacrifice the only copy to learn a system.
Test a new unit at a controlled upgrade and stage before rerolling traits or transferring stats. New-update showcase rankings may use perfect builds and supports. Your first task is to establish the unit’s role and accessible progression path.
Review the session
Record starting balance, ending balance, pulls used, visible pity before and after, units obtained, and the exact banner date. Lock every keepable unit and verify inventory before selling duplicates. If the recorded pity does not match expectations, stop and re-read the current rules.
Do not immediately reroll, transfer, or evolve every new result. Compare each pull with the missing-role list, choose one build project, and preserve resources for it. A summon session is successful when it improves a plan, not merely when it produces a rare animation.
Decide whether to skip
Skipping is a valid banner outcome. Skip when the pool lacks a missing role, the useful form is not realistically evolvable, the timer conflicts with a better confirmed goal, pity behavior is unclear, or spending would break the reserve. Existing accessible units can often solve progression with better placement or one finished evolution.
Create a short target sheet: unit, exact form, role, current source, evolution path, acceptable alternatives, spending cap, and stop condition. If the live banner does not match the sheet, close it. This protects Gems from presentation changes and launch hype.
Summon error checklist
If a pull result, balance, or pity display is unexpected, stop. Confirm the correct banner and currency, wait for the interface to update, reopen inventory, and capture before-and-after values. Do not repeat the purchase to test the issue. Use official support routes for unresolved paid-currency or delivery problems.
Summon FAQ
Should I pull whenever a Mythic appears?
No. Confirm the exact pool and whether the unit fills a needed role with an obtainable final form.
Does pity carry between banners?
Only rely on the carry behavior stated by the current Summon interface. Do not import rules from another banner or old update.
Are multi-summons luckier?
Use the rates and guarantees shown in the client. Button size or bundle presentation alone does not prove different odds.