Just another ThruBlocksB fixes If you will find any false positives please contact me via ticket on our Discord https://discord.gg/BR7ENr8YKy

Fast false positive fix for ThruBlocksB check

🛠️ 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.yml for 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.

🛠️ 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.

🛠️ DuckyAC v1.1.1 - Wind Charge Stability Update

In v1.1.1, we're addressing false positive reports triggered by Wind Charge usage and refining related checks for smoother gameplay.

🔍 Fixes

🌀 Wind Charge Detection

• Fixed false alerts caused when players legitimately used Wind Charge mechanics.
• Integrated Wind Charge awareness into both AirJumpA and FlyA checks for more accurate validation.

✍️ Improvements

• More consistent handling of legitimate motion boosts provided by Wind Charge.
• Lower risk of combat/movement disruptions from flagged Wind Charge actions.

⚠️ Config Changes

🔧 No need to reset your entire config.yml.
However, please ensure the following lines are added to the air-jump-a and fly-a sections:

detect-wind-charge: true
wind-charge-grace-ms: 900

These options enable correct detection while respecting Wind Charge's intended behavior.