> For the complete documentation index, see [llms.txt](https://whitepaper.hibikirun.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.hibikirun.com/index/how-it-works/main-game-properties/raffle-limit.md).

# Raffle limit

Raffle limit indicates how many times a user can play raffle machine in a single day.

### Headphone property - comfort

Raffle limit is closely tied with headphones' comfort property.

Higher comfort level will result in more raffle play times each day.

### Formula for daily raffle limit count "L"

#### L = greatest comfort point of one pair of headphones %10 (marginate)

| Highest comfort points of owned headphones + equipped Omamori | Daily raffle limit count |
| ------------------------------------------------------------- | ------------------------ |
| 10                                                            | 5                        |
| 20                                                            | 5                        |
| 30                                                            | 5                        |
| 40                                                            | 5                        |
| 50                                                            | 5                        |
| 60                                                            | 6                        |
| 70                                                            | 7                        |
| 80                                                            | 8                        |
| 90                                                            | 9                        |
| 100                                                           | 10                       |
| 110                                                           | 11                       |
| 120                                                           | 12                       |
| 130                                                           | 13                       |
| 140                                                           | 14                       |
| 150                                                           | 15                       |
| 160                                                           | 16                       |
| 170                                                           | 17                       |
| 180                                                           | 18                       |
| 190                                                           | 19                       |
| 200                                                           | 20                       |
| 210                                                           | 21                       |
| 220                                                           | 22                       |
| ...                                                           | ...                      |


---

# 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://whitepaper.hibikirun.com/index/how-it-works/main-game-properties/raffle-limit.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.