> 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/the-game/why-shodo-veil.md).

# Why SHODO VEIL?

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.

#### Why SHODO VEIL? <a href="#why-rocket-rush" id="why-rocket-rush"></a>

Why we have chosen exactly this game as a base to branch

1. It demonstrates high player engagement. Compared to the market average Day 1 retention rate of about 35%, this game shows a 60% retention rate.
2. It has tested game mechanics in the casual market, specifically in the idle arcade genre, which is currently performing very well. We haven't observed a similar genre in the web3 market.
3. This game is suitable for tokenomics. However, we don't believe every game is suitable. We currently have a first version of tokenomics and plan to work on transitioning this paper model into a mathematically/programmatically modeled system with the help of economists and data scientists.
4. Multiplayer functionality is a key factor. We are developing a multiplayer battle royale/team fight game, and the existing community of this game is eager to not only engage in PvE (Player vs. Environment) but also PvP (Player vs. Player) and other social mechanics (COOP) such as cooperative dungeon exploration. The desire for multiplayer functionality has been reinforced by the success of the MLU clone developed by fans on the Roblox platform. Hence, we are building robust late-game content with PvP and COOP modes for exploring maps, collaborative resource crafting, and participating in battles. Additionally, we are implementing Play-to-Own mechanics within the universe, utilizing NFT assets. This means that late gameplay encompasses a universe of NFT owned by different players, each with unique properties in terms of resources, difficulty, size, weather, and landscape.


---

# 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/the-game/why-shodo-veil.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.