1.0.0
Compatibility
Changes
Changelog v2.0.0 Added a complete AntiESP system to prevent unauthorized player tracking and wall-vision exploits. Improved entity visibility protection and server-side validation. Enhanced detection of suspicious ESP-related behavior. Added real-time monitoring for hidden player information access. Reduced false positives and improved overall accuracy. Optimized performance with lower resource usage. Strengthened security against external cheat tools and memory readers. Fixed multiple bugs and stability issues. Improved logging and administrative reporting features. General code cleanup and backend optimizations.
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:wU0cbYuH:adl4DY32"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wU0cbYuH:adl4DY32"
}

