> For the complete documentation index, see [llms.txt](https://guide.chillzone.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.chillzone.cc/support/bug-reporting.md).

# Bug Reporting

Whilst we do aim to thoroughly test all updates, unfortunately bugs will inevitably slip through the cracks. If you do discover one of these yourself, please create a support ticket in the discord.

Certain bugs may be classed as exploits if they give an unfair advantage, duplicate items, etc. These are not allowed to be publicly disclosed, and you may be punished for doing so. Being aware of any similar exploit and not reporting it is equally troublesome.

### Support Tickets

1. Head to our discord
2. Navigate to the support ticket channel\
   ![](/files/7N4UUWzL7UkTG1MrY9s2)
3. Select the corresponding category (It's just a general ticket for 99% of issues, including bug reports)\
   ![](/files/A85xxYlT1prMIcoGWdMH)


---

# 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://guide.chillzone.cc/support/bug-reporting.md?ask=<question>&goal=<endgoal>
```

`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.