Tags
Creators
Details
All versions
2.2.6+velocity
Release
AtomGuard v2.2.6 (Velocity)6 months ago 24
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4
Platform
Velocity
Changes
π 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 callingcount.decrementAndGet()immediately before cancelling the event. Same fix applied to the item-frame path.FrameCrashModuleβ StalearmorStandCountspersisting across chunk reloads:clearChunk(),clearAll(), andcleanup()only operated onframeCountsand completely ignoredarmorStandCounts. 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 fromarmorStandCounts.ExplosionLimiterModuleβ Wind Charge projectile not pushing players:EntityType.WIND_CHARGEandEntityType.BREEZE_WIND_CHARGEwere counted against the 10-explosion-per-second rate limit. When other explosions (TNT, creepers, beds) consumed the budget, wind chargeEntityExplodeEventwas cancelled, preventing its velocity/knockback effect. Both entity types are now exempt from the rate limit alongsideEND_CRYSTAL.InvalidSlotModuleβ Trial Chamber vault interaction blocked by too-strict slot cap:MAX_SLOTwas 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_SLOTraised 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 allBlockPhysicsEventin frozen chunks except WATER and LAVA. TheVAULTblock uses block-physics events to advance its state machine (INACTIVE β ACTIVE β UNLOCKING β DEACTIVATED), so physics cancellation prevented the vault from opening.VAULTis now added to the physics exemption list alongside WATER and LAVA.
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:QSQUthpe:QvOq49Zn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QSQUthpe:QvOq49Zn"
}

