Hosav's Custom UI Mod - 2.4.3
How to host Hosav's Custom UI Mod - 2.4.3 on game-serverhosting
- Downloads
- 409,010
- Categories
- Interface, Legacy
Hosav's Custom UI Mod 2.4.3 for the interface
This mod ranks among the most extensive UI overhauls available for Conan Exiles: more than 50 options let you reposition, toggle, and recolor practically every HUD element via a color wheel. On top of that you get a customizable minimap, damage indicators with distinct icons per damage type (melee, ranged, concussive, stamina, and armor-piercing), and a menu screen showing server name, region, and local time. It's explicitly built to work alongside IQoL, with individual hooks you can disable to avoid conflicts. With over 408,000 subscribers, it's become a go-to choice for servers wanting either a cleaner or a heavily customized interface. For load order, place it after other UI mods in modlist.txt to minimize conflicts, and make sure every player has subscribed to the same version via Steam Workshop.
Plan the rollout and operation
Hosav's Custom UI is useful when players need dense HUD information or a cleaner role-play layout. Do not force one arrangement on everyone; publish a recommended starting configuration instead. Check the minimap, damage indicators, and menus at several resolutions and alongside your other UI mods. If elements overlap, adjust hook or display options before rearranging the entire server mod list.
For a safe rollout, back up the world and server configuration, record the current modlist.txt including order, and start a copy on the exact same game version. Review the boot log for missing packages, then join with a client using the same Workshop list. A useful smoke test covers joining, spawning, one core mod feature, saving, restarting, and joining again. After major game updates, delay the live update until the mod and its dependencies are explicitly compatible. Change only one part of the list per test run; otherwise a crash cannot be traced to a specific entry. Before removal, use a world copy to check for stored items, buildings, thralls, or configuration owned by the mod. Remove its Workshop entry from production only after the save loads cleanly without those assets. This keeps rollback and diagnosis manageable.