1.3.2
Compatibility
Changes
Release 1.3.2 - Minor fixes and QoL
feat: added translation keys fix: harmonized deletion and append mechanics so that block that have no layered counterparts neither get appended or deleted fix: chat clog up on /pk and /pb commands and allow duplicate mod items in inventory
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:v8WesXLL:eIAfM0XW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v8WesXLL:eIAfM0XW"
}

