Mod Whitelist Forge NeoForge
Running a public Minecraft server means trusting strangers with your world, your rules, and your performance. The Mod Whitelist Forge NeoForge add-on gives server owners a reliable way to control exactly which mods and files players can use. Instead of guessing who installed what, you enforce a clear whitelist that the server itself validates. If you want a cleaner, safer multiplayer experience, this mod deserves a spot in your setup.
What Mod Whitelist Forge NeoForge Does
At its core, this is a modpack enforcement tool for Forge and NeoForge. It checks every connecting client against your config and kicks anyone running forbidden mods or blocked jar files. Because modern Minecraft networking changed how mods are reported, a server-only check is no longer trustworthy. This project uses a server plus lightweight client verification model, which makes checks accurate and tamper-resistant.
Key capabilities include:
- Both-side required mods that must exist on server and client
- Client-only required mods for mandatory client-side additions
- Client-only optional mods for performance, QoL, or visual packs
- Server-only mod separation so admin tools stay off the client list
- Denied mods and files rejected instantly on join
- Strict mode that accepts only explicitly allowed entries
- Optional SHA-256 file integrity verification for hardcore setups
- Configurable kick messages with clickable pack links
All decisions are server-authoritative. There is no analytics, no tracking, and no third-party services involved. Only technical mod identifiers and optional file hashes are transmitted, so personal data never enters the picture.
Supported Versions and Loaders
Mod Whitelist Forge NeoForge for Minecraft currently targets specific builds rather than every release at once. The confirmed lines are Minecraft 1.7.10, 1.20.1, and 1.21.1, with additional versions planned to match the same feature set and config structure over time. Both Forge and NeoForge are supported, which matters if you run a mixed community or plan to migrate loaders later.
How to Install Mod Whitelist Forge NeoForge
Installation follows the usual mod workflow. Place the jar in your mods folder on the server, and on the client if you use the verification model. Start the server once so the config directory generates automatically, then edit the JSON files to match your pack. If you prefer a smoother path, the foxygame.net launcher offers one-click install for Mod Whitelist Forge NeoForge alongside its add-on catalog, so version compatibility and updates are handled without manual file juggling.
Many admins simply download Mod Whitelist Forge NeoForge, drop it in, and run the collect workflow described below. The steps are straightforward:
- Start the server once to create config/modwhitelist/
- Add a trusted admin UUID to collectWhitelist in settings.json
- Run /modwhitelist collect on to enable collect mode
- Join with your reference client pack
- Review the auto-classified files and move mandatory client mods to client_required.json
Collect mode disables itself and restores strict mode after a successful run. This controlled process means you never hand-write a whitelist from scratch.
Config Structure and Deny Rules
The multi-file layout keeps things readable: settings.json, both_side_required.json, client_required.json, client_optional.json, server_only.json, and deny.json. Old single-file configs migrate automatically on first start, so upgrades are painless.
The deny.json file is your hard blacklist. Everything listed there is blocked even when strict is false. You can block mods by ID, use wildcards like example*, or block specific jar files by name and SHA-256 hash. This is where cheat mods, xray tools, and incompatible jars belong.
Commands Worth Knowing
All commands need operator permissions. Use /modwhitelist reload after editing configs, /modwhitelist init for fresh setups, and the collect subcommands to manage the automated workflow. Colored kick messages help players instantly see what is missing or blocked.
A Known Bug to Watch
Testing revealed an issue on Forge 1.7.10 where deny.json combined with required mod rules can incorrectly block all mods. It may affect other supported versions too. Until it is fixed, use deny.json alongside required mod rules with caution.
Final Thoughts
Mod Whitelist Forge NeoForge solves a real problem for server owners who are tired of surprise mods breaking their worlds. With strict mode, file hashes, and a clean collect workflow, you get control without chaos. Set it up once, keep your configs tidy, and let the server enforce the rules for you.