Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 months ago
Updated 23 hours ago
All versions
1.0.19+1.21.11
Release
Litematica Material HUD & Chest Finder 1.0.19+1.21.1123 hours ago 92
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.19 · Minecraft 1.21.11
New
- Look: Aell UI, Vanilla or Vanilla+. Settings → HUD → Interface style → Look. Aell UI is the default — nothing changes for you.
- Vanilla switches every window of the mod to Minecraft's own look: settings, schematic library, materials table, export, dialogs, placement editor, the HUD panel, toasts and tooltips get vanilla buttons, sliders, text fields, tabs, tooltip and pop-up frames, a blurred background and the Minecraft click sound. Settings become tiles "Name: value" in two columns, like Minecraft's Options — right-click a tile to reset it.
- Vanilla+ is the same, but settings are rows like Litematica's: name on the left, a value tile and Reset on the right.
- Litematica's own screens stay vanilla in both. Zone Focus and Easy Place Fix+ follow Material HUD's look unless they pick their own.
- Count up to Y. Settings → HUD → Count up to a height: the materials list counts everything at or below Y (−60…321) while the world still shows only your current layer — plan the whole lower part, build one layer at a time. The same toggle sits in the Materials tab of the schematics window.
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:7qv5z0tL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JmqA4Alf:7qv5z0tL"
}

