1.2
Compatibility
Required content
Changes
Changelog
UpdateChecker
Bug Fix — Spurious updates on latest version
parseVersion() now strips a leading v/V before parsing. Modrinth version strings like v1.2.3 were previously parsed as v1 → 0, making every release appear newer than the installed version and triggering a re-download even when already up to date.
Refactor — Hardcoded Modrinth project ID
Removed the projectId instance field and its constructor assignment. The ID is now a private static final constant (PROJECT_ID = "eT7gbibF"). The dead isBlank() / "YOUR_MODRINTH_PROJECT_ID" guard in start() was removed alongside it.
Improvement — Side-by-side version log
Both the Modrinth version and the installed version are now logged before the comparison runs, making any future version string mismatches immediately visible in the console.
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:eT7gbibF:XHYpneVR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eT7gbibF:XHYpneVR"
}

