Tags
Creators
Details
1.4.1
Compatibility
Changes
π οΈ Update v1.4.1 β The Developer & Owner Fix This update resolves critical false positives during fast mining actions and optimizes the punishment system to ensure a frustration-free experience for server staff and legitimate players alike.
π Changelog β¨ NEW: Operator Bypass
Server owners and players with Operator status (/op) are now completely excluded from all anti-cheat checks. No more false positives for admins working in creative mode or mining quickly in survival.
π‘οΈ X-Ray / Diamond Check Overhaul
Increased Tolerance Limit: The threshold for rapidly mined diamonds has been drastically increased. The system will now only trigger after a player breaks 20 blocks per minute.
Anti-Spam Alerts: When a player exceeds the limit, staff members will only be alerted once per minute. No more chat spam for every subsequent block mined.
Alerts Only: Removed the automatic 2-minute timeout for the diamond check entirely. The system now exclusively sends a silent notification to the console and online staff (anticheat.alert).
βοΈ Fly Check Optimizations
Airtime movement tolerance has been increased from 4 to 7 seconds to prevent rubberbanding loops during server lag.
Players swimming in water/lava or climbing ladders/vines are now correctly detected and will no longer face accidental rollbacks.
Fixed an issue where players could get stuck inside solid blocks after fast movements (the plugin now silently rolls them back to their last safe location).
πΎ Installation
- Stop your server.
- Delete the old .jar file from your plugins folder.
- Drop in the new version 1.4.1.
- Restart your server and enjoy!
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:38yyL0kS:X5PuDWw6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:38yyL0kS:X5PuDWw6"
}

