Where we are

...is deep inside refactoring the foe data model. This began with moving desired PlayerCharacter functionality into a base class (lamely called UnifiedActor, but we can get back to that). Common data includes race, class, gender, name, level, body parts, equippable slots (generated from body parts), stats (which includes modifiers and resources) and spellbooks. This involved some refactoring of the data model - races need to specify body parts, body parts need to specify how they generate equippable slots. Those data model updates are where I'm at now. The PlayerCharacter interface remains intact and backwards compatible, and inherits from UnifiedActor. After that I'll start on integrating it into the Foe data model. I think I can do this without touching any of the data in the foe database... at least initially.