> For the complete documentation index, see [llms.txt](https://wiki.helpch.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.helpch.at/clips-plugins/deluxechat/installation.md).

# Installation

How to setup deluxechat.

1. Put the **DeluxeChat jar** file you downloaded in your **plugins** folder. If you want to use it with BungeeCord, you'll have to put it in your BungeeCord's **plugins** folder too.
2. Download [**PlaceholderAPI**](https://www.spigotmc.org/resources/placeholderapi.6245/) plugin and put it in your plugins folder (not on BungeeCord).
3. Restart the servers.
4. Modify the **config.yml** and the **messages.yml** files that were generated to fit your server's layout (Files path: `/plugins/DeluxeChat/`).
5. Reload **DeluxeChat** `/dchat reload` (Some options require a restart to apply the changes).
6. Give your players the permission for their chat format `chatformat.<format-name>`. (Note: Players need the `chatformat.default` to gain access to the default format. Also, operators do not get the **chatformat** permissions by default.)
7. Check the [Commands & Permissions](/clips-plugins/deluxechat/commands-and-permissions.md) page, to give players access to the commands you want them to use.
8. And you're done! Give us a review about the plugin [here](https://www.spigotmc.org/resources/deluxechat.1277/).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.helpch.at/clips-plugins/deluxechat/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.