Difference between revisions of "TRE QSTFileType"

From SWGANH Wiki
Jump to: navigation, search
(task)
(Type=Nothing)
Line 43: Line 43:
 
  <task type="" id="" name="" taskOnFail="" >
 
  <task type="" id="" name="" taskOnFail="" >
 
Depending on the header, its content vary (more or less data fields, ...)
 
Depending on the header, its content vary (more or less data fields, ...)
===Type=Nothing===
+
===Type: Nothing===
 
====header====
 
====header====
 
*type=Nothing
 
*type=Nothing
Line 59: Line 59:
 
*target=
 
*target=
 
*parameter=
 
*parameter=
 +
 +
===Type: Go to Location===
 +
====header====
 +
*type=Go to Location
 +
*id=3
 +
*name=Go to Location
 +
*taskOnFail=false
 +
====content====
 +
*prerequisiteTasks=
 +
*exclusionTasks=
 +
*journalEntryTitle=some text
 +
*journalEntryDescription=
 +
*isVisible=true
 +
*showSystemMessages=0
 +
*allowRepeats=0
 +
*target=
 +
*parameter=
 +
*Planet=tatooine
 +
*LocationX(m)=220
 +
*LocationY(m)=190
 +
*LocationZ(m)=220
 +
*Radius(m)=10.0
  
 
==list==
 
==list==

Revision as of 07:15, 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

Each task packet starts with a header containing 4 fields:

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

Depending on the header, its content vary (more or less data fields, ...)

Type: Nothing

header

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

content

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

Type: Go to Location

header

  • type=Go to Location
  • id=3
  • name=Go to Location
  • taskOnFail=false

content

  • prerequisiteTasks=
  • exclusionTasks=
  • journalEntryTitle=some text
  • journalEntryDescription=
  • isVisible=true
  • showSystemMessages=0
  • allowRepeats=0
  • target=
  • parameter=
  • Planet=tatooine
  • LocationX(m)=220
  • LocationY(m)=190
  • LocationZ(m)=220
  • Radius(m)=10.0

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)