Match the kit to the problem before chasing a letter grade.
What this tier list can tell you
The role notes below compare published kits, not measured combat performance. Official character pages still carry a development disclaimer. Rarity, live balance and upgrade costs have not been independently verified; no S/A/B scores are assigned. These notes are not a complete roster.
How we evaluate characters
For early progression, we prioritize reliable activation, ease of use and the ability to cover a team weakness. For competitive play, a future ranking needs matchup evidence, counterplay and repeatable results. Neither context can stand in for the other. A score will require a named mode, patch, equipment and investment level.
| Context | What to compare | Evidence required |
|---|---|---|
| Early progression | Activation, survival, investment | Same encounter and upgrades |
| Competitive play | Matchup, counterplay, rotation | Repeated matches at known build |
Compare the exact variant
Record the full bracketed title, rarity shown in your client, ability progression and mode. Compare initial abilities with initial abilities. Final unlocks are a separate evaluation. If any identifier is missing, treat a comparison as provisional rather than merging characters with the same name.
Ichigo Kurosaki
[Substitute Soul Reaper]
Published kit: Arts 1 hits build an attack bonus. Consider him when you want a damage plan with a clear activation action.
Read official kit ↗Orihime Inoue
[Shunshunrikka]
Published kit: an entry debuff can reduce enemy Attack; her Mortal Blow reduces damage received by allies. Think endurance, not an assumed healing role.
Read official kit ↗Toshiro Hitsugaya
[Squad 10 Captain]
Published kit: critical damage activates an attack bonus and a Frostbite chance. Check activation reliability before treating that payoff as constant.
Read official kit ↗A practical selection example
If your current team fails because it takes too much damage, examine a defensive kit before adding another attacker. If it survives but cannot create pressure, inspect how the damage candidate activates its bonuses. This is our decision method, not a claim that any named lineup clears a particular stage.
Common mistakes
Do not turn a character announcement into a performance ranking. Do not use closed-beta impressions as release testing. When rankings disagree, compare their modes and investment assumptions before comparing their letter grades.
Compare reliability before peak potential
A useful comparison begins with the condition required for a benefit. An on-hit trigger, an entry effect and a return-to-Standby effect ask different things of the player. Consider how often you can make the trigger happen in the encounter you care about. A high ceiling with a condition you rarely satisfy is not automatically the better early choice. Conversely, a more demanding kit may become valuable when you learn its sequence. Record the reason for your selection, then revisit it when your execution or available teammates change rather than treating a tier letter as permanent advice.
Separate character ownership from investment
Owning a named character does not mean your copy matches a guide’s assumptions. Before comparing two recommendations, check the bracketed title, rarity, ability stage and upgrades. Ask whether the guide evaluates a fresh copy, a progressed copy or a final-stage kit. Our role table deliberately does not assign a rarity that has not been checked against the live client. If you have only one of the recommended options, the useful next question is how to use that kit well—not whether you must spend until a different character appears.
Why community rankings disagree
A ranking can prioritize easy progression, competitive matchups, favorite-character appeal or maximum investment. Those are different editorial choices. Ask the writer which they used and whether the evidence comes from a current client, a beta or a kit description. A collection of agreeing rankings can still repeat the same untested assumption. We use community discussion to find questions, then return to publisher material or reproducible tests for answers. That is why the role notes below are useful now even though a tested ordinal ranking remains unpublished.
Support roles at a glance
| Variant | Plan to examine | Question before choosing |
|---|---|---|
| Rukia / Squad 13 Lieutenant → | Attack an enemy with a Status Ailment to activate a team critical benefit. | Can you establish the condition when it matters? |
| Rangiku / Squad 10 Lieutenant → | Return to Standby to hand a critical benefit to the team. | Can your intended recipient take the field in time? |
| Sado / Brazo Derecho Del Gigante → | Use the specific Cover Change condition described by his Shield ability. | Are you evaluating a Cover Change or an ordinary switch? |
Publisher kit descriptions are subject to change. Verify live text and ability stage; no rarity or tested team ranking is inferred.
Sources
Official statements and our editorial advice are separate. These pages were read, not treated as evidence of hands-on play.