> 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/what-is-rebirth.md).

# What is Rebirth?

On Yami, **Rebirth** is an endgame loop for max-level characters. You trade your levels for permanent progress: points to spend, and a Tier that unlocks permanent bonuses.

{% hint style="warning" %}
This is **not** the normal "2nd class to High Novice" rebirth. That one is done at the Job Changer. The Rebirth System starts once you are already Transcendent or 3rd class.
{% endhint %}

## Who can do it

Any character that is a **Transcendent** class (for example Lord Knight, High Wizard, Sniper) or a **3rd** class (for example Rune Knight, Warlock, Ranger), and that has reached **base level 255**.

Classes that are neither Transcendent nor 3rd cannot use the Rebirth System. The NPC tells you: *"Only Transcendent and 3rd classes can rebirth."* See [Requirements](/server-features/rebirth-system/requirements.md) for the full list.

## The three counters

| Counter                 | What it means                                                            | Resets?                                             |
| ----------------------- | ------------------------------------------------------------------------ | --------------------------------------------------- |
| **Rebirth**             | Normal rebirths, from 0 up to 100.                                       | Goes back to 0 every time you Grand Rebirth.        |
| **Grand Rebirth**       | Grand Rebirths this season. This is your **ranking** number.             | Can be reset by staff at the start of a new season. |
| **Total Grand Rebirth** | Every Grand Rebirth you have ever done. This is what sets your **Tier**. | Never resets.                                       |

## The loop

1. Level to 255.
2. **Rebirth**. You go back to level 1/1 and get Rebirth Points.
3. Repeat until your Rebirth count is **100**.
4. **Grand Rebirth**. Your Rebirth count goes back to 0, both Grand Rebirth counters go up by 1, and you get a bigger RP reward.
5. When your Total Grand Rebirth reaches the next threshold, your **Tier** goes up and you get **2 new picks**.
6. Spend picks on **Power Ups** (permanent stat and damage bonuses).

## What you get out of it

* **Power Ups**: permanent bonuses chosen by you. See [Power Ups and Picks](/server-features/rebirth-system/power-ups-and-picks.md).
* **Rebirth Points (RP)**: currency for the [Rebirth Point Shop](/server-features/rebirth-system/rebirth-points-and-the-shop.md).
* **An aura** on your character at Tiers 3 to 9. See [Tiers and Rewards](/server-features/rebirth-system/tiers-and-rewards.md).
* **A spot on the ranking**. See [Ranking and Seasons](/server-features/rebirth-system/ranking-and-seasons.md).
* **A server-wide announcement** each time you Grand Rebirth or reach a new Tier.


---

# 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/what-is-rebirth.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.