Reply to thread

Message

<blockquote data-quote="reanjr" data-source="post: 2147880" data-attributes="member: 20740">As to the second point what you do is define functions inside different root elements.&nbsp; For example, stonecunning (the dwarf ability) is defined like so:[CODE]&lt;monsters&gt;&nbsp; &nbsp; &lt;function name=&quot;stonecunning&quot;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;text-representation&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;&quot;Stonecunning: automatically search secret doors...blah blah&quot;&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;/text-representation&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;add-conditional-skill-mod skill=&quot;search&quot; mod=&quot;2&quot; type=&quot;racial&quot; reason=&quot;stonecunning&quot; /&gt;&nbsp; &nbsp; &lt;/function&gt;&lt;/monsters&gt;[/CODE]Now in the dwarf data, we write[CODE]&lt;monsters&gt;&nbsp; &nbsp; &lt;monster name=&quot;dwarf&quot;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;stonecunning /&gt;&nbsp; &nbsp; &lt;/monster&gt;&lt;/monsters&gt;[/CODE]When you apply a race to a character (in this case dwarf), all of the stuff in the dwarf element is basically merged into the character element and executed.&nbsp; So you create a character, add dwarf stuff, which triggers stonecunning to execute, which in turn adds a conditional skill modifier to search checks.So, basically, because the stonecunning function is found inside &lt;monsters&gt;, that is its scope.&nbsp; But once monster data is merged with character data, it allows the character context to use the function.So, nope.&nbsp; No additional tags needed.I haven't seen a need for a new tag outside the data tags (create-context, add-data, add-property, delete-data, delete-property, and import-data) in several days, so it seems like a decent set of functions.&nbsp; I will probably have to think of string functionality of some kind, but I might just treat that like an array of chars.&nbsp; &quot;level&quot;::count would be 5 for instance and &quot;level&quot;::3 would be &quot;v&quot;.I think that actually pretty much covers it except for events, which I'll explain here just so that I have talked about it.&nbsp; I'll use the dwarven ability to move at full speed while encumbered as an example, because it's pretty straight forward.An event is declared in a similar fashion to a function, but it never takes arguments (I don't think, don't hold me to that).&nbsp; It generally handles a simple operation that could easily be done without a function.[CODE]&lt;event name=&quot;speed-change&quot; amount=&quot;0&quot; reason=&quot;&quot;&gt;&nbsp; &nbsp; &lt;set name=&quot;.speed&quot;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;add&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;.speed&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;amount&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;/add&gt;&nbsp; &nbsp; &lt;/set&gt;&lt;/event&gt;[/CODE]Basically, you can declare a function as normal but set two reserved properties on it: attach and when.attach indicates an event to attach the function to.&nbsp; when indicates when to run the function in relation to the event: &quot;before&quot; or &quot;after&quot;.So, in the monsters stuff you have[CODE]&lt;monsters&gt;&nbsp; &nbsp; &lt;function name=&quot;encumbered-movement&quot; attach=&quot;speed-change&quot; when=&quot;before&quot;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;assert&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;e&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;reason&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;&quot;encumbrance&quot;&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/e&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;set name=&quot;amount&quot;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;a&gt;0&lt;/a&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/set&gt;&nbsp; &nbsp; &nbsp; &nbsp; &lt;/assert&gt;&nbsp; &nbsp; &lt;/function&gt;&lt;/monsters&gt;[/CODE]When a character becomes encumbered, you call&lt;speed-change amount=&quot;-10&quot; reason=&quot;encumbrance&quot; /&gt;This triggers the encumbered-movement function because it was told to attach to the speed-change event.&nbsp; It was also told to run before the event itself.&nbsp; It checks the reason, which is &quot;encumbrance&quot;, and so sets the amount to 0.&nbsp; Then it lets the event run, but since amount has been changed to 0, it doesn't do anything.</blockquote>

[QUOTE="reanjr, post: 2147880, member: 20740"] As to the second point what you do is define functions inside different root elements. For example, stonecunning (the dwarf ability) is defined like so: [CODE] <monsters> <function name="stonecunning"> <text-representation> <a>"Stonecunning: automatically search secret doors...blah blah"</a> </text-representation> <add-conditional-skill-mod skill="search" mod="2" type="racial" reason="stonecunning" /> </function> </monsters> [/CODE] Now in the dwarf data, we write [CODE] <monsters> <monster name="dwarf"> <stonecunning /> </monster> </monsters> [/CODE] When you apply a race to a character (in this case dwarf), all of the stuff in the dwarf element is basically merged into the character element and executed. So you create a character, add dwarf stuff, which triggers stonecunning to execute, which in turn adds a conditional skill modifier to search checks. So, basically, because the stonecunning function is found inside <monsters>, that is its scope. But once monster data is merged with character data, it allows the character context to use the function. So, nope. No additional tags needed. I haven't seen a need for a new tag outside the data tags (create-context, add-data, add-property, delete-data, delete-property, and import-data) in several days, so it seems like a decent set of functions. I will probably have to think of string functionality of some kind, but I might just treat that like an array of chars. "level"::count would be 5 for instance and "level"::3 would be "v". I think that actually pretty much covers it except for events, which I'll explain here just so that I have talked about it. I'll use the dwarven ability to move at full speed while encumbered as an example, because it's pretty straight forward. An event is declared in a similar fashion to a function, but it never takes arguments (I don't think, don't hold me to that). It generally handles a simple operation that could easily be done without a function. [CODE] <event name="speed-change" amount="0" reason=""> <set name=".speed"> <add> <a>.speed</a> <a>amount</a> </add> </set> </event> [/CODE] Basically, you can declare a function as normal but set two reserved properties on it: attach and when. attach indicates an event to attach the function to. when indicates when to run the function in relation to the event: "before" or "after". So, in the monsters stuff you have [CODE] <monsters> <function name="encumbered-movement" attach="speed-change" when="before"> <assert> <e> <a>reason</a> <a>"encumbrance"</a> </e> <set name="amount"> <a>0</a> </set> </assert> </function> </monsters> [/CODE] When a character becomes encumbered, you call <speed-change amount="-10" reason="encumbrance" /> This triggers the encumbered-movement function because it was told to attach to the speed-change event. It was also told to run before the event itself. It checks the reason, which is "encumbrance", and so sets the amount to 0. Then it lets the event run, but since amount has been changed to 0, it doesn't do anything. [/QUOTE]

Verification