> 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/start-here/getting-started.md).

# Getting Started

First steps, daily progression and starter equipment for Bloodlust RO.

Welcome to **Bloodlust RO**, a modified 99/70 Pre-Renewal server.

## Your first steps

1. Install and patch the official client, choose your normal job and begin leveling.
2. Open the **Adventurer's Ledger** for level-appropriate supply, hunt and patrol contracts. Start building Renown and lifetime reputation early.
3. At **Base 70+**, claim your starter package from **Solo Package at prontera 162,182**. Choose carefully: one package per account.
4. Claim daily rewards when their 24-hour cooldown is ready. Online play also accumulates Hourly Points; click the HUD counter to shop.
5. Compare Quest, Streamer, Activity and MVP Shop equipment with genuine MVP-drop equipment. Choose effects for your build; identical sprites do not imply official bonuses.
6. At **99/70**, select a facet using a matching Spirit scroll. Apply matching Soul Link when you want its effects active.
7. Develop pets, relics, collections and Artisan appearances as optional long-term goals. Read the Ascension guide before accepting a rebirth reset.
8. A full equipped **+7 Armor/Garment/Shoes** set opens the Refinement Path selection UI automatically.

## Choose your starter build

Normal second-job families choose **Attack, Magic, Resist, Vitality or Support**. The same equipment automatically switches bonuses between eligible farming maps, PvP rooms and active WoE castles. Competitive modes require transcendent **Base 99 / Job 70**.

[Read the complete Starter Packages guide](https://bloodlust-ro.gitbook.io/bloodlust-ro-docs/start-here/getting-started/starter-packages) for claim steps, build bonuses, matching combos and map restrictions.

## Daily planning

* **Ledger:** 3 claims/account/day, with saved unfinished contracts.
* **Auto Hunt and Auto Support:** 6 hours each/day, or 8/10/12 with Bronze/Silver/Platinum VIP. Reset is midnight server time.
* Automation is limited to eligible fields/dungeons and blocked on MVP/mini-boss maps.
* **Daily Reward:** 24 hours after the previous claim, not midnight.
* **Events:** watch the server's every-two-hour announcements and use `@joinevent` while registration is open.

## Continue your progression

Browse **Custom Systems** for the Ledger, Facets & Soul Link, Artisan, Pets, Relics, Refinement Paths and VIP. Browse **Server Modifications** for current Quest, Point Shop, Donation and MVP-drop equipment effects.


---

# 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/start-here/getting-started.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.