generalhenry
First Post
This is very nice work, but I can't help feeling like it's the nerdiest thing I've ever seen.
Correct, this format only contains the data that the player chooses.banana said:- Ability scores don't include racial bonuses, right?
Yep! Thanks, I was trying to figure out exactly how to do that.banana said:- I think that the root <character> element should be including the schema definition:
<character xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="4eCharacter.xsd">
Currently, my editor will load sheets that don't include it but won't be able to validate them against the schema for correctness.
This is another cosmetic thing. There's no reason we couldn't have valuables in equipment, but they were separated on the official character sheet so I went that way to begin with. Also, if you can think of a synonym for <valuable> that includes money, gems and art objects but not magic items or mundane equipment, I'd be happy to use it!banana said:- Why is <wealth> separate to <equipment>? <valuable> could be in the <equipment> section along with <item>. Also, <valuable> is kind of a clunky name.
This is exactly why I wanted to make this schema!banana said:Here are some screenshots of opening the KotS character xml files:
Yes, I think this might actually be the better way to go. I think we should take extra care to note that this only applies for situations where you have a choice of feat, power, skill or language, though. For example, IMO the Dragonborn's racial power shouldn't go in the <powers> section, as it's mandatory. That means the <choice>s should stay in the <race> section.banana said:Thoughts on Humans: it's implied by being Human that you have a bonus feat. You don't need to specify it as a choice for your <race>! You can just go ahead and add an extra feat to the <feats> section. This applies to powers, skills and languages too.
I had a slightly different idea on this, actually... How about if we put all the Wizard's spellbook spells in his <powers> section, and only put his prepared spells in the <current> section? I think that fits the philosophy of the <current>/rest-of-the-file split.banana said:On spellbooks: that seems like it might be a good idea. I agree that dividing by level isn't necessary, as that can be inferred from the power name (then again, so can its action type...).
I'm glad we could make your high score list.generalhenry said:This is very nice work, but I can't help feeling like it's the nerdiest thing I've ever seen.
some FAQs about what we're doing, so people can see the benefits and it's not just a nerdzone.
Good point. I'll probably restructure the OP once the thread gets unwieldy, anyway.generalhenry said:I don't see it as a problem, it is a nerdzone. Only developers who want interoperability have any use for it.
To make it clear all it takes is three screen shots. The character in XML form and in two different formatted sheets.
Yep.<feats> <!-- Should I put human feat here? -->
that a staff takes two hands to use.
I agree that that's how it should be, but you can read the WotC Customer Service ruling in this thread: http://www.enworld.org/showthread.php?t=231261generalhenry said:that's a tricky one.
It's a two handed weapon, but it's also a one handed implement.
ninjeff said:I'm not sure what you did with ability scores, as they're pretty tough to reverse-engineer, so I gave you new ones. Feel free to change them back if I got it wrong.For reference, each ability score element's value should be your base score before racial modifiers and increases from levels. The racial modifiers are either determined by race or a choice relating to race, and so shouldn't be counted in this section. The increases attribute should count only increases from levels 4, 8, 14, 18, 24 and 28, not the automatic increases at levels 11 and 21. Forgive me if you'd already worked that out - like I said, ability scores are tough to reverse-engineer.
ninjeff said:As for magic item levels, I was going to go with the names in the tables in the PHB - e.g. "Bloodthread Armor +6". I'm pretty sure they can all be distinguished that way, but if anyone spots a problem with this method, let me know.![]()
ninjeff said:Also, the above section reminded me that we need a <wornItem> element in the current section, so I've added that. I didn't set you as using the staff of fiery might, as apparently WotC Customer Service has been quoted as saying that a staff takes two hands to use.