Skip to content

Quest Types

The Quest System supports five quest types, each with different progression mechanics, reset behavior and assignment rules.

TypeResetAssignmentTurn-inPool-based
DailyEvery day at configured timeRandom from daily poolQuestBookYes
WeeklyEvery week on configured dayRandom from weekly poolQuestBookYes
StoryNever (permanent)Auto-started or prerequisite-gatedQuest Book / NPCNo
SideNever (permanent)Available after prerequisites metQuest Book / NPCNo
HubNever (permanent)Player chooses from available sub-questsQuest BookNo

Daily quests are short, repeatable tasks assigned fresh each day. Players receive a set number of daily quests drawn randomly from the daily quest pool.

Key behavior:

  • Reset at the time configured in dailyResetTime (default: 04:00)
  • The number of quests assigned is controlled by dailyQuestCount (default: 3)
  • Quests are turned in in the Questbook — open it with /ksquest and press Claim reward
  • Support the tier system: each quest can have Common, Rare, Epic or Legendary variants with increasing difficulty and rewards
  • A finished daily counts as done until the next reset. When the same quest is drawn again later, it can be done again
  • Can be rerolled if the reroll system is enabled

Example daily quest definition:

{
"id": "daily_mine_stone",
"type": "daily",
"category": "gathering",
"difficulty": "easy",
"icon_item": "Tool_Pickaxe_Iron",
"name": {
"en": "Stone Breaker",
"de": "Steinbrecher"
},
"description": {
"en": "Daily blocks mined challenge.",
"de": "Taegliche blocks mined Herausforderung."
},
"objectives": [
{
"id": "obj_1",
"type": "blocks_mined",
"target": "Rock_Stone*",
"count": 50,
"description": {
"en": "Mine Rock Stone (0/50)",
"de": "Baue ab Rock Stone (0/50)"
}
}
],
"rewards": [
{ "type": "quest_tokens", "amount": 2 },
{ "type": "item", "item_id": "Ore_Iron", "amount": 5 }
],
"options": {
"repeatable": true,
"tier": "common",
"weight": 50,
"pool": "mining"
}
}

:::tip Tier Variants To create difficulty variants, define multiple quests with the same base concept but a different difficulty and objective counts. For example: daily_mine_stone (easy, 50 blocks), daily_mine_stone_rare (medium, 75 blocks), daily_mine_stone_epic (hard, 100 blocks). The difficulty decides the tier and its reward factor; how often each variant is drawn comes from its weight in the pool file. tier, weight and pool inside options (as in the shipped files) are not used for drawing or rewards. :::

Weekly quests are larger challenges that reset once per week. They typically have multiple objectives and offer better rewards than daily quests.

Key behavior:

  • Reset on the day configured in weeklyResetDay (default: MONDAY) at the dailyResetTime
  • The number assigned is controlled by weeklyQuestCount (default: 5)
  • Quests are turned in in the Questbook with Claim reward
  • Also support the tier system with weighted variants
  • Players have a full week to complete them

Example weekly quest definition:

{
"id": "weekly_master_miner",
"type": "weekly",
"category": "gathering",
"icon_item": "Tool_Pickaxe_Iron",
"name": {
"en": "Mine Master",
"de": "Bergbaumeister"
},
"description": {
"en": "Complete all objectives in this weekly challenge.",
"de": "Schliesse alle Ziele dieser woechentlichen Herausforderung ab."
},
"objectives": [
{
"id": "obj_1",
"type": "blocks_mined",
"target": "any",
"count": 300,
"description": { "en": "Mine (0/300)", "de": "Baue ab (0/300)" }
},
{
"id": "obj_2",
"type": "blocks_mined",
"target": "Ore_*",
"count": 30,
"description": { "en": "Mine Ore (0/30)", "de": "Baue ab Ore (0/30)" }
}
],
"rewards": [
{ "type": "quest_tokens", "amount": 8 },
{ "type": "lootbag", "lootbag_id": "ore_bundle_common" }
],
"options": {
"repeatable": true,
"tier": "common",
"weight": 50,
"pool": "mastery"
}
}

Story quests form the main narrative progression. They are permanent (never reset), follow a linear chain through prerequisites and guide players through the game world.

Key behavior:

  • Defined in story_quests.json (separate from other quest types)
  • The first story quest can auto-start for new players via "auto_start": true
  • Subsequent quests unlock through prerequisites (completing prior quests)
  • Objectives can be marked sequential (must be completed in order)
  • Support NPC interactions as objectives (talk to a specific NPC)
  • Organized into chapters for the quest book UI
  • Never expire or reset

Example story quest definition:

{
"id": "tutorial_first_steps",
"type": "story",
"category": "main",
"icon_item": "Tool_Hatchet_Crude",
"name": {
"en": "First Steps",
"de": "Erste Schritte"
},
"description": {
"en": "Craft your first crude tools from gathered materials.",
"de": "Crafte deine ersten Werkzeuge aus gesammelten Materialien."
},
"objectives": [
{
"id": "obj_1",
"type": "items_crafted",
"target": "Tool_Hatchet_Crude",
"count": 1,
"description": { "en": "Craft Tool Hatchet Crude (0/1)", "de": "Crafte Tool Hatchet Crude (0/1)" }
},
{
"id": "obj_2",
"type": "items_crafted",
"target": "Tool_Pickaxe_Crude",
"count": 1,
"description": { "en": "Craft Tool Pickaxe Crude (0/1)", "de": "Crafte Tool Pickaxe Crude (0/1)" }
}
],
"rewards": [
{ "type": "quest_tokens", "amount": 2 },
{ "type": "item", "item_id": "Wood_Sticks", "amount": 4 }
],
"prerequisites": {
"quests": ["tutorial_awakening"]
}
}

:::info Story Quest Options

  • "auto_start": true — Quest starts automatically when the player first joins
  • "sequential": true — Objectives must be completed in the order listed :::

Side quests are optional, permanent quests that provide additional content and rewards. They are typically tied to specific NPCs or regions and unlock after certain story milestones.

Key behavior:

  • Defined in quests.json alongside daily/weekly quests
  • Unlocked through prerequisites (usually a story quest)
  • Completed once per player, unless they are marked repeatable (see Quest Options)
  • Shown in the Side quests tab of the Questbook, together with every other quest that is not daily, weekly or story
  • Often involve NPC interactions (interact_npc objective type)
  • Can have multiple objective types mixed together (combat, gathering, crafting)

Example side quest definition:

{
"id": "side_riven_hunt",
"type": "side",
"category": "combat",
"icon_item": "Weapon_Sword_Iron",
"name": {
"en": "Big Game Hunt",
"de": "Grosswildjagd"
},
"description": {
"en": "Hunt goblins and Fen Stalkers for Riven.",
"de": "Jage Goblins und Fen Stalker fuer Riven."
},
"objectives": [
{ "id": "obj_1", "type": "kills", "target": "Goblin_*", "count": 10 },
{ "id": "obj_2", "type": "kills", "target": "Fen_Stalker", "count": 3 }
],
"rewards": [
{ "type": "quest_tokens", "amount": 10 },
{ "type": "lootbag", "lootbag_id": "hunter_reward" }
],
"prerequisites": {
"quests": ["story_trork_camp"]
}
}

Hub quests group multiple sub-quests together and track how many the player completes. They are used for “choose your own path” scenarios where players pick from a selection of available quests.

Key behavior:

  • The hub quest itself contains a complete_hub_quests objective that auto-increments when sub-quests complete
  • Players can choose which sub-quests to tackle from the available_quests list
  • Only required_to_progress sub-quests need to be completed (not all of them)
  • Displayed in the Side quests tab of the Questbook
  • Can have optional hubUI config for custom title, subtitle and layout

Example hub quest definition:

{
"id": "mining_hub",
"type": "hub",
"category": "gathering",
"icon_item": "Tool_Pickaxe_Iron",
"name": {
"en": "Mining Mastery",
"de": "Bergbau-Meisterschaft"
},
"description": {
"en": "Complete mining challenges to prove your skill.",
"de": "Schliesse Bergbau-Herausforderungen ab."
},
"objectives": [
{ "id": "complete", "type": "complete_hub_quests", "target": "mining_hub", "count": 3 }
],
"available_quests": ["mine_stone", "mine_ore", "mine_gems", "mine_crystal"],
"required_to_progress": 3,
"rewards": [
{ "type": "quest_tokens", "amount": 15 }
]
}
FieldRequiredDescription
available_questsYesArray of sub-quest IDs the player can choose from
required_to_progressNoHow many sub-quests must be completed (default: 1)
hubUINoOptional UI customization (see below)
"hubUI": {
"title": "Mining Challenges",
"subtitle": "Complete 3 of 4 challenges",
"layout": "grid"
}
FieldDefaultDescription
titleQuest nameCustom title for the hub selection UI
subtitle—Subtitle text
layout"grid"Layout mode: "grid" or "list"

All quest types use the same objective system. Here are the available objective types:

Objective TypeDescriptionExample Target
blocks_minedMine/break blocksRock_Stone*, Ore_*, any
blocks_choppedChop trees/woodWood_Oak*, any
blocks_dugDig dirt, sand, or gravelSand_*, Dirt_*, any
blocks_harvestedHarvest cropsPlant_Crop_Wheat*
blocks_placedPlace blocksBench_Campfire, Furniture_Crude_Torch
flowers_pickedPick flowersPlant_Flower_Common_Red, any
killsKill entities/mobsGoblin_*, Fen_Stalker, Scorpion
player_killsKill other playersplayer
damage_dealtDeal damage to entitiesScorpion, any
damage_takenReceive damageany
items_craftedCraft itemsTool_Pickaxe_Crude, Potion_*
items_collectedCollect/pick up itemsOre_*, @consumable
deliverHand items over to an NPCItem ID, plus deliverTo (NPC ID)
distance_traveledWalk/run distanceany
playtime_minutesPlay for a duration (minutes)any, total
interact_npcInteract with an NPCguide_finn, merchant_aldric
zone_discoveredDiscover/enter a zoneForgotten_Temple
command_executedExecute a server commandCommand name (no /)
level_reachedReach a player levelThe level, e.g. 10
waitWait a number of secondsnone (count = seconds)

items_consumed and complete_hub_quests are still read from files but are not counted by Quests 2.1. See Objectives.

:::tip Wildcard Targets Use * wildcards to match multiple items: Ore_* matches all ore types, Goblin_* matches all goblin variants. Use any to match everything. Use @consumable to match all food items. :::

Reward TypeFieldsDescription
quest_tokensamountAward quest tokens (internal currency)
itemitem_id, amountGive a specific item
lootbaglootbag_idGive a loot bag (random rewards)
currencycurrency, amountGrant a named currency (gold, silver)
rpg_xpamountGrant character XP
mmo_xpskill, amountGrant skill-specific XP
endless_xpamountGrant Endless leveling XP
leveling_xpamountGrant main leveling XP
titletitle_idUnlock a player title
achievementachievement_idUnlock an achievement
commandcommand, executorExecute a server command

Daily and weekly quests are assigned from pools defined in daily_pool.json and weekly_pool.json. Each pool entry has a quest ID and an optional weight:

{
"pool": [
{ "quest_id": "daily_mine_stone", "weight": 10 },
{ "quest_id": "daily_kill_mobs", "weight": 10 },
{ "quest_id": "daily_harvest", "weight": 8 }
]
}

Higher weight means the quest is more likely to be selected. Add your custom quests to the pool via the custom/ folder files.

These fields can be used on any quest type:

FieldTypeDefaultDescription
difficultystring—Difficulty level: "easy", "medium", "hard", "legendary"
sequentialboolfalseIf true, objectives must be completed in order
timeLimitint0Time limit in seconds (0 = no limit). Reserved for future use
setsFactstring—Fact key to set when the quest is completed
setsFactValuestring"true"Value to assign to the fact
triggerobject—Auto-start trigger (see Triggers)
nextQueststring—Quest ID to auto-offer after completion
optionsobject—Quest options (see below)
OptionDefaultDescription
auto_startfalseStarts on its own as soon as the prerequisites are met
auto_claimfalseCompletes and pays as soon as the last objective is done
sequentialfalseSame as the top-level sequential
hiddenfalseHidden in the Questbook while locked
trackabletrueCan be tracked on the HUD
rerollabletrueDaily/weekly can be rerolled
maxRerolls1Reroll limit for this quest
repeatablefalseA side or story quest can be done again after completion (dailies and weeklies always repeat with the pool)
repeat_cooldown_hours0For repeatable quests that are not daily or weekly: hours after the last completion before the quest can start again. 0 = right away, as before 2.1.0
"options": {
"repeatable": true,
"repeat_cooldown_hours": 24
}

The admin window sets these under Flow → Repeat. Its check warns when a repeatable quest has no cooldown.

The difficulty field controls the quest’s tier color and reward multiplier:

DifficultyColorMultiplierAliases
easyGray1.0xnormal, simple, basic
mediumBlue2.0xuncommon, moderate, challenging
hardPurple3.0xdifficult, very_hard, expert
legendaryGold5.0xextreme, mythic, artifact, ancient

Triggers automatically start quests when certain conditions are met. Add a trigger object to the quest definition:

{
"id": "tutorial_start",
"trigger": {
"type": "first_join",
"startsQuest": "tutorial_start"
}
}
Trigger TypeFieldsDescription
first_join—Player joins for the first time
zone_enterzoneIdPlayer enters a specific zone
npc_interactnpcIdPlayer interacts with a specific NPC
quest_completequestIdAnother quest is completed
dialog_completedialogIdA dialog is completed
dialog_choicedialogIdA dialog choice is selected

The types zone_exit, item_obtain, item_use and block_interact are still read from files, but nothing fires them in Quests 2.1. The admin window only offers the six types above.

Trigger fields:

FieldTypeDescription
typestringTrigger type (see above)
startsQueststringQuest ID to start (auto-filled with parent quest ID)
completesObjectivestringFormat: "quest_id:objective_id"
conditionstringFact condition that must be true
setsFactstringFact key to set when triggered
setsFactValueanyValue for the fact (default: true)

setsFact and completesObjective work since 2.1.0.