Tags
Creators
Details
1.5
Compatibility
Changes
-
Config Migration:
-
Doesn't use default bukkit config() anymore, and instead we use YamlConfiguration that finally doesn't replace "" to '' or sometimes its just plain text
-
Mace-was-crafted: config option was moved to data.yml, as it is used for data checking, and editing config while this value was also in config, could result in mace duplication, if for example it was 0, and someone crafted a mace it becomes 1, but once you finish editing config, and for your file its still 0, saving will make it 0, and then someone can craft it again
-
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:VhRnDS8v:hfZLW3tb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VhRnDS8v:hfZLW3tb"
}

