Reply to thread

Message

<blockquote data-quote="JimAde" data-source="post: 2132678" data-attributes="member: 16739">And fine ideas they are. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />&nbsp; I really like the history point.&nbsp; I wonder if it's really part of the data, though.&nbsp; I would think it would be the application's responsibility to keep track of previous versions of the data.&nbsp; Just as the spec for a Word document doesn't (I assume) include revisions, but the MS Word document keeps previous versions or information about actions taken for undo.&nbsp; So when you level your character, the application would archive the previous level in a known location and if you want to revert it can.&nbsp; Of course it would have to be smart enough to revert only things that are level-dependent and not, for example, equipment. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />Your second suggestion gets at something I was trying to say earlier.&nbsp; I would love it if we could define some kind of meta-data for modifying existing data.&nbsp; It's a major feature of d20 (and RPGs in general) that a lot of things can affect a lot of other things (pretty generic statement I know).&nbsp; So in your example, the &quot;house rules&quot; could include a bit of markup that says the spell called &quot;acid fog&quot; should have its level set to 8 for wizards and sorcerers.&nbsp; This might have a syntax something like&lt;modifier modifiedElementName=&quot;global.spell.acid fog.level.wizard&quot;&gt;&nbsp; &nbsp; &lt;modificationType=&quot;replace&quot; modifiedValue=&quot;8&quot; /&gt;&lt;/modifier&gt;&lt;modifier modifiedElementName=&quot;global.spell.acid fog.level.sorcerer&quot;&gt;&nbsp; &nbsp; &lt;modificationType=&quot;replace&quot; modifiedValue=&quot;8&quot; /&gt;&lt;/modifier&gt;</blockquote>

[QUOTE="JimAde, post: 2132678, member: 16739"] And fine ideas they are. :) I really like the history point. I wonder if it's really part of the data, though. I would think it would be the application's responsibility to keep track of previous versions of the data. Just as the spec for a Word document doesn't (I assume) include revisions, but the MS Word document keeps previous versions or information about actions taken for undo. So when you level your character, the application would archive the previous level in a known location and if you want to revert it can. Of course it would have to be smart enough to revert only things that are level-dependent and not, for example, equipment. :) Your second suggestion gets at something I was trying to say earlier. I would love it if we could define some kind of meta-data for modifying existing data. It's a major feature of d20 (and RPGs in general) that a lot of things can affect a lot of other things (pretty generic statement I know). So in your example, the "house rules" could include a bit of markup that says the spell called "acid fog" should have its level set to 8 for wizards and sorcerers. This might have a syntax something like <modifier modifiedElementName="global.spell.acid fog.level.wizard"> <modificationType="replace" modifiedValue="8" /> </modifier> <modifier modifiedElementName="global.spell.acid fog.level.sorcerer"> <modificationType="replace" modifiedValue="8" /> </modifier> [/QUOTE]

Verification