> For the complete documentation index, see [llms.txt](https://docs.arkada.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkada.gg/core-features/leaderboard/quest-royale-daily-battle.md).

# Quest Royale – Daily Battle

**Quest Royale** is Arkada’s unique raffle-style competition, where your daily activity turns into a chance to win real rewards. Every 24 hours, a new battle begins — and one lucky player walks away with **0.05 ETH**.

***

## How It Works

* **Every day**, a new Quest Royale round begins.
* Users enter automatically by completing quests and minting pyramids.
* The more pyramids you mint — the better your odds.
* At the end of the 24-hour cycle, **1 random winner** is selected.

***

## Access Requirements

* **Must own the latest Shogun NFT** to participate.
* Entry is fully automated: mint → track → win.

***

## Points System

| Action            | Points   |
| ----------------- | -------- |
| 1 Regular Pyramid | 1 point  |
| 1 Gold Pyramid    | 5 points |

Your **total Royale score** = total daily points × NFT multiplier.

***

## NFT Multipliers

Holding specific **Segun Collection NFTs** increases your chance:

| NFT Part  | Bonus |
| --------- | ----- |
| Gauntlets | +10%  |
| Helmet    | +20%  |
| Pauldrons | +30%  |
| Belt      | +40%  |

**Multipliers stack only if NFTs are unique**

* Pauldrons + Helmet = +50%
* Helmet + Helmet = +20% (no stack)

***

## Example

You minted:

* 5 Regular Pyramids
* 1 Gold Pyramid
* Own Gauntlets + Belt

> Chance: (5 + 5) × (1 + 0.1 + 0.4) = **15 points**

***

## Prize

* **0.05 ETH** to one winner per cycle
* Winners displayed publicly on the Quest Royale board
* Full transparency — all entries are visible

***

### Jump into your daily battle and get your deserved prize!


---

# 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://docs.arkada.gg/core-features/leaderboard/quest-royale-daily-battle.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.