Tags
Creators
Details
3.1.1
Compatibility
Changes
This version fixes a critical cache logic issue on Velocity.
The bug occurred in a specific scenario involving plugin event ordering. When a subsequent plugin denied the login event, our plugin incorrectly maintained a player/event reference due to improper disconnect reason validation.
Note: This issue is only presented in our Velocity plugin, Bungeecord is not affected. Users are advised to upgrade to avoid Out of Memory crashes / issues on their proxies.
This version requires at least Java 17 to run. We recommend using Java 21 or newer. Please avoid running on obsolete Java versions.
Deprecation Notice: Support for versions 2.5.0 and older will be discontinued on October 31st. Please update to the latest version. If you encounter any issues during the upgrade, feel free to contact us.
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:UbiduGN8:hxY4jFqM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UbiduGN8:hxY4jFqM"
}

