Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 months ago
Updated yesterday
All versions
1.0.18+1.21.11
Release
Litematica Material HUD & Chest Finder 1.0.18+1.21.116 days ago 42
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
1.0.18 · Minecraft 1.21.11
New
- Disable anything in the materials list. Right-click a row → Disable block now also works for water and lava (waterlogged stairs, slabs and fences stay dry), for entities — item frames, armor stands, paintings, minecarts, boats, End crystals — and for items in frames (the frame stays, empty). A disabled row stays in place, greyed out, with a gold button to bring it back. It leaves the holograms, the HUD, Easy Place and every export, and is remembered for that schematic file.
- Disable from the HUD list. The same menu item in the HUD list turns the block off in every enabled placement's schematic.
- The export window now says how many disabled blocks are left out of the table.
Fixed
- fix — "Only missing" did nothing in a schematic's list. A placed schematic is now checked against the world over the whole build — Litematica layers and the hologram don't matter, the placement can even be turned off. With the toggle on, Total becomes Left (what is still to place, the same number as in the HUD list) and the rows are sorted by it. For a schematic that isn't placed, the toggle is greyed out and its tooltip says why.
- fix — an entity hologram could vanish (a frame or an armor stand) when the same schematic was placed twice: Litematica's rebuild threads could overwrite each other.
Also out for 26.3 and 26.2.
📦 You need
Minecraft 1.21.11 · Fabric Loader · Fabric API · malilib · Litematica · Java 21 · Syncmatica — optional · Voxy — optional
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:JmqA4Alf:sYd9brkX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JmqA4Alf:sYd9brkX"
}

