|
34
|
1 <nodehandler class="tabber_handler" frame="636,449,290,93" icon="labtop" map="Traipse OpenRPG" module="containers" name="User Manual" version="1.0">
|
|
|
2 <nodehandler class="textctrl_handler" frame="400,400,0,48" icon="note" map="Traipse OpenRPG::User Manual" module="forms" name="Introduction" version="1.0">
|
|
|
3 <text hide_title="0" multiline="1" raw_mode="0" send_button="0">Welcome to Traipse OpenRPG.
|
|
28
|
4
|
|
|
5 This small user manual should help users learn about the details of OpenRPG that are often times obscure.
|
|
|
6
|
|
|
7 What is OpenRPG:
|
|
|
8 OpenRPG is a virtual game table software that allows users to connect via a network. The software includes a Map, Chat, and a Game Tree.
|
|
|
9
|
|
|
10 What is Traipse OpenRPG:
|
|
|
11 Traipse OpenRPG is a fork of the original software that is designed to be easy for users, extremely stable, and really powerful.
|
|
|
12
|
|
|
13 Traipse has features that set it apart from all other distributions of OpenRPG. The Traipse Suite includes a powerful Update Manager that makes it easy for new developers to create and share their own fork. The Suite also contains an in house Debug Console so users can see what errors, if any, occur.
|
|
|
14
|
|
|
15 The User Manual:
|
|
|
16 The user manual is divided into Chapters and Sections. Each Chapter will go over the various features of OpenRPG and attempt to explain them in an easy to understand format.
|
|
|
17
|
|
|
18 Adding to the Manual:
|
|
|
19 Do you see something that could be explained eaiser? Report the problem as a bug and it will be added to the manual.</text>
|
|
34
|
20 </nodehandler>
|
|
|
21 <nodehandler class="tabber_handler" icon="player" map="Traipse OpenRPG::User Manual" module="containers" name="Chat" version="1.0">
|
|
|
22 <nodehandler class="textctrl_handler" frame="400,400,0,47" icon="note" map="Traipse OpenRPG::User Manual::Chat" module="forms" name="Using Chat" version="1.0">
|
|
|
23 <text hide_title="0" multiline="1" raw_mode="0" send_button="0">The Chat window is a basic HTML Parser. It understands all basic HTML tags including table, td, tr, span, font, to name a few.
|
|
28
|
24
|
|
|
25 The chat includes a set of commands. You can learn about the commands by entering /help
|
|
|
26
|
|
|
27 The chat also has Settings in the Chat menu that allow you see a Chat Time Index, Images, or strip the HTML and see raw text.</text>
|
|
34
|
28 </nodehandler>
|
|
|
29 </nodehandler>
|
|
|
30 <nodehandler class="tabber_handler" icon="ccmap" map="Traipse OpenRPG::User Manual" module="containers" name="Map" version="1.0">
|
|
|
31 <nodehandler class="textctrl_handler" frame="400,400,310,82" icon="note" map="Traipse OpenRPG::User Manual::Map" module="forms" name="Using The Map" version="1.0">
|
|
|
32 <text hide_title="0" multiline="1" raw_mode="0" send_button="0">The Tabs:
|
|
28
|
33 The Map is divided into 7 tabs. They are Background, Grid, Miniatures, Whiteboard, Fog, and General. There are 6 layers to the map, one tab for each layer except General.
|
|
|
34
|
|
|
35 When you select one of the tabs you may access that map layer and it's settings. You may only select tabs based on your role.
|
|
|
36
|
|
|
37 Lurker or in the Lobby:
|
|
|
38 You cannot access any map tab or changes it's settings.
|
|
|
39
|
|
|
40 Player:
|
|
|
41 You have access to the Miniatures tab and the Whiteboard tab.
|
|
|
42
|
|
|
43 GM:
|
|
|
44 You have access to all of the tabs.
|
|
|
45
|
|
|
46 The Layers:
|
|
|
47 A small description of each of the layers.
|
|
|
48
|
|
|
49 Background:
|
|
|
50 You can set an image as the background, an image as a tile, or you can set a color.
|
|
|
51
|
|
|
52 Grid:
|
|
|
53 You can change the grid size, lines, turn off the grid snap, and change the grid shape.
|
|
|
54
|
|
|
55 Miniatures:
|
|
|
56 You can add new or remove miniatures and change mini properties and labels.
|
|
|
57
|
|
|
58 Whiteboard:
|
|
|
59 With the whiteboard you can draw lines or add text to the map.
|
|
|
60
|
|
|
61 Fog:
|
|
|
62 The fog layer hides the entire map from the prying eyes of players.
|
|
|
63 </text>
|
|
34
|
64 </nodehandler>
|
|
|
65 </nodehandler>
|
|
|
66 <nodehandler class="tabber_handler" frame="537,400,235,93" icon="gear" map="Traipse OpenRPG::User Manual" module="containers" name="Game Tree" version="1.0">
|
|
|
67 <nodehandler class="tabber_handler" frame="400,400,472,75" icon="tabber" map="Traipse OpenRPG::User Manual::Game Tree" module="containers" name="Namespace 2.0" version="1.0"><nodehandler class="textctrl_handler" frame="400,400,393,95" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Namespace 2.0" module="forms" name="Introduction" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">Namespace 2.0
|
|
|
68
|
|
|
69 Internal Namespace: !=NodeName=! or !=GridName::Row,Colum=!
|
|
|
70 External Namespace: !&Container::NodeName&! or !&Container::GridName::Row,Colum&!
|
|
|
71
|
|
|
72 Namespace 2.0 now has two different ways of finding nodes in your gametree: Internal and
|
|
|
73 External. The new version will find nodes differently based on which method you use. With External you start looking from the gametree but can define a "container" to be more specific. With Internal you start looking from the "node" the reference is in and look through the tree backwards. You can now reference cells within a grid using either.
|
|
|
74
|
|
|
75 *An explanation of terms*
|
|
|
76 Gametree: The list of objects on the left-hand side of the window that holds all your nodes.
|
|
|
77 Node: Refers to any object in the gametree.
|
|
|
78 Container: Refers only to those nodes that are capable of storing other nodes (Splitter,
|
|
|
79 Tabbers, Folder, Forms, etc.). Used here, it usually refers to the largest container, i.e. the
|
|
|
80 one that shows up in the gametree when fully collapsed. A Container can contain other
|
|
|
81 containers.
|
|
|
82 </text></nodehandler><nodehandler class="textctrl_handler" frame="400,400,393,95" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Namespace 2.0" module="forms" name="Internal" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">Internal Namespace: !=NodeName=!
|
|
|
83 -Used from within a node to call another node in the same container, such as a list node
|
|
|
84 calling a text node or grid. *Note* Will not work if multiple nodes within the same container
|
|
|
85 have the same name. Multiple nodes within the entirety of the gametree can have the same names
|
|
|
86 though as long as they are in different containers.
|
|
|
87 -Uses the !=NodeName=! syntax for normal nodes.
|
|
|
88 -Uses !=GridName::Row,Colum=! to reference cells within a grid
|
|
|
89
|
|
|
90 Examples:
|
|
|
91 !=Strength=!
|
|
|
92 (Will find the node named “Strength” in the same container and insert it in place of
|
|
|
93 !=Strength=!)
|
|
|
94
|
|
|
95 !=Ability Scores::3,5=!
|
|
|
96 (Will find cell in Row number 3 and Colum number 5 and insert the information contained there
|
|
|
97 in place of !=Ability Scores::3,5=! )</text></nodehandler><nodehandler class="textctrl_handler" frame="400,400,393,95" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Namespace 2.0" module="forms" name="External" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">External Namespace: !&Container::NodeName&!
|
|
|
98 -Can only be used from chat (currently) to call a node from anywhere in the gametree. You must
|
|
|
99 specify the container the node is in. You only have to specify the ‘largest’ container
|
|
|
100 (typically the one that shows in the gametree when fully collapsed). It doesn’t matter how
|
|
|
101 many smaller containers within the same container it’s in, you need only reference the
|
|
|
102 largest. *Note* Will not work if multiple nodes within the same container have the same name.
|
|
|
103 Multiple nodes within the entirety of the gametree can have the same names though as long as
|
|
|
104 they are in different containers.
|
|
|
105 -Uses the !&Container::NodeName&! syntax for normal nodes.
|
|
|
106 -Uses !&Container::NodeName::Row,Colum&! to reference cells within a grid.
|
|
|
107
|
|
|
108 Examples:
|
|
|
109 !&3.5 Character Sheet::Strength&!
|
|
|
110 (Will find the node named “Strength” within the larger container “3.5 Character Sheet” and
|
|
|
111 insert it in place of !&3.5 Character Sheet::Strength&!)
|
|
|
112
|
|
|
113 !&3.5 Character Sheet::Ability Scores::3,5&!
|
|
|
114 (Will find the cell in Row 3, Colum 5 in within the larger container “3.5 Character Sheet” and
|
|
|
115 insert its contents in place of !&3.5 Character Sheet::Ability Scores::3,5&!)</text></nodehandler><nodehandler class="textctrl_handler" frame="400,400,393,95" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Namespace 2.0" module="forms" name="Other Notes" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">Other Notes:
|
|
|
116 If you have similar nodes (i.e. have a lot of the same node names in them) located within the
|
|
|
117 same Larger container, Internal Namespace will still work as normal. With External Namespace,
|
|
|
118 you will have to specify which of the smaller containers you wish to call from.
|
|
|
119
|
|
|
120 For example, if you have a folder container that has two nodes in it, Internal will still work
|
|
|
121 fine from within either. However, if you are trying to use External, it you will have to
|
|
|
122 specify which of smaller containers you want like so:
|
|
|
123 !&LargerContainer::SmallerContainer::NodeName&!
|
|
|
124
|
|
|
125 I.E.:
|
|
|
126 The Largest container is called “Character Sheets.” It contains three other, Smaller
|
|
|
127 containers called “Luke,” “Leia,” and “Vader.” If you want to call the “Strength” node located
|
|
|
128 in “Leia” you will have to specify it like so: !&Character Sheets::Leia::Strength&!. </text></nodehandler><nodehandler class="textctrl_handler" frame="400,400,392,87" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Namespace 2.0" module="forms" name="Author Notes" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="1">The Namespace 2.0 is so far my greatest gift to OpenRPG. Namespace 2.0 surpasses the other Namespaces styles because it has a lightning bolt effect.
|
|
|
129
|
|
|
130 In 1.7.1 you could use a reference such as !@Name@! to get the name of the Behir (Example Node). The biggest problem with the Namespace was it would only look at the top most node.
|
|
|
131
|
|
|
132 Traipse changes how Namespace works by allowing users to be more specific without needing to be too specific. Namespace 2.0 works in a similar fashion, by finding the top most node with a similar name and attempting to use it. Yet, if you want to be more specific you can add node names to the reference and Namespace will find them in order.
|
|
|
133
|
|
|
134 I hope you enjoy the new Namespace very much. I tried to capture an OpenRPG users idea of how Namespace 'should' work and this time I think I set a new bar. I even created a plugin so Traipse users can use the Standard namespace references!
|
|
|
135
|
|
|
136 Below are some examples uses of the new Namespace. To try them out, create a 4e PC Sheet node and press the Send button.
|
|
|
137
|
|
|
138 <b>1:</b> !&4e PC Sheet::Slot 1&!
|
|
|
139 <b>2:</b> !&4e PC Sheet::Belt::Slot 1&!
|
|
|
140 <b>3:</b> !&4e PC Sheet::Inventory&!
|
|
|
141 <b>4:</b> !&4e PC Sheet::Inventory::Slot 1&!
|
|
|
142
|
|
|
143 Did you see what happened with the last two? Thankfully there is more than one way to get a node!
|
|
|
144
|
|
|
145 (Create a 4e PC Sheet node from the Templates and press Send ---v to try it)
|
|
|
146 </text></nodehandler></nodehandler><nodehandler class="textctrl_handler" frame="400,400,595,57" icon="note" map="Traipse OpenRPG::User Manual::Game Tree" module="forms" name="Grids" version="1.0">
|
|
|
147 <text hide_title="0" multiline="1" raw_mode="0" send_button="1">Grids can now be called from by adding a Row, Column to the end of the grid reference.
|
|
|
148
|
|
|
149 Example: !&Abilities::2,2&!</text>
|
|
|
150 </nodehandler><nodehandler class="tabber_handler" frame="527,400,259,85" icon="tabber" map="Traipse OpenRPG::User Manual::Game Tree" module="containers" name="Ornery (past)" version="1.0"><nodehandler class="tabber_handler" frame="410,490,334,45" icon="tabber" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)" module="containers" name="Reference Examples" version="1.0">
|
|
|
151 <nodehandler class="textctrl_handler" frame="400,400,484,144" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="forms" name="Quick Help" version="1.0">
|
|
|
152 <text hide_title="0" multiline="1" raw_mode="1" send_button="0">Quick Help:
|
|
|
153
|
|
|
154 Designer Note:
|
|
|
155 ===
|
|
|
156 For the life span of Ornery Orc the new Child, Parent, Root reference will exist, but in Pious the reference system will not transfer. This is because of the way the new Namespace works. Namespace will become the exclusive referencing system
|
|
|
157 ===
|
|
28
|
158
|
|
|
159 The referencing system is an update to the Core of how the Game Tree works. In it's current state I understand the syntax is difficult to pick up. Here are some tips to help you grasp the syntax further
|
|
|
160
|
|
|
161 A.
|
|
|
162 Think of the Game Tree has a folder on your hard drive. Each :: inside the reference syntax works just like a system separator (/ or \)
|
|
|
163
|
|
|
164 B.
|
|
|
165 Root References start at the tree itself. If the node being referenced changes location the reference will be invalid.
|
|
|
166
|
|
|
167 C.
|
|
|
168 Child References work at the location of the node containing the reference.
|
|
|
169
|
|
|
170 Example:
|
|
|
171 Game Tree
|
|
|
172 - Group
|
|
|
173 -- Text Node
|
|
|
174 --- Group_2
|
|
|
175 ---- Text Node_2
|
|
|
176 --- Group_3
|
|
|
177 ---- Text Node_3
|
|
|
178
|
|
|
179 In the above Tree example you can reference Text Node_2 with a root reference
|
|
|
180
|
|
|
181 !@Group::Group_2::Text Node_2@!
|
|
|
182
|
|
|
183 or you can use a Child Reference from within Text Node
|
|
|
184
|
|
|
185 !!Group_2::Text Node_2!!
|
|
|
186
|
|
|
187 D.
|
|
|
188 Parent References work with the Tree Map. Unlike Child references that look only at the current nodes location, Parent References are allowed to travel backwards in the gametree.
|
|
|
189
|
|
|
190 Using the above example, you could reference Text Node from Text Node_2 with the syntax: !#Group::Text Node#!
|
|
|
191
|
|
|
192 Parent References have a special power in that they need only a certain amount of data for the software to understand them. In the above example you could reference Text Node_3 from Text Node_2 with only this syntax !#Group_3::Text Node_3#!
|
|
|
193
|
|
|
194 The reference system is still a bit primitive in it's implementation. As I was saying it is an advancement to the Core technology of Traipse OpenRPG.
|
|
|
195
|
|
|
196 While it is confusing at first, the model is far superior to other tree referencing systems. Pre 1.8.0, no node could reference a Grid. The referencing system required the reference to be exact and started at the root. Also, the new model is designed to enable freedom of creation and greater control over the Game Tree.
|
|
|
197
|
|
|
198 With the Traipse Game Tree GMs are enabled to reference any data from the Game Tree, no matter where it stands. Players can create fewer nodes and use more of the data with fewer nodes.
|
|
|
199
|
|
|
200 EZ_Tree (One Touch Reference):
|
|
|
201 (ALPHA!)
|
|
|
202 The new EZ_Tree System will help benefit users who do not understand the syntax, nor care to learn.
|
|
|
203
|
|
|
204 The EZ_Tree System works from within Lists, Texts, and Grids. In the Design Panel you can push the Reference button and navigate the small gametree that pops up to the node you want. Double click that node and the software will create the most efficient node reference for you.
|
|
|
205
|
|
|
206 (ALPHA!) In it's Alpha state, Grids will not work completely. You can reference a grid, but you must add teh cell reference. That is not a design flaw, but a restriction of time constraints.
|
|
|
207
|
|
|
208 Developer Note:
|
|
|
209 The syntax is the hardest part to understand and I expect to change that in the future. The Core of a more expansive Game Tree model is designed. In Traipse you do not need to give access permissions to a node in order to reference it's entirety, which is what I see with Index and Namespace from OpenRPG Core.
|
|
|
210
|
|
|
211 In the OpenRPG Core model your Game Tree has a lot more freedom, but only if you grant it, which I always felt was a design flaw. Comparably, with Traipse you can access any data on the Game Tree, no matter where the location.
|
|
|
212
|
|
|
213 This freedom will help with future design and I feel it also frees up the hands of the GM who does not need to Index, un-Index, Namespace, un-Namspace the various creatures he or she may have in a Game Tree.</text>
|
|
34
|
214 </nodehandler>
|
|
|
215 <nodehandler class="textctrl_handler" frame="400,400,540,67" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="forms" name="Root Reference" version="1.0">
|
|
|
216 <text hide_title="0" multiline="1" raw_mode="1" send_button="1"><b>Root Reference</b>
|
|
28
|
217 Works at the tree level. Must be exact.
|
|
|
218
|
|
|
219 <b>Root Reference 1:</b> !@Reference Examples::Group::Child@!
|
|
34
|
220 <b>Root Reference 2:</b> !@Reference Examples::Grid::2,1@!</text>
|
|
|
221 </nodehandler>
|
|
|
222 <nodehandler class="textctrl_handler" frame="441,400,514,48" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="forms" name="Grid Reference" version="1.0">
|
|
|
223 <text hide_title="0" multiline="1" raw_mode="1" send_button="1"><b>Grid Reference</b>
|
|
28
|
224 Works by looking at the (Row, Column) of a Grid.
|
|
|
225
|
|
34
|
226 <b>Grid Reference 1:</b> !@Reference Examples::Grid::1,1@!
|
|
|
227 <b>Grid Reference 2:</b> !!Grid::1,1!!</text>
|
|
|
228 </nodehandler>
|
|
|
229 <nodehandler class="textctrl_handler" frame="400,400,517,63" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="forms" name="Child Reference" version="1.0">
|
|
|
230 <text hide_title="1" multiline="1" raw_mode="1" send_button="1"><b>Child Reference</b>
|
|
28
|
231 Works at the current tree location.
|
|
|
232
|
|
|
233 <b>Child Reference 1:</b> !!Group::Child!!
|
|
|
234 <b>Child Reference 2:</b> !!Group::Group_2::Child_2!!
|
|
|
235 </text>
|
|
34
|
236 </nodehandler>
|
|
|
237 <nodehandler class="textctrl_handler" frame="400,400,484,144" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="forms" name="Parent Reference" version="1.0">
|
|
|
238 <text hide_title="0" multiline="1" raw_mode="1" send_button="1"><b>Parent Reference</b>
|
|
28
|
239 Works by indexing the tree map of the node with the Reference. Allows you to start from a 'Parent'.
|
|
|
240
|
|
|
241 <b>Parent Reference 1:</b> !!Group::Group_2::Child_2!!
|
|
|
242 <b>Parent Reference 2:</b> !#Bonus Nodes::Deck::Draw#!</text>
|
|
34
|
243 </nodehandler>
|
|
|
244 <nodehandler border="1" class="group_handler" cols="1" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="containers" name="Group" version="1.0">
|
|
|
245 <nodehandler border="1" class="group_handler" cols="1" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples::Group" module="containers" name="Group_2" version="1.0">
|
|
|
246 <nodehandler class="textctrl_handler" frame="400,400,571,67" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples::Group::Group_2" module="forms" name="Child_2" version="1.0">
|
|
|
247 <text hide_title="0" multiline="1" raw_mode="1" send_button="0">!#Group::Child#!</text>
|
|
|
248 </nodehandler>
|
|
|
249 <nodehandler border="1" class="group_handler" cols="1" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples::Group::Group_2" module="containers" name="Group_3" version="1.0">
|
|
|
250 <nodehandler class="textctrl_handler" frame="400,400,571,67" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples::Group::Group_2::Group_3" module="forms" name="Child_3" version="1.0">
|
|
|
251 <text hide_title="0" multiline="1" raw_mode="1" send_button="0">!#Group::Child#!</text>
|
|
|
252 </nodehandler>
|
|
|
253 </nodehandler>
|
|
|
254 </nodehandler>
|
|
|
255 <nodehandler class="textctrl_handler" frame="400,134,382,175" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples::Group" module="forms" name="Child" version="1.0">
|
|
|
256 <text hide_title="0" multiline="0" raw_mode="1" send_button="0">Child Node Data</text>
|
|
|
257 </nodehandler>
|
|
|
258 </nodehandler>
|
|
|
259 <nodehandler class="rpg_grid_handler" frame="400,400,547,51" icon="grid" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)::Reference Examples" module="rpg_grid" name="Grid" version="1.0">
|
|
|
260 <grid autosize="1" border="1">
|
|
|
261 <row version="1.0">
|
|
|
262 <cell size="147">0</cell>
|
|
|
263 <cell>0</cell>
|
|
|
264 </row>
|
|
|
265 <row version="1.0">
|
|
|
266 <cell>!!Group::Child!!</cell>
|
|
|
267 <cell>0</cell>
|
|
|
268 </row>
|
|
|
269 </grid>
|
|
|
270 <macros>
|
|
|
271 <macro name="" />
|
|
|
272 </macros>
|
|
|
273 </nodehandler>
|
|
|
274 </nodehandler>
|
|
|
275 <nodehandler class="textctrl_handler" frame="400,400,393,95" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)" module="forms" name="Node Referencing" version="1.0">
|
|
|
276 <text hide_title="0" multiline="1" raw_mode="0" send_button="0"> 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.
|
|
28
|
277
|
|
|
278 (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)
|
|
|
279
|
|
|
280 Reference Types:
|
|
|
281 There are three ways of references node data. A Root Reference, a Child Reference, and a Parent Reference.
|
|
|
282
|
|
|
283 Root Reference:
|
|
|
284 A node reference that starts at the Game Tree. The location of the node must be exact or you will return an Invalid Reference!
|
|
|
285
|
|
|
286 A Root Reference uses this syntax:
|
|
|
287 !@Node::Child::Data@!
|
|
|
288
|
|
|
289 Child Reference:
|
|
|
290 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.
|
|
|
291
|
|
|
292 A Child Reference uses this syntax:
|
|
|
293 !!Node::Child::Data!!
|
|
|
294
|
|
|
295 Parent Reference:
|
|
|
296 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.
|
|
|
297
|
|
|
298 A Parent Reference uses this syntax:
|
|
|
299 !#Node::Child::Data#!
|
|
|
300
|
|
|
301 Syntax for Special PC Sheet Nodes:
|
|
|
302 The nodes for the specialized PC Sheets now have a new syntax.
|
|
|
303
|
|
|
304 Skills, Saves, and Abilities:
|
|
|
305 Skills, Saves, and Abilities all have a similar referencing syntax. You can return the base value of each by using the correct syntax.
|
|
|
306
|
|
|
307 Examples:
|
|
|
308 !@Jonethan::Skill::Jump@! (Returns Jump ranks)
|
|
|
309 !@Mikael::Strength@! (Returns Ability Score and Mod)
|
|
|
310 !@Draj::Will@! (Returns Will Save and Mod)
|
|
|
311
|
|
|
312 (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)
|
|
|
313
|
|
|
314 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
|
|
|
315
|
|
|
316 Combat:
|
|
|
317 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.
|
|
|
318 Example: !@Kammen-Pai::Attack::M::Dagger@!
|
|
|
319
|
|
|
320 Modifier Type:
|
|
|
321 There are two modifier types Melee (M) or Ranged (R) You will see I added can use the long word or the short hand.
|
|
|
322
|
|
|
323 Powers, Spells and Feats:
|
|
|
324 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.
|
|
|
325
|
|
|
326 Examples:
|
|
|
327 !@Kammen-Pai::Cast::Ray of Frost@!
|
|
34
|
328 !@Kammen-Pai::Feat::Ability Focus@!</text>
|
|
|
329 </nodehandler>
|
|
|
330 <nodehandler class="textctrl_handler" frame="400,400,452,36" icon="note" map="Traipse OpenRPG::User Manual::Game Tree::Ornery (past)" module="forms" name="Additions & Tips" version="1.0">
|
|
|
331 <text hide_title="0" multiline="1" raw_mode="0" send_button="0"> With the new additions to the Game Tree using nodes has never been easier nor has it ever been more fluid. Included here is a list of the additions to the Game Tree referencing model as well as some tips on how to make the Game Tree work the way it was intended.
|
|
|
332
|
|
|
333 Grid Nodes:
|
|
|
334 Grid nodes are now reference-able with the coordinates of the grid. Example: !@Grid::(1,1)@!
|
|
|
335 The example will return the top left most cell data. The grid understands coordinates like this (Row, Column)
|
|
|
336
|
|
|
337 Grid nodes can reference node data just like any other node can. With a new added feature grids are even more useful. By using a new die rolling syntax you can draw just the number of the modified roll. While this will not pass during game play, you can use it with the grid node to create a random chart. The new die roll syntax is [#XdY]. # works just like q, yet it returns only the modified die result.
|
|
|
338
|
|
|
339 Here is an example with a 3 x 3 Grid
|
|
|
340 Example: !@Grid::([#1d3], [#1d3])@!
|
|
|
341
|
|
|
342 The result will be a random event from the grid.
|
|
|
343
|
|
|
344 Bonus Node Included: A 52 Card Deck with 4 columns and 13 rows. (4 * 13 = 52)
|
|
|
345
|
|
|
346 List Nodes:
|
|
|
347 List nodes now have a check box that allows users to send the content as a macro. List nodes are a prime reference holder because users can place a lot of references into one small node.
|
|
|
348
|
|
|
349 For the best results from a list node my tip to users would be to create a list node and place it next to the character sheet they are using, inside a the PC Sheet. The list will then use the Child Referencing syntax, but the PC Sheet can go anywhere in the tree and the player will have easy access to all the references.
|
|
|
350
|
|
|
351 (List Nodes inside a Tool created PC sheet vanish when moved, or I would recommend the list be placed inside these sheets also.)
|
|
|
352
|
|
|
353 Here is an example of a Fortitude save inside the recommended list node: !!Fort::Check!!
|
|
|
354
|
|
|
355 Text Nodes:
|
|
|
356 Text nodes remain little changed. I agree with all the 1.7.1 users who tell me, if it's not broke don't fix it. With that in mind I have some good tips for text nodes.
|
|
|
357
|
|
|
358 Text nodes can be used in conjunction with the new grid features to create random encounters. A GM could place a list of text nodes into a folder and the grid could reference the nodes.
|
|
|
359
|
|
|
360 Text nodes also work great when you need to have story text at hand that you don't want to type out during play. Create chapters with folder nodes and add the adventure text to different nodes. You can then use a List Node or a Grid Node to reference the different chapters.
|
|
|
361
|
|
|
362 Bonus Node Included: A small book node with 1 Chapter and 3 Parts.</text>
|
|
|
363 </nodehandler>
|
|
|
364 </nodehandler></nodehandler>
|
|
|
365 <nodehandler class="tabber_handler" icon="labtop" map="Traipse OpenRPG::User Manual" module="containers" name="The Server" version="1.0">
|
|
|
366 <nodehandler class="textctrl_handler" frame="400,400,310,82" icon="note" map="Traipse OpenRPG::User Manual::The Server" module="forms" name="Setting up a Server" version="1.0">
|
|
|
367 <text hide_title="0" multiline="1" raw_mode="0" send_button="0">In Traipse starting a server has never been easier. The setup is as easy as 1., 2., 3
|
|
28
|
368
|
|
|
369 1. You will need to first start the Server GUI or the basic text based Server at least once so your software creates the server_ini.xml files in your myfiles directory. You can start it once and quit.
|
|
|
370
|
|
|
371 2. Edit the server_ini.xml file. Here you can set the server's name, the boot password, and even set the servers port.
|
|
|
372
|
|
|
373 Traipse allows you to specify a server port instead of the software demanding port 6774.
|
|
|
374
|
|
|
375 3. This is the hardest step. You need to make sure your selected port is forwarded by your router and open to your firewall.
|
|
|
376
|
|
|
377 That's it! You can now start the server and register it to the meta for all users to enjoy!</text>
|
|
34
|
378 </nodehandler>
|
|
|
379 </nodehandler>
|
|
|
380 <nodehandler class="tabber_handler" frame="400,400,0,48" icon="browser" map="Traipse OpenRPG::User Manual" module="containers" name="Links" version="1.0">
|
|
|
381 <nodehandler class="link_handler" icon="html" map="Traipse OpenRPG::User Manual::Links" module="forms" name="Release Notes" version="1.0">
|
|
|
382 <link href="http://www.assembla.com/wiki/show/traipse" />
|
|
|
383 </nodehandler>
|
|
|
384 <nodehandler class="link_handler" icon="html" map="Traipse OpenRPG::User Manual::Links" module="forms" name="Traipse User Guide" version="1.0">
|
|
|
385 <link href="http://www.assembla.com/wiki/show/traipse/User_Manual" />
|
|
|
386 </nodehandler>
|
|
|
387 </nodehandler>
|
|
|
388 </nodehandler>
|
|
|
389 |
