Revision as of 06:04, 12 June 2007

QueST files are the new version of quests that appear with publish 10 when SOE introduced the journal in the game.

Basic Structure

<?xml version="1.0"?>
  <quest version="1.0" >
    <tasks availableId="" >
      <task type="" id="" name="" taskOnFail="" >
        <data value="" name="" />
        <data value="" name="" />
        <data value="" name="" />
        ...
        <task type="" id="" name="" taskOnFail="" >
          <data value="" name="" />
          <data value="" name="" />
          <data value="" name="" />
          ...
        </task>
      </task>
    </tasks>
    <list>
      <data value="" name="" />
      <data value="" name="" />
      <data value="" name="" />
      ...
    </list>
  </quest>

We have:

• a XML header
• a quest packet (1 per file)
  • a tasks packet containing 2 things:
    • a task packet (the main one of the quest) containing some informations:
      • name=value
      • ...
      • and 0 or more other task packets which can each contain 0 or more other task packet and so on...
    • a list packet containing some informations:
      • name=value
      • ...

In Depth Structure

task

header

Each task packet starts with a header containing 4 fields:

<task type="" id="" name="" taskOnFail="" >

• type=Nothing
• id=0
• name=Nothing
• taskOnFail=false

content

• prerequisiteTasks=
• exclusionTasks=
• journalEntryTitle=
• journalEntryDescription=
• isVisible=true
• showSystemMessages=0
• allowRepeats=0
• target=
• parameter=

list

Each variable of the list packet is stored this way:

<data value="" name="" />

Let's view what they are and their values:

• journalEntryTitle=some text
• journalEntryDescription=some text
• prerequisiteQuests=
• exclusionQuests=
• allowRepeats=true (or false)
• target=
• parameter=
• category=Test (or any other category)
• completeWhenTasksComplete=true (or false)