Links
Tags
Creators
Details
1.2.2+26.3
Compatibility
Changes
Registry-related codecs now mention the registry it's part of when it cannot find an element or tag with a specific id. If those codecs mentioned a registry before, they now no longer do to prevent duplicate mentions of registries.
Changed messages:
| Old | New |
|---|---|
Cannot get a holder with id {id} |
Cannot get a holder with id {id} from registry {registry} |
Cannot get a registry tag with id {id} |
Cannot get a tag with id {id} from registry {registry} |
Registry tag {tag} is not part of the current registry set |
Tag {tag} is not part of the current registry set |
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:Hv68tUe1:VrDfhswp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hv68tUe1:VrDfhswp"
}

