Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 months ago
Updated 2 weeks ago
All versions
2.8.0
Release
VoidAC 2.8.0last month 35
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.10
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Void 2.8.0
Full Minecraft 26.3 support
- Commands work again on Paper 26.3 (Cloud 2.0.1).
- New 26.3 entity interpolation for accurate reach and hitboxes, position-based teleports, punch packet, cushions, shelf mushrooms, vehicles floating in any fluid and new block hitboxes.
Complete 26.2 support
- Sulfur geysers are simulated, sulfur cubes and 26.2 mob sizes are tracked, friction and air drag are exact below 26.2.
Smarter connection handling
- Players with a frozen client (minimized with vsync) are no longer kicked while they still answer keep-alives. New option max-frozen-client-time (default 300s) in every language.
- Movement sent with an expired transaction clock is cancelled and the player is disconnected immediately.
Fewer false flags
- Sneaking off a block edge while sprinting.
- Standing up from a cushion or dismounting in the air.
- Mounting horses, boats and other vehicles: speed and ground state now start from the vehicle.
- Closing an inventory while seated or right after dismounting (MultiActionsD).
- Swim hops through bubble columns and honey on 1.21.2+.
Stronger detection
- Player hitboxes follow crouching, swimming and crawling poses on 1.14+.
- Keepsprint bypass on 1.21.2+ closed.
- Inventory sneaking on 1.21.9+ is detected (MultiActionsC).
- 1.8 wither skeleton hitbox, RotationPlace/RotationBreak buffer fix.
Better diagnostics
- Diagnostic logs are written live and kept on shutdown, and show start velocity, allowed movement range and vehicle timing. (Only useful if false positives / bypasses occur, development-wise.)
Performance
- Collision searches no longer allocate per block, AntiESP and decoys do less work when disabled.
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:aauFRVwy:dXCmA0wb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aauFRVwy:dXCmA0wb"
}

