> 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/tournamnet-details.md).

# Tournamnet Details

<figure><img src="/files/9IHwclFmPFIwOwfncNRJ" alt=""><figcaption></figcaption></figure>

1. Whether or not there is a reward
2. Schedule
3. Format of the tournament
   1. Sponsor Name
   2. Type (Elimination, Round-robin)
   3. Participation Limit
   4. Number of registrations
   5. Allow List
   6. Allow Jump-in Participation
   7. Rewards
4. Rules
   1. Tournament Rank (affects basic parameters and skill cost)
   2. Number of Monsters
   3. Maximum Turns of Battle
   4. Special Rules for the passage of turns
   5. Availability of Monster Memory
5. Player Requirements
   1. SMS verification required
   2. Player Rank
   3. Cycle Score
   4. Number of Battles (Ranked Match)
   5. Playing Days
6. Monster Requirements
   1. Cycle when Monster was born
   2. Available Monster Types
   3. Age (in weeks)
   4. Terrain specialty
   5. Main Seed
   6. Sub Seed
7. Situational button display


---

# 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/tournamnet-details.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.