Sets and Runes Guide: Activate Thresholds, Not Just Slots

Equipment sets grant their bonuses at piece counts, and the current catalog uses the two-piece and three-piece pattern: two pieces grant a stat bonus, three pieces add a conditional effect. An item that belongs to a set contributes nothing until the threshold is met, so a half-set is a set that does not exist. The equipment database /equipment shows every set, its piece thresholds, and its exact effects, including the conditional ones.

The conditional effects deserve a close read because they define when the bonus applies. The current sets include effects that trigger on tagging, on status application, or on other combat events, and each has a duration. A three-piece bonus that triggers on tagging only pays for teams that tag often, so the set's condition must match the rotation's rhythm.

The set choice starts from the team's statuses and cadence, then flows down to slots. A Stun-damage set belongs to a Stun chain; a tag-triggered buff belongs to a team that tags frequently; a survival set belongs to a connector that keeps dying mid-chain. The team builder /team-build shows the rotation, and the equipment database /equipment lists the sets, so the match is visible before any farming starts.

Mixed sets are often the efficient midgame answer. Two two-piece bonuses that both trigger are usually worth more than a three-piece bonus that does not, and the build planner /build-planner shows the comparison with the actual pieces. The set decision should also consider the option pool on the available pieces: a perfect set with a bad pool loses to a mixed pair with the right stats.

Runes add a separate layer to equipment, with their own selection, replacement, and removal rules, and some slots require specific Runes to unlock their full value. The Rune layer multiplies the loadout: the same five slots carry both the set progress and the Rune effects, so a Rune decision should be made after the set decision, not instead of it. The equipment database /equipment and the Rune tools on the equipment pages show what each slot accepts.

The practical order is: settle the five-piece set progress, then fill the Rune slots that support the same goal. A Rune that boosts the chain's status damage compounds the set bonus; a Rune that boosts an unused stat does not. When Rune materials are shared with the rest of the budget, the material planner /material-planner shows the cost of both layers together.

Farming a set is a milestone with a countable cost: the pieces, their option pools, the enhancement target, and the Runes. The item database /items and the Orbis map /map show where the pieces drop, and the show where the pieces drop, and the material planner /material-planner merges the set cost with every other upgrade target. Before starting the chase, confirm that the finished set outperforms the current loadout at the same material cost—the merges the set cost with every other upgrade target. Before starting the chase, confirm that the finished set outperforms the current loadout at the same material cost—the build planner /build-planner answers that comparison without spending anything.

If the set's best pieces are locked behind content the team cannot clear yet, farm the accessible pieces first and run the set's two-piece bonus in the meantime. A partial set that triggers its threshold beats a full set that sits in the inventory.

Set value shifts with content: a set that was perfect for story fights can be wrong for Raids, Hunts, or the Tower of Trials, where the conditions and survival needs differ. When the team moves to a new content type, re-run the set question—thresholds, conditions, Runes—against that content's demands. The equipment database /equipment and build planner /build-planner keep both sides current, and the keep both sides current, and the boss database /bosses shows what the new content actually requires.

Do the comparison in the planner before farming, because the set chase is a sunk-cost trap. A three-piece set that took a week to assemble can lose to a mixed pair the moment the content changes, and the build planner /build-planner shows both loadouts side by side with the same enhancement assumptions. When the comparison says the mixed pair wins, farm the missing piece of the pair instead of defending the old set—the item database /items shows where it drops, and the shows where it drops, and the Orbis map /map turns the farm into a route.