Tags
Creators
Details
1.1.3
Compatibility
Changes
๐ ๏ธ DuckyAC v1.1.3 - Stability & AutoTrap Update
In v1.1.3, we're addressing a key false positive related to wall signs/banners, removing outdated exceptions, adjusting reach values for better accuracy, and introducing a brand-new combat check: AutoTrapA, complete with full configuration support.
๐ Fixes
๐ชง ThruBlocksB -- Sign Hitbox False Positive
- Fixed an issue where players standing inside the hitbox of wall signs / hanging signs & banners were incorrectly flagged.\
- Ray-trace logic now properly ignores sign-type blocks, eliminating unintended violations.
๐ Removed Obsolete Exception from ThruBlocksA
- Cleaned up outdated exception logic to improve predictability and consistency across the ThruBlocks system.
๐ ReachA & ReachB -- Updated Base Range
-
Updated the default reach calculation values for ReachA and ReachB.\
-
Now they use:
base-range: 5.0 # In ReachA base-range: 4.0 # In ReachB -
Improves consistency, reduces edge false positives, and aligns the checks more closely with real in-game combat behavior.
โจ New Features
๐ชค AutoTrapA (New Check)
- Introduced a new combat automation detection: AutoTrapA.\
- Detects suspicious automated trap-placement behavior around players.\
- Optimized for low overhead and minimal risk of false positives.
โ๏ธ Config Additions
Added full configuration support for AutoTrapA:
- New section in
config.ymlfor toggling and tuning AutoTrapA.\ - ConfigManager updated to load & manage all new values.\
- Default settings ensure safe, predictable behavior even without manual configuration.
๐ฆ Version
- Updated plugin version to 1.1.3
๐ Summary
This update enhances detection accuracy in ThruBlocksB, removes outdated logic in ThruBlocksA, introduces AutoTrapA, and standardizes reach detection with a new 5.0/4.0 base range for ReachA and ReachB. Server owners now benefit from more stable and flexible combat detection.
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:eoikzWdt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BoCwnbvl:eoikzWdt"
}

