> For the complete documentation index, see [llms.txt](https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/combat-roles/overview.md).

# Roles Overview

Your **role** is your identity in Aincrad Legacy: you pick how you contribute to a fight. There are three core roles, each with a distinct strength and a deliberate trade-off.

## The three core roles

| Role                                                                | Fantasy          | Signature trade-off                                     |
| ------------------------------------------------------------------- | ---------------- | ------------------------------------------------------- |
| [Damage Dealer](/aincrad-legacy-docs/combat-roles/damage-dealer.md) | Glass cannon     | Deals 20% more damage, but takes 20% more too           |
| [Tanker](/aincrad-legacy-docs/combat-roles/tank.md)                 | Unbreakable wall | Takes 20% less damage than anyone else                  |
| [Supporter](/aincrad-legacy-docs/combat-roles/support.md)           | Force multiplier | Deals 20% less damage, but empowers and protects allies |

Each role's profile at a glance:

```
              Damage Dealer | Tanker | Supporter
DAMAGE             ***      |   **   |    *
TOUGHNESS           *       |  ***   |    **
UTILITY             **      |   *    |    ***
```

## How roles work

* You choose a core role at **Character Level 10** (see [Choosing Your Role](/aincrad-legacy-docs/getting-started/choosing-your-role.md)) through the [Adventurer's Company](/aincrad-legacy-docs/progression/adventurers-company.md).
* Every role has its signature **damage dealt / damage taken** modifier, applied to everything as a **final damage multiplier** - this is the heart of the role system.
* Each role grants perks that grow with your **Adventure Level**, plus a set of **10 passive skills to choose from**, leveled with the points your Adventure Level grants.

## Roles in a party

The roles are designed to work together:

* **Tankers** stand at the front, soak damage, and hold enemies in place.
* **Damage Dealers** stand behind the Tanker and burn the enemy down.
* **Supporters** empower allies and weaken enemies, tilting the fight in the party's favor.

A balanced party covers all three. Thanks to the [Party Play](/aincrad-legacy-docs/economy-and-social/party-play.md) sharing system, grouping up is rewarding even when your roles differ wildly.

## Specializations

Each core role later specializes through the AC's **Specialized Forces**:

* **Damage Dealer** - specializes into **Brawler** or **Veteran**
* **Tanker** - specializes into **Fortress** or **Elusive**
* **Supporter** - specializes into **Booster**, **Breaker** or **Handler**

See [Advanced Roles](/aincrad-legacy-docs/combat-roles/advanced-roles.md). *(Not implemented yet.)*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://aincrad-legacy.gitbook.io/aincrad-legacy-docs/combat-roles/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.