Tags
Creators
Details
1.1.0
Compatibility
Changes
🛠️ DuckyAntiCheat v1.1.0 — Core Checks Expansion
In v1.1.0, we’re shipping a big wave of new core checks for movement and combat integrity, plus refinements that cut down false positives.
🔍 What’s New?
✅ AirJumpA Check
- Detects upward ascents while already airborne (classic “air-jump” behavior).
- Jump‑pad–safe: ignores recent external velocity boosts and pressure‑plate triggers to prevent false flags.
✅ AirPlaceA Check
- Detects illegitimate block placements while mid‑air or without proper support.
- Targets scaffold‑style placements outside normal reach/grounding.
✅ GroundSpoofA Check
- Detects spoofed onGround states and inconsistencies between client reports and server‑side physics.
- Helps prevent fall‑damage bypass and related exploits.
✅ FlyA Check
- Detects hovering, sustained airtime, and vertical motion that doesn’t match gravity/drag curves.
- Designed to respect legitimate mechanics (e.g., teleports, damage knockback, levitation) where applicable.
✅ ReachA Check
- Baseline combat reach detection using tick‑accurate distance checks and latency‑aware margins.
✅ ReachB Check
- Advanced reach analysis with improved motion/hitbox interpolation to reduce false positives in crowded fights.
✅ HitboxA Check
- Detects abnormal attack angles / target alignment and attempts to interact through invalid hitboxes (e.g., hitting “around” blocks).
✍️ Improvements
- 📉 Fewer false positives in movement scenarios (notably jump pads, slime bounces, bubble columns, and post‑teleport moments).
- 🧪 Clearer debug messages to explain why a movement was ignored or flagged.
⚠️ Config Changes
🛠️ Please delete and regenerate your
config.yml, then reapply your settings. This release adds new sections and defaults for the checks above (e.g., toggles and thresholds). Steps: stop the server → removeconfig.yml→ start the server to regenerate → re‑configure to taste.
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:BoCwnbvl:n1PNG3XO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BoCwnbvl:n1PNG3XO"
}

