Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="jlhorner1974" data-source="post: 4787353" data-attributes="member: 8628">This is no knock on the developers that work on Builder, as I believe they have all given a lot of effort and have put out a good product despite apparently severe restrictions on budget and time.It seems to me that their XML output closely reflects the internal data structure of their program.  Any calculated number is a stat, and stats can have any number of modifiers to them (statadd in their lingo).  This certainly makes sense from a programming standpoint, but it creates havoc on those trying to consume the information, as was said.  My guess is that they are just programmatically looping through all of the stats and spitting out XML based on each particular item.  But they haven't given any real context on what stat is what -- you see stats like "Bluff", "initiative", "Speed", and "Saving Throws" all tossed in the same section.Some things have been changed for the better -- short descriptions for feats, class abilities, can now be found with the item instead of having to search through the textstring section for an ITEM_NOTE_ entry that matches the name of the item (which is a pain).  Also, the new Powers section is helpful, giving a breakdown of power data by weapon.But some information completely missing -- there used to be a RulesElementField section that let you know what item slot a magic item used, but now it seems to be gone.  Right now, there is insufficient data in the file to determine what the currently equipped Arms slot item is, for instance (I guess that the Viewer is looking up the item in the database to figure this out.)  It's also a pain to figure out what powers or magic items were used.I think one of the biggest problems is that the .dnd4e file consists of some sections with choices that were made when creating the character (the "internals", that comprise what Builder and the Viewer *actually* need to reconstruct the character) interspersed with "user friendly" sections (calculated values that Builder/Viewer do not really need to load).  It is clear that Viewer has its own ability to calculate things, or else you wouldn't be able to pencil in your own numbers on the sheet and have things recalculate.  So why store calculated values at all, unless you are intending on having third parties look at or consume them?It's also clear that Viewer also has access to the rules database, as things like the Regional Benefit, power, and magical item full descriptions can be seen (and printed) in the Viewer, but this information does not show up in the .dnd4e file (which is understandable).IMO, if Builder/Viewer are going to store calculated results in the .dnd4e file, there should be two distinct sections in the file -- one for internals (that the builder/viewer actually look at) and one for the actual character sheet in XML form.  The character sheet section should have enough information in it that you can easily use an XSLT to create a sheet that contains all the information on the standard sheet with a different look and feel.  This XML should be hierarchical and follow the layout of the standard sheet -- Skill stat data should go under a <Skills> section, for instance.  Also, the output  should reflect what state the sheet is in when it was saved.  Powers should output stats for the weapons that appear on the standard power cards that print with the sheet (taking into account user customizations that hide cards or determine which weapons' stats appear on which power cards).  Don't tell us that there is a penalty to a stat if heavy armor is equipped or if the character does not have a certain weapon/armor proficiency -- we can't change what things are equipped or what proficiencies a character has from within the builder anyway.  It would be even better if the viewer accepted a custom XSLT so that it would apply the formatting for us and let us print custom power cards and magic item cards, because there is no way Wizards will ever export the descriptions for those in XML form.  (It'd be way to easy for others to use it to generate their own electronic tools that way.)My point is that the Viewer holds all of the information on what needs to be displayed on a character sheet -- the "XML Output" feature of Builder/Viewer should simply output all the information needed to reconstruct the standard built-in sheet.  Just tell us what belongs in every box and on every line of the sheet without having to apply any logic!</blockquote>

Verification