If Minecraft stops on the loading screen with a message saying Litematica “requires malilib” — or that the MaLiLib version you have is outside the range Litematica needs — you have a version mismatch. Litematica cannot start without MaLiLib, and MaLiLib is not interchangeable between game versions: each Litematica build expects the MaLiLib line released for the same Minecraft version, in practice the current build of that line. The good news is that this is the most mechanical fix in this whole section — match the pair, remove the leftovers, and the error is gone.
What the Error Actually Means
Fabric Loader checks every mod’s declared dependencies before the game opens. Litematica declares MaLiLib as a required dependency with a version range. Players typically see one of three things:
- A loader error along the lines of “Mod ‘Litematica’ requires ‘malilib’, which is missing” — the library is not in the mods folder at all.
- A similar message saying the installed MaLiLib version does not satisfy the range Litematica asks for — you may see wording mentioning a required range between two version numbers. That means your MaLiLib is from the wrong line or an outdated build of the right line.
- The game reaches the title screen but Litematica behaves as if it is not there — rarer, and usually a duplicate-jar problem (see below) rather than a true mismatch.
The Fix: Install the Matched Pair
Use the pair for your Minecraft version. Both files go in the same mods folder.
| Minecraft | Litematica | MaLiLib | Java |
|---|---|---|---|
| 26.3 | 0.29.1 | 0.30.2 | 25 |
| 26.2 | 0.28.8 | 0.29.6 | 25 |
| 26.1 / 26.1.1 / 26.1.2 | 0.27.14 | 0.28.12 | 25 |
| 1.21.11 | 0.26.16 | 0.27.20 | 21 |
| 1.20.1 | 0.15.4 | 0.16.3 | 17 |
- Open your
modsfolder (the one belonging to the instance/profile you actually launch). - Delete every existing
litematica-*.jarandmalilib-*.jarin it. Do not just add the new files next to them. - Download the matched pair for your game version from the download page — every row there lists both files together.
- Drop both jars into
mods, unzipped, and start the game with the Fabric profile.
The file names tell you what you have: malilib-fabric-26.3-0.30.2.jar is MaLiLib 0.30.2 for Minecraft 26.3. If the game version in the file name is not your game version, the file is wrong no matter how new it looks. The full release-by-release table is on the version history page, and the latest version page tracks the current pair.
The Duplicate Jar Trap
The most common reason this error survives a “correct” reinstall: the mods folder quietly keeps an old MaLiLib (or an old Litematica) next to the new files. With two MaLiLib jars present, the loader may pick the older one, refuse both, or report a duplicate mod — and the error message looks identical to the original problem, which makes people reinstall the same files in circles. Sort the folder by name, and make sure there is exactly one litematica-*.jar and exactly one malilib-*.jar. The same applies when you update after a Minecraft release: moving to a new game version means replacing both files, every time.
Not MaLiLib: The Loader Version Error
A different loader message says Litematica requires a newer Fabric Loader version. That is not about MaLiLib at all. Fix it by running the Fabric installer for your game version again and choosing the latest loader it offers, or by updating the loader inside your launcher’s instance settings. As a rule: read the error literally — it names the thing that is missing or too old. If it names malilib, fix the pair above; if it names the loader, update the loader; if the game crashes without a loader message at all, use the startup crash guide instead. A general sweep of symptoms is on the Litematica not working page.
How to Tell Which Versions You Actually Have
When the error will not go away, stop guessing from memory and read the evidence. First, the file names: every jar states its target in its name — malilib-fabric-26.2-0.29.6.jar is MaLiLib 0.29.6 built for Minecraft 26.2, and it will never satisfy a 26.3 install, no matter that it is “newer” than what you had before. Second, the loader’s error screen itself names the mod and the requirement it failed, and the mod list shows the versions that actually loaded. Third, remember the rhythm this creates: a Minecraft update is never just a Minecraft update for Litematica users. Each game version needs its own Litematica build and its own MaLiLib build, so the working habit is to treat the pair as one item — when you move the game, replace both jars together; and when an error names malilib, re-check the pair rather than swapping one file at a time and hoping. When in doubt, the pair table above is the whole answer.
Frequently Asked Questions
What MaLiLib version do I need for Minecraft 26.3?
MaLiLib 0.30.2, paired with Litematica 0.29.1. Each Minecraft line has its own MaLiLib line: 26.2 uses 0.29.6, 26.1.x uses 0.28.12, 1.21.11 uses 0.27.20 and 1.20.1 uses 0.16.3.
Can one MaLiLib version work for every Minecraft version?
No. MaLiLib is locked to the Minecraft version it was built for, just like Litematica. When you change game versions, replace both jars with the matched pair for the new version.
I installed the right MaLiLib but the error is still there. Why?
The usual cause is an old malilib jar still sitting in the mods folder next to the new one, so the loader uses or trips over the wrong file. Keep exactly one litematica jar and one malilib jar in the folder.
Next Steps
With the pair matched, the install guide shows the two in-game checks that confirm everything loaded, and the troubleshooting hub covers every other common failure.