> 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/map/adventure-searching-and-creating.md). # Adventure Searching & Creating Entering a biome, the player finds themselves in a room with available adventures. It's possible that no adventures are available, in which case the player can create a new one. The available adventures are adventures that were previously opened by other players who were unable to complete them. If a hero perishes in adventure (permanent death), they lose all their equipped items and potential rewards. In case of a loss (the loss of life chance), the hero only loses potential rewards. As a result, the available adventures may contain rewards left behind by previous players. If a new player successfully completes a given adventure, they will receive not only their own rewards but also the additional rewards left by previous players. Each adventure is generated from scratch every time, with rooms appearing randomly. It's impossible to predict the number of rooms and the specific content within the adventure. --- # 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/map/adventure-searching-and-creating.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.