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

# The Problem

1. Most “Play-to-Earn” games in the market focus more on the earning aspect than the overall game play, sacrificing gamers' user experience.
2. Matchmaking is not always fair. Heavy spenders are pitted against newcomers ruining the experience for all. Pay to win players are usually seen at the top of the leaderboards which discourage new players to keep putting hours into the game. 
3. Not every voice is heard. The Game players usually do not get a say in what policies or changes should be made for their games. Ideas and recommendations suggested by players are often overlooked and hardly ever get noticed.
4. Most P2E games currently in the marketplace lack scalability, sustainability or a proper revenue stream. Product longevity for players is short-lived.

![](/files/ecG62BBymwXcfqbPQh1m)


---

# 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/the-problem.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.