Crazy Jerome
First Post
Second, a small number of classes (artificer, beast-druid and monk come to mind) have very distinct powers because they are a highly flavored variation on their power source. That kind of design may require some specialized power lists, but I tend to think that that's OK as an exception.
And this brings us to why if the game is to be exception-based design, it should be exception-based design done properly. Right up front is that things that are alike are classed alike, and things that are not alike, are not.
This is why I said that even if most powers and features are done in common lists, there should be room for the exceptions. Classes can have their own powers and features. Classes can have more or less access to the common lists.
Assume for a moment that all powers of a given level and purpose are close enough to equal to be tolerable. Then it matters not if the paladin has, say, 8 common powers and features and only 2 special paladin ones, while the monk reverses this ratio. That just says that the monk class is more of an exception than the paladin, and the writers have chosen neither to clutter the common lists with powers only the monk will have, nor make the paladin, fighter, etc. have highly redundant list simply to meet the arbitrary demand of each list being separate.
There is a small argument to be made that each class having a separate list would lead to some ease of use by the players, and this would be worth whatever redundancy crept in. At launch, it wasn't completely off-base, especially for people not familiar with some of the common pitfalls of misapplied exception-based design. However, I think 4E has proven that argument false.

It is rather surprising that this misapplication of the design persisted when they had the good sense to realize that "filling out the grid" simply to have it filled out, was not good. Thus the relunctance to do the martial controller.
