> 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/helpchat-plugins/deluxetags/formatting.md).

# Formatting

Configure legacy colors, hex colors, and MiniMessage formatting

DeluxeTags supports legacy ampersand color codes, hex colors, and MiniMessage formatting in tags, messages, and GUI text.

## Legacy colors

Legacy color and style codes continue to work:

```yaml
tag: '&7[&e&lVIP&7]'
```

## Hex colors

With `legacy_hex: false`, use the standard `#RRGGBB` format:

```yaml
legacy_hex: false

deluxetags:
  vip:
    tag: '#ffaa00[VIP]'
```

With `legacy_hex: true`, use the legacy `&#RRGGBB` format instead:

```yaml
legacy_hex: true

deluxetags:
  vip:
    tag: '&#ffaa00[VIP]'
```

Hex colors require a server version that supports RGB chat colors. On older versions, unsupported hex values are removed.

## MiniMessage

MiniMessage is disabled by default. Enable it with:

```yaml
use_minimessage: true
```

You can then use MiniMessage tags in tag values, GUI text, and messages:

```yaml
deluxetags:
  vip:
    order: 1
    category: general
    tag: '<gradient:#ff0000:#ffaa00><bold>[VIP]</bold></gradient>'
    displayname: '<gold>Tag: <yellow>%deluxetags_identifier%'
    description:
      - '<gray>A gradient VIP tag'
      - '%deluxetags_available%'
    item: NAME_TAG
    data: 0
```

Legacy `&` codes and configured hex colors remain supported when MiniMessage is enabled, which allows existing formatting to be migrated gradually.

{% hint style="warning" %}
Quote MiniMessage strings in YAML. This prevents characters such as `:` and `#` from being interpreted as YAML syntax.
{% endhint %}

Run `/tags reload` after changing `use_minimessage` or `legacy_hex`.


---

# 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/helpchat-plugins/deluxetags/formatting.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.