Reply to thread

Message

<blockquote data-quote="Greg K" data-source="post: 7320915" data-attributes="member: 5038"><p>Well, as far as I am concerned, the WOTC in-house designers (including those that left for Paizo) are, in general, not good class designers- Owen K Stephens was/is a rare exception.&nbsp; They are good at a lot of other aspects of game design, but they pale in comparison to Owen K. Stephens and Steve Kenson whom, when building classes based on fantasy archetypes, actually look at the cultural and legendary abilities of those archetypical versions and then build a general class that can handle those while using the subclasses (or in 5e prestige classes) to hone in on specific versions.&nbsp; To me this is a better than coming up with a single remotely related gimmick to build the class around or abilities specific to one interpretation, throwing in random inappropriate or overly specific ribbons into the base class, and then trying to force the subclasses to fit into the base class (and this assumes the gimmick has anything remotely to do with the archetype used for the class or subclass name in the first place).</p></blockquote><p></p>

[QUOTE="Greg K, post: 7320915, member: 5038"] Well, as far as I am concerned, the WOTC in-house designers (including those that left for Paizo) are, in general, not good class designers- Owen K Stephens was/is a rare exception. They are good at a lot of other aspects of game design, but they pale in comparison to Owen K. Stephens and Steve Kenson whom, when building classes based on fantasy archetypes, actually look at the cultural and legendary abilities of those archetypical versions and then build a general class that can handle those while using the subclasses (or in 5e prestige classes) to hone in on specific versions. To me this is a better than coming up with a single remotely related gimmick to build the class around or abilities specific to one interpretation, throwing in random inappropriate or overly specific ribbons into the base class, and then trying to force the subclasses to fit into the base class (and this assumes the gimmick has anything remotely to do with the archetype used for the class or subclass name in the first place). [/QUOTE]

Verification