2.1.0+26.1.2-neoforge
Compatibility
Changes
2.1.0 - The client mod now keeps itself up to date automatically. On startup it silently checks Modrinth in the background and downloads any newer version, applying it when you quit the game - no action needed. You can turn this off in config/modchecker.json (set auto_update to false) or with -Dautoupdate.enabled=false. Both auto-update and telemetry are disabled in development environments. No gameplay or networking change otherwise; the client still only talks to servers running ModChecker.
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:pZZSQM2X:Is7dj4Dj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pZZSQM2X:Is7dj4Dj"
}

