CoreChatX 2026.3.1

Added

• Added optional full advancement synchronization between Paper backends in the same Velocity group. The proxy stores criteria, partial progress and completion dates in YAML or MySQL, progressively merging each player's existing progress as they visit each backend. Explicit revocations stay revoked when older backend data is imported.
• Historical advancement progress is restored without repeating chat announcements, toasts, XP, items or reward functions. New completions can announce live across participating backends; inventories, XP balances, statistics and recipe books are not synchronized.
• Added death-messages.network-enabled to relay public death messages within the same Velocity group. It respects the source world's death-message rule and excludes hidden, cancelled and team-restricted messages; local death messages remain unchanged.
• Added optional PremiumVanish hooks on Paper standalone and Velocity. Hidden players' join, first-join and quit announcements are suppressed, including their corresponding bridge messages; accepted first joins and counters are still recorded.

Configuration

• Advancement synchronization and network death messages are disabled by default. Advancement sync requires advancement-sync.enabled on Paper and velocity-advancements.properties on Velocity, explicit backend-to-group pins and a unique secret per backend. Its authenticated endpoint saves independently of online plugin-message carriers. Use HTTPS or an encrypted tunnel between separate machines; endpoint settings require a restart. Disable other plugins' advancement synchronization first. See the setup guide.
• hooks.premiumvanish is enabled by default in Paper config.yml and Velocity velocity-config.properties. Install PremiumVanish on the proxy for Velocity-owned network announcements. Paper hook changes apply through /corechatx reload; Velocity changes require a restart.

Migration

• Before updating, stop the affected servers and back up every file and subfolder in their plugin folders, the complete Minecraft worlds and the CoreChatX database when MySQL is used. Stop Paper backends before Velocity so final saves can finish. Install matching 2026.3.1 JARs on the proxy and all participating backends, then start Velocity first.
• MySQL adds schema migration V004 and ccx_player_advancements, including installations that leave advancement sync disabled. The normal schema auto-migration applies it at startup; if schema-auto-migrate=false, arrange the schema upgrade before boot. Older builds reject schema version 4: reverting only the JAR is not a database downgrade.
• Canonical backups containing advancement records use format 3 and retain that progress through Velocity YAML-to-MySQL migration and rollback. Backups without advancement records keep format 1 or 2, and both remain readable. Keep pre-update backups for downgrades, and retain each backend's existing world files until the required player visits have imported their progress.