2.4
Compatibility
Changes
Added startup and reload config migration for bundled YAML files that preserves existing server values and creates backups. Improved custom pack directory handling, URL encoding, async pack hashing, resource-pack server safety, and enforcement config key usage.
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:8yUJvGSE:P2Pq1OaO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8yUJvGSE:P2Pq1OaO"
}

