Tags
Creators
Details
0.5.1
Compatibility
Changes
Connection Guard 0.5.1 is a maintenance release for Paper/Spigot, BungeeCord/Waterfall and Velocity.
- Fix Velocity bStats initialization with the verified project ID 22913. The injected factory is bundled in the JAR, the Metrics instance stops on shutdown, and statistics failures leave connection checks active. The global bStats opt-out is respected.
- Make clean optional-addon builds independent of the unavailable upstream Maven path by pinning the unchanged, hash-verified MIT LimboAPI 1.1.26 compilation archive. The API is excluded from runtime JARs.
- Add canonical website links and update README branding.
- Add a reproducible developer benchmark suite with actual-JAR policy, provider-failure and recovery gates in CI. It is a development tool, not a new detection algorithm or a claim of measured performance superiority.
- Synchronize asynchronous webhook test fixtures with their worker before assertions; production webhook behavior is unchanged.
Upgrade: stop the server/proxy, replace the main JAR with connection-guard-0.5.1-all.jar and restart. Keep only one main JAR. Existing configuration and the Cloud protocol/defaults are unchanged.
Cloud is optional and on by default. Disable it with cloud.enabled: false, /cg cloud disable or CONNECTIONGUARD_CLOUD=false. Plugin privacy disclosure.
Qualification: 431 regression tests including loopback Redis, reproducible main/addon archives, packaging/version-history guards and artifact-bound benchmark checks. The final JAR is checked for startup/help/reload/shutdown on Paper 1.21.11-132, Velocity 3.4.0-566, Paper 26.3-151, Folia 26.2-7, Velocity 4.2.0-30 and 4.2.1-SNAPSHOT-36. Current Paper/Folia builds are beta builds; Velocity 4.2.1 is a development snapshot. The actual Velocity bStats factory, service ID and collectors are verified with telemetry disabled; live bStats ingestion is not established. Exact qualification scope and limits.
Compatibility metadata includes stable Minecraft releases through 26.3 and Hangar Velocity entries through 4.2.1. These selected checks do not prove every intermediate version or authenticated account/login scenario.
Download and docs: https://connectionguard.net/download
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:H3pbvvCe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Zaz0XyvF:H3pbvvCe"
}

