Ukulib Mod Forge vs Fabric: Current NeoForge Support Explained

“Ukulib mod forge” is a common search phrase, but the current 2.x project documentation names NeoForge rather than classic Forge. That distinction should guide file selection.

What current documentation supports

Ukulib 2.x explicitly documents Fabric and NeoForge. Version 2.0.0 introduced NeoForge support alongside the existing Fabric path.

Why “Forge” search intent needs clarification

Users often use Forge as a broad term for Forge-family loaders, but file compatibility is exact. A NeoForge build should not be relabeled or assumed to be a classic Forge build without explicit project support.

The artifacts are loader-specific

Current development dependencies use ukulib-fabric for Fabric and ukulib-neoforge for NeoForge, with ukulib-common available for loader-independent shared code in multi-loader projects.

Minecraft target still matters

Even after choosing the correct loader, the Ukulib release must target the right Minecraft version. For example, 2.2.0+26.3 targets 26.3, while legacy 1.21.x uses older 1.x builds.

How to choose between Fabric and NeoForge

Use the loader already required by the rest of your profile and by the dependent mod. Ukulib is a dependency; it should follow the platform decision rather than drive it.

Do not mix loader ecosystems in one test

When troubleshooting, keep a clean instance with one loader family, the matching Ukulib build, and the minimum dependent mod set. This makes loader errors obvious and reproducible.

Continue with the site guides

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