Tags
Creators
Details
1.1.4
Compatibility
Changes
1.1.4
- Fixed a bug that caused resource-pack defined item models with custom scaling to render improperly with custom item renderer.
- Fixed a bug that caused custom item renderer 3D models to have incorrect rotations.
1.1.3
- Fixed regression causing missing method crashes with some mods.
- Fixed a crash that could occur when rendering custom tooltips.
1.1.2
- Fixed a bug with custom item renderer causing items rendered with alpha to be upside down and with incorrect lighting.
- Fixed dependency information to correctly only work on 1.19.3.
1.1.1
- Fixed a bug where explicitly-placed tooltips sometimes had incorrectly positioned titles.
1.1.0
-
New item selector functionality is now available.
- Added wildcard selector (*), which matches all items.
- Selectors can now be negated by prepending them with a tilde (~).
- Multiple selectors can now be specified in a single string, separated by a plus sign (+). This will cause these selectors to be applied with an AND operation.
- See full documentation: Item Selectors Documentation
-
Fixed a bug that caused tooltip titles that spanned multiple lines to not be centered properly.
-
Injects tooltip color support into Forge on 1.19.3, where it is missing.
-
More developer utilities have been added:
- Iceberg's custom item renderer can now render item "detail" models directly into GUIs. This model is the worn/held model for equipment (armor/tools) and horse armor, and the entity model for minecarts and boats. For other items, it is the standard item model.
- Added vertex collector class, which can be used anywhere buffer sources are used to collect vertex information.
- Added checked buffer source class, which is a wrapper around buffer sources that can determine if any valid rendering occurred.
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:5faXoLqX:wog3r1ZM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5faXoLqX:wog3r1ZM"
}

