> For the complete documentation index, see [llms.txt](https://shodo-veil.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shodo-veil.gitbook.io/whitepaper/game-modes.md).

# Game Modes

Anything on this page is subject to change throughout the development progress of the game. We will thoroughly test and validate any feature before it goes live.

**Casual Mode:** Fun matches with no stakes.

* **Ranked Mode:** Competitive leaderboard-driven gameplay.
* **Tournaments:** Seasonal events with exclusive rewards.
* **Custom Lobbies:** Private matches for community play.

**Story Mode (Single-Run Progression, Non-Replayable)**

* Players start from **Level 0 to Level 5.**
* No level replay; if they lose all lives, they must restart from **Level 0**.

**Tridge Mode (Replayable Levels)**

* Players can select and replay unlocked levels.
* Requires owning a **Tridge NFT** corresponding to the level.

**Seasonal Events & Rewards**

* Limited-time events that reward active ecosystem participants.
* Special staking challenges for NFT holders.
* Reward claiming system for event participants.


---

# 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://shodo-veil.gitbook.io/whitepaper/game-modes.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.