Ukulib Mod Features: Configuration, Widgets & Utilities

Ukulib is infrastructure for other client mods. Its value comes from shared configuration code, reusable interface widgets, Minecraft-facing utilities, and a cleaner multi-loader architecture in the 2.x line.

The feature set is library-first, not gameplay-first

The official project describes Ukulib as a Minecraft library used across the developer’s mods. That distinction matters: installing the library alone is not intended to create a large new gameplay system. Most visible behavior comes from the mod that depends on Ukulib.

Configuration is a core part of the library

Current documentation highlights a simple but comprehensive configuration system. For dependent mods, that means settings structures and presentation logic can live in a shared layer rather than being reimplemented in every project.

Reusable widgets support configuration screens

Ukulib includes utilities and widgets for config screens. The 2.2.0 release also reworked TextInputWidget internals and deprecated getText/setText in favor of getValue/setValue, showing that the UI layer is an actively maintained part of the API.

Minecraft utilities reduce repeated client code

The library also groups Minecraft-related helper code. The exact utility a player benefits from depends on the dependent mod, but the architectural goal is consistent: move repeated client-side plumbing into one maintained dependency.

Ukulib 2.x is designed for Fabric and NeoForge

Starting with 2.0.0 for Minecraft 26.1, the project supports both Fabric and NeoForge and publishes common, Fabric, and NeoForge artifacts for development. That makes loader boundaries explicit and helps multi-loader mods keep shared logic separate from platform code.

What this means for players

Treat Ukulib as a version-sensitive dependency. Match the Minecraft target, loader, and version range requested by the mod that requires it. The newest library release is not automatically correct for an older profile.

Continue with the site guides

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