QuestData

Version Support

Version	Status
v92	Full
v90	-
v86	-

QuestData files (.quest extension) define quest entries: metadata, requirements, triggers, and task chains that form the quest progression.

Each quest is stored in its own file using the naming convention {questId:D6}.quest (e.g., 048721.quest).

DSL Support

Entity: quests Operations: create, update, delete Inline blocks:

strings: — creates/updates StrSheet_Quest entries

Quick Recipes

Create

spec:
  version: "1.0"
  schema: v92

quests:
  create:
    - id: 99000001
      header:
        questNumber: 990001
        questTitle: "Sample Quest"
        questType: General
        repeatType: OneTime
        cancellable: Allowed
        startTaskId: 1
      requirements:
        minLevel: 20
        maxLevel: 65
      tasks:
        - taskId: 1
          type: HuntTask
          body:
            targetCount: 10
            templateId: 12345
        - taskId: 2
          type: VisitTask
          nextTaskId: 0
          body:
            npcId: 63001

Update

spec:
  version: "1.0"
  schema: v92

quests:
  update:
    - id: 99000001
      changes:
        header:
          questType: Daily
        requirements:
          minLevel: 25

Delete

spec:
  version: "1.0"
  schema: v92

quests:
  delete:
    - 99000001

Properties Reference

Quest Root

Property	Type	Since	Required	Description
`id`	`int`	v92	Yes	Unique quest identifier (used for file name)
`header`	`object`	v92	No	Quest header configuration
`requirements`	`object`	v92	No	Level and prerequisite requirements
`tasks`	`list`	v92	No	List of task definitions
`strings`	`object`	v92	No	Inline quest string definitions

Header Properties

Property	Type	Since	Required	Description
`questNumber`	`int`	v92	No	Internal quest number
`questTitle`	`string`	v92	No	Quest title (localization key or inline string)
`storyGroupId`	`int`	v92	No	Story group for quest chain organization
`designersNote`	`string`	v92	No	Internal documentation note
`questType`	`string`	v92	No	Quest category. See QuestType.
`repeatType`	`string`	v92	No	Repeatability setting. See RepeatType.
`repeatCount`	`int`	v92	No	Number of times quest can be repeated
`cancellable`	`string`	v92	No	Whether quest can be abandoned. See Cancellable.
`startTaskId`	`int`	v92	No	First task ID in the chain
`linkedQuest`	`int`	v92	No	Follow-up quest ID
`recommendedPartySize`	`int`	v92	No	Suggested party size
`recommendedLevel`	`int`	v92	No	Suggested character level
`summaryInfo`	`int`	v92	No	Quest log summary reference
`questDialogue`	`string`	v92	No	Dialogue reference
`shareable`	`string`	v92	No	Can be shared with party (`true`/`false`)
`autoShare`	`string`	v92	No	Auto-share with party (`true`/`false`)

Requirements Properties

Property	Type	Since	Required	Description
`minLevel`	`int`	v92	No	Minimum character level
`maxLevel`	`int`	v92	No	Maximum character level
`excessLevel`	`int`	v92	No	Over-level threshold
`minItemLevel`	`int`	v92	No	Minimum equipment item level
`prerequisites`	`list[int]`	v92	No	Required completed quest IDs

Task Properties (Common)

Property	Type	Since	Required	Description
`taskId`	`int`	v92	Yes	Unique task identifier within the quest
`type`	`string`	v92	Yes	Task type. See Quest Tasks reference.
`nextTaskId`	`int`	v92	No	Next task in chain (0 = quest complete)
`failureReturnTaskId`	`int`	v92	No	Task to return to on failure
`continentId`	`int`	v92	No	Continent ID for task location
`worldPosition`	`string`	v92	No	World coordinates
`journalText`	`string`	v92	No	Quest journal entry text
`journalText2`	`string`	v92	No	Secondary journal entry
`hasReward`	`boolean`	v92	No	Whether task grants rewards
`cinematicId`	`int`	v92	No	Cinematic sequence ID
`dungeonId`	`int`	v92	No	Associated dungeon ID
`body`	`object`	v92	No	Task-type-specific properties

XML Structure

The XML schema follows a multi-level nesting structure:

QuestData/{questId:D6}.quest
└── Quest (id)
    ├── Header
    │   ├── Quest metadata (questNumber, questTitle, questType, ...)
    │   ├── Requirements (minLevel, maxLevel, prerequisites, ...)
    │   └── Triggers (npcDialogue, itemUse, ...)
    └── Task (id) [multiple]
        ├── Task header (nextTask, journalScript, ...)
        └── Task body (type-specific properties)

Enum Reference

QuestType

Value	Description
`General`	Standard one-time quest
`Daily`	Daily repeatable quest
`Mission`	Story mission quest
`ImportantMission`	Critical story quest
`Guild`	Guild-specific quest
`Alliance`	Alliance faction quest
`RecommendedNormal`	Recommended general quest
`DarkRift`	Dark Rift event quest
`GeneralPurpose`	Multi-purpose quest
`Repeatable`	Infinitely repeatable quest

RepeatType

Value	Description
`OneTime`	Can only be completed once
`Repeatable`	Can be repeated
`Daily`	Resets daily
`Infinite`	No completion limit

Cancellable

Value	Description
`Allowed`	Quest can be abandoned
`Forbidden`	Quest cannot be abandoned

Common Pitfalls

File naming: Quest files use the format {id:D6}.quest (6-digit zero-padded, e.g., 099000.quest). The system generates this automatically.
Task chain termination: Set nextTaskId: 0 on the final task to mark quest completion. Omitting this creates an incomplete chain.
Task IDs are local: Task IDs are unique within a quest, not globally. Two quests can both have a task with taskId: 1.
Type-specific body properties: Each task type uses different body properties. Using wrong properties for a task type will be ignored. See Quest Tasks reference for per-type properties.
Enum casing: Enum values are case-insensitive (General, general, GENERAL all work).
Inline strings: Use the strings: block to create quest display text. String IDs are auto-calculated based on quest ID.