Tags
Creators
Details
5.6.13
Compatibility
Changes
1e6341c fix: title in config only appearing after a reload - Thatsmusic99
02544cf chore: update wiki link - Thatsmusic99
4906c9f chore: redundant import - Thatsmusic99
61de326 fix: EXP payments being calculated incorrectly - Thatsmusic99
97bca7c fix: plugin not handling unloaded worlds in /spawn, /w debugging - Thatsmusic99
11337b3 fix: main spawn not being loaded in non-main worlds - Thatsmusic99
cdd30da fix: #58 and #109 - backport v6 weak player referencing - Thatsmusic99
6588ae4 fix: check for void air - Thatsmusic99
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:BQFzmxKU:9XlCBrpp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BQFzmxKU:9XlCBrpp"
}
