Quest Smart Object Template Documentation

From Nexus Mods Wiki
Revision as of 14:32, 25 September 2019 by WarhorseStudios (talk | contribs) (Created page with " Quest Smart Object template This article aims to explain the structure and inner workings of the default quest template. Every new quest tree (created in Swift) looks like t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Quest Smart Object template

This article aims to explain the structure and inner workings of the default quest template. Every new quest tree (created in Swift) looks like this.

Read MBT, Quest System, Smart objects, XGEN NPC Editor, and Flow Graph documentations first.

Sections

Quest Smart Object Template Image1.png

Logic flow

Quest Smart Object Template Image2.png

  1. Right after the game starts, the whole tree is stuck at nodes “2” and “4”, and waits for quest activation.
  2. When the quest is activated this tree receives the message, processes it, and runs the node “1”
  3. This in turn unlocks the node “2”
  4. What follows is an init sequence which should load up all needed assets and set initial states. The end of the init sequence is node “3”.
  5. This in turn signals that all assets are loaded and unlocks node 4
  6. Sections marked “5” usually contain over 95% of the quest’s MBT logic.
  7. Nodeset “6” serves for unlocking the tree (specifically node “2”) after loading. All trees are restarted after loading and this logic simply reconstructs the function of node “1”, which cannot be executed more than once.