Tags
Creators
Details
1.1.1-beta
Compatibility
Changes
Hotfix: Update Checker
A critical defect in both UpdateChecker classes silently broke in-game update notifications on v1.1.0-beta — admins running v1.0.0-beta were never notified that v1.1.0-beta was available. This hotfix restores the update channel.
- Modrinth project ID typo —
XOF1R6bb→XOFIR6bb(one missingI). The v2 API call returned 404 silently; the JSONversions[0]was always null, so the "Update Available" banner never printed. - Wrong download URL in update banner —
/mod/craftyai→/plugin/craftyaito match the canonical Modrinth slug the project is published under. - Both defects existed in two parallel implementations:
craftyai-common/src/main/java/com/demonz/craftyai/common/UpdateChecker.java(used by Fabric 1.20, Fabric 1.26, and Forge)craftyai-plugin/src/main/java/com/demonz/craftyai/UpdateChecker.java(Spigot 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:XOFIR6bb:B9XslZct"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XOFIR6bb:B9XslZct"
}

