A support is only strong when its effect activates for the party and improves the chosen fight. Public version 7.2 rankings highlighted several names, but later community update records reached v9.0.3. Use the historical list to find cards to inspect, then rank them with current card text and tests.
Historical support watchlist
The older highest group included Black Slime, Fallen Knight, Shinobi Cells, Orb of Dominance, and Slayer Mark. Another high group included Limitless, Galaxy, Vorpal Soul, Binding Light, Truck, Sky Drum, and Mech Contract.
Those names preserve a dated community snapshot, not a promise of current availability or order. A later rework, new attacker, or mode rule may change the result even when the support itself is unchanged.
Verify activation first
Read the support’s required ally tags, trigger, round timing, target, stack limit, and party restriction. Build a test party that satisfies every requirement. Enter a familiar fight and look for the effect indicator, stat change, summon, domain, mark, or other result described by the card.
If nothing happens, do not rank the support yet. Remove conflicting cards, check one-per-party rules, and confirm the unit is in the active party rather than only owned.
Measure team gain
Compare the full team’s result with and without the support. A support that contributes no direct damage can still be the best slot if it improves three attackers, accelerates activation, or enables a strong interaction. Conversely, a famous support can be worse than a third attacker when its condition is unmet.
Use completion time for farming, sustained damage for bosses, survival or checkpoint progress for towers, and win consistency under current Ranked rules. Change one slot at a time.
Account for stacking and restrictions
Do not assume two similar buffs stack. Read effect limits and watch the live indicators. Domains, summons, marks, revives, and other special effects may compete for space or allow only one source. The best individual supports may form a poor pair.
Write down the exact reason each support is present. If two cards claim the same job, test each alone and together. Keep the combination only when the additional slot earns measurable value.
Rank by content
For short Story farming, early activation and broad compatibility matter. For long bosses, scaling, repeated triggers, and sustained team gain can become more valuable. Towers may reward survival or a specific answer to floor behavior. Ranked requires a separate check because scaling, duplicates, traits, and bans can change.
Maintain content-specific labels instead of one global letter. A situational support is not “bad” when it is the correct answer to one mode.
Invest after the role is proven
Test at a small investment level first. If the support consistently improves the team, add levels, a compatible item, and eventually a trait if the current rules make it useful. Do not spend scarce rerolls just to match an old screenshot.
Preserve the baseline loadout and note the trait or equipment used in the test. This keeps future comparisons fair.
Create a personal support board
Group owned supports into universal fit, specific synergy, boss, farming, Ranked, needs development, and collection. Record a compatible attacker beside each specific support. Add the check date and current version if visible.
After an update, re-read activation wording before repeating the benchmark. Use Attacker Rankings for damage candidates, Card List to verify the current entry, and Traits before committing rerolls.
Use a support test matrix
For each candidate, record the compatible attacker, activation trigger, visible effect, time to activate, stack or party limit, and best-performing content. Test the deck once without the support, once with it, and once with the most plausible alternative. This reveals whether the slot creates team value or only looks impressive in isolation.
When two supports seem equal, prefer the one that works across more owned attackers or activates more consistently in the target mode. A narrow support can still rank first for one boss, but its label should state that scope. Keep an older working support until the new interaction is reproduced.
If a trait, artifact, Moon phase, or mode scaling changes the result, record that condition beside the placement. A transparent conditional rank helps another player test the same idea without pretending the effect is universal.