Ukulib Armor HUD Mod Compatibility: What the Dependency Does

Ukulib does not create an armor HUD on its own. The official setup documentation cites armor-hud as a concrete project example that can depend on Ukulib for shared infrastructure.

Separate the HUD mod from the library

The HUD mod supplies the visible armor interface. Ukulib supplies reusable client-side components such as configuration and utility code that the dependent project can call into.

Why the dependency exists

Shared libraries let a family of mods reuse configuration patterns, widgets, and Minecraft helpers. That reduces duplicate implementation work and gives related projects a common dependency surface.

Match the armor HUD release first

Check which Ukulib version range the armor HUD build requires, then select the corresponding Minecraft and loader build. The dependent mod’s metadata should guide the dependency choice.

Fabric and NeoForge are separate in 2.x

For modern Ukulib 2.x, use the loader-specific build that matches the HUD mod and profile. Do not pair a Fabric dependent mod with the NeoForge library artifact or vice versa.

Legacy 1.21.x profiles need legacy Ukulib

If the HUD mod targets Minecraft 1.21.x, use the compatible 1.x Ukulib release for that exact game version rather than the newer 2.x line intended for Minecraft 26.x.

Troubleshoot from the dependency error

If the HUD mod fails to load, check the launcher log for missing or incompatible Ukulib requirements before changing HUD settings. A dependency failure happens before normal in-game configuration can help.

Continue with the site guides

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