Browse

Browse

All Heroes

Compare all 19 playable heroes by role, ability, status, and Signal coverage.

Hero database guide

How to compare heroes and plan a roster

Use the hero database to answer role, skill, Tag-chain, growth, and team-building questions with the current published records instead of a generic tier list.

Start with the job your team still needs

The hero list is most useful when the question is specific: who can start a Tag chain, who can react to a status, which hero attacks at range, or which role is missing from the current three-person team. Search by name when you already know the character. When you do not, combine role, attack type, applied status, activation condition, and Signal filters. Compare only heroes that solve the same problem. A damage dealer, connector, and defensive option may all be strong records, but they are not interchangeable candidates. The current catalog contains nineteen heroes, so two deliberate filters usually produce a shortlist that can be checked without hiding an important alternative.

Read complete skills, not summary labels

A hero card is an index, not a verdict. Open the detail page and read every skill level, the applied statuses, activation requirements, targeting language, and unlock level. For Tag planning, an effect that applies Airborne or Knockdown is different from a condition that merely requires that status. The database keeps those two statements separate so a requirement is not mistaken for an outgoing effect. Check whether the same skill both reacts and applies the next status, or whether the connector needs two actions. Also note that a valid text relationship does not prove animation timing, energy flow, cooldown alignment, immunity behavior, or damage. Those encounter-dependent questions still require an in-game test.

Open the team builder

Compare growth at the same target

Hero investment questions should be compared at an equal Awaken target, not by portrait rarity or an isolated maximum value. Each detail page exposes the published growth steps, required Gold, material quantities, and the records connected to those materials. Decide the next useful milestone first, then total every step up to that milestone. This prevents a cheap early upgrade from being compared with a complete late progression. When several heroes compete for the same resources, add each target to the material planner and inspect the combined shortage. The planner can account for quantities you already own locally, but ownership does not change the verified requirement shown by the game data.

Plan hero upgrade materials

Move from a hero choice to a legal build

After choosing a hero, verify the complete loadout rather than assuming every high-grade record is compatible. The build planner checks all five equipment slots, ability restrictions, set thresholds, Karma relationships, Rune choices, enhancement targets, and the Familiar slot. Start with the hero, add equipment that satisfies the published restriction, then inspect main-option candidates and set progress. Add Karma only after checking whether it is regular or bound to a particular hero. A Familiar is a separate team choice and does not create a skill Tag connection by itself. Saving one configuration per hero in the browser makes it possible to compare alternatives without overwriting a different character’s plan.

Configure a hero build

Use the database as evidence, not a ranking

The page answers what the current records publish: names, roles, skill text, levels, status relationships, equipment records, Karma links, and growth costs. It does not claim a universal best hero, calculate final encounter damage, predict balance changes, or know which characters and materials exist on your account. A hero with a valid Tag route can still be difficult to play, resisted by a boss, or unsuitable for a survival check. Revisit the filters whenever the team objective changes, compare equal progression states, and confirm live combat behavior in game before spending scarce resources. This evidence-first workflow remains useful after updates because changed rows can be reviewed without preserving an outdated tier-list conclusion.