CoreChatX 2026.3.0.1-hotfix

Changed

• Paper and Velocity now display prominent, colored console banners for Modrinth updates: green for recommended stable releases and yellow for experimental alpha/beta builds, with installed/available versions and the download link.
• Added the CoreChatX wiki link to the Paper and Velocity startup banners.

Fixed (hotfix-related)

• Fixed the first public chat message after joining or switching a Velocity backend being rejected because moderation data was only requested when the player tried to chat. Paper now loads player settings, privacy, channel, mute and global state proactively on join, with bounded read retries. Chat remains protected while authoritative moderation data is unavailable.
• Fixed delayed proxy join callbacks applying display changes or first-join announcements to a disconnected or replaced player session. Accepted-join effects now wait for confirmed player and moderation data.
• Fixed proxy request timeouts and first-join warnings reporting only null. Diagnostics now identify the operation, request, backend and player; timed-out writes are not automatically retried because they may already have committed.
• Fixed the Modrinth update checker rejecting four-part hotfix versions such as 2026.3.0.1-hotfix. This build orders hotfix revisions numerically and continues to detect later stable, beta and alpha versions.

Compatibility

• Updating from 2026.3.0 requires no configuration conversion or MySQL schema migration. Existing YAML/MySQL data and protocol 29 are unchanged.

Migration

• Stop the affected servers and back up every file and subfolder in the CoreChatX plugin folders before replacing the JARs; also back up MySQL when used. Install the matching hotfix JAR on Velocity and each participating Paper backend, then restart. Download this hotfix manually: the update checker in the older 2026.3.0 build does not recognize this version format. For upgrades from 2026.2.6 that also move YAML data to MySQL, follow the step-by-step migration guide.