Team Roles & Rotations

A role describes a job, not a tier

An on-field attacker uses the active Character’s field time. An off-field attacker leaves damage behind after switching. A support can supply healing, protection, buffs, application or Energy; several of these jobs may belong to the same Character.

Fischl can summon Oz and switch out. Bennett can provide healing and an ATK buff while another Character takes the field. These mechanics explain possible jobs; they do not establish one universally strongest four-Character lineup.

Put prerequisites before the damage window

A rotation is a planned ability sequence. Place required buffs, summons and auras before the attacks that use them. The order must also leave enough time for particles to reach their intended recipient.

For a Bennett–Xiangling sequence, Bennett can cast his Burst and Skill before Xiangling takes the field to collect Pyro particles and cast Pyronado inside the buff. Complete the rest of the order according to the actual teammates, cooldowns and available Energy.

A written order is a starting plan, not a promise that every enemy encounter lasts the same amount of time. Movement, interrupted casts and wave changes can require adjustment.

Build a repeatable loop

Check more than the opening Burst. When the planned loop restarts, are the important abilities off cooldown and charged? Does an off-field summon remain active for the intended window? Does a buff expire before the attacks it was meant to support?

If the loop fails, identify the limiting job. Adding ER addresses particle-based Energy income, not a cooldown that is still running. Adding another attacker may consume field time needed to collect particles or refresh a support effect.

Observed teams are context, not instructions

The Team Comp Finder reports admitted complete-team observations for a specific mode and phase. A frequent pairing is not evidence of a particular weapon, artifact set, rotation or optimal lineup.

Use Character guides to understand each job, then inspect the exact Kit for conditions. Use analytics to see what was observed in its stated context. Keep those questions separate when comparing teams.