Back to mods
QuestLines GUI project artwork

CurseForge · Hytale mod

QuestLines GUI

Build custom in-game interfaces for your Hytale server — no Java, no rebuilds, no restarts

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which QuestLines GUI release should I use?

Updated yesterday
Latest stable file questlines-gui-1.2.2.jar
Game version 0.6
Mod system Built-in Hytale mod system

QuestLines GUI questlines-gui-1.2.2.jar targets 0.6. Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer. No required dependencies listed for this file.

Where it goes

Where should QuestLines GUI be installed in Hytale?

Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer.

Separate client mod Not supported
World host / dedicated server Required
Mod system for this release Built-in Hytale mod system
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

Put Hytale mods on the world host or dedicated server. Singleplayer runs a local server too; Hytale does not use separate client mods.

What else does QuestLines GUI questlines-gui-1.2.2.jar need?

questlines-gui-1.2.2.jar. Change the file and its required mods may change too.

No required dependencies listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional project dependencies. Check the creator notes before changing an existing world.

Before you install it

Add QuestLines GUI without breaking your instance.

Built for QuestLines GUI questlines-gui-1.2.2.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use questlines-gui-1.2.2.jar. It targets 0.6; another release may target a different game build or dependency set.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Enable it on the world host

    Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside questlines-gui-1.2.2.jar. It opens that exact file at the source.

About this project

What does QuestLines GUI add?

🔵 Discord ☕ Ko-fi ⭐ Patreon 📖 Wiki

Officially partnered with Bearded.Host Need a server? Get **25% off** at our partner Bearded.Host with code **Redstoner**.

QuestLines GUI

Build fully interactive in-game interfaces for your Hytale server — no Java, no rebuilds, no restarts.

QuestLines GUI turns 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

  • 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, so state is always accurate and never stale.

Headline Features

  • Visual Web Editor — design interfaces in a 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 based on tags, quests, permissions, economy, levels and every other Core requirement type
  • Unified Action System — buttons run the same action strings used in dialogues: give items, run commands, modify tags, open other GUIs
  • Dynamic Text Variables — all Core variables ({player}, {tag:*}, {track:*}), resolved fresh on every open
  • Per-Player Rendering — requirements re-evaluate every time the GUI opens
  • Native Core Integration — shares Core's requirement parser, action executor and variable system
  • In-game documentation — GUI registers its help pages with the in-game wiki alongside the rest of the suite

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.html files
  • Re-import existing GUIs for editing

In-game: /qlgui editor

Core Integration

QuestLines GUI registers a new action:

opengui:<guiId>

Use it 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:

economy:canafford:10, not:hastag:has_sword

and actions:

economy:take:10, item:iron_sword:1, addtag:has_sword

If you can write a dialogue response, you can build a GUI.

Element Types

Label          - Styled text with full variable support
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, rather than hiding it
  • Layout stays clean and player-specific

Button Behavior

  • Close on Click — execute actions and close the GUI
  • Refresh (default) — execute actions and reopen; ideal for dynamic interfaces
  • Stay Open — execute actions without re-rendering; useful for cosmetic or one-off actions

Commands

/qlgui open <id> [player]  - Open a GUI
/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 and QuestLines Core. GUI relies on Core for actions, requirements and variables — while it can technically load without Core, it is not functional in isolation.

Summary

  • Build complex UI without code
  • Fully dynamic, per-player rendering
  • Native integration with QuestLines Core
  • Visual editor plus raw control
  • No restarts required

QuestLines GUI live server and player stats

The QuestLines Suite

Every plugin works standalone; together they share one ecosystem.

  • QuestLines Core — dialogue, quests, requirements, actions
  • Icons — floating quest-state icons above NPCs
  • Dialog — in-game linear dialogue builder
  • Titles — player title and rank rewards
  • GUI — custom in-game interfaces, no code required (this plugin)
  • Claims — land protection, regions, rent and buy plots
  • Denizens — native NPC manager
  • Arcade — arcade, board and puzzle games
  • Hooks — early plugin unlocking extra quest tracking
  • MMO — parties, guilds, dungeons, duels and item sets
  • Mimics — chests that stand up and fight
  • Nations — cities and nations built on Claims (via Discord)

Project description from CurseForge.

Pick your setup

QuestLines GUI releases for each Hytale build.

Choose the version and loader you play, then open the matching release.

2 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

QuestLines GUI releases and Hytale builds

7 of 7 releases match

Looking for an older file? The official CurseForge project page is in Resources.