2.6.0
Compatibility
Changes
Keep custom variant prices separate restored the OP check for the webadmin command added custom display names, fixed stored_item delivery, consolidated templates, and added /shopadmin setname fixed special item display names not rendering in the shop GUI routed stored_item delivery through the dialog buy path made stored_item variants use their own base price with inflation kept custom variant prices separate
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:OzSmbRQS:OA2TTi9V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OzSmbRQS:OA2TTi9V"
}

