Mod Whitelist Forge NeoForge

✨ Feature

• Added the new multi-file ModWhitelist configuration system to Forge 1.19
• Added singleplayerDevMode for testing ModWhitelist in singleplayer/integrated server environments
• Added SHA-256 based deny rules for individual mod files
• Added automatic classification into both_side_required, client_required, client_optional and server_only
• Added chunked client scan responses for large modpacks

🔧 Improvement

• settings.json is now generated on client startup so singleplayerDevMode can be configured before starting a world
• Reworked Collect Mode to automatically classify client and server mods/files
• Switched scan nonce generation to SecureRandom
• Improved kick messages and scan validation
• Improved cleanup of pending player scans on logout

🐛 Fix

• Fixed Collect Mode being blocked when strict=false
• Required mod and SHA-256 checks are no longer unintentionally skipped when strict mode is disabled

🧩 Refactor

• Updated the Forge 1.19 networking protocol to support chunked scan packets
• Reworked the legacy single-file configuration system to match the current ModWhitelist architecture
• Updated ModWhitelist commands to the current command structure

📁 File/Project structure

• Replaced the old config/modwhitelist.json layout with:
  • settings.json
  • both_side_required.json
  • client_required.json
  • client_optional.json
  • server_only.json
  • deny.json
• Added automatic migration from the legacy modwhitelist.json configuration
• Added ModScanChunkPacket for segmented client scan responses

⚙️ Compatibility

• Forge 1.19 is now aligned with the current ModWhitelist feature set used by the newer supported versions
• Network protocol updated to version 2