Tags
Creators
Details
1.4.0
Compatibility
Changes
π‘ AntiCheatPlugin 1.4.0 β Enforcement Update
This update takes server moderation to the next level.
Stronger detection. Smarter punishment. Full admin control.
β Fly Hack Detection β Upgraded
Detects players flying longer than 4 seconds
Teleports them back to their last safe ground location
Automatic timeout
Instant admin alert
No more silent fly hackers.
π Advanced X-Ray Monitoring
Diamond mining is now intelligently tracked.
5+ diamonds in 60 seconds triggers suspicion
Suspicion points are displayed in alerts
15 points = automatic timeout
Fully automated system
Example:
[AntiCheat] Player mined many diamonds quickly. (Suspicion: 9/15) π§ Suspicion System
A scalable internal tracking system designed for:
Future cheat checks
Progressive punishment
Smarter detection logic
This is the foundation for bigger updates.
π₯ Complete Admin GUI System
New /acgui command introduces a full moderation interface:
β° Timeout Player (Clock)
π Active Timeouts Viewer
Player head selection
Timeout duration selection:
5 Minutes
10 Minutes
30 Minutes
60 Minutes
Remove Timeout button
Fully exploit-safe inventory
Clean. Simple. Fast.
β± Reason-Based Timeout Screen
Players now see:
Reason
Duration
Example:
You have been timed out!
Reason: Fly Hack Duration: 10s
Professional moderation experience.
π Smart Alert System
Console logging
Permission-based staff alerts
Unified AntiCheat prefix
Suspicion progress display
π― What 1.4.0 Delivers
β Fly Detection with Safe Teleport β Suspicion-Based X-Ray Detection β Admin GUI Moderation Workflow β Reason-Based Timeout System β Exploit-Proof GUI β Real-Time Active Timeout Viewer
π₯ Why This Update Matters
1.4.0 transforms AntiCheatPlugin from a basic detection tool into a real moderation system.
More control. More visibility. More authority.
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:jc1SKgrq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:38yyL0kS:jc1SKgrq"
}

