Common Issues

A checklist for the most frequent reports. For a full technical trace of the chat pipeline, see Chat Compatibility.


Colors aren't appearing in chat

Work through this in order:

  1. Check the startup line. It should read Chat hook: MODERN (AsyncChatEvent), priority HIGHEST on Paper. If it says LEGACY and you are on Paper, something set chat-hook explicitly — set it back to AUTO in config.yml. The exception is ChatManager: with it installed, AUTO picks LEGACY at priority HIGH on purpose.
  2. Confirm apply-to-message: true and late-bind: false in config.yml. Either one turns message coloring off, by design — late-bind: true is only for setups where a formatter like LPC places the color through %chatcolor_message%, see PlaceholderAPI. If another chat plugin (chat-hover, chat-format) is installed, that setup can leave chat uncolored — switch back to the defaults.

Chat stops sending with LPC ("Legacy formatting codes have been detected")

The console shows Legacy formatting codes have been detected in a MiniMessage string and no messages go through. LPC 4.x parses its whole format as MiniMessage, and %chatcolor_message% returned § codes. Fix it with either:

  • Set papi-output: "AUTO" (the default) or "MINIMESSAGE" in ChatColor's config.yml. AUTO returns MiniMessage for LPC 4.x on 26.9.1 and newer.

LPC needs the placeholder, so don't switch back to {message}: LPC rebuilds the message from its plain text and the color would be lost. See Chat Compatibility.

/color opens another plugin's menu

Another plugin registered /color, /chatcolor or /colors and took it from ChatColor. ChatColor names the plugin in a startup warning. /chatcolor:color always reaches ChatColor. To get the short commands back, turn the other plugin's command off. For LPC-Pro that is commands.color.enabled: false in plugins/LPC-Pro/advanced/command-settings.yml. 3. Run /color debug as the affected player, say something, and read the console. See Chat Compatibility for how to interpret it.

%chatcolor_message% shows the previous message

Every chat line shows what the player said the time before, and the first line after joining is empty. Formatters that build chat on the legacy chat event (ChatManager, for one) read the placeholder before ChatColor had seen the new message. Fixed in 26.11.0: update ChatColor.

With ChatManager you don't need the placeholder at all: keep {message} in its Chat_Format. If you keep %chatcolor_message%, set apply-to-message: false. See Chat Compatibility.

Orphaned §x markers in chat or console

A player seeing §xt§xt§xt — stray §x markers — is the signature of another plugin stripping hex color codes out of a legacy-pipeline message (EssentialsChat's strip pattern removes §0-§9 and §a-§f but not the leading §x, which leaves the debris). Setting chat-hook: "AUTO" (or MODERN) fixes it — see Chat Compatibility.

A color/gradient/pattern shows "no access" in the GUI

This is expected, not a bug. Entries a player lacks permission for are still shown in the GUI, marked with no-access lore, so players can see what's available to unlock. Remove the entry entirely from colors.yml/patterns.yml if you want it hidden instead. See GUI.

A config change doesn't seem to have applied

  • Most settings apply on /color reload — no restart needed, including gui/gui.yml.
  • If you deleted a standard color/gradient/pattern and it came back after updating, this only happens on the first update after ChatColor's config-migration ledger shipped — delete it once more and it stays gone. See Automatic Configuration Updates.
  • If a file won't load at all, check plugins/ChatColor/backups/ — invalid YAML is moved there as <name>.corrupted-<timestamp> and replaced with a fresh copy so the server still starts.

After updating the plugin, something behaves differently

Read the startup migration summary in console (=== ... Migration Summary ===). Lines marked ! are the only ones needing action — see Reading the startup log for what each marker means. Your previous file version is always in backups/ if you need to recover a value.