> For the complete documentation index, see [llms.txt](https://electrum-decisions.gitbook.io/electrum-decisions-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-hero/classes-and-subclasses.md).

# Classes and Subclasses

Warrior and Mage, and the four subclasses each of them can become.

Every hero starts as a **Warrior** or a **Mage**. At **level 5** the hero chooses a **subclass** — a role in battle with its own skills and its own gear. The choice is made once and stays with the hero to the end.

## Warrior

Physical damage. A warrior's battle resource is **Rage**: it builds up during the fight and pays for skills.

| Subclass            | Role in battle                                                          | Signature skills                                                         |
| ------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Guardian**        | The wall of the team. Draws enemies onto himself and protects the line. | Shield Bash, Iron Defence, Taunt, Shield Wall, Cover of the Line         |
| **Berserker**       | Raw damage. The angrier he gets, the harder he hits.                    | Sweep, Bloodlust, Frenzy, Armour Crush, Whirlwind Strike                 |
| **Hunter**          | A marksman with a bow or a crossbow. Marks targets and pins them down.  | Aimed Shot, Snare, Hunter's Mark, Volley, Binding Shot                   |
| **Standard Bearer** | Leads the team under a banner: boosts allies and frightens enemies.     | Under the Banner, Cry of Onslaught, Banner of Fortitude, Banner of Dread |

## Mage

Magic damage. A mage's battle resource is **Mana**.

| Subclass      | Role in battle                                                 | Signature skills                                                   |
| ------------- | -------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Archmage**  | Pure magic destruction and protective barriers.                | Destructive Charge, Magic Barrier, Spell Storm, Arc of Destruction |
| **Sorcerer**  | Curses, mirages and draining — weakens the enemy team.         | Mirage, Mark of Vulnerability, Curse of Weakness, Wave of Curses   |
| **Healer**    | Keeps the team alive: heals, cleanses and punishes with light. | Healing, Renewal, Group Restoration, Cleansing Wave, Great Healing |
| **Enchanter** | Seals and domes: silences, shackles and shields.               | Seal of Silence, Quick Barrier, Seal of Shackles, Group Dome       |

## Choosing a subclass

When your hero reaches level 5, the game reminds you, and the choice opens on the hero page. Each card shows the role and the skills. Click a card to look at it; the decision is confirmed by holding the button.

{% hint style="warning" %}
**A subclass is for ever.** It decides your skills, your gear and your role in the team.
{% endhint %}

Every skill of every subclass is in [Skills](https://electrum-decisions.gitbook.io/electrum-decisions-docs/skills/skills.md), every set in the [Gear Catalog](https://electrum-decisions.gitbook.io/electrum-decisions-docs/gear-catalog/gear.md). Suggested builds: [Hero Builds](https://electrum-decisions.gitbook.io/electrum-decisions-docs/guides/hero-builds.md).

Next: at level 15 the hero chooses an **element** — see [Elements and Paths](https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-hero/elements-and-paths.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-hero/classes-and-subclasses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
