> For the complete documentation index, see [llms.txt](https://wiki.yami-ro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.yami-ro.net/server-features/rebirth-system/ranking-and-seasons.md).

# Ranking and Seasons

## The ranking board

Open `@rebirth` > **Rebirth Ranking** to see the **top 10** characters and your own rank.

Characters are ordered by:

1. **Grand Rebirths this season**, highest first
2. then **Rebirth count**, highest first
3. then whoever reached their last Grand Rebirth **earliest**

Each entry shows name, class, Grand Rebirths (GR), Rebirths (RB) and Total Grand Rebirth.

If you have never rebirthed this season, you are shown as *"You are currently unranked."*

## Seasons

The ranking uses your **season** counters, not your lifetime total. Staff can start a new season, which sets **everyone's** counters back to 0:

| Reset at a new season  | Kept                |
| ---------------------- | ------------------- |
| Grand Rebirth (season) | Total Grand Rebirth |
| Rebirth count          | Tier                |
|                        | Power Ups and picks |
|                        | Rebirth Points      |

{% hint style="warning" %}
A new season also clears your normal **Rebirth count**, so progress toward your next Grand Rebirth is lost at that moment.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.yami-ro.net/server-features/rebirth-system/ranking-and-seasons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.