Tags
Creators
Details
1.21.11-0.8.2
Compatibility
Changes
Changelog 1.21.11-0.8.2
Fixed REST API parsing when the API response is wrapped in a success object. Fixed delivery deserialization issues caused by API fields being returned as strings instead of integers. Prevented errors when optional fields (order_id, delivered) are missing from the API response. Fixed startup version display not updating correctly due to resource filtering issues. Improved compatibility with Minecraft 1.21.x (tested up to 1.21.11). Improved the Delivery model more tolerant to API changes and backward compatible. Improved error handling when the REST API returns success = false. Cleaned up resource processing to ensure correct plugin.yml version expansion.
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:t8eLuzvc:OE26ceSW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t8eLuzvc:OE26ceSW"
}

