Mercurial > traipse_dev

comparison orpg/templates/feature.xml @ 143:dc74dca250d1 alpha

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Traipse Alpha 'OpenRPG' {091123-02} Traipse is a distribution of OpenRPG that is designed to be easy to setup and go. Traipse also makes it easy for developers to work on code without fear of sacrifice. 'Ornery-Orc' continues the trend of 'Grumpy' and adds fixes to the code. 'Ornery-Orc's main goal is to offer more advanced features and enhance the productivity of the user. Update Summary (Cleaning up for Beta) Added Bookmarks Fix to Remote Admin Commands Minor fix to text based Server Fix to Pretty Print, from Core Fix to Splitter Nodes not being created Fix to massive amounts of images loading, from Core Added 'boot' command to remote admin Added confirmation window for sent nodes Minor changes to allow for portability to an OpenSUSE linux OS Miniatures Layer pop up box allows users to turn off Mini labels, from FlexiRPG Zoom Mouse plugin added Images added to Plugin UI Switching to Element Tree Map efficiency, from FlexiRPG Added Status Bar to Update Manager default_manifest.xml renamed to default_upmana.xml Cleaner clode for saved repositories New TrueDebug Class in orpg_log (See documentation for usage) Mercurial's hgweb folder is ported to upmana Pretty important update that can help remove thousands of dead children from your gametree. Children, <forms />, <group_atts />, <horizontal />, <cols />, <rows />, <height />, etc... are all tags now. Check your gametree and look for dead children!! New Gametree Recursion method, mapping, and context sensitivity. !Infinite Loops return error instead of freezing the software! New Syntax added for custom PC sheets Tip of the Day added, from Core and community Fixed Whiteboard ID to prevent random line or text deleting. Modified ID's to prevent non updated clients from ruining the fix.
author sirebral
date Mon, 23 Nov 2009 19:52:56 -0600
parents b4e02e8cd314
children c2caca988a11
comparison
equal deleted inserted replaced
141:2ffc5de126c8 143:dc74dca250d1
1 <nodehandler class="tabber_handler" icon="help" module="containers" name="Traipse OpenRPG" version="1.0"> 1 <nodehandler class="tabber_handler" icon="help" module="containers" name="Traipse OpenRPG" version="1.0">
2 <nodehandler class="textctrl_handler" frame="400,400,139,110" icon="note" map="Traipse OpenRPG" module="forms" name="Node Referencing" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">Traipse node referencing is unlike other distributions of OpenRPG. The gametree 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. 2 <nodehandler border="1" class="group_handler" cols="1" icon="labtop" map="Traipse OpenRPG" module="containers" name="User Manual" version="1.0">
3 <nodehandler class="link_handler" icon="html" map="Traipse OpenRPG::User Manual" module="forms" name="Traipse User Guide" version="1.0">
4 <link href="http://www.assembla.com/wiki/show/traipse/User_Manual" />
5 </nodehandler>
6 <nodehandler class="link_handler" icon="html" map="Traipse OpenRPG::User Manual" module="forms" name="Release Notes" version="1.0">
7 <link href="http://www.assembla.com/wiki/show/traipse" />
8 </nodehandler>
9 <nodehandler class="textctrl_handler" frame="400,400,139,110" icon="note" map="Traipse OpenRPG::User Manual" module="forms" name="Node Referencing" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">Traipse node referencing is unlike other distributions of OpenRPG. The gametree 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.
3 10
4 There are two ways of references node data. A Root Reference and a Child Reference. 11 (Note: Renaming your node causes problems with the mapping until you restart the software. You can just move the node and the software will reset the map)
12
13 Reference Types:
14 There are two ways of references node data. A Root Reference and a Child Reference.
15
16 Root Reference: A node reference that starts at the gametree. The location of the node must be exact or you will return an Invalid Reference!
5 17
6 A Root Reference uses this syntax: 18 A Root Reference uses this syntax:
7 !@Node::Child::Data@! 19 !@Node::Child::Data@!
8 20
9 Root References find the data within the node first by looking at the nodes in the tree. The location of the node must be exact or you will return an Invalid Reference! 21 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.
10 22
11 A Child Reference uses this syntax: 23 A Child Reference uses this syntax:
12 !!Node::Child::Data!! 24 !!Node::Child::Data!!
13 25
14 Child References work from within a container. Child References obtain the map from a child node and then look for the node data using an appended Root Reference. As long as the Child Reference node remains in in the same location relative to the reference, you can move the nodes around and never need to change your references again. 26 Syntax for Special PC Sheet Nodes:
27 The nodes for the specialized PC Sheets now have a new syntax.
15 28
16 Child Referencing works from within a PC Sheet node as well. 29 Skills, Saves, and Abilities:
30 Skills, Saves, and Abilities all have a similar referencing syntax. You can return the base value of each by using the correct syntax.
31 Examples:
32 !@Jonethan::Skill::Jump@! (Returns Jump ranks)
33 !@Mikael::Strength@! (Returns Ability Score and Mod)
34 !@Draj::Will@! (Returns Will Save and Mod)
17 35
18 Syntax for Special PC Sheet Nodes: 36 (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)
19 The nodes for the specialized PC Sheets now have a new syntax.
20 37
21 Abilities: 38 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
22 To reference an Ability, use the name or abbreviation of the Ability.
23 Example: !@Mikael::Strength@!
24
25 This will return the Ability, the Ability Score, and it's Modifier.
26
27 Mod Referencing:
28 If you want to find the Ability Modifier only, use Ability::Mod
29 Example: !@Mikael::Strength::Mod@!
30
31 Ability Checks:
32 Ability Checks are simplified as well. Simply add Check to the reference.
33 Example: !@Mikael::Strength::Check@!
34
35 The new referencing features are useful if you want to refence the ability modifier in other nodes.
36
37 Skills:
38 Skills work the similar to Abilities. To refence a skill's ranks use the Skill syntax
39 Example: !@Jonethan::Skill::Jump@!
40
41 This will return the ranks you have in Jump. Skill Checks are made by appending Check to the statement.
42 Example: !@Jonethan::Skill::Jump::Check@!
43
44 If you want to reference the skills modifier, use the Mod syntax
45 Example: !@Jonethan::Skill::Jump::Mod@!
46 39
47 Combat: 40 Combat:
48 You can now reference your attacks easily with the gametree. Using the Attack syntax you can select modifier type, and a weapon to attack with. 41 You can now reference your attacks easily with the gametree. Using the Attack syntax you can select modifier type, and a weapon to attack with.
49 Example: !@Kammen-Pai::Attack::M::Dagger@! 42 Example: !@Kammen-Pai::Attack::M::Dagger@!
50 43
51 Modifier Type: 44 Modifier Type:
52 There are two modifier types Melee (M) or Ranged(R) You will see I added can use the long word or the short hand. 45 There are two modifier types Melee (M) or Ranged (R) You will see I added can use the long word or the short hand.
53 46
54 Spells: 47 Powers, Spells and Feats:
55 If the PC Sheet you are using has Spells and Powers, you can use the Cast syntax to cast a spell or use a power. 48 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.
56 Example: !@Kammen-Pai::Cast::Ray of Frost@!
57 49
58 The data returned is the description of the spells actions. Spell actions are difficult to remember, and even harder to code, so this will at least work as an emoteable reference and a reminder of how the spell works. 50 Examples:
51 !@Kammen-Pai::Cast::Ray of Frost@!
52 !@Kammen-Pai::Feat::Ability Focus@!
59 53
60 Feats: 54 </text></nodehandler><nodehandler class="textctrl_handler" frame="400,400,350,33" icon="note" map="Traipse OpenRPG::User Manual" module="forms" name="Gametree Additions &amp; Tips" version="1.0"><text hide_title="0" multiline="1" raw_mode="0" send_button="0">With the new additions to the gametree using nodes has never been easier nor has it ever been more fluid. Included here is a list of the additions to the gametree referencing model as well as some tips on how to make the gametree work the way it was intended.
61 Feats will work the same way as spells. Because Feats and Spells have rulings that require such finesse it is not very easy to code them. However you will receive an easy to use reference point for what your Feat does.
62 Using the Feat syntax you can the description of the Feat.
63 Example: !@Kammen-Pai::Feat::Ability Focus@!
64 55
65 </text></nodehandler><nodehandler class="link_handler" icon="html" map="Traipse OpenRPG" module="forms" name="Release Notes" version="1.0"> 56 Grid Nodes:
66 <link href="http://www.assembla.com/wiki/show/traipse" /> 57 Grid nodes are now referenceable with the coordinates of the grid. Example: !@Grid::(0,0)@!
67 </nodehandler> 58 The example will return the top left most cell data. The grid understands coordinates like this (Row, Column)
68 <nodehandler class="link_handler" icon="html" map="Traipse OpenRPG" module="forms" name="Traipse User Guide" version="1.0"> 59
69 <link href="http://www.assembla.com/wiki/show/traipse/User_Manual" /> 60 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].
70 </nodehandler> 61
71 <nodehandler class="file_loader" icon="help" map="Traipse OpenRPG" module="core" name="Load Die Roller Notes" version="1.0"> 62 # works just like q, yet it returns only the modified die result. Here is an example with a 3 x 3 Grid
63 Example: !@Grid::([#1d3-1], [#1d3-1])@!
64
65 The result will be a random event from the grid.
66
67 Bonus: Make a 52 Card deck with 4 columns and 13 rows. (4 * 13 = 52)
68
69 List Nodes:
70 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.
71
72 For the best results from a list node my tip to users would be to create a list node and place it inside the character sheet they are using. Then all references will use the Child Referencing syntax, but the character sheet can go anywhere in the tree and the player will have easy access to all the references.
73
74 Here is an example of a Fortitude save inside the recommended list node: !!Fort::Check!!
75
76 Text Nodes:
77 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.
78
79 Text nodes can be used in conjuction 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 them.
80
81 Text nodes also work great when you need to have story text at hand that you don't want to type out during play.</text></nodehandler><group_atts border="1" cols="1" />
82 </nodehandler><nodehandler class="file_loader" icon="help" map="Traipse OpenRPG" module="core" name="Load Die Roller Notes" version="1.0">
72 <file name="die_roller_notes.xml" /> 83 <file name="die_roller_notes.xml" />
73 </nodehandler> 84 </nodehandler>
74 <nodehandler border="1" class="group_handler" cols="1" icon="gear" map="Traipse OpenRPG" module="containers" name="Templates" status="useful" version="1.0"> 85 <nodehandler border="1" class="group_handler" cols="1" icon="gear" map="Traipse OpenRPG" module="containers" name="Templates" status="useful" version="1.0">
75 <group_atts border="1" cols="1" /> 86 <group_atts border="1" cols="1" />
76 <nodehandler border="1" class="group_handler" cols="1" icon="flask" map="Traipse OpenRPG::Templates" module="containers" name="Nodes" status="useful" version="1.0"> 87 <nodehandler border="1" class="group_handler" cols="1" icon="flask" map="Traipse OpenRPG::Templates" module="containers" name="Nodes" status="useful" version="1.0">