Alright, Races and Classes is awesome. I am so excited for 4e and looking forward working with it in our business.
I am thoroughly impressed with the human flaw too. Brilliant and very thought provoking. I would love to have been there when the designers hit that idea, and knew it was the one. It stirs something inside when you read it.
My concern though, is with the roles for player characters. Defender, Striker, Controller and Leader. I think there is a mistake made.
Leader is improperly labelled. It should be Support (or something to that effect). Here is my reasons:
1) It is misleading: the party leader should not default to cleric or warlord. It should be the player whose character naturally feels takes on leadership roles, which any class should be able to do. Leadership is not a unit function in the same reagard as defender, striker or controller is.
2) Leaders don't always lead: Clerics are not really the party leader and their function is not to direct the other members. Likewise, the warlord (who is mislabeled to) is intended to coordinate and support the rest of the group. He takes on the 3.5 bard's role to a degree.
Support classes are the classes that buff, remove negative effects, heal, use their actions to aid or guide other party members. They also coordinate group activity and have a flexiblility to change from frontline to behind the lines role.
When looking at both the Cleric and Warlord in this light, I think the defination of Support makes more sense.
Another point I like to add. I think your team should look at dual role classes. For example, the paladin is really a defender/support, the bard a controller/support, the druid a defender/ controller, the sorcerer could be a striker/ support, the swordmage a striker/defender or defender/controller.
This makes the classes much more verstile and interesting to design.
I am thoroughly impressed with the human flaw too. Brilliant and very thought provoking. I would love to have been there when the designers hit that idea, and knew it was the one. It stirs something inside when you read it.
My concern though, is with the roles for player characters. Defender, Striker, Controller and Leader. I think there is a mistake made.
Leader is improperly labelled. It should be Support (or something to that effect). Here is my reasons:
1) It is misleading: the party leader should not default to cleric or warlord. It should be the player whose character naturally feels takes on leadership roles, which any class should be able to do. Leadership is not a unit function in the same reagard as defender, striker or controller is.
2) Leaders don't always lead: Clerics are not really the party leader and their function is not to direct the other members. Likewise, the warlord (who is mislabeled to) is intended to coordinate and support the rest of the group. He takes on the 3.5 bard's role to a degree.
Support classes are the classes that buff, remove negative effects, heal, use their actions to aid or guide other party members. They also coordinate group activity and have a flexiblility to change from frontline to behind the lines role.
When looking at both the Cleric and Warlord in this light, I think the defination of Support makes more sense.
Another point I like to add. I think your team should look at dual role classes. For example, the paladin is really a defender/support, the bard a controller/support, the druid a defender/ controller, the sorcerer could be a striker/ support, the swordmage a striker/defender or defender/controller.
This makes the classes much more verstile and interesting to design.