lumitier
Docs

Installing

Where the jar files go, and what to do when a mod doesn't show up.

Where the files go

Drop the .jar files into your mods folder:

Windows %APPDATA%\.minecraft\mods
macOS ~/Library/Application Support/minecraft/mods
Linux ~/.minecraft/mods

If you use a launcher with separate instances — Prism, MultiMC, the Modrinth app — each instance has its own mods folder, and that is the one that counts.

The file without -sources in its name is the mod. The sources jar is the code, it does nothing in game.

One version per mod

Never leave two versions of the same mod in the folder. Which one Fabric loads is not predictable, and the mismatch shows up as a crash somewhere else entirely — usually a missing method, minutes later, in a completely unrelated screen.

When you update, delete the old jar rather than just adding the new one.

When a mod doesn’t appear in the hub

The hub lists what registers itself, not everything installed. A mod that is missing from the list is either not loaded at all, or too old for the LumiLib you have.

Check logs/latest.log for lines mentioning the mod. Fabric says plainly when it refuses to load something and why.

When the game doesn’t start

Fabric prints the reason in the launcher’s log before the window appears. The two usual causes are a missing dependency — Fabric API or YACL — and a version that doesn’t match your Minecraft.