> For the complete documentation index, see [llms.txt](https://www.btkwiki.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.btkwiki.info/ingame-guides/ro-lotto.md).

# RO: Lotto

<figure><img src="/files/gEROIdbGw1QLJSZ4WxhW" alt=""><figcaption></figcaption></figure>

* **Buy** from the **Lotto Agent** NPC or with `@lotto`.
* Pick **6 unique numbers** between **1–58** (order **doesn’t** matter).
* Draw happens daily at **??? server time** (sales close at **???**).
* <mark style="color:$primary;">**Prizes**</mark>**&#x20;(per winning ticket):**
  * **6/6** → Item | Gcash  (configured by server)
  * **5/6** → Item **+** Zeny
  * **4/6** → Zeny
  * **3/6** → Zeny
* Claim via the NPC or `@claimlotto`. If you’re overweight or near the zeny cap, claim later.

### How to Play

#### 1) Start the purchase

* **Talk to the NPC** → *Buy Ticket*\
  or
* **Use the command:**

  ```
  @lotto
  ```

#### 2) Choose numbers

You have two options:

* **Quick Pick (random):** The system picks 6 unique numbers for you.
* **Manual Pick:** Enter 6 numbers yourself.
  * **Range:** 1 to 58
  * **No duplicates** on the same ticket (the NPC will stop duplicate entries).

> **Note:** The *order* of numbers doesn’t matter matching is based on sets.

#### 3) Pay

* The **ticket price** is displayed.
* Zeny is deducted when you confirm purchase.

#### 4) Get your ticket

* Your ticket is saved for the **current draw ID**.
* You can buy **multiple tickets** (default limit: **10 tickets per account per draw**).

### Checking Your Tickets

* **NPC:** *My Tickets (this draw)*
* **Command:**

  ```
  @mytickets
  ```

This lists your tickets for the current draw, including each ticket’s six numbers.

***

### Results & Prizes

#### After the draw

* The system generates **6 unique winning numbers** from 1–58 (uniformly at random).
* The NPC shows the **last result** under *Last Result*.
* An announcement shows the result and counts of winners per tier.

#### Prize tiers (per ticket)

| Matches | Prize Type                               | Example Display in NPC |
| ------- | ---------------------------------------- | ---------------------- |
| 6 / 6   | **Zeny \| Gcash \| Costume \| and more** |                        |
| 5 / 6   | **Item + Zeny**                          |                        |
| 4 / 6   | **Zeny**                                 |                        |
| 3 / 6   | **Zeny**                                 |                        |

> **Important:** Exact items and zeny amounts are **configured by the server**. Always check the NPC’s **Prizes** section for the current values.

#### Multiple winners & duplicate picks

* **Per‑ticket payout**: If your ticket hits a tier, that ticket is a winner.
* If **several players** have winning tickets, **each** receives the full prize (no splitting).
* If **you** have multiple tickets that win, you get **paid for each ticket**.

#### What does not happen

* **No rollover**: Unwon prizes do **not** carry over.
* **No splitting**: Prizes are **not** divided among winners.
* **Order doesn’t matter**: Only how many of your numbers are in the winning set.

### Commands (Player)

```
@lotto        → Buy a ticket (quick pick menu)
@mytickets    → Show your tickets for the current draw
@claimlotto   → Claim any unclaimed prizes (zeny/items)
```

### Fairness & Rules

* **Random draw:** Winning numbers are generated uniformly at random from 1–58 with no repeats.
* **Unique numbers per ticket:** The NPC enforces **no duplicate numbers** on the same ticket.
* **Per‑ticket rewards:** Each winning ticket is paid independently—no pool split.
* **No refunds:** After purchase, tickets are locked to the current draw.
* **Server time:** All times (sales close/draw) are in **server time**.

Have fun, and good luck!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.btkwiki.info/ingame-guides/ro-lotto.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.