Tag Chain Team Guide: Build a Three-Hero Rotation That Actually Connects
Learn how status application, Signal activation, slot order, and the connector hero determine whether a three-hero Tag route works in play.
Current Orbis version

What a working Tag chain needs
A Tag chain is a directional sequence: one skill applies a status to an enemy, and the next hero's Signal skill consumes that same status to fire. The verified roster shows eight chain statuses—Air, Down, Stun, Bleed, Fire, Poison, Shock, and Ice—and each hero only applies and consumes a subset of them. The chain works only when the applying hero's status matches what the receiving hero's Signal requires, so the skill bar must be read as a directed graph, not a list of keywords. The team builder /team-build evaluates exactly this direction for any three-hero line-up.
The middle slot carries the whole route. It must consume the status the opener applies and then apply the status the finisher consumes. Castella is a clean example: her Stun Blow applies Stun, while her Upper Blow consumes Down and applies Air. She can therefore sit between a hero that applies Down (such as Alex) and a hero whose Signal consumes Air (such as Aria), but only if the skills in question are unlocked and leveled.
Choose the opener and finisher from verified statuses
Start from the statuses each hero can actually apply and consume, then assemble the route backwards. Lute applies and consumes both Stun and Down, which makes him flexible as an opener or a connector. Theresia applies and consumes Bleed and Stun. Charlotte applies Poison, Air, and Down, and consumes Poison and Air. Roxy applies Bleed and consumes Stun and Bleed. Compare those directions against the finisher's Signal requirements in the hero database /heroes before committing materials.
A common failure is a roster that looks compatible on paper: both heroes mention the same status word, but neither skill applies it to an enemy, or the receiving Signal is still locked behind a level or ascension step. The chain rules distinguish application from activation explicitly, and the team builder /team-build reports which edge is missing instead of guessing.
Treat the connector as the constrained slot
When two heroes chain but the third does not, keep the working pair and test replacements for the middle slot first. The connector needs two verified edges: an incoming link from the opener and an outgoing link to the finisher. Heroes that apply and consume overlapping status sets—Lute (Stun/Down), Ornette (Shock/Down), Kalsion (Fire/Air), Johnny (Poison/Air)—cover more routes than specialists that only push one status.
The same pair can also fail when both edges exist but the connector must use different skills for each side. A rotation that forces the connector to swap out before the finisher can respond is still broken in practice. Check the exact skill that applies and the exact skill that consumes on the connector page of the team builder /team-build rather than assuming any skill with the status word will do.
Verify the route in combat before investing
Skill data proves direction and requirements; it does not prove that a target stays alive, stays in range, or avoids interrupting the setup. Test a candidate chain against ordinary enemies at your current level: apply the opener, watch for the Signal prompt, and confirm the finisher fires before the status expires. Some statuses require stacks or extra activation conditions, which appear in the skill's published requirements. If the Signal does not appear, check unlock state first, then application, then target behavior—one variable at a time.
Before spending enhancement materials or Karma on a chain, use the build planner /build-planner to compare the same heroes with the planned equipment and Karma, and confirm the skill levels that unlock the required Signal are within reach. A route that needs an unaffordable ascension step is a different decision from a route that works today.
Fix broken chains with substitutes, not a full rebuild
When only one edge is broken, replace one slot instead of discarding the team. The hero database exposes which skills each candidate applies and consumes, so a substitute can be chosen for a specific missing direction. After swapping, rerun the same combat test and keep notes on what changed: slot order, skill level, or target behavior. The hero database /heroes and team builder /team-build together turn "this team feels weak" into a checkable list of edges and unlock requirements.
The note-taking is the part players skip, and it is the part that saves the most time. Write down which opener applied which status, whether the Signal prompt appeared, and what the target did in response—two lines are enough. After three test fights the pattern becomes obvious, and the equipment database /equipment and material planner /material-planner can be used to fix the real bottleneck instead of guessing at a new team.