CoreChatX 2026.1.7

Nicknames

• Split player display placeholders:
  • {player_name} always resolves to the real Minecraft username.
  • {player_nickname} resolves to the custom nickname when set, otherwise the real username.
• Added nicknames.prefix in config.yml.
  • The prefix is included directly in {player_nickname} only when a custom nickname exists.
• Updated default chat, group chat, join/quit, first-join, and ChatItem preview titles to use {player_nickname} where a display name is intended.
• Added safe MiniMessage support to /nick.
  • Allowed: named colors, formats, hex colors, and gradients.
  • Legacy & codes and &#rrggbb hex still work.
  • Unsupported MiniMessage tags are stripped silently while keeping their text.
• Added nickname permissions for hex and gradients:
  • corechatx.nick.color.hex
  • corechatx.nick.color.gradient
  • corechatx.nick.color grants both children.
• Added duplicate nickname protection.
  • Custom plain nicknames cannot duplicate another custom nickname or another player's real username.
  • A player may still set their own real username as nickname text, useful for color-only setups.
• Added /realname <nickname>.
  • Permission: corechatx.command.realname
  • Tab completion suggests only custom nickname plain text, without the configured prefix.

Proxy State Sync

• Fixed cross-server nickname state propagation inside the same Velocity channel group.
• Player state sync now fans out to the other registered backends in the same group, instead of only caching the update on the proxy.
• Player state sync remains group-isolated and does not cross into other network-channel groups.
• Stale or invalid state sync packets for players not currently online in the source group are ignored by Velocity.

Network Compatibility

• The CoreChatX plugin-message protocol remains 11.
• Network chat packets carry real username and nickname separately.
• Paper and Velocity should both run 2026.1.7; mixed plugin/proxy versions are not supported for this release line.