CoreChatX 2026.3.0

Added

• Added asynchronous Modrinth update checks after startup and every 24 hours by default. Console and OP players receive stable-update recommendations and separate experimental alpha/beta announcements; no automatic installation occurs.
• Optional MYSQL runtime storage for standalone Paper and Velocity: preferences, nicknames, statistics, active/hidden channels, ignores, mutes, global state, Discord links, unlink records and pending codes. YAML remains the default; Velocity keeps each network group separate.
• Added /ccxstorage on Paper and Velocity for health checks, file/database validation, checksummed backups, migration plans, parity checks, history, resume and abort. Confirmations and durable journals protect migration/rollback; unfinished transitions keep affected gameplay storage unavailable.
• Added the Channel compass in /ccxsettings and /chatsettings: Persistent keeps the last channel; Non persistent restores the configured default on reconnect, including after restarts. Changing the preference leaves the current channel unchanged, as do proxy backend transfers within the same connection.

Changed

• Settings, nickname, channel, ignore and moderation changes now report success after authority confirmation. Single-setting updates preserve other preferences; /ignore and /unignore apply the requested final state and enforce saved-list limits. A response timeout does not cancel an accepted database write.
• With MYSQL, Paper loads complete player state before admission. Gameplay storage waits for database readiness and ownership checks; failures never silently select YAML. A database lease prevents two live processes from writing the same scope.

Fixed

Storage and recovery

• Fixed /ccxstorage migrate files-to-mysql abort deleting rows that a planned/failed run never imported. Abort now preserves later imports and refuses deletion when imported contents have changed.
• Fixed recovery accepting run IDs from another namespace or scope. Migration operations now enforce the configured owner, preventing cross-group changes.
• Fixed Paper treating malformed persistent YAML as empty data and overwriting it. Startup reports the error; failed player/global reloads block writes and shutdown flushes until the file is repaired and successfully reloaded.
• Fixed older concurrent YAML snapshots replacing newer data. Write failures now reach callers, and maintenance drains accepted writes—including timed-out requests—before migration or rollback.
• Fixed writes retaining authority after waiting on locks past lease expiry. Shutdown also resolves queued operations and late completions, preventing expired owners from writing and callers from waiting indefinitely.
• Fixed migration/rollback retries after a successful abort being mistaken for completed cutovers. Verified aborts can be retried without deleting journals; Velocity also supports cancelling unexecuted plans and safely repeating interrupted aborts.
• Fixed MySQL startup deadlocks when network groups initialize separate scopes concurrently. Duplicate owners of the same scope remain rejected.
• Fixed YAML saves after MySQL-to-YAML rollback dropping runtime-updated-at, regressing player aggregate versions and breaking canonical backup parity.
• Fixed MySQL startup checksum mismatches from packaged migration line endings. JARs preserve the original migration bytes; never edit database checksums to bypass validation.

Player state and moderation

• Fixed delayed proxy mute lookups clearing newer mutes or leaving backend caches incorrectly cleared.
• Fixed proxy public chat and PMs bypassing mutes before the player state loaded. With mute enforcement enabled, messages receive temporary-unavailability feedback until the authoritative mute lookup completes.
• Fixed simultaneous Velocity YAML nickname changes assigning the same visible name to different players. Full player updates and /nick enforce normalized nickname ownership atomically.
• Fixed late completions overwriting newer settings, channels, statistics, mutes, global state or Discord links/unlinks. Old quit cleanup no longer evicts newer login state; delayed code reads cannot restore invalidated Discord codes.
• Fixed /chatmute overwriting the first-join counter and concurrent settings/ignore changes replacing unrelated values.
• Fixed /corechatx reload temporarily resetting proxy preferences or statistics. Hydrated mirrors and pending requests survive reload, then refresh after transport registration. Deployment and storage identity changes still require restart.

Discord and integrations

• Fixed link instructions showing /link with custom Discord command names. Minecraft code help, required-link admission and Discord DMs now use the configured standalone/proxy command.
• Fixed the first inbound Discord message showing an unresolved linked-player nickname before proxy player state loaded.
• Fixed mandatory Discord linking admitting unlinked players when commands were unavailable or code creation failed. account-linking.require-linked-to-play now denies entry; Velocity checks before backend entry. deny-if-unverifiable only controls role checks for already linked players.
• Fixed Velocity Discord console feedback missing messages sent through current or typed Adventure calls.
• Reduced resource-pack fingerprint string copying during Discord ChatItem image initialization, cutting avoidable Paper startup/reload work while preserving the cache fingerprint format.
• Fixed Discord token verification and gateway shutdown blocking Paper startup or /corechatx reload. Reconnection is asynchronous; retired connections and queued role callbacks cannot revive the old bridge.
• Fixed linked Discord messages being dropped on standalone MySQL after the Minecraft player quit or the server restarted. Offline nickname/staff checks load saved settings asynchronously, honor allow-offline-linked-players and deny delivery when settings are unavailable.

Chat and menus

• Fixed dragging items into the temporary /ccxsettings inventory and losing them when the menu closed.
• Fixed cross-server PM timeouts silently discarding pending deliveries. Each affected sender is now notified once.
• Fixed inbound bridge and outbound Telegram length limits splitting emoji UTF-16 pairs.

Configuration

• Added update-check.enabled and update-check.interval-hours to Paper config.yml and Velocity velocity-config.properties. Customize OP notices through messages.yml keys updates.stable and updates.preview; Velocity notifications are console-only.
• Added {link_command}, the configured Discord command name without /, to linking messages. Use /{link_command} code:{code}; standalone Paper or Velocity supplies account-linking.link-command-name. Exact older stock messages adapt automatically; customized messages need the placeholder added manually.
• Paper storage.yml and Velocity velocity-storage.yml now configure storage.backend, stable namespace/scope, MySQL connections/TLS, bounded pools/executors, timeouts, leases and schema-auto-migrate. Supply credentials through storage.mysql.password-env; TLS defaults to VERIFY_IDENTITY.
• Added saved persistent-channel-enabled, defaulting to true for existing players, and link-check-unavailable-kick in Paper Discord messages and Velocity account-linking messages.

Permissions

• Added corechatx.command.storage for inspection and backups: default op on Paper; grant it through the permission provider on Velocity. Migration/rollback changes remain console-only, including for operators. Velocity transitions require --all-scopes.

Compatibility

• Paper and Velocity JARs include the MySQL runtime and JDBC driver. Install only the matching platform JAR; separate storage-module, HikariCP or Connector/J installs are unnecessary. YAML-only setups need no database.

Migration

• Before updating, stop the affected servers and back up every file and subfolder in the CoreChatX plugin folders, including configuration, player data, credentials, journals and backups. Keep the old JARs separately; also back up MySQL when used.
• The website includes a 2026.2.6 YAML → 2026.3.0 MySQL migration guide for standalone Paper and Velocity: backups, configuration, verified migration, activation, rollback and interruption recovery.
• Upgrade Velocity and every participating Paper backend together. Protocol 29 cannot reliably exchange complete runtime state and mutations with older JARs.
• Legacy storage.sql.* never enabled MySQL. Use storage.backend: MYSQL and storage.mysql.*; existing YAML data requires /ccxstorage migrate files-to-mysql plan and confirmed execute/restart. Changing the backend alone does not migrate data.
• Schema V003 adds persistent channels as the default for existing players. With schema-auto-migrate: false, arrange the schema upgrade before startup. Older builds reject schema 3; replacing the JAR cannot downgrade the database.
• Keep corrected 2026.3.0 JARs after abort: older builds cannot read the ABORTED local journal state. Use each new plan's run IDs and tokens; never delete journals or alter checksums to force a retry.
• Use /ccxstorage rollback mysql-to-files to export current MySQL data before returning to YAML; never overwrite newer data with a pre-migration backup. Canonical format 1 remains readable; non-persistent channel preferences require format 2 and its matching newer build.

Known issues

• Discord rate limits can delay channel-topic updates after rapid joins/restarts. Chat and linking continue while topic updates retry.
• The 2026.2.6 migration was tested with synthetic legacy data, not production data. Rehearse with an isolated copy of your own data and retain complete backups before cutover.