Reply to thread

Message

<blockquote data-quote="MaxKaladin" data-source="post: 2132647" data-attributes="member: 1196">Just a couple of comments from the peanut gallery.&nbsp; 1.&nbsp; I think history should be a part of any such data model.&nbsp; You should be able to look at the data and see exactly how the character progressed to the level they're at.&nbsp; I think this is important for a couple of reasons.&nbsp; One is if people use this at the game table and you have temporary level loss affect the character.&nbsp; This would make it easy to just click a button to apply that loss and the application can know exactly how to 'downgrade' the character.&nbsp; Another is for DMs making NPCs.&nbsp; One thing I sometimes do when making NPCs with programs like PCGen is decide I want to take a few levels off either to add them to a different class or just for balance.&nbsp; I generally find this to be a pain to do since you then end up having to go through and manually subtract skill points, feats and stat bonuses (which may then affect skill points) and so on.&nbsp; A history would make this much easier.&nbsp; 2.&nbsp; I think the data model should include tags that allow modifications for specific rulesets.&nbsp; For instance, you could specify that acid fog is level 8 in a specific set of house rules and when a program is switched to a set of house rules, it could go through the list and apply all of the modifications to the various elements in the data.&nbsp; You would probably need to specify what the specific set of rules is, what to modify and what to change it to.&nbsp; If you're really ambitious, you could also allow for new variables that aren't in the standard rules like spell points for house rules that use them.Yeah, I know its too early to define the data but I just wanted to throw those ideas out there.</blockquote>

[QUOTE="MaxKaladin, post: 2132647, member: 1196"] Just a couple of comments from the peanut gallery. 1. I think history should be a part of any such data model. You should be able to look at the data and see exactly how the character progressed to the level they're at. I think this is important for a couple of reasons. One is if people use this at the game table and you have temporary level loss affect the character. This would make it easy to just click a button to apply that loss and the application can know exactly how to 'downgrade' the character. Another is for DMs making NPCs. One thing I sometimes do when making NPCs with programs like PCGen is decide I want to take a few levels off either to add them to a different class or just for balance. I generally find this to be a pain to do since you then end up having to go through and manually subtract skill points, feats and stat bonuses (which may then affect skill points) and so on. A history would make this much easier. 2. I think the data model should include tags that allow modifications for specific rulesets. For instance, you could specify that acid fog is level 8 in a specific set of house rules and when a program is switched to a set of house rules, it could go through the list and apply all of the modifications to the various elements in the data. You would probably need to specify what the specific set of rules is, what to modify and what to change it to. If you're really ambitious, you could also allow for new variables that aren't in the standard rules like spell points for house rules that use them. Yeah, I know its too early to define the data but I just wanted to throw those ideas out there. [/QUOTE]

Verification