Tag Chain Team Guide: Build a Three-Hero Rotation That Actually Connects

Start with the question you need to answer, not with a copied endgame build. The useful route is the one that matches your unlocked roster, current inventory, and next playable objective. A valid Tag chain is order-sensitive: one skill must apply the status that the following Signal skill requires, and the middle slot must support both edges. Team Builder.

Players usually open the team builder to answer a rotation question: can one hero apply the status that the next hero needs, and can the middle hero continue that chain into the finisher? Start with the opener, connector, and finisher rather than three individually strong portraits. Barraging Spear, Shadow Grab, and Swordgrab illustrate why order matters: Airborne must be applied before it can activate the next skill, and Knockdown must exist before the final response. The useful output is a documented route, not a generic tier list.

Select one slot at a time and read both edges around the connector. Each valid edge names the applying skill, the matched status, the consuming or activating skill, and its first unlock requirement. If the first edge works but the second breaks, keep the opener and connector fixed while checking finishers; use the reverse approach when only the opening edge is missing. Substitute suggestions are valuable because they preserve the two choices you already want to play instead of rebuilding the entire party after one failed match. Heroes.

Fill the five slots in order and leave the picker on compatible records for the fastest workflow. Use Show all only when you need to understand why a specific item is disabled. After choosing a piece, inspect its main-option candidates, secondary-option candidates, enhancement target, reroll lock costs, and Rune socket. The Venomfog Shade Helmet example shows why these controls stay separate: an option displayed in the candidate pool is not a stat the item already owns, and a selected Rune roll is a planning input rather than a promised drop.

Treat names, requirements, relationships, counts, and displayed values as evidence. Treat live timing, random outcomes, account-specific availability, and unlisted triggers as checks that still belong in the game. A status requirement is never counted as a status output. Stack count, Transcendence, Master Skill, exclusive Karma, self-state, resource, and linked-summon requirements remain attached to the exact action variant that uses them. This prevents conditions from one variant being combined with the output of another.

The summary combines only published relationships and the choices currently made in the workspace. Set progress comes from equipped pieces; conditional set text remains conditional; exclusive Karma links stay tied to their supported hero; Rune values use the exact published roll selected in the socket. The verification row reports the current counts for equipment, sets, Karma, option entries, and Runes so the player can see the scope being searched. Probability labels describe candidate distributions and must not be converted into a prediction for one reforging or loot result. Team Builder.

Compare one constraint at a time. Keeping the same target while changing only the route, hero, slot, or milestone makes the cost of that decision visible and prevents several assumptions from being mixed together. A continuous status route helps plan who starts the exchange and who follows, but it does not rank total damage. Before investing in a new connector, check whether both relevant skills are unlocked, whether the order fits the encounter, and whether another hero can preserve the same status transition with fewer requirements. A route that is valid on paper can still be awkward when energy, cooldowns, animation time, enemy resistance, positioning, or survival interrupts it. Use the builder to narrow candidates, then test execution in the intended fight.

Compare builds by the constraint that matters, not by filling every visible field. For a set plan, check whether the threshold survives replacing one weak slot. For a main-stat plan, compare only pieces available to the same hero and body part. For a Rune plan, distinguish the socketed published value from random equipment options. Enhancement and lock-cost views help budget a target, but the interface does not calculate final damage or conditional uptime. A cheaper compatible configuration may be more actionable than a theoretical combination that depends on several missing rolls. Build Planner.

If a route fails, inspect the broken edge and its stack or progression requirement, then try a substitute for only that slot. Open the relevant hero skill to see all of its applied states and trigger conditions. A connected route still does not prove damage, cooldown, energy, resistance, or encounter timing. Heroes.

Before committing, reopen every selected piece and confirm the hero restriction, part, set, main option, enhancement step, Rune roll, and Karma link. If a piece is missing, move to the equipment database or material planner instead of inventing a substitute stat. Revisit the loadout when inventory or the published options change, because saved selections can remain understandable while their available alternatives evolve. The planner establishes compatibility and published values; actual drops, reforging results, combat rotations, resistances, and final performance still require in-game confirmation. Finish by writing down one next action that can be verified: open a named page, test a rotation, visit a mapped point, confirm an unlock, or update the local plan after spending materials.