Reply to thread

Message: <blockquote data-quote="Crazy Jerome" data-source="post: 5600575" data-attributes="member: 54877">That would be good, but a better way would be to let you to set up a profile that was pick and choose on every power, rule, etc. Then that is the one that people would see in your campaign. That would be a nightmare if they tried to manage it from the service side, since that is basically versioning. But for individual tables, it would be fine: "I'll take the lastest of everything, as of 6/1/2011. Wait, we don't like that version of Tide of Iron. Check an earlier one. Yeah, that's the one we want. OK, mark it in the profile." The only reason to not let people use item by item selection on revision is that if you were forced to do it that way, it would be a user interface nightmare. So basically, it is a bit more work in the UI, and a bit of extra work in the databases to store the revisions.  And then some common profiles predefined so that people can mostly ignore the option when it doesn't apply to what they want to do. A nightmare on paper or a static app, but just good design on a more dynamic app. Heck, the same kind of UI and changes would solve all of the customization issues with wanting to exclude selected items, and would more readily facilitate house rules too. (Your house rule becomes just another revision, albeit one stored in a different place and marked a bit differently.)</blockquote>