> 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/equipment-and-customization/refinement-paths.md).

# Refinement Paths

Refinement Paths — current Bloodlust RO guide, reviewed 27 September 2026.

Refinement Paths use your equipped **Armor + Garment + Shoes**. Your **lowest refine among those three pieces** determines the full-set tier. Weapons, shields and headgear do not determine this tier.

At full **+7**, the path-selection UI opens automatically. There is no visible path-selection NPC to visit. Review Guardian, Harmony and Arcane, then confirm **one path per character**. Choosing **Decide Later** brings the prompt back on your next eligible login. A path is needed to refine these set pieces beyond +7.

Only the highest eligible tier applies. Tier bonuses **do not add together**. Removing a required piece removes the full-set bonus.

## Before choosing a path

Full +5: **Max HP/SP +1%**. Full +6: **Max HP/SP +2%**.

## Guardian

| Full-set refine | Max HP | Neutral resistance | Ranged resistance | Boss resistance |
| --------------- | ------ | ------------------ | ----------------- | --------------- |
| +7              | 3%     | 1%                 | —                 | —               |
| +8              | 4%     | 2%                 | 1%                | —               |
| +9              | 5%     | 2%                 | 2%                | 1%              |
| +10             | 7%     | 3%                 | 3%                | 2%              |

## Harmony

| Full-set refine | Max HP/SP | Melee / ranged / magic resistance |
| --------------- | --------- | --------------------------------- |
| +7              | 2%        | 1% each                           |
| +8              | 3%        | 2% each                           |
| +9              | 4%        | 3% each                           |
| +10             | 6%        | 4% each                           |

## Arcane

| Full-set refine | Variable cast time | After-cast delay | SP consumption |
| --------------- | ------------------ | ---------------- | -------------- |
| +7              | −2%                | —                | −2%            |
| +8              | −3%                | −1%              | −3%            |
| +9              | −4%                | −2%              | −4%            |
| +10             | −5%                | −4%              | −6%            |


---

# 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/equipment-and-customization/refinement-paths.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.