Planning Tools Guide: Use the Build, Material, and Team Pages as a Workflow

The planning pages answer three different questions, and they work best in sequence. The team builder /team-build answers "does this rotation connect" from the apply-and-consume rules. The build planner /build-planner answers "what does this team wear" from compatibility, options, sets, and Runes. The answers "what does this team wear" from compatibility, options, sets, and Runes. The material planner /material-planner answers "what does all of this cost" from the cumulative upgrade ledger. Starting with the wrong tool wastes the session, so the workflow matters more than any single page.

The pipeline order is: team first, build second, materials third. A team that does not connect makes the build irrelevant; a build that cannot be afforded makes the materials the real constraint. Running the three pages in order turns every upgrade decision into a checkable sequence.

The weekly habit starts with the rotation. Open the team builder /team-build, re-verify the active trio's chain against the current roster and rules, and confirm that any new unlock did not change the edges. The builder reports which edge is missing when the chain fails, so the first fix is usually one slot, not a rebuild. When the rotation is confirmed, the team question is closed for the week.

The team question should be re-run after every unlock, patch, or respec, because the chain facts are computed from the current data. A connector that was optimal last week can have a cheaper route this week, and the builder shows it without spending anything.

Once the rotation connects, the build question starts: which equipment fits the team, which set thresholds the loadout activates, and which Runes support the same goal. The build planner /build-planner holds the loadout state—the five slots, the pieces, the enhancement targets, the Rune slots—and compares alternatives without spending materials. The build answer feeds the farm targets: a set piece, an option pool, an enhancement level.

The build planner also catches the cross-tool mistakes: a set that looks good in the database but conflicts with the team's statuses, or a Rune that boosts a stat the rotation never uses. Comparing the loadout against the chain keeps the two answers consistent.

The final question is cost. The material planner /material-planner merges the team's skill milestones, the build's enhancement targets, and any Karma or cooking goals into one shortage ledger, and the ledger is the farming schedule. The route for the shortages comes from the item database /items and the and the Orbis map /map, and the weekly loop feeds the rest. When the ledger shows a shortage with no documented source, that item becomes an in-game check rather than a planned yield.

The ledger is also the reality check. A build that looks perfect but costs three weeks of a shared material is a different decision once the number is visible, and the planner makes the number visible before the spend. The honest workflow ends with the ledger, not with the build.

The three pages work best as a single weekly review: team in the team builder /team-build, loadout in the build planner /build-planner, budget in the , budget in the material planner /material-planner, and the remaining questions routed to the databases and the map. The review takes minutes, and it replaces three improvisations with one plan. When the game changes—a patch, an unlock, a new content type—the same review re-runs against the current data, so the plan never outlives its facts.

For a brand-new player, the pipeline has a gentler entry point: learn one page per week. Start with the team builder /team-build until the rotation question feels natural, add the build planner /build-planner once gear decisions matter, and finish with the once gear decisions matter, and finish with the material planner /material-planner when the budget becomes the bottleneck. Each page is a lens on the same team, and the weekly review becomes a habit only after each lens is familiar—trying to master all three in one session usually ends with none of them used.