Tags
Creators
Details
4.0.9.0
Compatibility
Changes
[#] Fixed support for Minecraft 26.3
[#] Spartan is now DRM-Free
[#] Fixed Criticals never detecting due to an always-true ceiling check
[#] Improved the adaptive false-positive limits so widespread detections become stricter while a single player cannot lower their own baseline
[#] Fixed GhostHand ignoring its exemptions (flying, mcMMO, printer mode, gamemode and reach attributes)
[#] Fixed XRay comparing players against an incorrectly scaled average and deviation
[#] Fixed Velocity tracking the closest vertical motion incorrectly
[#] HitReach now only cancels attacks when prevention applies and recovers faster from isolated flags
[#] Fixed IrregularMovements flagging players whose elytra gliding legitimately stopped (swapping the elytra, it breaking or entering a vehicle)
[#] Speed no longer grants its nearby-entity allowance for items, experience orbs and projectiles
[#] Fixed rotation deltas being miscalculated when the view crosses the horizon or the yaw wraps, which affected every aim check
[#] Fixed violation history losing or overwriting entries, and never being sorted, when stored in internal lists
[#] Fixed database queries freezing their thread forever when the database is unreachable, and logs breaking on apostrophes
[#] Fixed background worker threads dying permanently after a single task error, and scheduled tasks being cancelled after one error
[#] Fixed the z coordinate being read as the y coordinate when analysing block placement
[#] Fixed configuration values written as whole numbers crashing check loading
[#] Fixed the bypass command throwing on non-numeric seconds and the wave command looking up players before verifying permission
[#] Fixed the maximum of all-negative values being reported as zero, and duplicated player profiles under concurrent joins
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:CzhWXA8H:pBXypzj8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CzhWXA8H:pBXypzj8"
}

