Tags
Creators
Details
0.1.2+26.2
Compatibility
Required content
Changes
0.1.2 · Minecraft 26.2 — Sections
The 0.1 line comes to Minecraft 26.2 (the last 26.2 build was 0.0.8). Your existing zones are kept.
New
- Sections — several schematics, each split its own way. A section is one or more schematics plus a rule: a grid, the schematic's sub-regions, or zones drawn by hand. New section window, Combined bounds for several schematics, a section list in Manage zones (rename, hide, split again, delete), S2 · Z7/24 labels in the HUD, Next / Previous section keys.
- Other sections don't get in the way: Hide other sections (on by default) and Other sections' frames.
- Cut with the mouse on the 2D map, one block per step; right-click for Cut here / Remove cut. 2D map from the top, front and side.
- Look: Aell UI, Vanilla or Vanilla+ (Counting → Interface style).
- Chat messages are off by default — feedback appears above the hotbar.
Fixed
- fix — a clear Fabric window instead of a crash on world join with an old Fabric Loader.
- fix — Material HUD numbers did not refresh when a second schematic was enabled, moved or turned off inside a zone; a manual zone and a grid counted overlapping schematics differently; auto-switching jittered where two zones overlap.
Not yet on 26.2
3D of a section made of several schematics, the cut handles in 3D and the height slider need a newer Material HUD than the one available for 26.2. Zone Focus detects this by itself: 3D works for single-schematic sections, as before.
📦 You need
Minecraft 26.2 · Fabric Loader 0.19.5+ · Fabric API · malilib · Litematica · Java 25 · Litematica Material HUD (optional)
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:9sJgSVdW:BWJQW5DU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9sJgSVdW:BWJQW5DU"
}

