Tags
Creators
Details
1.5.0
Compatibility
Changes
Changes:
- The update checker has been completely revamped!
- Previously, update checker contacted the SpigotMC API to check for updates, we now use the Modrinth API!
Why?
This change is being done to prepare for when I no longer post updates on Spigot. While I love the Spigot platform, and will still support the server software for now, its site is super outdated, writing change logs and posting updates has become tedious.
Along with that, this change allows me to give information about the update when notifying users about the update! This wasn't possible without switching API's (or at least wouldn't have been worth it)
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:CD4bmArk:KFPR1ynS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CD4bmArk:KFPR1ynS"
}

