CoreChatX 2026.2.0

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 now stored per Velocity network-channel group.
• Added Velocity-side Discord bot support 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 PlaceholderAPI placeholder %corechatx_player_nickname%, matching CoreChatX {player_nickname} output.

Changed

• In PROXY, Paper backends now act as runtime/cache clients for cross-server data and send writes to Velocity instead of persisting network runtime state locally.
• Required Discord link/role checks can now 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.

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 the previous Discord role-check limitation that required a backend authority server with an online player carrier. Velocity now checks Discord roles directly.

Configuration

velocity-config.properties now 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 now 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"

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.0, 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>/.