> 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/limits-and-caps.md).

# Limits and Caps

| Limit                                         | Value                                    |
| --------------------------------------------- | ---------------------------------------- |
| Base level needed to rebirth                  | 255                                      |
| Job level needed                              | none                                     |
| Normal rebirths before you must Grand Rebirth | 100                                      |
| Grand Rebirths per season                     | 5,000                                    |
| Highest Tier                                  | 10 (at 4,000 Total Grand Rebirths)       |
| Picks per Tier                                | 2                                        |
| Picks from tiers at Tier 10                   | 20                                       |
| Extra picks you can buy                       | no limit, 1,000,000 RP each, from Tier 1 |
| Power Ups                                     | 29                                       |
| Ranks per Power Up                            | 6                                        |
| Ranking board size                            | top 10                                   |
| Auto Rebirth delay after reaching 255         | 0.5 seconds                              |
| Max bundles per shop purchase                 | 30,000                                   |

## How far is the next Tier?

| From   | To      | Extra Grand Rebirths | Normal rebirths that takes (100 each) |
| ------ | ------- | -------------------- | ------------------------------------- |
| Tier 0 | Tier 1  | 100                  | 10,000                                |
| Tier 1 | Tier 2  | 150                  | 15,000                                |
| Tier 2 | Tier 3  | 150                  | 15,000                                |
| Tier 3 | Tier 4  | 350                  | 35,000                                |
| Tier 4 | Tier 5  | 350                  | 35,000                                |
| Tier 5 | Tier 6  | 400                  | 40,000                                |
| Tier 6 | Tier 7  | 500                  | 50,000                                |
| Tier 7 | Tier 8  | 600                  | 60,000                                |
| Tier 8 | Tier 9  | 700                  | 70,000                                |
| Tier 9 | Tier 10 | 700                  | 70,000                                |

When you have no picks left, the Power Ups menu tells you how many Total Grand Rebirths the next Tier needs.


---

# 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/limits-and-caps.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.