> For the complete documentation index, see [llms.txt](https://docs.remonster.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remonster.world/play-guide/open-beta/pvp/sponsored-torunament/flow.md).
# Flow
***
## Player
1. Register by the day before the event.\
-If the number of registrations exceeds the maximum number of participants, a drawing will be held\
2. Entry begins 30 minutes prior to the event.\
3. If there are not enough participants by 10 minutes before the start of the event, or if there are not enough participants and the number of participants is permitted, participants may jump in until 1 minute before the start of the event.\
4. Wait until the start time.\
5. The battle begins and is repeated with different opponents according to the settings.\
6. At the end of the tournament, the winner can claim a reward according to the settings.\
***
## Sponsor
1. Create the tournament.
2. Publish the content once it has been finalized.
3. Redeem the collateral OAS after the tournament is over.\
---
# 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.remonster.world/play-guide/open-beta/pvp/sponsored-torunament/flow.md?ask=&goal=
```
`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.