CoreChatX 2026.2.1

Added

• Added Velocity-owned runtime data authority for PROXY deployments. Player settings, nicknames, ignore lists, active channels, mutes, global state, first-join count, Discord links and pending link codes are stored per Velocity network-channel group.
• Added Velocity-side Discord bot ownership through plugins/corechatx/velocity-discord.yml for proxy networks. In PROXY, Discord bridge I/O, Discord account linking, required-link-to-play and required-role-to-play are handled by Velocity.
• Added group-specific Discord required role gates through account-linking.required-play-roles.groups.<network-channel>, so separate CoreChatX proxy groups can require different Discord roles.
• Added optional Paper backend Discord console-only bots in PROXY mode through discord.yml -> discord.console.*, intended for per-backend console access with separate bot tokens.
• Added configurable Discord join/quit/first-join mirrors with plain text or embed output, including separate join, first-join and quit descriptions and colors.
• Added CoreChatX PlaceholderAPI values:
  • %corechatx_player_nickname% returns the same visual value as CoreChatX {player_nickname}.
  • %corechatx_first_join_date% returns the player's recorded first join date.
  • %corechatx_messages_count% returns the player's persisted public message count.

Changed

• In PROXY, Paper backends act as runtime/cache clients for cross-server data and send writes to Velocity instead of persisting network runtime state locally.
• Join, quit and first-join network announcements are coordinated through Velocity in PROXY mode, so backend switches inside the same CoreChatX group do not create extra connection messages.
• Required Discord link/role checks can be decided before the player fully enters a backend when Velocity can resolve the target backend group through backend-groups.<velocity-server-name>.
• Minecraft -> Discord messages in proxy mode are rendered by Paper, then delivered by the Velocity Discord bot. Discord -> Minecraft messages are read by Velocity and routed to the configured CoreChatX group/channel.
• Minecraft-to-Discord bridge output can prevent raw Discord mention syntax from pinging users, roles, @everyone or @here.

Fixed

• Fixed the previous proxy limitation where a backend without online players could miss Discord link state and incorrectly kick a linked player after a server switch.
• Fixed Velocity Discord link-state replay on backend switch so previously empty backends get delayed retry replays instead of an immediate failed replay warning while plugin messaging is not ready yet.
• Fixed the previous Discord role-check limitation that required a backend authority server with an online player carrier. Velocity now checks Discord roles directly.
• Fixed the first join after a proxy/backend restart sometimes using the real player name instead of the saved CoreChatX nickname in proxy-level connection messages.
• Fixed duplicate Discord join/quit mirrors when multiple exported CoreChatX channels mapped to the same Discord target.
• Fixed proxy runtime player-state cache reads re-sending unnecessary GET_PLAYER_STATE requests after the state was already cached, reducing duplicate proxy data traffic during repeated settings/nickname lookups.
• Fixed Discord and Telegram outbound bridge messages showing raw MiniMessage tags from formatted labels, bridge templates, nicknames or rank prefixes. Values like <color:#e8481D>[EXAMPLE]</color> now appear as [EXAMPLE].
• Fixed legacy and hex formatting leaking into external bridge output from identity fields. Values like &b&lIce, &3&lUser and &#ff0000Rank are now sent as plain text.
• Fixed deployment.mode changes during /corechatx reload partially switching storage authority without a full restart.

Configuration

velocity-config.properties supports backend group pins for pre-backend login gates:

network-channel=corechatx:survival,corechatx:minigames
backend-groups.survival-1=corechatx:survival
backend-groups.minigames-1=corechatx:minigames

velocity-discord.yml owns proxy Discord setup:

account-linking:
  enabled: true
  require-linked-to-play: true
  required-play-roles:
    enabled: true
    guild-id: "123456789012345678"
    role-ids:
      - "234567890123456789"
    groups:
      "corechatx:survival":
        role-ids:
          - "345678901234567890"

discord:
  enabled: true
  bot-token: "your-token"
  inbound:
    channel-routes:
      "456789012345678901":
        channel: "global"
        network-channel: "corechatx:survival"

Safety

• Bridge formatting cleanup applies to labels and identity/template fragments. Player message content in {plain_text} is preserved, so normal text such as R&D or links in angle brackets is not stripped.

Compatibility

• Paper and Velocity CoreChatX jars must be updated together. The plugin-message protocol changed for the new proxy data authority and mixed-version Paper/Velocity networks are not supported.

Migration

• A clean setup is recommended for 2026.2.1, especially on existing Velocity networks. Regenerate fresh Paper and Velocity config files, then manually reapply values such as deployment.*, channel formats, Discord token, Discord routes and required role IDs.
• In PROXY, do not treat old Paper backend runtime YAML files as authoritative network data. Velocity now owns cross-server runtime/user state under plugins/corechatx/data/groups/<encoded-channel>/.