Tags
Creators
Details
Licensed MIT
Published last month
Updated last week
All versions
1.0.21+26.2
Release
Litematica EasyPlaceFixPlus 1.0.21+26.22 weeks ago 80
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
1.0.21 · Minecraft 26.2
The first 26.2 build since 1.0.6 — it carries everything released for 26.3 in 1.0.10–1.0.21. The highlights:
New
- Entities from the schematic: armor stands, cushions, item frames (with item and rotation), paintings, end crystals and minecarts.
- Finishing plants: vine tips trimmed with shears, glow berries added with bone meal, shelf mushrooms grown. Powered shelves filled from the schematic.
- Iron guards: Block placing off the schematic and Block placing the wrong block, with toggle keys.
- Hide blocks without support and Support from the next layer; Give up on cells the server refuses.
- Corner stairs connect the right way, snow layers from any side, pumpkins carved to match.
- Look: Aell UI, Vanilla or Vanilla+ for the settings window; chat messages are off by default.
Fixed
- fix — observers, pistons, dispensers, droppers and barrels face the way the schematic says.
- fix — redstone dust dots are no longer placed as crosses.
- fix — the second half of a slab is placed again.
- fix — patterned banners, decorated pots and heads with a name are taken from the inventory; blocks with item data no longer wait until you place one by hand.
- fix — fast building on servers no longer places the wrong block; cushions on deep snow, candles, turtle eggs, sea pickles, petals, curved rail rings and cauldron filling work.
- fix — the invisible Light block is placed, with exactly the right level.
📦 You need
Minecraft 26.2 · Fabric Loader · Fabric API · malilib · Litematica · Java 25
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:8yXLuMTt:c6vxfwwb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8yXLuMTt:c6vxfwwb"
}

