Armor HUD searches often lead users to Ukulib because the visible HUD mod and its supporting library are installed together. This guide clarifies which file creates the overlay, which file supplies shared components, and how both versions must align.
The library and the HUD are separate mods
Ukulib is a shared dependency, while an armor HUD mod provides the visible equipment display. Installing only the library does not automatically create an armor overlay. Installing only the HUD may fail if that release declares Ukulib as required. Keep both roles clear when diagnosing a missing feature.
Why a HUD mod may use Ukulib
A client HUD often needs configuration controls, screen widgets, saved positions, and shared utility functions. A library can provide those building blocks so the HUD project focuses on its visible feature. This arrangement also lets multiple related mods use a consistent settings system.
Match both files to the same environment
The armor HUD file and Ukulib must target the same Minecraft version and compatible loader. A valid Ukulib release cannot make an outdated HUD mod compatible with a newer game version. Check the metadata for both files, remove duplicates, and avoid mixing Forge with NeoForge.
When the HUD does not appear
First confirm that the feature mod itself is enabled. Then open its keybinds or configuration screen, check whether the overlay is disabled, and verify that no other HUD mod places an element over it. If the game crashes before the menu, inspect the dependency error instead of changing display settings.
Updating a working HUD profile
Back up the instance before updates. Upgrade the game, loader, Ukulib, and HUD only when compatible releases exist for the same target. Test the profile without unrelated new mods, then reintroduce other changes gradually. This makes it easier to identify whether the library migration or the HUD update caused the problem.