Equipment Build Guide: Plan Five Slots, Sets, Options, and Runes

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 loadout has five body slots. Compatibility, set progress, candidate options, enhancement, reroll locks, and Rune values answer different questions and should remain separate. Equipment.

The build planner answers a loadout question before materials are spent: which Head, Chest, Leg, Hand, and Foot records are compatible with the chosen hero, and what official options can each selected piece actually roll? Begin with the hero because ability restrictions determine which equipment remains usable. Then decide whether the goal is completing a set threshold, checking a main-option pool, planning enhancement, socketing a Rune, or testing an exclusive Karma. Keeping that goal explicit prevents an attractive but incompatible piece from becoming the basis of the plan.

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. Build Planner.

Build the queue one target at a time, then enter quantities already owned. Required, owned, and remaining values stay separate so a local inventory edit cannot change the verified source requirement. Shared materials from multiple targets merge into one ledger row, while Gold is summed across all included steps. The Eileen and Cliffside regression example demonstrates the expected behavior: common items are aggregated once, and changing either target immediately recalculates the total and the shortage without rewriting the underlying costs.

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. 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.

Use source labels beside missing items to decide what to inspect next, but read them at the level of certainty actually published. A named source is evidence that the item is associated with that source; it is not a promise of a particular drop rate, shop stock, event limit, or shortest route. Every growth step keeps its hero, Karma, materials, and Gold connected through player-facing names. Local inventory is stored on the device and can be cleared with confirmation without altering the published requirements. Equipment.

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. 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.

The most useful comparison is between competing upgrade queues. Check whether two targets share expensive materials, whether finishing one lower step unlocks an immediate benefit, and whether the current inventory covers a complete milestone rather than a fraction of several milestones. Removing or lowering a target shows the opportunity cost immediately. The tool can expose a concentrated shortage, but it cannot decide how valuable that upgrade is for your team, calculate stamina, or choose an optimal farming route without verified availability and reward evidence. Items.

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. Build Planner.

Before farming, review every target, final step, Gold total, owned quantity, and remaining row. Follow the item page for detailed sources and the build or Karma page for the reason the material is needed. Update inventory after crafting or spending so the shortage remains useful, and rebuild the plan when the published material costs change. Keep live rotations, random drops, shop limits, event schedules, and account-specific bonuses outside the calculation unless they are confirmed in game; the planner is a deterministic budget, not a loot forecast. 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.