> For the complete documentation index, see [llms.txt](https://docs.dungeons.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dungeons.game/gameplay/the-training-ground/talents.md).
# Talents
{% hint style="info" %}
The Talent Tree allows Heroes to specialize in certain stat trees, granting unique bonuses across the game.
{% endhint %}
The talent tree adds depth, choice, and opportunity cost to a Hero's build. Users earn 1 talent point for every 20 stat levels. At the maximum level (140), this allows a user to spend a total of 7 talent points across the talent tree.\
\
Each path in the Talent Tree specializes in one of the 4 main stats: Power, Vitality, Fortune, and Luck.\
\
Each Talent offers a unique bonus that influences the Hero's gameplay. For instance, in the Power tree, a user can select the 'Glass Cannon' Mastery (Tier 5), which boosts their chance to defeat bosses but also heightens their risk of dying. Each Mastery (Tier 5) provides a potent bonus with a trade-off, enabling users to further customize their builds according to their preferred playstyle.\
\
*Talents will not be available on launch of The Forge.*
---
# 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://docs.dungeons.game/gameplay/the-training-ground/talents.md?ask=&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.
