Litematica turns Minecraft builds into copyable schematics

Litematica was built for players without Forge on the client

Litematica started as an alternative to Schematica, and the reason matters more than the feature list. The README states it was created for players who do not want Forge installed on their client, which is why it was developed for LiteLoader in the first place. That constraint shaped the whole project. A schematic mod that saves and restores block regions has to run somewhere on the client, and if the target audience is avoiding a heavyweight mod loader, the tool has to live inside whichever lightweight loader is already there. The result is a client-side mod, which means the world editing happens on the player's machine rather than on the server. The topic list on the repository places it firmly in the creative mode toolset, alongside schematic pasting, area cloning, moving, filling, and deletion.

One port set at a time, from LiteLoader through to Fabric

Litematica is not a single build but a family of ports across Minecraft versions and loaders, and the README is specific about where each one stands. It is primarily developed on MC 1.12.2 for LiteLoader. It has been ported to Rift on MC 1.13.2, and ported for Fabric on MC 1.14 and later. Forge versions exist for 1.12.2. For Forge on 1.14.4 and later, the documentation says ports are planned but blocked, because Forge will need to start shipping the Mixin library before those can happen. That last clause is the honest bit: it is a dependency on a third party roadmap rather than on work Litematica itself controls. Anyone planning a Forge based pack on a modern version has to watch that upstream change rather than the Litematica repository.

malilib is a hard dependency, Fabric API is not

The download note in the README is short and worth reading literally: Litematica also requires the malilib library mod, but Fabric API is not needed. That is unusual enough to call out because the usual expectation for a Fabric mod is the opposite. Malilib appears to be the companion library that holds shared utility code rather than something players install separately by choice, and the documentation treats its presence as a non-negotiable part of the install. The absence of a Fabric API requirement is the other side of the same coin, since the newer ports are built on Fabric without pulling in the full API mod. Anyone scripting an installation for players should treat the pair of jars as a unit: Litematica without malilib is not a working configuration, and the README does not describe what the failure looks like when one is missing.

Building the mod from the repository with Gradle

The repository includes gradlew, gradlew.bat, build.gradle, settings.gradle, gradle.properties, and a src directory, so the source builds with the bundled Gradle wrapper. The README lists the steps: clone the repository, open a terminal in that directory, and on 1.12.x run the decompilation setup task first. The wrapper task is the long pole for 1.12 development, since Minecraft has to be decompiled and mapped before the mod can compile against it:

gradlew setupDecompWorkspace

The README notes that this step can be skipped if the same 1.12.x Minecraft version, the same mappings, and the same mod loader have already been set up for another project. After that, the build task produces the jar:

gradlew build

The compiled jar ends up inside build/libs/. The default branch is ornithe/1.12.2, so a fresh clone lands on the 1.12.2 line rather than on the newest port, and switching to a different port means changing branches yourself. The README does not describe the build steps for the newer Fabric or Rift targets in detail, so anyone working on those branches is relying on the repository state rather than on documented instructions.

Compiled builds come from CurseForge and a personal site

For players, the README points to CurseForge for compiled downloads and to a separate address for more up to date development builds hosted by the author. The distinction matters in practice. CurseForge holds the stable, reviewed artifacts that most players will want, while the development build listing is where you look for the newest port for a version that CurseForge has not caught up with. The README describes the repository itself as having no GitHub releases, so there is no release page on the project's own hosting to compare against. That is a small detail that changes how you evaluate the project. The absence of tagged releases means you cannot infer a support timeline from the repository page, and you have to check the download listings instead to know which versions have actually shipped.

Schematica does the same job on Forge, with a different loader requirement

The alternative named in the README is Schematica, the mod Litematica was written as an alternative to. The difference is not in the feature list, since both deal in saving and restoring regions of blocks. The difference is the installation requirement. The README's stated reason for Litematica's existence is that its target players did not want Forge on the client. Litematica was created so that players could keep schematics without installing Forge, using LiteLoader, Rift, or Fabric depending on the Minecraft version. The practical decision for a server administrator is therefore about the client pack rather than the feature set. If your players already run Forge and you are happy with that, Schematica is the path with fewer moving parts. If you want the schematic workflow for players on lightweight loaders, Litematica is the version that reaches them.

The Forge ports depend on somebody else's Mixin timeline

The most important limitation in the README is a dependency on another project. Forge ports for 1.14.4 and later are planned, but the documentation explains that Forge will need to start shipping the Mixin library before those can happen. That makes the modern Forge path contingent, and it also means the 1.12.2 LiteLoader build remains the primary development target even though newer versions exist. The default branch reinforces the same point: ornithe/1.12.2 is where development happens by default. A team standardising on Forge for a modern server should treat Litematica as unavailable for now rather than as pending, and should plan for a different workflow until Forge ships Mixin. The documentation is unusually clear about this, which is worth crediting, because it prevents a pack builder from chasing a port that cannot exist yet.

LGPL-3.0, a profiler donation, and steady repository activity

Litematica is licensed under LGPL-3.0, which is a condition many server owners check before distributing a client mod with their own edits. The repository also contains a LICENSE.txt, a .gitignore, .gitattributes, and a .github directory. The last push to the repository was on 2026-10-17, so the code is moving. The README also notes that the developers use YourKit, which provides profiler licences for the project to help with performance work. That is a modest signal about how the team works rather than a user facing feature, but it is the kind of detail that tells you the project has a maintainer paying attention to runtime cost. The repository itself carries no GitHub releases and no homepage, so the CurseForge listing and the author's build site remain the authoritative channels for what is out there.

Editorial conclusion

Litematica fits creative mode builders and server administrators who want to prototype structures without hand placing every block, on clients running LiteLoader, Rift, or Fabric. It does not fit a Forge 1.14.4 or later setup, because the documentation states those ports depend on Forge shipping the Mixin library first, and it does not fit players who need schematic editing to work on a server they do not control. Before installing, confirm your client loader matches one of the supported combinations, add malilib alongside it, and check that the build you download matches your Minecraft version rather than the latest listing on CurseForge.

Frequently asked questions

Official sources

1. Issues
2. License: LGPL-3.0
3. maruohon/litematica on GitHub
4. README