CoreChatX 2026.3.2

Changed

• ChatItem previews and remote PMs now limit overlapping requests, with customizable busy feedback in chatitems.yml and messages.yml. Older previews may expire early under heavy load. Forwarded PMs consume the configured cooldown even if later rejected or timed out.
• Discord console logging now recovers from stalled requests, and ChatItem disk-cache limits remain enforced across reloads, with memory fallback on cache errors. Image transfers and Discord/Telegram exports also have workload limits and timeouts; overloaded exports may be dropped while Minecraft chat continues.

Safety

• Strengthened Velocity backend/player validation, Discord account-link updates and chat-text handling. Added stricter checks for runtime libraries, downloaded assets and custom resource packs; invalid libraries block Velocity startup, failed asset updates keep the working cache, and oversized textures may need resizing.

Migration

• Update Velocity and all participating Paper backends together. Stop Paper backends before Velocity, install matching 2026.3.2 JARs everywhere, then start Velocity first. Mixed 2026.3.1/2026.3.2 networks are incompatible. No database migration is required when upgrading from 2026.3.1.
• Ensure Paper deployment.server-id matches its registered Velocity backend name. For multiple groups, add backend-groups.<server>=<network-channel> in velocity-config.properties for every participating backend and match its Paper deployment.network-channel; these mappings are optional with one group.
• Telegram now accepts incoming messages only from explicitly mapped chats/topics in telegram.inbound.routes. Set telegram.inbound.allow-unmapped-chats: true to restore the previous default-channel fallback. Custom pings from Telegram or other generic remote sources require an empty use-permission.