> For the complete documentation index, see [llms.txt](https://mhnt.gitbook.io/metahunt-wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mhnt.gitbook.io/metahunt-wp/rankings.md).

# Rankings

In the MHUNT platform, the progression through the ranks hinges directly on a player's performance, primarily their kill score. For every kill, a player earns one experience point (XP). Conversely, being killed results in a loss of one XP (-1 XP for death, +1 XP for a kill). 

To illustrate how XP impacts level progression, consider the following breakdown:

* **Level 1 to Level 10:** Players level up for every 10 XP earned.
* **Level 11 to Level 20:** Players level up for every 20 XP earned.
* **Level 21 to Level 30:** Players level up for every 25 XP earned.

It's crucial to understand that a player's kill score is cumulative across game rounds. This means players aren't required to achieve a specific number of kills in a single game session to level up. Instead, each kill contributes to their ongoing progress, dictating when they achieve the milestone of leveling up and securing the associated rewards. 

{% content-ref url="/pages/uoR5EihHmBngDnx8Nwbp" %}
[Matchmaking](/metahunt-wp/rankings/matchmaking.md)
{% endcontent-ref %}


---

# 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://mhnt.gitbook.io/metahunt-wp/rankings.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.