Traipse "OpenRPG"

Just

The gametree serves a dual purpose; it acts as a placeholder.storage Ifor willthe adduser documentationdata, here.typically in the form of character sheets but also various other things, and it also acts as a definition of two distinct user interfaces to that data. The main user interface it supports is the "Use" dialog. This brings up a dialog which contains a node and all of its children in a way that enables ease of reading the data and sending things such as die rolls to chat. The other user interface is the tree's display within the window. This is the "raw" user interface where each node is directly accessed but it is required for the initial creation of the character sheets and so on and has all the character sheet authoring functionality.

The tree is used three times,

1. To develop (or import) the character sheet, or create the node(s) -- often the DM does this or gets someone else to for the whole group
2. To edit the nodes to have the specific PC's data, including updating it -- performed by the player
3. Using the character sheet during live play -- performed by the player

Node Types

Text node -- and macro node

• List node
• Grid node
• Resource node
• Container nodes -- four types
• Miniature node
• Minilib node -- a library (list) of minis (minatures).
• File node
• Image node
• Link node
• Loader node
• Custom nodes -- specifically the d20-based custom character sheets