Description
QuestLines GUI
Build fully interactive in-game interfaces for your Hytale server — no Java, no rebuilds, no restarts.
QuestLines GUI transforms raw HyUIML layouts into dynamic, requirement-driven player interfaces. Design visually in the web editor or hand-author your layouts, drop them into your server, and open them from anywhere in QuestLines Core.
Overview
QuestLines GUI enables fully dynamic UI screens powered by QuestLines Core:
- Open GUIs from dialogues, commands, auto-triggers, or actions
- Build anything from shops and class selectors to admin panels and leaderboards
- Use the same requirements, actions, and variables as Core — no new system to learn
Every GUI is rendered per-player and per-open, ensuring accurate, real-time state with zero stale data.
Headline Features
- Visual Web Editor
Design interfaces using the hosted drag-and-drop editor — no local tools required - Raw HyUIML Support
Full control for advanced users who prefer hand-authored layouts - Requirement-Based Rendering
Show or remove elements dynamically based on:- Tags, quests, permissions, economy, levels, and all Core requirement types
- Unified Action System
Buttons and elements execute the same action strings used in dialogues:- Give items, run commands, modify tags, open other GUIs, and more
- Dynamic Text Variables
Supports all Core variables:{player},{tag:*},{track:*}, etc.- Resolved fresh on every open
- Per-Player Rendering
Requirements are re-evaluated every time the GUI opens — layouts are always accurate - Native Core Integration
Shares Core’s:- Requirement parser
- Action executor
- Variable system
Web Editor
The hosted editor is the primary workflow for most users:
- Visual layout with live preview
- Drag-and-drop UI construction
- Add and configure elements without touching files
- Bind actions and requirements directly in the editor
- Export ready-to-use
.gui.htmlfiles - Re-import existing GUIs for editing
In-game command:
Core Integration
QuestLines GUI registers a new action:
Use this anywhere in QuestLines Core:
- Dialogue responses
- AutoTriggers
- LoadActions
- Conditional flows
GUIs can open other GUIs, enabling full menu systems:
- Shops with categories
- Confirmation dialogs
- Nested admin tools
Example:
Requirements:
Actions:
If you can write a dialogue response, you can build a GUI.
Element Types
Button - Clickable action runner
Item Grid Slot - Item display with optional interaction
Checkbox - Toggle tied to a player tag
Panel - Container for grouped elements
Divider - Horizontal separator
Spacer - Layout spacing
- Every element supports requirements
- Failed requirements remove the element entirely (not hidden)
- Layout is always clean and player-specific
Button Behavior
Each button supports one of three execution modes:
- Close on Click
Execute actions and close the GUI - Refresh (Default)
Execute actions and reopen the GUI
Ideal for dynamic interfaces - Stay Open
Execute actions without re-rendering
Useful for cosmetic or one-off actions
Commands
/qlgui list - List loaded GUIs
/qlgui reload - Reload all GUI files
/qlgui editor - Get editor link
All commands require: questlines.admin
Dependencies
- Required: Hytale Server API, QuestLines Core
QuestLines GUI relies on Core for:
- Actions
- Requirements
- Variables
While it can technically load without Core, it is not functional in isolation.
Part of the QuestLines Suite
QuestLines GUI is part of a modular ecosystem:
- QuestLines Core — dialogue, quests, requirements, actions
- QuestLines GUI — custom UI system (this plugin)
- QuestLines Icons — NPC quest indicators
- QuestLines Dialog — in-game dialogue editor
Each plugin works standalone, but they are designed to integrate seamlessly.
Summary
- Build complex UI without code
- Fully dynamic, per-player rendering
- Native integration with QuestLines Core
- Visual editor + raw control
- No restarts required


