> For the complete documentation index, see [llms.txt](https://whitepaper.cryptofights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cryptofights.com/world/combat/leaderboards.md).
# Leaderboards
Demo Leaderboard: Improved Leaderboard Under Development
The leaderboard in CryptoFights is where valor and skill are immortalized. Itβs a testament to the prowess of players who dominate PvP battles, offering not just glory but tangible rewards for those who rise to the top.
### **π― Purpose**
* Rewards players for their combat skills and strategic thinking to foster engagement and competition
* Encourages return players with limited-time leaderboards, event rewards, and Ascension Season-specific items
* Nurtures a lively community by motivating players to improve and engage more, enhancing the gameplay experience for all involved
### **π Types of Leaderboards**
* **Champions:** Celebrates the warriors who clinch the most victories, highlighting the elite of PvP combat.
* **Defenders:** Honors the most active gladiators, rewarding engagement and perseverance, win or lose.
* **Event:** Shines during special occasions, offering exclusive rewards for various achievements like vanquishing the most bosses during Ascension Seasons.
### π**Rewards**
Rewards typically vary and are divided by rank, usually in groups of ten such as 1-10, 11-20, and so on. These rewards may include Gold or Equipment (like Weapons, Armor, Components, or Recipes). In some instances, rewards must be claimed within a certain timeframe before they expire. In other situations, rewards will stay in the reward tab indefinitely. This system encourages players to come back to the game to claim their rewards and take advantage of event-specific or limited-time items.
---
# 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://whitepaper.cryptofights.com/world/combat/leaderboards.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.