CoreChatX 2026.1.6

Added

• Added join-quit.mode in config.yml to choose how join, first-join, and quit messages are delivered.
  • LOCAL keeps messages on the current Paper backend.
  • NETWORK forwards true network join/leave events through Velocity when proxy transport is available.
• Added Velocity multi-channel proxy groups through the existing velocity-config.properties -> network-channel key.
  • Legacy single-channel format still works: network-channel=corechatx:main.
  • Multiple isolated groups use a comma-separated list: network-channel=corechatx:survival,corechatx:minigames.
  • Each Paper backend joins the group matching its own config.yml -> deployment.network-channel.
• Added persistent /nick support on Paper.
  • /nick <nickname> sets your nickname.
  • /nick off, /nick clear, and /nick reset clear it.
  • /nick <player> <nickname|off> lets permitted staff change another online player's nickname.

Changed

• Velocity routing is now isolated per configured network channel.
  • Network chat, private messages, player directory, TAB/completions, state sync, ChatItem snapshot routing, and join/leave routing stay inside the source channel group.
  • Private message lookup now searches only players known inside the same proxy group, not the whole proxy.
  • ChatItem snapshot cache and pending routes are naturally isolated because each channel has its own router.
• Velocity now learns backend group membership from plugin messages and a lightweight registration handshake.
  • Paper still does not need a new config field.
  • If a backend starts sending CoreChatX packets on another configured channel, Velocity moves it to that group and logs the change.
• Network join/leave messages now understand group boundaries.
  • Moving between backend servers inside the same group does not emit fake quit/join announcements.
  • Moving between different CoreChatX proxy groups emits quit in the old group and join in the new group.
  • Proxy disconnect emits quit only in the player's last known group.

Nicknames

• Nicknames are persisted in player data and synchronized through CoreChatX state sync in proxy mode.
• Chat, PMs, spy output, broadcasts, join/quit/first-join messages, and network chat display the nickname when one is set.
• Real player identity remains unchanged: lookup, replies, ignores, privacy, routing, and state sync still use UUIDs and real Minecraft names internally.
• Added dedicated permissions:
  • corechatx.command.nick
  • corechatx.command.nick.others
  • corechatx.nick.color
  • corechatx.nick.format
• Added per-code nickname permissions so server owners can allow specific colors or styles only.
  • Example color child: corechatx.nick.color.red
  • Example format child: corechatx.nick.format.bold
• Added nicknames.change-only-colors in config.yml.
  • false lets /nick IceWolf change the visible text.
  • true only allows color/style changes while the visible text stays exactly the player's real Minecraft username.

Configuration

config.yml now includes:

nicknames:
  # false = /nick can change the visible name text and styling, for example IceWolf23X -> IceWolf.
  # true = /nick can only change allowed colors/styles; the visible text after removing formatting must stay exactly the real Minecraft username.
  # Example with true: IceWolf23X may use &cIceWolf23X, but not &cIceWolf.
  change-only-colors: false

join-quit:
  # LOCAL = announce only on the current Paper backend.
  # NETWORK = in PROXY mode, announce true network join/leave through the Velocity module.
  mode: "LOCAL"
  join-enabled: true
  quit-enabled: true

velocity-config.properties now supports a list:

# Comma-separate values to split this proxy into isolated CoreChatX network groups.
# Each Paper backend joins the group matching its deployment.network-channel.
network-channel=corechatx:main

Example multi-group setup:

network-channel=corechatx:survival,corechatx:minigames

Paper backends still use:

deployment:
  network-channel: "corechatx:survival"

Compatibility

• Existing single-channel Velocity installs keep their previous behavior.
• Existing Paper configs do not need a new deployment key.
• Existing nickname-free player data remains valid.
• The player state sync decoder accepts the previous protocol shape for compatibility and treats missing nickname data as blank.