> For the complete documentation index, see [llms.txt](https://dotaro.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dotaro.gitbook.io/wiki/core-gameplay-systems/ranking-system.md).

# Ranking System

Climb the competitive ladder by proving your strength in both PvP battles and MVP hunts. Every victory, contribution, and performance pushes you closer to greatness—unlocking prestigious ranks inspired by Dota 2:

**Herald → Guardian → Crusader → Archon → Legend → Ancient → Divine → Immortal**

Each rank grants exclusive **title achievements** that showcase your dominance across the server, along with **bonus stats** that enhance your power as you rise through the tiers. The higher your rank, the greater the rewards—giving you both recognition and a competitive edge.

***

## Once you reach certain rank points, you can claim your Title on the "Achievements Menu." Claiming and equipping (Alt + Q under Title Tab) your title grants you a bonus attribute depending on what rank you're in!

<figure><img src="/files/tcHBbJaeHQ9cgGyvLSsN" alt=""><figcaption></figcaption></figure>

***

> Just like in Dota 2, when you win, you earn rank points and when you lose, you lose rank points. So be careful and don't die too much when climbing the ranks!

Rank points per MVP Kill: <mark style="color:$success;">1</mark>

Rank points lost per Character Death: <mark style="color:$danger;">-30</mark>

## MVP Ranking System

{% tabs %}
{% tab title="Herald" %}

* Number of MVP's to Kill: 3000
* Bonus Attributes: All Stat +1
* Rank Title: <mark style="color:$success;">MVP Herald</mark>
  {% endtab %}

{% tab title="Guardian" %}

* Number of MVP's to Kill: 5000
* Bonus Attributes: All Stat +3
* Rank Title: <mark style="color:$success;">MVP Guardian</mark>
  {% endtab %}

{% tab title="Crusader" %}

* Number of MVP's to Kill: 10000
* Bonus Attributes: All Stat +5
* Rank Title: <mark style="color:$success;">MVP Guardian</mark>
  {% endtab %}

{% tab title="Archon" %}

* Number of MVP's to Kill: 12000
* Bonus Attributes: All Stat +7
* Rank Title: <mark style="color:$success;">MVP Archon</mark>
  {% endtab %}

{% tab title="Legend" %}

* Number of MVP's to Kill: 14000
* Bonus Attributes: All Stat +9
* Rank Title: <mark style="color:$success;">MVP Legend</mark>
  {% endtab %}

{% tab title="Ancient" %}

* Number of MVP's to Kill: 16000
* Bonus Attributes: All Stat +11
* Rank Title: <mark style="color:$success;">MVP Ancient</mark>
  {% endtab %}

{% tab title="Divine" %}

* Number of MVP's to Kill: 18000
* Bonus Attributes: All Stat +13
* Rank Title: <mark style="color:$success;">MVP Divine</mark>
  {% endtab %}

{% tab title="Immortal" %}

* Number of MVP's to Kill: 20000
* Bonus Attributes: All Stat +15
* Rank Title: <mark style="color:$success;">MVP Immortal</mark>
  {% endtab %}
  {% endtabs %}

***

> Just like in Dota 2, when you win, you earn rank points and when you lose, you lose rank points. So be careful and don't die too much when climbing the ranks!

Rank points per Player Kill: <mark style="color:$success;">1</mark>

Rank points lost per Character Death: <mark style="color:$danger;">-3</mark>

## PVP Ranking System

{% tabs %}
{% tab title="Herald" %}

* Number of Players to Kill: 500
* Bonus Attributes: Resist All Elements +1%
* Rank Title: <mark style="color:$success;">PVP Herald</mark>
  {% endtab %}

{% tab title="Guardian" %}

* Number of Players to Kill: 1000
* Bonus Attributes: Resist All Elements +3%
* Rank Title: <mark style="color:$success;">PVP Guardian</mark>
  {% endtab %}

{% tab title="Crusader" %}

* Number of Players to Kill: 1500
* Bonus Attributes: Resist All Elements +5%
* Rank Title: <mark style="color:$success;">PVP Crusader</mark>
  {% endtab %}

{% tab title="Archon" %}

* Number of Players to Kill: 2000
* Bonus Attributes: Resist All Elements +7%
* Rank Title: <mark style="color:$success;">PVP Archon</mark>
  {% endtab %}

{% tab title="Legend" %}

* Number of Players to Kill: 4000
* Bonus Attributes: Resist All Elements +9%
* Rank Title: <mark style="color:$success;">PVP Legend</mark>
  {% endtab %}

{% tab title="Ancient" %}

* Number of Players to Kill: 6000
* Bonus Attributes: Resist All Elements +11%
* Rank Title: <mark style="color:$success;">PVP Ancient</mark>
  {% endtab %}

{% tab title="Divine" %}

* Number of Players to Kill: 8000
* Bonus Attributes: Resist All Elements +13%
* Rank Title: <mark style="color:$success;">PVP Divine</mark>
  {% endtab %}

{% tab title="Immortal" %}

* Number of Players to Kill: 10000
* Bonus Attributes: Resist All Elements +15%
* Rank Title: <mark style="color:$success;">PVP Immortal</mark>
  {% endtab %}
  {% endtabs %}

***

Every 3 months, there will be a season reset and your MVP / PVP rank points will go back to zero. Those who are in the TOP 3 will receive exclusive rewards for being the best PVP / MVP player in DotaRO.

> Stand above the rest, earn your title, and carve your name into DotaRO history.


---

# 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://dotaro.gitbook.io/wiki/core-gameplay-systems/ranking-system.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.