All versions
2.0.0
Release
CheatclientDetector 2.0.05 months ago 76
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Changes
Changelog
v2.0.0 (Latest)
- Expanded Mod Detections (18 New Mods): Added checks for LiquidBounce, Wurst, FDP Client, Replay Mod, Freecam (Kapiteon & Zergatul), SeedcrackerX, Auto Totem, Inventory Profiles Next, Autoclicker, Auto Fishing, Marlow's Crystal Optimizer, DonutSMP Crystal Optimizer, FastCrystal, Tweakeroo, and Xaero Minimap/Worldmap.
- Granular Punishment System: Added the ability to enable/disable and customize first/second strike actions (NONE, KICK, BAN, COMMAND) per individual mod.
- Custom Reusable Commands: Added a
custom-commandsconfiguration block to define named command sets (such asclear-invfor clearing inventories,warn-playerfor display warnings, etc.) and assign them usingCOMMAND:<name>as strike punishments. - Premium Configuration Overhaul: Reorganized
config.ymlinto a cleanly separated, documented, and categorized layout. - Tuned Delay Configuration: Expanded timings to allow per-check tick delay tuning for all sign check cycles.
v1.0.0 (Initial Release)
- Sign Translation Checks: Initial detection cycles targeting Meteor Client, Baritone, and FreeCam.
- Brand & Channel Inspections: Monitoring handshake brands and packet messaging channels for client identity verification.
- Vanilla Spoof Protection: Identification of clients claiming to be vanilla while running modded environments.
- Discord Webhook Integration: Logging detections directly to Discord webhooks.
- Folia Support: Full multi-threaded region safety out-of-the-box.
- Admin Commands: Commands for scans, reloads, player info details, and webhook testing.
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:8LRd2ORu:6Zntur77"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8LRd2ORu:6Zntur77"
}
