> For the complete documentation index, see [llms.txt](https://october-studio.gitbook.io/monster-survivors-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://october-studio.gitbook.io/monster-survivors-documentation/testing/presets.md). # Presets ## Testing Presets To make testing specific moments in stages under specific conditions you can use a built-in solution: Testing Presets. \ \ Let's take a look at a Testing Preset. By default, you can find one here:

Upon opening it in the inspector, you will find the following parameters:

Here you can set the time a stage will start from, XP level of the character, and starting abilities. {% hint style="info" %} These settings are useful for testing boss encounters, for example, or some difficulty spikes. {% endhint %} \ To activate the preset, assign it in the appropriate field in the Game Management component in the Game scene:

Now, you can start the game as usual, and these settings should apply automatically upon entering a stage. {% hint style="info" %} Don't forget to remove the assigned preset when you don't need it. {% endhint %} --- # 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://october-studio.gitbook.io/monster-survivors-documentation/testing/presets.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.