Tools
Every tool reads the same database the wiki uses — no login, no backend. Pick a question, get the answer, follow the link into the underlying page to verify the full context.
Pick a hero and get a focused build: equipment, skill priority, rune focus and team composition, all read from the current-patch catalog.
Line up any two or three heroes in one table — baseline stats, community tier, slot-by-slot skills, signature gear and build guidance. Shareable link.
Type a material and see every campaign stage whose recommended level brackets it, sorted by closeness.
Pick the material you need and get a single “safest” stage with reasoning, plus a recommended hero.
Submit 3× Tier 3 items to roll 1× Tier 4 item of the same category.
All seven days of the Cube rotation, lined up so you can pre-stage inputs for the recipes that fire later in the week.
How these tools fit together
1. Pick the question, not the page
“What does this hero need?” → Build Planner. “Which stages bracket this material tier?” → Drop Finder. “Where should I test first?” → Farming Optimizer. “What should I do in the Cube today?” → Today.
2. Verify on the detail page
Every result links to the matching database entry so you can inspect the recorded level, difficulty, boss and source context before testing a run.
3. Cross-reference the guides
Tools answer a single question. The guides explain the meta around that question — when to spend, when to save, when to skip.
Built for accuracy
All tools are pure client-side reads of the public wiki data — no accounts, no tracking, no rate limits. The underlying numbers are reviewed against the current public snapshot on each patch update.
