> For the complete documentation index, see [llms.txt](https://docs.sacra.cc/sacra-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sacra.cc/sacra-whitepaper/game-overview/gameplay/starting-the-adventure/quests.md). # Quests Embark on thrilling adventures and uncover the rich tapestry of quests and stories that lie at the core of our game. The world is teeming with intricate tales, and the possibilities are endless, offering an abundance of potential outcomes based on your choices. In the realm of quests, the unexpected can always happen, and your decisions wield immense power, shaping both the narrative and your hero's karma. With every twist and turn, you could earn powerful buffs, grapple with challenging debuffs, stumble upon rare item drops, engage in intense battles, or, in the worst-case scenario, face the harsh sting of defeat. Your choices carry the weight, and they can lead you to thrilling victories or perilous setbacks. So, when you encounter a mysterious stranger in a new quest, choose your words and actions wisely, for the story unfolds at your command. --- # 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://docs.sacra.cc/sacra-whitepaper/game-overview/gameplay/starting-the-adventure/quests.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.