> For the complete documentation index, see [llms.txt](https://cubicdev.gitbook.io/amazingchat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cubicdev.gitbook.io/amazingchat/main-page.md).

# Main Page

AmazingChat is a plugin that allows to customize the chat in your server in a reliable and easy way. Is a simple plugin that adds: 

1. Chat formats based in <mark style="color:$warning;">permissions</mark>.
2. Private Messages.
3. Mentions. (e.g: <mark style="color:blue;">**@User**</mark>)
4. Chat lockdown.
5. Global chat clearing for staff team.

The plugin supports <mark style="color:orange;">external</mark> and <mark style="color:yellow;">local</mark> storage (For now, MariaDB and SQLite respectively).&#x20;

The plugin has full PlaceholderAPI and MiniMessage support.

{% hint style="success" %}
All the plugin is formatted in MiniMessage (Language, formats, etc).

You can only use legacy in the format section, for PlaceholderAPI compatibility reasons.
{% endhint %}

{% hint style="info" %}
Read the next pages to understand how to configure the plugin!
{% 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://cubicdev.gitbook.io/amazingchat/main-page.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.