TOOL: Quests Debbuger

The Quests Debugger is a useful tool to test your newly created quests.

This tool first and foremost present the the treeview of questlines related to the save that was last loaded in the Editor.

Open the Quests Debuggers

To open the Quests Debugger go to Tools > Debuggers > Quests Debugger.

The tool will open as the Quest Editor but with additional options for debug.

Open

Node Graphs

Double clicking a tree item will show its node graph in the node editor. Currently active signals are highlighted. You can navigate to the child sub-trees by clicking on the node’s title.

Open

You can also select a node and continue from that node by right clicking on one of the node’s attachment pins and using this context menu option:

Saving changes

If you want the edited values to be immediately reflected on the game, use File > Save from the toolbar’s context menu: 

Facts DataBase

This is not a tool, but a system that many quests and other systems depend on. Facts DataBase is a base of variables with number values assigned to them. They can be added or modified, either by scripts or via quests (quest block FactsDB Change). Later on, these facts can be checked in quest, scene or script conditions.

When you open the Quest Debugger, one of the tabs can show the actual state of the Facts DataBase, where the fact variables can be monitored.

Each variable’s value can be seen at the right pane of the panel next to the Val: label. Also if you need to evaluate a specific fact but only for a time period, you can make them expired as well. The label called Exp. no here says that this variable cannot be expired.

The list of variables can be filtered and searched at the bottom pane of the panel.

Table of contents: