> For the complete documentation index, see [llms.txt](https://rouniverse.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rouniverse.gitbook.io/wiki/on-going-event/undefined-1/undefined-2.md).

# 𝐑𝐞𝐟𝐢𝐧𝐞 𝐌𝐚𝐬𝐭𝐞𝐫

<div data-with-frame="true"><figure><img src="https://2203365669-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiYtFLjBIGX2JwtHxZNiE%2Fuploads%2FTSGqjwghBFqlw1ThXLQ8%2Frefine.jpg?alt=media&amp;token=20cba072-3146-47ea-b3a7-01ff26f27856" alt=""><figcaption></figcaption></figure></div>

## 🔨 REFINE MASTER EVENT

Prove your luck and strategy to become the first Refine Master in RO Universe during the CBT period! Who will be the fastest to reach Refine +10?

#### 📌 Event Rules

* Event Period: Valid throughout the CBT duration.
* Event Target: Achieve a refinement level of Refine +10.
* Winner Selection: The first player to reach +10 in each equipment category wins.

#### 🏆 Rewards

* ⚔️ Weapon Level 1 (+10): 100,000 CP
* ⚔️ Weapon Level 2 (+10): Rp50,000 + 100,000 CP
* ⚔️ Weapon Level 3 (+10): Rp100,000 + 200,000 CP
* ⚔️ Weapon Level 4 (+10): Rp200,000 + 200,000 CP
* 🛡️ Body Armor (+10): Rp150,000 + 200,000 CP

#### ⚠️ Terms & Conditions

* Only refinement results achieved during the CBT period will be counted.
* Each equipment category has only 1 winner slot (first come, first served).
* The committee's decision is final and non-negotiable.

*Prepare your Oridecon, Elunium, and luck — claim the Refine Master title in RO Universe!*


---

# 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://rouniverse.gitbook.io/wiki/on-going-event/undefined-1/undefined-2.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.