> 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/background-story.md). # Background Story Thousands of years ago, there were humans still venturing and exploring a no man's land. They were fearless and hungry for survival. Then one day, a few discovered a magical land filled with mythical creatures and bounteous resources. The chosen ones started to relocate themselves and began their new chapter in life. Words about this land spread quickly. Many more came to the new world and it gradually became overpopulated. Resources once overflowing were now depleted. Territories once seemed boundless were now limited. Original inhabitants blamed humans. Newcomers ravaged out of control. Once again, the humans had to fight back for their survival. Shattered dreams of peace and there came ceaseless battles. Humans, as always, found clever ways of winning and started forming Allies with their trusted friends and families. Together they fought. And the next chapter in life where battles never ceased --- # 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/background-story.md?ask=&goal= ``` `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.