AtomGuard

🐛 Bug Fixes

• FrameCrashModule — Armor stand counter overflow causing permanent placement block: When blocking a spawn, count.incrementAndGet() was called but never rolled back, permanently inflating the per-chunk counter so all future placements in that chunk were rejected indefinitely. Fixed by calling count.decrementAndGet() immediately before cancelling the event. Same fix applied to the item-frame path.
• FrameCrashModule — Stale armorStandCounts persisting across chunk reloads: clearChunk(), clearAll(), and cleanup() only operated on frameCounts and completely ignored armorStandCounts. On chunk unload/reload the stale counter was reused instead of being recalculated from real entity counts, causing all new armor stand spawns to be blocked. All three methods now also remove/clean entries from armorStandCounts.
• ExplosionLimiterModule — Wind Charge projectile not pushing players: EntityType.WIND_CHARGE and EntityType.BREEZE_WIND_CHARGE were counted against the 10-explosion-per-second rate limit. When other explosions (TNT, creepers, beds) consumed the budget, wind charge EntityExplodeEvent was cancelled, preventing its velocity/knockback effect. Both entity types are now exempt from the rate limit alongside END_CRYSTAL.
• InvalidSlotModule — Trial Chamber vault interaction blocked by too-strict slot cap: MAX_SLOT was set to 90 (double chest + player inventory), which is insufficient for vault inventories in Trial Chambers. Any CLICK_WINDOW packet with a slot ID above 90 was cancelled and the inventory force-closed, preventing the vault from being opened with the trial key. MAX_SLOT raised to 128 to cover all vanilla container types.
• SmartLagModule — Trial Chamber vault state machine blocked during lag freeze: During a lag-freeze cycle, onPhysics() cancelled all BlockPhysicsEvent in frozen chunks except WATER and LAVA. The VAULT block uses block-physics events to advance its state machine (INACTIVE → ACTIVE → UNLOCKING → DEACTIVATED), so physics cancellation prevented the vault from opening. VAULT is now added to the physics exemption list alongside WATER and LAVA.

🐛 Bug Fixes

• FrameCrashModule — Armor stand counter overflow causing permanent placement block: When blocking a spawn, count.incrementAndGet() was called but never rolled back, permanently inflating the per-chunk counter so all future placements in that chunk were rejected indefinitely. Fixed by calling count.decrementAndGet() immediately before cancelling the event. Same fix applied to the item-frame path.
• FrameCrashModule — Stale armorStandCounts persisting across chunk reloads: clearChunk(), clearAll(), and cleanup() only operated on frameCounts and completely ignored armorStandCounts. On chunk unload/reload the stale counter was reused instead of being recalculated from real entity counts, causing all new armor stand spawns to be blocked. All three methods now also remove/clean entries from armorStandCounts.
• ExplosionLimiterModule — Wind Charge projectile not pushing players: EntityType.WIND_CHARGE and EntityType.BREEZE_WIND_CHARGE were counted against the 10-explosion-per-second rate limit. When other explosions (TNT, creepers, beds) consumed the budget, wind charge EntityExplodeEvent was cancelled, preventing its velocity/knockback effect. Both entity types are now exempt from the rate limit alongside END_CRYSTAL.
• InvalidSlotModule — Trial Chamber vault interaction blocked by too-strict slot cap: MAX_SLOT was set to 90 (double chest + player inventory), which is insufficient for vault inventories in Trial Chambers. Any CLICK_WINDOW packet with a slot ID above 90 was cancelled and the inventory force-closed, preventing the vault from being opened with the trial key. MAX_SLOT raised to 128 to cover all vanilla container types.
• SmartLagModule — Trial Chamber vault state machine blocked during lag freeze: During a lag-freeze cycle, onPhysics() cancelled all BlockPhysicsEvent in frozen chunks except WATER and LAVA. The VAULT block uses block-physics events to advance its state machine (INACTIVE → ACTIVE → UNLOCKING → DEACTIVATED), so physics cancellation prevented the vault from opening. VAULT is now added to the physics exemption list alongside WATER and LAVA.

🐛 Bug Fixes

• FrameCrashModule — Armor stand counter overflow causing permanent placement block: When blocking a spawn, count.incrementAndGet() was called but never rolled back, permanently inflating the per-chunk counter so all future placements in that chunk were rejected indefinitely. Fixed by calling count.decrementAndGet() immediately before cancelling the event. Same fix applied to the item-frame path.
• FrameCrashModule — Stale armorStandCounts persisting across chunk reloads: clearChunk(), clearAll(), and cleanup() only operated on frameCounts and completely ignored armorStandCounts. On chunk unload/reload the stale counter was reused instead of being recalculated from real entity counts, causing all new armor stand spawns to be blocked. All three methods now also remove/clean entries from armorStandCounts.
• ExplosionLimiterModule — Wind Charge projectile not pushing players: EntityType.WIND_CHARGE and EntityType.BREEZE_WIND_CHARGE were counted against the 10-explosion-per-second rate limit. When other explosions (TNT, creepers, beds) consumed the budget, wind charge EntityExplodeEvent was cancelled, preventing its velocity/knockback effect. Both entity types are now exempt from the rate limit alongside END_CRYSTAL.
• InvalidSlotModule — Trial Chamber vault interaction blocked by too-strict slot cap: MAX_SLOT was set to 90 (double chest + player inventory), which is insufficient for vault inventories in Trial Chambers. Any CLICK_WINDOW packet with a slot ID above 90 was cancelled and the inventory force-closed, preventing the vault from being opened with the trial key. MAX_SLOT raised to 128 to cover all vanilla container types.
• SmartLagModule — Trial Chamber vault state machine blocked during lag freeze: During a lag-freeze cycle, onPhysics() cancelled all BlockPhysicsEvent in frozen chunks except WATER and LAVA. The VAULT block uses block-physics events to advance its state machine (INACTIVE → ACTIVE → UNLOCKING → DEACTIVATED), so physics cancellation prevented the vault from opening. VAULT is now added to the physics exemption list alongside WATER and LAVA.

🐛 Bug Fixes

• FrameCrashModule — Armor stand counter overflow causing permanent placement block: When blocking a spawn, count.incrementAndGet() was called but never rolled back, permanently inflating the per-chunk counter so all future placements in that chunk were rejected indefinitely. Fixed by calling count.decrementAndGet() immediately before cancelling the event. Same fix applied to the item-frame path.
• FrameCrashModule — Stale armorStandCounts persisting across chunk reloads: clearChunk(), clearAll(), and cleanup() only operated on frameCounts and completely ignored armorStandCounts. On chunk unload/reload the stale counter was reused instead of being recalculated from real entity counts, causing all new armor stand spawns to be blocked. All three methods now also remove/clean entries from armorStandCounts.
• ExplosionLimiterModule — Wind Charge projectile not pushing players: EntityType.WIND_CHARGE and EntityType.BREEZE_WIND_CHARGE were counted against the 10-explosion-per-second rate limit. When other explosions (TNT, creepers, beds) consumed the budget, wind charge EntityExplodeEvent was cancelled, preventing its velocity/knockback effect. Both entity types are now exempt from the rate limit alongside END_CRYSTAL.
• InvalidSlotModule — Trial Chamber vault interaction blocked by too-strict slot cap: MAX_SLOT was set to 90 (double chest + player inventory), which is insufficient for vault inventories in Trial Chambers. Any CLICK_WINDOW packet with a slot ID above 90 was cancelled and the inventory force-closed, preventing the vault from being opened with the trial key. MAX_SLOT raised to 128 to cover all vanilla container types.
• SmartLagModule — Trial Chamber vault state machine blocked during lag freeze: During a lag-freeze cycle, onPhysics() cancelled all BlockPhysicsEvent in frozen chunks except WATER and LAVA. The VAULT block uses block-physics events to advance its state machine (INACTIVE → ACTIVE → UNLOCKING → DEACTIVATED), so physics cancellation prevented the vault from opening. VAULT is now added to the physics exemption list alongside WATER and LAVA.

Dev Build #76

• e74c95d 🔖 Release v2.2.4 — Dispenser/Dropper Shulker & Armor + Armor Stand Freeze Fix (ATOMGAMERAGA)
• 306c3dc 🔖 Release v2.2.3 — Dispenser/Dropper False Positive Fix (ATOMGAMERAGA)
• c546980 🔖 Release v2.2.2 — VPN/Proxy Detection Overhaul & IP+Username Pair Verification (ATOMGAMERAGA)
• 51a3c5d 🔖 Release v2.2.1 — False Positive & Thread Safety Overhaul (ATOMGAMERAGA)
• 83d59c8 🔧 Fix GitHub release ID parsing & re-tag v2.2.0 as stable (ATOMGAMERAGA)
• 2638acb 🔧 Fix Jenkinsfile Groovy syntax error on line 161 (ATOMGAMERAGA)
• fb1e5c0 🔖 Release v2.2.0 — Velocity False Positive & Error Elimination (ATOMGAMERAGA)
• 0d5f294 🔖 Release v2.1.4 — Heuristic False Positive Kick Fix (ATOMGAMERAGA)
• 97ea350 🔖 Release v2.1.3 — Hit Registration & Timeout Fix (ATOMGAMERAGA)
• 7e7c9df 📝 Update CHANGELOG for v2.1.2 — Block Breaking Kick Fix (ATOMGAMERAGA)