1.20.1-3.0.0

Modwhitelist v2.0.0

✨ Feature

• Split the config into multiple files for better structure and easier maintenance:

  • settings.json
  • both_side_required.json
  • client_required.json
  • client_optional.json
  • server_only.json
  • deny.json

• Added support for client-only required mods

• Added support for both-side required mods

• Added support for server-only mods

• Added support for optional client-side mods in a cleaner separated setup

🔧 Improvement

• Added a new collect mode workflow to automatically classify:

  • both-side required mods
  • client-optional mods
  • server-only mods

• Improved overall config clarity for server admins

• client_required.json is now intentionally kept manual, so admins can decide which client-only mods are truly required

• Added support for denied files in addition to denied mod IDs

🐛 Fix

• Improved kick messages with colored formatting for better readability
• Kick messages are now much clearer when mods or files are missing, denied, or not allowed
• Fixed command structure by simplifying collect mode usage

📁 File/Project structure

• Moved from a single modwhitelist.json to a structured multi-file config folder:
  • config/modwhitelist/

⚙️ Compatibility

• Added automatic legacy migration from the old single-file config to the new multi-file structure

Commands

• /modwhitelist reload
• /modwhitelist init
• /modwhitelist collect on
• /modwhitelist collect off
• /modwhitelist collect clear

Notes

• Old configs are migrated automatically on first start
• Auto-collect writes to:
  • both_side_required.json
  • client_optional.json
  • server_only.json
• client_required.json must be adjusted manually if you want certain client-only mods to be mandatory