Reply to thread

Message: <blockquote data-quote="Dr. Strangemonkey" data-source="post: 4178912" data-attributes="member: 6533">I'm going with Merric B.The Role functions as a test.Once you've put together the ethos and basic mechanics of the class, you ask yourself, 'Does it fulfill a role? If so which one?' and then go back and revise the class so that whatever else it does it fulfills a role effectively and compellingly.So a hybird result is simply one where instead of having a lot of options to fulfill one role you have the same number of options spread across two roles.  So a Druid might be a very interesting character with whole lot of options, but it's not going to be as interesting a Striker as a Warlock or as interesting a Controller as a Wizard.It's still as effective at either role, but where a Wizard when faced with a problem might say, 'Wait, I've got another controller solution,' the Druid says, 'I've used all of my controller options so I'm going to use my striker option to turn into a griffin and go sickhouse on them'I don't think hybrid is interesting as as design goal.  I wouldn't want to see the big book of hybrids, for instance.  But I do think it will function as a good way to build an interesting character.</blockquote>