Tags
Creators
Details
v2.1.4
Compatibility
Changes
a bunch of internal cleanup (please report any regression !) tested for minecraft 26.3
The cleanups also cause ? some API "breakage" not really, just make the contract more explicit by enforcing nullability everywhere. It now make all the expectations explicit instead of having some marked as nullable/not-nullable, some not
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:S75Ueiq9:Dz1shMKL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:S75Ueiq9:Dz1shMKL"
}

