The official Steam page confirms that DragonSword : Awakening has 19 Heroes and highlights Active Skills, Signal Skills, Status Ailments and switching. Players therefore need more than a name list. They need a way to understand what a hero contributes to a party and a way to notice when a public roster claim is not yet verified. This guide provides that method while keeping the full roster and role fields open for later evidence.
Start with a roster record
For every hero you can inspect, record the exact displayed name, where the hero appears, the date, the current level, the basic attack pattern and the wording of every visible active or signal-related skill. Add a short observation about range, recovery and the enemy type you tested. Leave a blank field when the interface does not explain an effect. A blank field is more useful than an invented value because it tells the next editor what evidence is still missing.
The public total of 19 is a useful completeness check, not a license to copy a third-party table. If a community page lists fewer or more names, compare its date and product scope. It may include a demo, an update, an unreleased character, a mistaken translation or a different DragonSword product. Keep DLC and non-base products out of this base-game roster unless a future scope audit authorizes them.
Choose three different questions
Build a test party by assigning questions rather than tiers. The first question is entry: who can begin an encounter while you learn the enemy? The second is conversion: which available hero changes the target state after an Active Skill, Signal Skill or Status Ailment? The third is recovery: who lets you survive when the first plan fails? These are working role labels, not official class names.
Run one repeatable encounter with the same party. Note who starts, who enters after the first visible effect and who is active when you reset. If two heroes appear to solve the same problem, replace one and compare the result. If the party becomes weaker, do not immediately call the replacement bad; check whether the switching order or enemy choice changed the test.
Evaluate role fit in context
A damage-focused hero can be the wrong choice when an enemy punishes a long animation. A control tool can be more valuable in one room and less useful in another. A status effect can look weak on a resistant target. A Familiar or meal may change the outcome. Because the official public page does not publish a complete matchup chart, the page should explain the context behind a recommendation.
Use a compact note: “Useful when,” “weak when,” “evidence,” and “next check.” For example, a hero may be useful when you need a short control window, weak when the target ignores that state, supported by a current tooltip, and due for a test against a second enemy. This format avoids the false precision of a score while still giving a player an action.
How to use community roster pages
Recent independent pages are valuable for discovering searches such as best heroes, hero guide, tag team and party synergy. They may also contain details not visible on the public Steam page. Use the page’s date and links, compare its claims with the current game, and retain only the parts you can reproduce. A “S tier” label without a mode, version or test condition is a lead, not an answer.
Pay special attention to copied tables. If several pages use the same wording, they may share one unverified source. Independent agreement raises the priority of a fact to check; it does not turn it into an official fact. The site’s update process should preserve the original claim, the verification date and the reason for any later change.
Investment decisions
Before upgrading a hero, ask whether the character has solved the same problem twice, whether the skill text is understood, whether the material is shared, and whether a future roster change would leave the resource stranded. If the answer is unclear, spend only enough to learn the character. Lock or favorite systems should be used when available so a roster cleanup does not remove a tested project.
When replacing a hero, keep the old record. A character that is not useful for the current encounter may still answer another status, route or party need. The 19-hero count makes this historical record practical: it can become a search index rather than a ranking wall. If an official patch changes a skill, update the affected field and the test date rather than rewriting the entire roster from memory.
Roster FAQ
Does 19 Heroes mean a three-hero party?
The official page confirms the total and switching language, but this audit does not treat an undocumented party-size rule as official. Use the current party interface.
Can I copy a best-hero list?
Use it to choose a character to test. Verify the role, mode, date and current skill text before spending resources.
How do I compare two similar heroes?
Use the same enemy, route and preparation, change one hero, and record entry timing, control, survival and conversion rather than a single damage number.
Why are some roster fields blank?
Because the public product page confirms the total but not every hero field. Blank evidence is safer than a repeated unsupported claim.