Tags
Creators
Details
2.7.1
Compatibility
Changes
#VoidAC 2.7.1
Fixed
AntiSpoofA now respects the config (I forgot to hook it into the config...). The blacklisted client kick from AntiSpoofA is no longer forced unconditionally. It is now hooked into the config, so servers can decide whether Void should automatically disconnect players detected on blacklisted client channels.
Added
- Added anti-spoof.auto-kick to enable or disable automatic kicks from AntiSpoofA.
- Added anti-spoof.kick-message to customize the kick message used when auto-kick is enabled.
Changed
- AntiSpoofA still alerts staff when it detects a blacklisted client channel.
- Automatic disconnects now only happen when anti-spoof.auto-kick: true.
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:JS333j9r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aauFRVwy:JS333j9r"
}

