How to Install Ukulib Mod Safely on Fabric or NeoForge

Installing a library mod is straightforward when the dependency chain is clear. The important work happens before copying the file: version matching, loader matching, and preserving a rollback path.

1. Record the working profile first

Before changing dependencies, copy the instance or at least preserve worlds, configs, and the current mod list. A backup turns troubleshooting from guesswork into a reversible test.

2. Identify the exact Minecraft target

Use the Ukulib suffix to confirm the intended game version. Current 2.2.0+26.3 targets Minecraft 26.3; legacy 1.21.x profiles use corresponding 1.x releases rather than the current 2.x line.

3. Match Fabric or NeoForge

Current Ukulib 2.x supports both Fabric and NeoForge through separate loader-specific builds. Install the build for the loader your profile actually runs.

4. Use the built JAR, not repository source

Minecraft loaders expect a compiled mod JAR in the mods folder. A GitHub source ZIP is useful for source inspection or development but is not a drop-in replacement for the released JAR.

5. Launch and inspect the first relevant error

If the game does not start, look for the first message that names a missing dependency, unsupported version, or loader conflict. Fix one dependency problem at a time instead of replacing several files at once.

6. Restore the wider mod list gradually

Once the minimal required set works, add optional mods back in groups. This makes incompatibilities easier to isolate and leaves you with a known-good baseline.

Continue with the site guides

Use the compatibility section to check versions, then review the troubleshooting section before changing several dependencies at once.