Traipse node referencing is unlike other distributions of OpenRPG.  The Game Tree mapping is a fluid map that changes with the location of your nodes.  This allows you to create a reference node that will stay with your character sheet, and if you change the location of your character sheet the reference will still work.

(Note: Renaming your node causes problems with the tree mapping until you restart the software. You can just move the node and the software will reset the Game Tree map)

Reference Types:
  There are three ways of references node data. A Root Reference, a Child Reference, and a Parent Reference.

Root Reference:
  A node reference that starts at the Game Tree. The location of the node must be exact or you will return an Invalid Reference!

A Root Reference uses this syntax:
!@Node::Child::Data@!

Child Reference:
  A node reference syntax that starts by looking at within the current container node. As long as the Child Reference is in the same container as the node, the container can change location and the reference will not be damaged. Child References work from within a PC Sheet node as well.

A Child Reference uses this syntax:
!!Node::Child::Data!!

Parent Reference:
  A node reference syntax that starts by looking at the tree map and the reference used, then makes an addendum to the node's map to create a reference.  The Parent Node is used when you want to reference the data in a node that is within a different child container of the same parent node.

A Parent Reference uses this syntax:
!#Node::Child::Data#!

Syntax for Special PC Sheet Nodes:
  The nodes for the specialized PC Sheets now have a new syntax.

Skills, Saves, and Abilities:
  Skills, Saves, and Abilities all have a similar referencing syntax.  You can return the base value of each by using the correct syntax.

Examples:
!@Jonethan::Skill::Jump@! (Returns Jump ranks)
!@Mikael::Strength@! (Returns Ability Score and Mod)
!@Draj::Will@! (Returns Will Save and Mod)

(Saves and Abilities have a short hand and a long hand. Abilities can use the three letter abbreviation, while saves short hand are Fort, Ref, and Will)

  You can append Check to check each of these against a 1d20 roll, or you can append Mod to discover the Modifier. The Mod can be useful in other nodes

Combat:
  You can now reference your attacks easily with the Game Tree.  Using the Attack syntax you can select modifier type, and a weapon to attack with.
Example: !@Kammen-Pai::Attack::M::Dagger@!

Modifier Type:
  There are two modifier types Melee (M) or Ranged (R) You will see I added can use the long word or the short hand.

Powers, Spells and Feats:
  Power, Spells and Feats are hard to sometimes hard to remember, and even harder to code.  The use of the Power, Spell or Feat syntax serves as an emote of what you are doing, as well as a reminder of what your Power, Spell, or Feat does.

Examples:
!@Kammen-Pai::Cast::Ray of Frost@!
!@Kammen-Pai::Feat::Ability Focus@!

Game Tree
- Tabber
-- Abilities (Grid)
-- Details (Form)
--- Name (Text)
--- Level (Text)
-- Weapons (Grid)
-- Attacks (List)
-- Special (Tabber)
--- Super Attacks (List)

!!Details::Name!! does an attack <b>Attack</b> [1d20 + !!Abilities::(1,3)!!] <b>Damage:</b> [1!!Weapons::(2,3)!!]

!#Details::Name#! does an attack <b>Attack</b> [1d20 + !#Abilities::(1,3)#!] <b>Damage:</b> [1!#Weapons::(2,3)#!]

Game Tree
- PCs
-- Another PC Tabber
--- Abilities (Grid)
--- Details (Form)
---- Name (Text)
---- Level (Text)
--- Weapons (Grid)
--- Attacks (List)
--- Special (Tabber)
---- Super Attacks (List)
-- Tabber
--- Abilities (Grid)
--- Details (Form)
---- Name (Text)
---- Level (Text)
--- Weapons (Grid)
--- Attacks (List)
--- Special (Tabber)
---- Super Attacks (List)
-- 3rd Tabber
--- Abilities (Grid)
--- Details (Form)
---- Name (Text)
---- Level (Text)
--- Weapons (Grid)
--- Attacks (List)
--- Special (Tabber)
---- Super Attacks (List)