> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/forge/standards/mode-setup.md).
# Mode Setup
Setup standards and requirements for different mode experiences.
In order to have a consistent experience across multiple levels, mode setup standards have been created to ensure players know what to expect and to keep a general baseline consistency between different levels while playing the same mode.
{% hint style="warning" %}
These mode setup standards are documented by the Forge community by means of reverse-engineering the gameplay setups on dev-made levels in Halo Infinite and piecing together bits of information from official sources.
Even though some of the information is not officially confirmed to be true by Halo Studios, it is commonly accepted amongst Forgers to be true, and community levels with gameplay setups that follow these standards can be seen in Matchmaking and Halo Studios hasn't brought up issues regarding them.
{% endhint %}
## Learn more about
#### Contributors
Okom
---
# 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://wiki.thescriptersguild.com/forge/standards/mode-setup.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.
