> 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-relic.md).
# Relic System
Relic System — current Bloodlust RO guide, reviewed 27 September 2026.
Visit **Relic Keeper** at `mall01 120 108` to review the trial, core upgrades and current effects.
## Obtain the relic
Complete the assigned two-monster trial (**30 kills each**) and bring **100 Jellopy, 50 Clover, 30 Animal Skin, 20 Mane and 100,000 Zeny**. The quest relic is bound.
## Upgrade cores
Each attempt costs **3 Relic Fragments (#70223) + 25,000 Zeny**. The first core is guaranteed. A failed upgrade consumes that attempt's cost but **keeps the current core level**.
When using multiple attempts, the process stops at the first success and refunds unused attempts. Only the highest eligible core applies; duplicate cores do not stack their bonuses.
| Target core level | Success chance |
| ----------------- | -------------- |
| 1 | 100% |
| 2 | 90% |
| 3 | 85% |
| 4 | 80% |
| 5 | 70% |
| 6 | 60% |
| 7 | 50% |
| 8 | 40% |
| 9 | 30% |
| 10 | 20% |
## Current core effects
Relic Core Lv1 — 70213
* Max HP +50
* Monster EXP +1%
* Item drop rate +1%
* Class: Mount
* Weight: 0
Relic Core Lv2 — 70214
* Max HP +100
* Monster EXP +1%
* Item drop rate +1%
* ATK +2
* MATK +2
* Class: Mount
* Weight: 0
Relic Core Lv3 — 70215
* Max HP +150
* Monster EXP +2%
* Item drop rate +2%
* ATK +3
* MATK +3
* Max SP +15
* Carry capacity +50
* Class: Mount
* Weight: 0
Relic Core Lv4 — 70216
* Max HP +200
* Monster EXP +2%
* Item drop rate +2%
* ATK +4
* MATK +4
* Max SP +20
* Carry capacity +75
* Class: Mount
* Weight: 0
Relic Core Lv5 — 70217
* Max HP +250
* Monster EXP +3%
* Item drop rate +3%
* ATK +5
* MATK +5
* Max SP +25
* Carry capacity +100
* Class: Mount
* Weight: 0
Relic Core Lv6 — 70218
* Max HP +300
* Monster EXP +3%
* Item drop rate +3%
* ATK +6
* MATK +6
* Max SP +30
* Carry capacity +125
* Class: Mount
* Weight: 0
Relic Core Lv7 — 70219
* Max HP +350
* Monster EXP +4%
* Item drop rate +4%
* ATK +8
* MATK +8
* Max SP +35
* Carry capacity +150
* Class: Mount
* Weight: 0
Relic Core Lv8 — 70220
* Max HP +400
* Monster EXP +4%
* Item drop rate +4%
* ATK +10
* MATK +10
* Max SP +40
* Carry capacity +200
* Class: Mount
* Weight: 0
Relic Core Lv9 — 70221
* Max HP +450
* Monster EXP +5%
* Item drop rate +5%
* ATK +12
* MATK +12
* Max SP +45
* Carry capacity +250
* Class: Mount
* Weight: 0
Relic Core Lv10 — 70222
* Max HP +500
* Monster EXP +5%
* Item drop rate +5%
* ATK +15
* MATK +15
* Max SP +50
* Carry capacity +300
* Class: Mount
* Weight: 0
---
# 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-relic.md?ask=&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.