Tags
Creators
Details
Licensed MIT
Published 3 weeks ago
Updated 5 days ago
All versions
1.1.0+1.21.11-neoforge
Release
1.1.0+1.21.11last week 16
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Changes
1.1.0
- Per-item model and texture overrides through the vanilla
minecraft:custom_datacomponent ({armor_model_api:{model, texture, glowmask, trim}}), settable by commands, loot tables, recipes and datapacks - no custom component, the library stays client-side - A stack naming both
modelandtexturetakes over an item nobody registered (any vanilla or third-party armor piece), with a default glow + trim pass stack ArmorRenderContextcarries the base texture in effect (texture()) and the stack'soverrides(); layers deriving assets from the base texture should read it from there
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:onz2NN2n:xxj8GvZf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:onz2NN2n:xxj8GvZf"
}

