> For the complete documentation index, see [llms.txt](https://battle-saga.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://battle-saga.gitbook.io/untitled/litepaper/sagaverse.md).

# Sagaverse

<figure><img src="/files/bVY8n2layiQ7HTK7nKvZ" alt=""><figcaption></figcaption></figure>

The Sagaverse will enable its players to immerse themselves into the virtual world of Battle Saga and allow players to socialize and bring them closer to create a next generation gaming experience. The Sagaverse will be implemented in three phases; in the first phase players will be able to communicate with their Allies and visit their base camps. In the second phase, players will be able to go to the Marketplace together to shop. Finally in the third phase, players will be able to battle in the sagaverse-live. In the Sagaverse, the in-game NFT heros that players own will be the avatars for the players in the virtual world of Battle saga.

\
Battle Saga is played within the vast metaverse of 10,000 plots of Realms(lands) which are NFT’s of their own. Players are encouraged to explore, own, rent and customize their plots. Players can build their own empires and form allies to enjoy social communities by hosting parties, organizing tournaments, building mini games and going to Allies War. They can also create further revenue generating assets by structuring and purchasing other in-land assets such as buildings, sculptures, flag poles and various decorations which can add on extra values. <br>

All of this is available on the Battle Saga Marketplace, where various digital assets can be bought and sold. Enjoying such NFT rewards is one of many Battle Saga's economic promotion mechanisms.

{% file src="/files/Uwo0PlK4whyAtEL8FjYJ" %}


---

# 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://battle-saga.gitbook.io/untitled/litepaper/sagaverse.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.