Tags
Creators
Details
2.6.2
Compatibility
Changes
VoidAC 2.6.2
Fixed: false Simulation flags when landing after flight
Landing while flying, creative flight, spectator, or elytra produced Simulation violations on the first tick back under prediction. Landing while sneaking made it worst of all, with offsets large enough to trigger an immediate setback, so players were flagged and rubber-banded every single time they touched down.
The player's collision box was not being advanced while flight was active, so it stayedfrozen wherever they were last checked. The first tick that got predicted again tested its collision against that stale box, missed the floor the player had just landed on,and reported the whole descent as a violation.
This also affected leaving spectator mode and ending an elytra flight, which share the same code path.
Addition: Implemented back code from 2.6.0
Fixed some critical findings that made the simulation engine crash and ban legit players.
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:I3auCCPB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aauFRVwy:I3auCCPB"
}

