Reply to thread

Message: <blockquote data-quote="Mustrum_Ridcully" data-source="post: 4040595" data-attributes="member: 710">I think I prefer a "Top-Down" approach. First, make n broad class concepts, then expand on these and create "subclasses. It's not neccessary that these concepts are always called classes. 4E "top class" are the 4 roles, but they aren't actually classes, instead the subclass of roles are called classes. Beyond that, things like talent trees can be used to implement further subclassing, if desired or neccessary.The approach has the key advantage that you slowly begin to understand what options do you have."Do you want to fight in melee, ranged or cast spells?""If you want to fight in melee, do you want to be light and agile or heavily armored and armed""If you want to be heavily armored, do you also want to use a shield, or do you prefer a large weapon?""If you want to fight with a large weapon, do you prefer fighting with a polearm or with a closer combat weapon?"If you start the questions somewhere in the middle, it gets difficult to see the possibilities (and a system starting this way has a high change of missing important subtypes.)</blockquote>