All versions
1.3.1
Release
v1.3.1last month 4
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platform
Paper
Changes
Added
- NeoForge Platform Support: ProtectCord now supports NeoForge (Minecraft 1.21.1). Includes the full feature set: IP protection, auto-update system, ban/mute/kick/warn commands, Discord webhooks, Staff IP Protection, LuckPerms integration, and bStats metrics. Requires NeoForge 21.1.172+.
- NeoForge Auto-Updater: Same Modrinth-integrated auto-update system as all other platforms — checks, downloads, SHA-1 verifies, and stages JARs for restart-apply.
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:y05wfnBZ:7zI4BDoo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:7zI4BDoo"
}

