> 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-contract-board.md).

# Adventurer's Ledger

Adventurer's Ledger — current Bloodlust RO guide, reviewed 27 September 2026.

The Adventurer's Ledger replaces the old fixed Contract Board with rotating map objectives. It remains the source of **Renown for Artisan**.

## Your daily route

1. Open the board and review today's regions and offers for your level range.
2. Accept up to **2 active contracts per character**.
3. Complete the requested supplies, target kills or patrol kills.
4. Return to claim. The daily limit is **3 completed claims per account**.

Each day offers **2 random regions and 6 contracts**. The level bands are **1–39, 40–59, 60–79 and 80–99**. The rotation draws from 24 configured regions, encouraging different farming routes.

| Contract type | Objective                                              |
| ------------- | ------------------------------------------------------ |
| Supply        | Deliver 15 of the listed material                      |
| Threat Hunt   | Defeat 20 of the assigned monster                      |
| Route Patrol  | Defeat 25 eligible normal monsters on the assigned map |

**Unfinished contracts are retained overnight.** There is no login-streak penalty or automatic loss of an accepted contract at midnight. Daily claim limits reset separately.

Party kill credit requires eligibility, proximity and recent activity; dead or inactive characters and boss kills do not supply ordinary patrol credit.

## Claim rewards

Each current daily contract grants **1 Renown and 1 lifetime reputation**, its displayed EXP reward, and a supply choice: **1 Quest Gacha Ticket (#50025), 10 White Potions or 20 Fly Wings**. Check the claim screen for the exact reward before confirming.

## Lifetime milestones

| Lifetime reputation | Premium Renown | Other milestone reward |
| ------------------- | -------------- | ---------------------- |
| 10                  | 1              | 50 Fly Wings           |
| 25                  | 2              | 20 Butterfly Wings     |
| 50                  | 3              | 50 White Potions       |
| 100                 | 4              | 20 Blue Potions        |

Milestones are claimed **once per account**, not once per character or per day. These four milestones award **10 Premium Renown total**. Previously claimed milestones can receive their missing Premium Renown once without repeating their old item rewards.

Spend ordinary Renown on regular Artisan skins and slot unlocks. Premium Renown unlocks the separate premium appearances and their slightly higher utility bonuses.


---

# 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-contract-board.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.