Hero Roles & Class Notes
This page keeps class names, base HP, weapon types, and DLC status in one guide-oriented reading flow. The point is not just to show all six heroes, but to answer what you need most right now: safer progression, faster farming, team sustain, or boss burst.
This local page keeps `Knight / Ranger / Sorcerer / Priest / Hunter / Slayer` on one decision chain and links the hero page directly into Builds, Runes, Stages, and Gear instead of isolating class notes on their own.
How To Read Heroes
Hero pages are easy to turn into generic class summaries, but most players only need a few practical answers: should they add a front liner, a main carry, a healer, or a later high-pressure swap slot? Read by goal first, then move into actual builds.
At character creation, only compare `Knight / Ranger / Sorcerer` first. The key here is to settle a baseline setup, not to mix future DLC heroes into the opening three-choice decision.
This is the point where comparing how Ranger and Sorcerer carry efficiency is more useful than spreading investment evenly across every damage slot.
Free content does not mean limited choices. `Knight / Ranger / Sorcerer` are starter picks, while `Priest` is free DLC and can be deployed through `Hero Menu → Formation` after a restart.
Hunter and Slayer are closer to specialist tools than automatic shortcuts into endgame. First decide whether your goal is boss pressure or specialized efficiency.
Editorial Notes
The official store feature list keeps highlighting party composition, pets, runes, Cube, and idle farming together for a reason: class choice matters most when it fixes the job your current account is missing. That is the logic this page now pushes harder.
A good roster page should not flatten `Knight`, `Ranger`, `Sorcerer`, `Priest`, `Hunter`, and `Slayer` into six equal portraits. Their value changes based on whether you are still creating a character, stabilizing Formation, or testing boss-specific swaps.
Before Formation, players are mostly solving one-hero opening pressure. After Formation, hero value starts being measured by team jobs and recovery consistency instead.
`Knight` matters earlier when pressure is the problem. `Ranger` and `Sorcerer` matter more when the account can already keep a route alive and wants better throughput.
If the free baseline still collapses, `Hunter` or `Slayer` rarely fix the real cause. They pay off most when you already know whether the missing piece is burst, precision, or swap pressure.
Hero Explorer
This is not just six portraits in a row. Each card combines the class name, base HP, main and off-hand weapon types, access method, and next-step links so players can answer whether that hero fits the current goal immediately.
Ranking Lens
If this site wants rankings that survive real play, the missing bridge is not more hero adjectives. It is a cleaner split between hero job, map pressure, route purpose, and account maturity. That is what turns class notes into a usable ranking system.
A useful ranking starts by asking what the slot needs to do. Front-line safety, routine farming, sustain, and boss burst should never be flattened into one ladder.
A hero that looks amazing on an old farm map can look average on a collapse-prone boss route. Stage pressure changes what counts as strength.
A guide-oriented ranking should score a route by what it is trying to solve now, not by pretending every account wants the same outcome.
`Gear`, `Runes`, `Cube`, `Formation`, and pets are the main missing layer behind most bad tier lists. The same hero performs very differently before and after those systems stabilize.
Practical Workflow
The fastest way to ruin a hero ranking is to compare six portraits while silently changing the route, the map, the team shell, and the system baseline at the same time. A practical ranking has to lock those variables down first.
If you want this section to help real players, each ranking judgment should start from a repeatable route context. That means the map, team shell, and account state need to be visible before the hero verdict itself.
Use `Knight + Priest + Ranger` as the baseline when the account is still proving it can live through pressure. Compare survivability roles first, not greed upgrades.
When the route survives long enough, compare `Ranger` and `Sorcerer` inside a `Priest + Ranger + Sorcerer` style shell and judge long-session value instead of one pretty run.
If the real problem is `1110 / 1210 / 1310`, compare boss swaps like `Knight + Priest + Slayer` there. Boss value is easy to hide when you test on low-pressure farm maps.
Maps like `3309` and `4307` can be useful standards, but only for mature accounts. A high-end benchmark should not become the universal frame for beginners or midgame players.
Ranking Buckets
This is the practical split that makes the site's current hero, stage, build, and rune pages actually work together. Each bucket asks different questions and will naturally produce a different top tier.
Use this ladder when the account is still proving it can clear reliably. Here, stability outranks greed almost every time.
Use this ladder only after the route already survives. This bucket exists to improve value, not to rescue unstable progression.
This ladder exists for walls, not for routine idle. A hero that looks mediocre in farming can become top tier once boss pressure is the real question.
Use this ladder after the free baseline already works. It exists to judge whether a paid or niche slot fixes one specific account gap better than the current shell.
Adjustment Signals
This is the part most rankings skip. Players do not just need a list. They need to know which failure signal means the list should change.
Do not automatically drop the whole route into a lower tier. First raise the priority of safe-slot heroes and stability systems.
This is when damage, attack speed, and map-compression heroes start deserving higher placement than pure safety slots.
That usually means the farm ladder is no longer the right ladder. Swap to a boss lens before calling the current heroes weak.
Do not rerank too fast. That usually means the route assumptions changed underneath the hero comparison.
Role Ladder
Most users are not here to memorize a roster chart. They want to know who they should pick right now. This section gives four practical class-reading paths based on real goals.
Team Matrix
A hero's value is never only about raw strength. It depends on what job that hero performs inside the team. This section points toward the setup entries players would actually keep revisiting in a real guide.
Cross-System Use
Hero pages have limited value on their own. Their real job is helping players choose more quickly between Builds, Runes, Stages, and Gear.
