Creators
Details
2.0.3
Compatibility
Changes
Version 2.0.3
Fixed a critical container issue:
Until now, containers (chests, barrels, shulker boxes, etc.) had a serious problem where, when a blueprint under construction required a single item, that item was removed from all stacks of the same type instead of just one.
For example, if a build required 1 dirt block and a chest contained two stacks of dirt, normally one stack should go from 64 to 63 while the other remains unchanged. Instead, both stacks were reduced to 63. This meant that for a single block, you were effectively paying 2 items.
This issue has now been fixed. I apologize to everyone who encountered this problem in survival mode while using containers.
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:pTRNOhPP:XssXx0bW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pTRNOhPP:XssXx0bW"
}

