Links
Tags
Creators
Details
0.0.14+26.2
Compatibility
Required content
Changes
New: Litematica ZoneFocus module
Zone Focus splits a placed schematic into zones so you can build it piece by piece. It lives as Material HUD's third built-in module, next to Ghost Alpha and Easy Place, on a tab of its own.
- Off by default. One toggle on the new Zone Focus tab turns it on; all keybinds ship unbound.
- Every zone action lives on the tab: split into a grid (by zone count or by zone size), one zone per sub-region, a zone from your Litematica selection, the zone list with progress, clear. An action that can't run right now is greyed out with the reason.
- Materials are counted for the active zone, and Litematica layers keep working inside it — you scroll layers within the zone as usual (or count the whole zone at once, there's a toggle). Storage search can cover the whole zone too.
- Everything outside the zone is simply not rendered: no geometry is built for it at all, so a huge schematic stops weighing on FPS while you build its piece.
- Mark a zone with the mouse: hold LMB and drag a box right in the world; the scroll wheel moves a face. There's a slot-like button next to your inventory for it.
- The split screen shows a top-down diagram: it repeats the actual shape of the schematic and draws the cut lines and the first zone in the same colours you see in the world. Numbers can now be typed in — click a number, type, Enter.
- No duplicated settings. Zone blocks are checked by Material HUD's usual block check and chests are found by its usual storage search — both simply follow the active zone.
- Plays nice with the standalone mod. If the separate Litematica Zone Focus is installed, it keeps running the engine, and the tab here edits its settings — the values are the same on both screens.
In action




📦 You need
Minecraft 26.2 · Fabric Loader 0.18.2+ · Fabric API · malilib · Litematica · Java 25
Optional dependencies
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:6J7SZbgT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JmqA4Alf:6J7SZbgT"
}

