Creators
Details
1.17.2
Compatibility
Changes
[BUILD] Lint every module with the gradle-plugin linter\n[BUILD] Run the architecture checks on pull requests\n[FIX] Play the item pick-up sound only when an item was added\n[BUILD] Drop project dependencies nothing imports\n[REFACTOR] Split soul storage into data/dao contracts and data/exposed\n[REFACTOR] Pick up a soul in one use case with its rules on the model\n[REFACTOR] Show armor stands through a display contract chosen in DI\n[REFACTOR] Move command, core, platform and renderer files into kind packages\n[REFACTOR] Move the command failure handler and time-ago text into the command unit\n[REFACTOR] Keep the throttle and flow helpers beside the soul call worker\n[REFACTOR] Name the soul DI modules without Service\n[DOCS] Describe every unit in a one-sentence README\n[REFACTOR] Name lambda parameters and order declarations as detekt checks\n[BUILD] Accept the renderer variant packages until the checker knows them\n[CHORE] Bump version to 1.17.2
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:tnr41XhG:dTaJk7Ht"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tnr41XhG:dTaJk7Ht"
}

