Choose where the text will be used, build a palette and copy an output made for the selected Hytale API or plugin. Each format shows its supported features and limitations.
Hytale does not have one universal color string that works in every context. Native Java messages, libraries, chat mods, prefix systems, and configuration files can require different syntax even when the visual preview looks identical.
The tool generates output for the selected integration and disables combinations that the target does not support. Always match the target to the mod, API, file, or command that will actually parse the text.
The correct output depends on where the text will be used and which API, library, or server mod will parse it. A Java Message object, a TaleMessage tag, an EliteEssentials chat message, and a LuckPerms command are different targets even when the preview looks similar.
Always select the exact integration installed on your server. HyTools changes the output, file type, supported styles, and setup notes to match the selected adapter.
Start with a short plain color test before pasting a long gradient. If the raw codes appear in chat, the formatter is not active for that context, the required permission is missing, or another chat system is handling the message.
Review the integration documentation after updates. Formatting capabilities can change by version, and symbols or styles accepted in one context may fail in another.
| Target | Best for | Gradient strategy | Styles |
|---|---|---|---|
| Native Message API | Java mod development | Colored message segments | Bold, italic, monospace |
| TaleMessage | Plugin configs and templates | Documented multi-point tag | Bold, italic, underline, monospace |
| PrefixesPlus | Permission-based prefixes | Documented JSON and command | Bold, italic, monospace |
| EliteEssentials | Player chat and group formats | Per-character HEX output | Bold where supported |
| Essentials Plus | Broadcasts and configured messages | Documented gradient tag | Bold where supported |
| GlymeraEssentials | Group formats and message values | Per-character HEX output | Color-focused |
| MVPColorChat | Player chat gradients | Two-color command | Supported chat styles |
| Palette only | Visual planning | CSS preview | Preview only |
No. The native server API builds structured Message objects, while libraries and plugins can define their own text syntax. Select the exact destination before copying an output.
It generates output for the native Hytale Message API, TaleMessage, PrefixesPlus, EliteEssentials, Essentials Plus, GlymeraEssentials and MVPColorChat, plus a palette-only mode. Each option only exposes features documented for that destination.
Yes, after EliteEssentials chat formatting is active. chatFormat.enabled must be true, colors need chatFormat.allowPlayerColors or eliteessentials.chat.color, and bold separately needs the formatting setting or eliteessentials.chat.format.
Literal &c or &#RRGGBB text means the message was not parsed by EliteEssentials. Confirm chatFormat.enabled, run /ee reload, verify the color permission rather than only the formatting permission, and check for another chat formatter handling the message.
LuckPerms stores prefix and suffix metadata, but another chat or formatting mod must render it. Choose the renderer you use, such as EliteEssentials or MVPColorChat, so HyTools can generate the syntax that mod understands.
The native MOTD is managed as plain text in the dedicated MOTD generator. This tool is intended for messages, prefixes, items and mod interfaces that support formatted Message content.
Each target supports a different set of features. HyTools disables options that the selected API or plugin does not document instead of generating misleading syntax.
No. Preview, generation, downloads and draft storage run in your browser.
