Talk:Druid (Evaluational Base Class Layout)/Table: The Druid

From D&D Wiki

Jump to: navigation, search

Table: The Druid[edit]

Table: The Druid would appear to list class abilities received at each level. So, why are class skills spliced onto the end? How does this feature fit into the table any better than, say, weapon and armor proficiencies? (Answer: It doesn't.) I've been told that's the way some of the later books do it, but the PHB format makes a whole lot more sense to me, not to mention being more aesthetically appealing. --CĂșthalion 20:58, 2 April 2007 (MDT)

I have come to like it and if it also is how WotC makes their tables, why not? I like it because it says the same thing in a lot less space and is easier to use at a glance. --Green Dragon 13:26, 9 April 2007 (MDT)
I think it looks good. All the main information in one general area. Armond 15:00, 9 April 2007 (MDT)
Weapon and armor proficiencies are nothing more than a class feature, and WotC has made them a special case in that they're a class feature that is not list in the table. So the better question is "Why are weapon and armor proficiencies the only class feature not listed in the table?" —Sledged (talk) 11:08, 11 April 2007 (MDT)
They're inherent feats to (nearly) every class. It's way too cluttery to put them on the table (especially for unorthodox proficiencies like the rogue, though I suppose they could call them "rogue proficiencies" and leave it at that). Try putting more than three class features on one line - it's looks horrible. (A couple classes I've made have had to be rebalanced because it looked so ugly I had to change their class feature progressions :P) Armond 11:20, 11 April 2007 (MDT)
I am for just keeping only the class features on the table and not other things — call it the D&D Wiki style if you like ;). --Green Dragon 21:31, 12 April 2007 (MDT)
Home of user-generated,
homebrew pages!
system ref. documents

admin area
Terms and Conditions for Non-Human Visitors