All versions
1.2.0
Release
Custom Item Highlighter 1.2.03 months ago 379
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
1.2.0
Added
- Multi-MC-version support. Separate jars now built for Minecraft 1.21.11 (Yarn), 26.1, 26.1.1, and 26.1.2.
- HUD overlay compatibility. The highlight now appears wherever an item is rendered — vanilla container slots, the hotbar, MiniHUD / Tweakeroo's inventory preview, and Inventory HUD+'s armor / hotbar / inventory overlays. Previously only items rendered through the public 3-arg
item()path (essentially just picked-up cursor items) were caught.
Fixed
- Highlight no longer shows as a solid box on items with transparent pixels. The 4-thin-rectangle border is drawn at the slot edges only; the item area in the middle is left untouched.
- Highlight renders under the item sprite and the count number / damage bar / cooldown overlay. Switched the inject point from
RETURNtoHEADso the item and its decorations always draw on top of the border. pack.mcmetaaccepted by MC 26.1.x. Datapacks use themin_format/max_formatarray form required forpack_format > 81.
Changed
- Lore-color highlight is on by default. Items with a "Tier" line in their lore that contains multiple colored characters cycle through those colors automatically. Toggle off in the config if you preferred the static color.
- Custom items in the vanilla hotbar are now highlighted on the HUD. Lower the alpha or open an issue if you want a config toggle to suppress this.
Implementation note
- Switched from a
HandledScreen/AbstractContainerScreenslot mixin to a universal mixin on the private 6-argitem(LivingEntity, Level, ItemStack, int, int, int)(or the YarndrawItemequivalent on 1.21.11). All publicitem()overloads delegate to this method, so the highlight fires once for every rendered item regardless of which entry point the caller used.
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:57dJdvhY:GckXGaVv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:57dJdvhY:GckXGaVv"
}

