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

# Solutions

1. The Team at Battle Saga makes efforts to create an enjoyable gaming experience by not merely focusing on the earning aspects.
2. Battle Saga uses a unique matchmaking algorithm, matching players of the same in-game levels. As upgrading options for buildings, troops and heroes are phased with player's level, two players of the same level will have similar level of armors and defenses, giving fair matchmaking for all players.
3. Most games do not allow players to take part in in-game updates and developments. Games often leave flaws that players wish developers would remove or correct. Implementing an innovative DAO system provides players optimum voting rights in the process of game development and improvement.
4. Often games lack sustainability due to lack of proper profits. Battle Saga, on the other hand, has a number of revenue streams such as in-game NFTS, Marketplace trades, Royalpass, Breeding Commissions, etc. that guarantees its autonomy.

![](/files/mi3OB1RNsHvIbX9qzYrJ)


---

# 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/solutions.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.