> For the complete documentation index, see [llms.txt](https://enchantedmobs.superiormc.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enchantedmobs.superiormc.cn/for-ultimatequest/features/color-code.md).

# Color Code

UltimateQuest text fields may be parsed through the plugin's text formatter and, when enabled, MiniMessage-compatible formatting.

## Legacy colors

```
&6Legendary Quest
&cError: insufficient cost
```

## Hex colors

```
&#ff0000Red text
```

## Gradient-style endpoints

The project also uses endpoint color syntax in rarity and display formats:

```
&<#F43F5E>Mythic Quest&<#C084FC>
```

Whether a field renders a continuous gradient or preserves endpoint formatting depends on the text parser and receiving Minecraft component.

## Language placeholders

Formatting may surround language placeholders:

```yaml
name: '&<#60A5FA>{lang:example-name}&<#22D3EE>'
```

Avoid putting raw untrusted user input inside MiniMessage tags. Test colors in the exact output surface—chat, action bar, GUI title, item lore, or reward preview—because client rendering rules differ. In YAML, quote text that begins with `&`, for example `name: '&aMining Task'`. The `config-files.force-parse-mini-message` option in `config.yml` controls forced MiniMessage parsing.