Ukulib can support the configuration layer used by compatible HUD and client utility mods. This guide focuses on settings screens, widgets, position controls, conflicts, and safe configuration resets rather than treating the library as the visible HUD itself.
Ukulib supports the configuration layer
Ukulib’s documented feature set includes configuration utilities and widgets for config screens. This can support HUD mods that need toggles, positions, text fields, or other controls. The exact options are defined by the dependent mod, so two Ukulib-based mods can still present very different menus.
Find the dependent mod’s settings
Look in the mod list, options screen, keybind list, or the mod’s documented entry point. Ukulib itself may not expose a standalone settings page containing every feature. The library supplies components, while the integrating mod decides where and how the screen appears.
Reset a broken HUD position safely
If a HUD element is off-screen, back up the profile and inspect the dependent mod’s config file rather than deleting the entire game directory. Close Minecraft before editing configuration. Reset only the relevant position values, then launch at the same window size and UI scale.
Avoid configuration conflicts
Two HUD mods can use the same screen region or keybind even when both dependencies are correct. Move elements one at a time, check UI scale, and disable overlapping modules temporarily. Dependency errors happen during loading; visual conflicts happen after the game launches, so they require different troubleshooting paths.
Preserve settings during updates
Copy the config folder before updating a library or feature mod. Major versions can rename options or remove deprecated settings. If the updated profile behaves incorrectly, test with a fresh config in a backup instance, then migrate only the settings that remain supported.