QuestStrings

Version Support

Version	Status
v92	Full
v90	-
v86	-

StrSheet_Quest.xml contains quest string entries: localized text for quest titles, dialogue, journal entries, and UI elements.

Quest strings can be created inline with quest operations or managed separately.

---

DSL Support

Entity: questStrings Operations: create, update, delete Inline block: strings: on quest operations

---

Quick Recipes

Create (Standalone)

spec:
  version: "1.0"
  schema: v92

questStrings:
  create:
    - id: 99000001
      string: "The Missing Merchant"

Create (Inline with Quest)

spec:
  version: "1.0"
  schema: v92

quests:
  create:
    - id: 99000001
      header:
        questTitle: "@quest:99000001001"
      strings:
        name: "The Missing Merchant"

Update

spec:
  version: "1.0"
  schema: v92

questStrings:
  update:
    - id: 99000001
      changes:
        string: "The Lost Merchant"

Delete

spec:
  version: "1.0"
  schema: v92

questStrings:
  delete:
    - 99000001

---

Properties Reference

QuestString Entry

Property	Type	Since	Required	Description
id	int	v92	Yes	String entry ID
string	string	v92	Yes	Localized text content

Inline Strings Block

Property	Type	Since	Required	Description
name	string	v92	Yes	Quest title/name text

---

String ID Convention

Quest strings follow a predictable ID pattern:

String ID = (Quest ID * 1000) + Offset

Offset	Purpose
001	Quest title
002-009	Quest summary/description
010-099	Task dialogue
100+	Additional text

Example: Quest 99000001 would have:

• Title: @quest:99000001001
• First dialogue: @quest:99000001010

---

Common Pitfalls

• ID collision: When creating strings manually, ensure IDs don’t conflict with auto-generated inline strings.

• Reference format: Quest strings are referenced using @quest:{stringId} format in quest properties.

• Inline vs standalone: Inline strings are convenient for quest titles. Use standalone operations for complex dialogue trees or when updating strings independently.