Litematica 1.20.1

Minecraft 1.20.1 is a long-lived modpack version, and its Litematica build has not changed since July 2024: litematica-fabric-1.20.1-0.15.4.jar, paired with malilib-fabric-1.20.1-0.16.3.jar. If your 1.20.1 pack runs on Forge, the Fabric jars will not load and you need a different file. Both cases below, as read on 2026-10-05.

1. Check your loader. Fabric 1.20.1 takes the original mod; a Forge 1.20.1 pack needs the Forgematica port instead (see below).
2. On Fabric, make a 1.20.1 instance and launch it once so the mods folder exists.
3. Download Fabric API for 1.20.1, then malilib-fabric-1.20.1-0.16.3.jar from Modrinth.
4. Download litematica-fabric-1.20.1-0.15.4.jar and put all three jars in the instance's mods folder.
5. Open a world and press M to confirm the Litematica menu, then load a .litematic from the schematics folder.

What is pinned to what

Unlike newer lines, the dependency here is a family (0.16.x), not a minimum. A newer MaLiLib will not do. That is the usual reason a 1.20.1 launch fails after someone updates everything to the latest: MaLiLib 0.17 and up belong to later Minecraft versions.

Fabric or Forge on 1.20.1?

Litematica is a Fabric mod. Its Modrinth description says the Forge version is only for 1.12.2 and that later Forge versions have third-party ports. For 1.20.1 that port is Forgematica: Modrinth lists Forgematica-0.1.13-mc1.20.1.jar (Forge, 2025-04-19) with MaFgLib as its required library. It is a different project with its own behaviour, so treat the option names on this site as Fabric Litematica's. The decision between the two is on Litematica on Forge and NeoForge. If a Forge pack is the only reason you are stuck, a second Fabric 1.20.1 instance for building is often simpler.

Security note for an old line

The July 2026 path-traversal announcement lists fixed builds for Minecraft 1.21 and newer (table here); 1.20.1 is not in it, and its latest build is from 2024. Download only from the Modrinth or CurseForge project page and treat files sent by a server as untrusted.

Loading a schematic

Put the file in the schematics folder of the instance, open a world, press M, choose Load Schematics, select it, and place it. Steps and paths per launcher: how to import a litematic. A 1.20.1 client runs on Java 17; no extra setup is needed with the official launcher.

Generator files on a 1.20.1 client

The generator writes Litematica format version 6 with Minecraft data version 4189 (Java 1.21.4). A 1.20.1 world is data version 3465. The 1.21.x builds of Litematica print a future-version warning in that gap; the 0.15.4 jar does not contain that message, so it will read the file silently. The risk is in the blocks, not the header. A comparison on 2026-10-05 of all 96 block ids the generator can write against the PrismarineJS 1.20 block list found none missing, including cherry and bamboo planks, which arrived in 1.20.

Still, nobody here has loaded a generator file into 1.20.1, so do this once: generate a small build, load it, open the Material List (M, then Material List) and compare the block counts with the list on the generator page. A missing line means the client dropped a block. If you want zero guesswork, build in a 1.21.4 instance.

Common 1.20.1 errors

• Fabric stops on malilib. Wrong line (not 0.16.x) or Fabric API absent. See MaLiLib missing.
• Nothing happens in a Forge pack. The Fabric jar is ignored there. Use the port or a Fabric instance.
• Schematic loaded but not visible. Placement is in the wrong spot or rendering is toggled off; see schematic not showing.

Test file: the schematic generator makes a .litematic plus material list. All other versions are in the Litematica download table.

Reviewed 2026-10-05. Not affiliated with Mojang or Microsoft.