Tags
Creators
Details
2.6.0
Compatibility
Changes
VoidAC 2.6.0
Critical: auto-punish could ban legitimate players
If you have punishments.auto-punish enabled, please read this. The threshold was
compared against a single check's violations, not the total across all checks as the
config described — and it defaulted to 10. Simulation reaches 10 violations on completely
honest players as a matter of course (its own alert threshold is 100), so enabling
auto-punish would remove real players from your server.
Thresholds are now configured per check, with sensible built-in minimums that protect you even if your config file predates this option. The global default moved from 10 to 100.
False positive fixes
- GroundSpoof no longer flags players whose game window is minimised or sitting in the pause menu. A starved client stops ticking evenly, and its ground status was being judged against ticks it never ran.
- Fixed water and lava currents applying a push the client never made. Below vanilla's cutoff a negligible current was scaled up to a full-strength push — several times larger than the flag threshold, on every tick in flowing water.
- Fixed 1.8–1.13 players drifting on every tick while on the ground: the ground speed calculation was missing the branch those versions use.
- Fixed jump prediction on pre-1.20.5 clients, which read a value those versions do not use, and on pre-1.14 clients using Jump Boost.
- Fixed levitation being mispredicted by the tick-skip estimator.
- Fixed pre-1.17 players in boats and minecarts having their position discarded.
- Fixed swimming predictions offering jumps the player never pressed.
- Book writing no longer flags when the only page is blank.
- Improved precision across fluid levels, diagonal movement and sprinting to match the client exactly.
- Sprint hunger check now runs with settled state and correctly treats 6 food as hungry.
- Added missing collision shapes for potted golden dandelion and sulfur spike.
Fixes
- Fixed "No SLF4J providers were found" errors on startup. Log output from PacketEvents, the connection pool and Redis was being silently discarded; it now reaches the console.
Additions
- Support for 26.2's attribute-driven friction, air drag and bounciness, including the reworked bed and slime bounce. Older clients are unaffected.
- Updated to PacketEvents 2.13.1.
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:T4wGBvoh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aauFRVwy:T4wGBvoh"
}

