Chat Games v2.5

v2.1 fixes the crash some players hit after updating, makes cross-server mode behave correctly, and is a bit kinder to your server on large networks. No settings were removed - everything keeps working exactly as before.

Fixed The "Contact the Developers" Crash
Some players saw /chatgames top and /chatgames reload fail with an error telling them to contact the developers. This happened when a language or config file could not be read. Now the plugin logs the real reason, keeps a backup of the broken file (as .broken), and rebuilds a fresh copy from the bundled defaults so the commands keep working.

Fixed Invalid Material Name in Crafting Recipes
The Observer and Daylight Detector recipes used the old name NETHER_QUARTZ, which no longer exists on Paper 1.21+. They now use QUARTZ. If you already have an older config, change NETHER_QUARTZ to QUARTZ in crafting.crafts to remove the console warnings.

Fixed Slave Servers No Longer Judge Answers
In Redis mode, only the MASTER server now decides who wins and updates the leaderboard. A player on a slave server no longer gets a win recorded only on that server's database or a game that silently ends. The /chatgames status command now shows whether this server judges answers.

Fixed No More Main-Thread Lag from Redis
Redis messages are now sent on a background task instead of on the server's main thread, so a slow Redis connection can't stall your server.

Improved Cleaner Logs
Cross-server messages are no longer dumped in full into the console, keeping the log easier to read on busy networks.

Improved Faster Streak Resets
When streaks are enabled, the plugin used to update every player's streak one by one. It now does this in a single database step, which matters on servers with many online players.

Good News No Settings Are Removed
Your current config and language files keep working exactly as before. The update-checker option is now shown in the shipped config.yml so you can turn it off if you wish.

1. Replace ChatGames.jar with the new version.
2. No manual config changes are required.
3. If the console shows invalid material 'NETHER_QUARTZ', change it to QUARTZ in your config.yml.
4. Restart the server.