> For the complete documentation index, see [llms.txt](https://gainhive.gitbook.io/gainhive-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gainhive.gitbook.io/gainhive-whitepaper/gameplay/leveling.md).
# Leveling
The level in the game has no boundaries. However, it gets progressively harder to level up characters. This is especially true for characters who do not use any equipment.
Leveling is permanent, this means the avatars are sold with their level on them.
Stat distribution is not permanent. When an avatar is put on the market their stats will be reset.
An avatar cannot be sold without resetting its stats.
Stats can be reset for a small amount of money/tokens to allow changes in tactics and strategy of the using player.
### Experience Requirements
| Level | Total Exp | Exp Required |
| ----- | --------- | ------------ |
| 1 | 0 | 1000 |
| 2 | 1000 | 1500 |
| 3 | 2500 | 2250 |
| 4 | 4750 | 3375 |
| 5 | 8125 | 5063 |
| 6 | 13188 | 7594 |
| 7 | 20782 | 11391 |
| 8 | 32173 | 17086 |
| 9 | 49259 | 25629 |
| 10 | 74888 | 38443 |
Experience required to go from Level X to Level X+1 is calculated by the following:
### Gaining Experience
Actions taken inside the game provide experience to the players. In general spending energy provides experience however, different actions have different weights on how experience is generated.
| Action | Modifier |
| ----------- | ---------------------------------- |
| Mining | x1 |
| Attacking | x 0.2 x Damage x √Level Difference |
| Adventuring | x1.5 |
### Gaining and Distributing Stats
Avatars will gain a free “stat” point which can be assigned to any stat in-game. These stats can be redistributed if they want.\
We can have a timer to allow redistribution or we can make it cost tokens to perform a redistribution.
---
# 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://gainhive.gitbook.io/gainhive-whitepaper/gameplay/leveling.md?ask=&goal=
```
`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.