> 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/characteristics.md).

# Characteristics

The six characteristics, the combat lines and how to spend points.

A hero has **six characteristics**. Every new level gives **free points** to put into them.

| Characteristic | What it does                                                                                                                                       |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Vitality**   | More health. Also helps your defence and helps a block to hold.                                                                                    |
| **Knowledge**  | A bigger pool of the battle resource — Mana for a mage, Rage for a warrior. A mage also restores mana faster.                                      |
| **Strength**   | Physical damage and the power to break through a block. A warrior builds Rage faster. Your own Strength also raises how much weight you can carry. |
| **Wisdom**     | Magic damage and the power to break through a block with magic.                                                                                    |
| **Agility**    | Dodge, and accuracy against an enemy's dodge. You also act earlier in a round.                                                                     |
| **Luck**       | Critical strikes and defence against criticals. Helps to break through a block.                                                                    |

{% hint style="info" %}
Warriors usually lean on **Strength**, mages on **Wisdom** — but every build needs **Vitality** to survive and some **Knowledge** to pay for skills. The hero page shows exactly what changes before you save.
{% endhint %}

## Combat skill points

Apart from characteristics, each level also gives **combat skill points**. They go into **combat lines** — fine-tuning of how the hero fights:

* **Critical chance** and **anti-critical**
* **Dodge** and **anti-dodge**
* **Physical** and **magic damage power**, **physical** and **magic defence**
* **Elemental power** and **elemental resistance** — Flame, Frost, Stone, Storm

These are **ratings**: what they do in a battle depends on the rating of your opponent.

## Spending points

1. Open the hero page (**C**).
2. Press **+** next to a characteristic or a combat line. The page shows what changes.
3. Press **Save**.

{% hint style="warning" %}
The Circle of War lets you in only after saving: no points may hang unspent.
{% endhint %}

## Weight

Everything the hero wears and carries in the bag has **weight**. The weight limit grows with the hero's **own Strength** — the Strength from items does not count. When the bag is full, take something off or sell it in the shop.


---

# 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/characteristics.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.
