> For the complete documentation index, see [llms.txt](https://docs-old.zipclash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.zipclash.io/zipclash-goodies/leaderboard-clusters.md).

# Leaderboard Clusters

The game consists of a fixed number of leaderboard clusters, each rewarding each rank with an appointed number of tokens every 24 hours. ZipClash gives dividends to players with in-game coins for activities like upgrading planets, adding boosters, and managing interplanetary restaurants.

The more time you spend on the game, the more chances you have of entering the highest cluster. Likewise, if you stay idle and are not as active as other players, you will be kicked out of the higher clusters and downgraded into lowers ones with less income because other players outperformed you. You can buy special NFTs, tokens, and boosters to spike into higher clusters, but you must compete to stay in the current cluster even if you have gained a competitive advantage by buying special boosters.

<figure><img src="https://zipclash.io/whitepaper/user/pages/05.Game%20Economy/02.Leaderboard%20Clusters/Ranking-Model.webp" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://docs-old.zipclash.io/zipclash-goodies/leaderboard-clusters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
