Tags
Creators
Details
All versions
1.19.2-3.0.0
Release
Mod Whitelist Forge NeoForge 1.19.2-3.0.02 months ago 1
Compatibility
Minecraft: Java Edition
1.19.x
Platform
Forge
Supported environments
Client and server
Changes
β¨ Feature
- Added the new multi-file ModWhitelist configuration system to Forge 1.19
- Added
singleplayerDevModefor 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_optionalandserver_only - Added chunked client scan responses for large modpacks
π§ Improvement
settings.jsonis now generated on client startup sosingleplayerDevModecan 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.jsonlayout with:settings.jsonboth_side_required.jsonclient_required.jsonclient_optional.jsonserver_only.jsondeny.json
- Added automatic migration from the legacy
modwhitelist.jsonconfiguration - Added
ModScanChunkPacketfor 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
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:EquEmW1Q:b7rN7Td7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EquEmW1Q:b7rN7Td7"
}

