Comprehensive guidance for Hytale plugin UI modding using native .ui files, Common.ui styling, layout and markup rules, the Java UI API (CustomUIHud, MultipleHUD, CustomUIPage, InteractiveCustomUIPage), and Item HUD UI (attaching .ui overlays to items via item JSON HudUI field). Use when creating or updating custom HUDs/pages, writing .ui markup, binding UI events, attaching HUDs to items, or troubleshooting UI issues.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Comprehensive guidance for Hytale plugin UI modding using native .ui files, Common.ui styling, layout and markup rules, the Java UI API (CustomUIHud, MultipleHUD, CustomUIPage, InteractiveCustomUIPage), and Item HUD UI (attaching .ui overlays to items via item JSON HudUI field). Use when creating or updating custom HUDs/pages, writing .ui markup, binding UI events, attaching HUDs to items, or troubleshooting UI issues.
Hytale Native UI Modding Skill
Use this skill for Hytale's native .ui system and the server-side Java UI API.
Important: use native UI only. Do not use HyUI.
Quick start
Read the architecture overview first. See references/overview.md.
Put .ui files under src/main/resources/Common/UI/Custom/.
Import Common.ui when you want shared styles and components. See references/common-styling.md.
Build layout with Anchor, Padding, and LayoutMode. See references/layout.md.
Use markup patterns like named expressions, templates, and translations. See references/markup.md.
Bind UI events with UIEventBuilder and always sendUpdate after handling events. See references/java-api.md and references/events.md.
For assets, use @2x.png and set IncludesAssetPack in manifest. See references/assets-and-packaging.md.
To attach a HUD to an item (shown when held/active), use the item JSON HudUI field. See references/item-hud-ui.md.
For translation keys and localized runtime strings, check references/translations.md.
If something fails at runtime, check references/troubleshooting.md.
Reference library
references/INDEX.md
references/overview.md
references/common-styling.md
references/layout.md
references/markup.md
references/type-documentation.md
references/java-api.md
references/anchor-ui.md
references/events.md
references/assets-and-packaging.md
references/item-hud-ui.md
references/translations.md
references/examples.md
references/troubleshooting.md
Project conventions
.ui base path: Common/UI/Custom/. Relative paths inside .ui are resolved from the file location.
Use %translation.key in .ui and add the key to the language files under src/main/resources/Server/Languages.
Use MultipleHUD for multiple HUDs per player. Do not rely on a single CustomUIHud instance.
Item HUD UIs are asset-driven: declare them in item JSON via the HudUI array field. No server-side Java is needed to show/hide them — the client manages their lifecycle automatically when the item is active.
The official type documentation is a generated index. Use it when you need the exact property name, type, or enum values for an element.
Common.ui is the preferred source for cohesive styling. Import it and reference styles instead of duplicating them.
Added in server 2026.02.26-7681d338c: Item HUD UI support. Items can now declare .ui overlays in their JSON HudUI field that the client renders automatically when the item is held/active. See references/item-hud-ui.md.
TabNavigation UI element documentation has been updated with examples and known issues. See the official type docs for current TabNavigation behavior. Items can now declare .ui overlays in their JSON HudUI field that the client renders automatically when the item is held/active. See references/item-hud-ui.md.
