Tags
Creators
Details
0.4.11
Compatibility
Changes
Connection Guard 0.4.11 — urgent bStats hotfix
Fixes a missing bStats runtime dependency (MetricsBase) that could prevent Connection Guard from enabling on Bukkit/Paper and BungeeCord. bStats Base 3.0.2 is now bundled and relocated inside the plugin; the build checks that the required classes are present.
This hotfix is based on published 0.4.10. Existing configuration, translations and connection-check behavior are retained.
Upgrade: Stop the server/proxy, replace the old JAR with connection-guard-0.4.11-all.jar, and restart. Keep only one Connection Guard JAR installed.
Validation: 48 regression tests, combined JAR/descriptor/bytecode verification, repeatable-build CI, and a real isolated Paper 1.21.11 build 132 / Java 21 startup, plugin activation, configuration reload, synthetic offline backend join and clean shutdown. These controlled tests add no new platform or real-world detection-accuracy claim.
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:Zaz0XyvF:GDbfvBfL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Zaz0XyvF:GDbfvBfL"
}

