> For the complete documentation index, see [llms.txt](https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/community/reporting-bugs-errors.md).

# Reporting Bugs/Errors

### You found a bug!

Now, the first step after you find a bug, is to first ask a staff member if this is a bug or intentional behavior. They will likely be able to tell you if it is something that is not fixable by our Developers, or if it is a proper bug. 

### Opening A Ticket

To open a ticket, join our discord, and go to the channel named Tickets under support. You should then open a ticket under "Bug Reports". In there, please be sure to put maximum detail on the bug you found, how you found it, and how to recreate the bug for our Developers to test and fix. <br>

### Resolving a Ticket

Once a Developer has reviewed your ticket and found a proper fix for the reported bug, you may be compensated for finding the bug. After that, the ticket will be closed and marked as resolved. \
Please do not @ Staff members in your ticket. They will get to it when they are avaliable!


---

# 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:

```
GET https://mellowcraft-plugins-and-info.gitbook.io/mellowcraftguides/community/reporting-bugs-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.