All versions
1.2.26
Release
v1.2.26last month 5
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
Fixed
- Forge: Fixed
WritingException: Unsupported value type: HashMapcrash when using/protectcord whitelist add,/protectcord warn, audit log, or any purge command - Forge: Fixed the same HashMap crash recurring when existing audit/warning entries were read back and re-saved
- Forge: Fixed
removeWarningand allpurgecommands also crashing with the HashMap serialization error - Forge: Fixed command aliases (
/pc,/protect) silently overwriting the main/protectcordcommand tree - Forge: Fixed
player.connection.disconnect()being called from an async thread — now scheduled on main server thread - Forge: Fixed missing
ServerStoppingEventhandler — mod resources now properly shut down when server stops - Forge: Fixed
isValidIP()performing DNS resolution (accepting hostnames as valid IPs) - Forge: Fixed mods.toml version range allowing mod to load on incompatible Forge versions (MC 26.x)
- Forge: Fixed startup banner showing wrong MC version range
- Forge: Fixed double IP lookup counter in bStats, unsafe cast in audit logs, nil UUID in purge, mutable internal lists
Changed
- All platforms: Dashboard tracking now logs HTTP errors to console instead of silently failing
- All platforms: Added
User-Agentheader to dashboard tracking requests - Dashboard API: API key validation now auto-syncs keys from main ProtectCord API — fixes players not appearing in Game Management
- Main API: Added
/plugin/validate-keyendpoint for dashboard key synchronization
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:g6OyNFyv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:g6OyNFyv"
}

