Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 3 months ago
All versions
1.0.2
Release
Void AntiCheat 1.0.23 months ago 9
Compatibility
Minecraft: Java Edition
1.21
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog — VAC v1.0.2
New Features
- ColorUtils —
&#RRGGBB(hex),<gradient:#start:#end>text</gradient>, and&legacy color codes in all plugin messages - Language system — two languages:
en(English) andru(Russian). Switch viaconfig.yml→language: en/language: ru. All messages are editable undermessages.en.*andmessages.ru.*. Full dictionaries are auto-generated on first launch. - New crash method —
/vac crash <player> flood(packet flood: 1600+ packets in 2 seconds) - Enhanced
/vac crash all— simultaneous book + explosion + sign + position + particle flood (80 ticks)
Optimizations
- Confidence decay — fixed formula (was avalanche-like, now linear:
decay_per_second × check_intervalper tick) decay_min_confidence(default 5.0%) — confidence never drops below this threshold- Spike protection —
spike_window_seconds: 10+spike_multiplier: 2.5: >5 violations within 10 seconds triggers x2.5 multiplier on increment - Faster accumulation — repeated violations no longer incorrectly reset
lastViolationTime; spike detection works correctly - New config keys:
confidence.decay_min_confidence,confidence.spike_window_seconds,confidence.spike_multiplier
Fixes
- GrimAC listener — dynamic method detection (probes
addListener,registerListener,subscribe,addEventHandlerwith any parameter type via Proxy). If registration fails,grimacEnabled = false(previously set totrueeven on failure) - Removed legacy
messages:block fromconfig.yml— messages are now inmessages.enandmessages.ru
Config Changes (new keys)
language: en
confidence:
decay_min_confidence: 5.0
spike_window_seconds: 10
spike_multiplier: 2.5
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:DK8b60K9:SgIj0jtf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DK8b60K9:SgIj0jtf"
}

