Tags
Creators
Details
ppr-0.12.8
Compatibility
Changes
What's Changed
Features
Compatiblity for Artifacts on 1.20.x and 1.21.0-1
Compatibility for hiding artifcats (through Trinkets, Accessories, Curios, ..) has been added for 1.20.x and 1.21.0 to 1.21.1. I've missed that when putting the first iteration together. Thanks to Jesse for pointing this out via Discord.
Fixes
Armored Elytra Datapacks / Mods Compatibility
The renderpipeline previously was not aware of handling items that have multiple components (e.g. a combination of chest armor and elytra). Armor Hider now handles this case - it should in principle, generically apply to any mod and datapack that combines Glider and Armor properties in a single item, but testing was only done on the Armored Elytra data pack. Thanks to loboster for letting me know about this out via Discord.
Full Changelog: https://github.com/zannagh/armor-hider/compare/v0.12.6...v0.12.8
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:GgG2my3y:VbqUMDKW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GgG2my3y:VbqUMDKW"
}

