I sincerely hate this form of "behaviors", simply because you lose all the useful stuff coming from ProfileElement. Subclassing ProfileElement lets you have full-blown XML element support (which also ensures XML validity against required custom tags). It also enforces some certain documentation (such as author, etc) that is incredibly helpful to everyone. Secondly, you can subclass from QuestProfileElement to get access to some quest-related API (specific to quest tags).
Oh, just wait for v0.2 then! I was intending to plug everything back into it eventually! (And I'll even use QuestProfileElement!) With the work on the quest profiles, I was just really looking for a generic type to fill in some behaviors I was working on. There's 4-5 more tags I've been using that seem much more useful that I'll be posting in a bit, just had life pull me away is all!
