> For the complete documentation index, see [llms.txt](https://docs.kortstrid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kortstrid.io/lore-and-backstory.md).

# Lore & Backstory

Discover the world of Kortstrid

In the mystical world of Kortstrid, an ancient prophecy foretells the emergence of heroes, destined to defend their realm from the relentless darkness that seeks to consume it. Hailing from the twelve elemental regions of the planet Jotunn, these heroes are bound by a mysterious connection that transcends time and space. As the malevolent God of Chaos, born from sin itself, threatens to shatter the very fabric of the Kortstrid Universe, the Kortstrid heroes must uncover the truth of their shared destiny and embrace their roles as the protectors of Jotunn. With the fate of their world and the universe hanging in the balance, the heroes embark on an epic journey to battle the forces of darkness and restore the harmony that was once lost.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kortstrid.io/lore-and-backstory.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
