2026-08-18
Clear and re-enter your observations after updates that change how a Hero performs.
Score only the Heroes you enter. The result is your weighted comparison, not an official or community ranking.
Enter your own Hero labels, choose early progression, farming, challenges, co-op, support, carry, or a custom use case, then weight clear speed, survivability, utility, access ease, growth, and staying value. The result is your comparison, not an official roster ranking.
Clear and re-enter your observations after updates that change how a Hero performs.
Compare picks by clear speed, survival, unlock cost, support value, replacement risk, and late-game scaling.
The current exact-game Hero roster and comparative results are not available, so this page does not invent either.
Score every positive dimension from 1 (weak for your use case) to 5 (strong). This is your local comparison, not an official ranking.
Enter at least one Hero label and one score to create your comparison.
Weight access ease, survival, and replacement risk using what you can observe.
Weight clear speed and staying value using your measured repeat runs.
Weight utility and survival, then move your labels into the Squad Planner.
Use your local comparison as one input, then organize roles without assuming official synergy or an optimal team.
Open the Squad Planner to arrange the labels and roles you chose.
WikiUse the entity notes page to record fields before treating an observation as reusable.
ReferencesCheck the current game and update context before carrying an old observation forward.
Pick one task before scoring: early progression, repeated farming, challenges, or co-op. Score only what you have personally observed. Clear speed asks how quickly the Hero completes the same repeatable test. Survivability asks whether the Hero remains usable through that test. Utility covers visible help such as control or support, while access ease reflects the cost and effort you actually faced.
Use equal weights for a neutral first pass. Raise a weight only when that dimension matters more for your current task, and use zero to exclude something you cannot observe. A tied score means the available observations do not separate the entries; it is not a reason to invent a hidden tiebreaker. Re-enter scores after updates because a local result can become stale even when the Hero label stays the same.
Turn the comparison into a lineup in the Squad Planner. One high local score does not prove synergy, an optimal slot count, or an official role. Record why each label is present, which task you are targeting, and what replacement condition would make you reconsider it. That makes the plan useful without presenting unsupported Hero names or a fictional global meta.