Tags
Creators
Details
2.3.3
Compatibility
Changes
Fix: UUID matching not working properly for offline players / Geyser servers (thanks @itscainnotkain)
Fix: Duplicated command queue handling for Folia (thanks @sluhtie)
Fix: Permission checks on certain Fabric versions (thanks @chaaadii )
Fix: /buy GUI will no longer show if a store is not connected
Fix: ArrayIndexOutOfBounds exception for multithreaded servers
Fix: Memory optimization and thread-safety improved for Fabric and BungeeCord
Fix: Backwards compatibility support for all GUI colors
Fix: Incorrect telemetry sent from Fabric plugins
Fix: ClassCastException on certain store types when commands are executed
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:nRA0jiJt:VgBqrRqc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nRA0jiJt:VgBqrRqc"
}

