Reply to thread

Message

<blockquote data-quote="reanjr" data-source="post: 2145436" data-attributes="member: 20740">OK, in that case, we're on the same page.&nbsp; I have no problem supporting a history in the design spec.&nbsp; I just wanted to make sure it was built from current -&gt; back rather than from starting -&gt; forward so &quot;dumb&quot; clients could still use the character.&nbsp; I'm sold on that idea.Good idea about the history tag.&nbsp; That would actually work well for one of the design issues I was trying to come up with a solution for - how to separate temporary modifiers from permanent ones (by temporary, I mean ones that are not saved to the character but are added from, for instance, a temporary spell effect or something like that).&nbsp; My initial thought was to go through the various &quot;source&quot; attributes checking to see if the source attribute was a permanent one or not, but it seemed clunky, which, of course, it was.So you could have something like:[CODE]&lt;strength&gt;17&nbsp; &nbsp; &lt;history mod=&quot;2&quot; source=&quot;race&quot; /&gt;&nbsp; &nbsp; &lt;history mod=&quot;1&quot; source=&quot;level&quot; meta=&quot;4&quot; /&gt;&nbsp; &nbsp; &lt;modifier mod=&quot;4&quot; source=&quot;spell&quot; meta=&quot;1&quot; /&gt;&lt;/strength&gt;[/CODE]Notes:&nbsp;- There's a good reason I used meta instead of level that I needn't go into now.&nbsp;- The meta for spell is sort of an id for the spell that an event can be attached to so that, when the spell runs out, it can be removed.Then when saving the character, any application that supported temporary modifiers could remove all modifier tags (and reduce the value accordingly) before saving.&nbsp; Unless you wanted to have an option to save exact state (if you leave off gaming in the middle of a battle or you are playing a PbP type game).I think that would work pretty well.[edit] Maybe even a third tag for non-permanent, but long term modifiers (such as a continuous magic item).&nbsp; I'll think more on that idea after I get the first two or three chapters of the PHB translated to markup.</blockquote>

[QUOTE="reanjr, post: 2145436, member: 20740"] OK, in that case, we're on the same page. I have no problem supporting a history in the design spec. I just wanted to make sure it was built from current -> back rather than from starting -> forward so "dumb" clients could still use the character. I'm sold on that idea. Good idea about the history tag. That would actually work well for one of the design issues I was trying to come up with a solution for - how to separate temporary modifiers from permanent ones (by temporary, I mean ones that are not saved to the character but are added from, for instance, a temporary spell effect or something like that). My initial thought was to go through the various "source" attributes checking to see if the source attribute was a permanent one or not, but it seemed clunky, which, of course, it was. So you could have something like: [CODE] <strength>17 <history mod="2" source="race" /> <history mod="1" source="level" meta="4" /> <modifier mod="4" source="spell" meta="1" /> </strength> [/CODE] Notes: - There's a good reason I used meta instead of level that I needn't go into now. - The meta for spell is sort of an id for the spell that an event can be attached to so that, when the spell runs out, it can be removed. Then when saving the character, any application that supported temporary modifiers could remove all modifier tags (and reduce the value accordingly) before saving. Unless you wanted to have an option to save exact state (if you leave off gaming in the middle of a battle or you are playing a PbP type game). I think that would work pretty well. [edit] Maybe even a third tag for non-permanent, but long term modifiers (such as a continuous magic item). I'll think more on that idea after I get the first two or three chapters of the PHB translated to markup. [/QUOTE]

Verification