Links
Tags
Creators
Details
1.0.22+26.3
Compatibility
Required content
Changes
1.0.22 · Minecraft 26.3
New
- Block check (Ctrl+B) now highlights schematic entities too — cushions, armor stands, item frames, paintings. A red box means the entity is missing or the frame is empty; a yellow box means it stands wrong (rotation, another cushion colour, another item in the frame). Same layers, area and range as blocks, and the count goes into the check summary.
- Padlock in the placement editor. Type the coordinates, press the padlock, and the schematic can no longer be moved by the mouse, the keys or Litematica's tool (it is Litematica's own lock). A locked placement shows a gold padlock and a gold frame in the world. In the Placements tab the right-click menu has Lock / Unlock. Cancel in the editor restores the lock as it was.
- "Look at the world" in the placement editor, like in the Selection tab. The editor closes, you walk and fly, and a placement card with live coordinates stays in the top right. R puts the cursor on the card (fields, +/−, rotate, mirror, To me, Move in world, padlock), Esc returns to the editor.
- Placement editor buttons are coloured by meaning: Done green, Cancel red dashed, −/+ in their axis colour, rotate and mirror blue, the padlock gold.
- Rename schematics in the Library. Right-click a schematic → Rename…. Placements in the world, block replacements and disabled blocks from Materials, Zone Focus zones and the thumbnail move to the new name with the file. The message after renaming has Undo.
- Easy Place lights fire. Fire and soul fire from the schematic are placed with flint and steel (or a fire charge): the mod clicks the block under the cell, as a player would.
- Redstone, rails and string are visible in holograms. The "missing block" overlay used to cover them with a solid blue square; now they get only the cell frame and you can see where the line goes. Settings → Ghost Alpha → Redstone, rails and string without fill (on by default).
Fixed
- fix — a patterned banner was not placed while a banner of the same colour without a pattern (or with another pattern) was in hand. Easy Place thought the right banner was already in hand and did not take it from the backpack, so the cell stayed empty. It happened mostly with a full hotbar. Now the banner with exactly the right pattern is taken.
- fix — Easy Place did not place string. A string cell was silently skipped in survival and creative.
- fix — not every row of the Materials tab could be disabled — Glow Berries, a flower in a pot, dirt under farmland and other rows whose item differs from the block had no Disable. Every row can be disabled now.
- fix — water and lava from the schematic were never counted as built, so the Water Bucket row never went down.
- fix — with "Count up to Y" blocks were counted on the current layer only when Litematica's layer mode was not All. Blocks are now counted up to Y, like entities.
- fix — banners, pots and heads inside a shulker box or bundle did not count as "with you" in the HUD. Plain blocks did; now both do.
- fix — Light levels were merged into one row of the Materials table. Each level has its own row now, as in the HUD.
- fix — after removing the last placement, "HUD list" in the table still showed the old rows.
- fix — typing into a coordinate locked by axis in Litematica silently did nothing. The field is grey now and the editor says the axis is locked.
Also out for 26.2 and 1.21.11. With Easy Place Fix+ installed, update it to 1.0.22 too: the banner, string and fire fixes for Easy Place live there.
📦 You need
Minecraft 26.3 · Fabric Loader · Fabric API · malilib · Litematica · Java 25 · Syncmatica — optional · Voxy — 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:JmqA4Alf:FOehq8jL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JmqA4Alf:FOehq8jL"
}

