Tags
Creators
Details
Licensed Apache-2.0
Published 2 years ago
Updated 6 months ago
All versions
1.9.4
Release
Kauri AntiVPN 1.9.4last year 861
Compatibility
Minecraft: Java Edition
1.21–1.21.9
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platforms
Bukkit
BungeeCord
Paper
Purpur
Spigot
Velocity
Waterfall
Changes
[1.9.4] - 2025-09-30
Added
- New dependency management system with automatic library loading and relocation
- Caffeine cache implementation to replace Guava
- Sponge platform support with full event handling and command system
- UUID lookup functionality for player validation
- Enhanced kick checking system with scheduled task execution
- Support for Java 17 and Java 21 runtime environments
- New database metrics tracking for bStats
Changed
- BREAKING: Minimum Java version upgraded from 8 to 17
- Replaced Guava cache with Caffeine cache for better performance
- Modernized player checking system with asynchronous processing
- Improved database connection handling with proper resource management
- Enhanced VPN/Proxy detection with new
CheckResultandResultTypesystem - Updated Maven dependencies and build process
- Reorganized project structure (Assembly → Universal module)
- Improved error handling and exception logging throughout codebase
Fixed
- H2 database compatibility issues with automatic backup and recovery
- Memory leaks in database result set handling with try-with-resources
- Thread safety issues in player cache management
- Command registration and unregistration during plugin lifecycle
- Proper cleanup of database drivers on shutdown
- Resource management in SQL connections and prepared statements
Removed
- Guava dependency (replaced with Caffeine and built-in utilities)
- Legacy cached response handling system
- Old table format compatibility code
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:5UF9tf3G:YSKZ6ycb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5UF9tf3G:YSKZ6ycb"
}

