Tags
Creators
Details
1.1.2
Compatibility
Changes
π οΈ DuckyAC v1.1.2 β Edge & Water Grace Update
In v1.1.2, weβre addressing false positives around block edges, water transitions, and Elytra flight, while also simplifying reach detection for more predictable results.
π Fixes
πͺ¨ GroundSpoofA Edge Detection
- Fixed false alerts when players were standing on the edge of a block.
- The check now probes multiple points (center, axis, corners) around the playerβs feet before flagging.
π Water Transition Handling
- Fixed false alerts when leaving water.
- Added a 300 ms grace window after exiting water where checks are skipped.
πͺ Elytra Grace
- Fixed false alerts when toggling Elytra flight.
- Checks are skipped while gliding and Β±300 ms around start/stop.
π ReachA Stability
- Removed reliance on per-player attributes for reach distance (unreliable across versions).
- Always falls back to the configured
base-range+ tolerance.
βοΈ Improvements
- Clearer debug messages with explicit reasons why a check was skipped (e.g., teleport, damage, velocity, Elytra, water).
- More predictable ping compensation logic for ReachA and FlyA.
- Reduced risk of combat/movement disruption caused by legitimate transitions.
β οΈ Config Changes
π§ No need to reset your entire
config.yml.
Just ensure the following lines are present (new keys have safe defaults if missing):
reach-a:
base-range: 5.0
π Summary
This update focuses on reducing false positives and giving server owners more control over movement tolerance. Default values are tuned for stability, but can be customized in config.yml if needed.
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:V2E7IgSR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BoCwnbvl:V2E7IgSR"
}

