Tags
Creators
Details
3.4
Compatibility
Changes
Fixed the premium database name problem
Added client brand managing, now velocity or bungeecord will check on the user's client name, and if it's not allowed, it will be flagged
Added custom command bypass before the login
Changed how the packet events dependency work, now you can chose if the plugin should use the built-in (bundled) version of packet events, or get the api from the PacketEvents plugin
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:A5foNgax:CFJq35cu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A5foNgax:CFJq35cu"
}

