> For the complete documentation index, see [llms.txt](https://bloodlust-ro.gitbook.io/bloodlust-ro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bloodlust-ro.gitbook.io/bloodlust-ro-docs/custom-systems/legacy-progression/legacy-ascension.md).

# Ascension (Divergent)

Ascension (Divergent) — current Bloodlust RO guide, reviewed 27 September 2026.

Visit **Ascension Master** at `mall01 124 108`. Ascension is a five-stage rebirth progression for eligible **99/70 transcendent second jobs**; third and baby jobs are excluded.

Accept the next trial, finish both assigned monster targets, collect the materials and Zeny, then review the confirmation. **Claiming performs a real rebirth: you return to High Novice and your levels, stats and skills reset.** Plan your build and equipment before confirming.

Stages after the first consume the previous stage ring. Rewards are bound; this is a replacement progression, not five simultaneously granted rings.

| Stage               | Kills per assigned monster (2 targets) | Zeny      | Materials                                |
| ------------------- | -------------------------------------- | --------- | ---------------------------------------- |
| I — Awakening       | 25                                     | 500,000   | 50 Clover + 50 Animal Skin               |
| II — Ascension      | 40                                     | 1,000,000 | 40 Mane + 40 Talon                       |
| III — Transcendence | 60                                     | 2,000,000 | 50 Fabric + 30 Horn                      |
| IV — Dominion       | 80                                     | 3,000,000 | 40 Bear’s Footskin + 30 Horrendous Mouth |
| V — Legacy          | 100                                    | 5,000,000 | 1 Four Leaf Clover + 3 Gold              |

## Current ring effects

<details>

<summary>Bloodlust Ring I — 50030</summary>

* All stats +1
* Max HP +150
* Class: Etc
* Weight: 0

</details>

<details>

<summary>Bloodlust Ring II — 50031</summary>

* All stats +1
* Max HP +300
* ATK +5
* MATK +5
* Class: Etc
* Weight: 0

</details>

<details>

<summary>Bloodlust Ring III — 50032</summary>

* All stats +2
* Max HP +450
* ATK +10
* MATK +10
* Max SP +40
* Class: Etc
* Weight: 0

</details>

<details>

<summary>Bloodlust Ring IV — 50033</summary>

* All stats +2
* Max HP +600
* ATK +15
* MATK +15
* Max SP +60
* Carry capacity +250
* Class: Etc
* Weight: 0

</details>

<details>

<summary>Bloodlust Ring V — 50034</summary>

* All stats +3
* Max HP +750
* ATK +20
* MATK +20
* Max SP +80
* Carry capacity +250
* Class: Etc
* Weight: 0

</details>


---

# 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://bloodlust-ro.gitbook.io/bloodlust-ro-docs/custom-systems/legacy-progression/legacy-ascension.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.
