Tags
Creators
Details
2.6.8
Compatibility
Changes
VoidAC 2.6.8
Fixed
Console flooding from crasher tools. A malformed packet used to dump a full
netty stack trace to the log, so tools that spam invalid packet ids could bury
your console in seconds. It is now a single line, and the player is still
kicked. Set debug-packet-exceptions: true in the config if you need the full
trace back for debugging.
Added
- Malformed packets now report who sent them. Staff get an alert naming the player.
Changed
- Transaction ids are randomised per player instead of counting down from a fixed starting point so that modified client can't detect VoidAC.
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:g0iM8DsI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aauFRVwy:g0iM8DsI"
}

