Hypersmurf
Moderatarrrrh...
A no ability to customise them.
That means no Barbarian Slayer, no Paladin Guardian and no Ranger Archer.
It doesn't if the fighter's schtick is 'extra themes'.
-Hyp.
A no ability to customise them.
That means no Barbarian Slayer, no Paladin Guardian and no Ranger Archer.
Backgrounds are just what skills you have. Themes are just what feats you get. The fighter would continue to be the blandest class that can't do anything that anyone else couldn't.So I maintain that all we need is one "fighter class," with a variety of Backgrounds (skills, proficiencies, flavor) and Themes (special abilities, feats) to add as desired. This will allow us to build any of these other "classes" quickly and easily, and with one-tenth the page count.
Depends on where you draw the line and how far you're willing to go in bringing the fighter up to par. Part of the problem with the fighter is that there is great resistance to giving it, well, anything. "The Fighter is best at fighting" is balanced by "the fighter sucks at everything else and gets no interesting or useful abilities." That really limits customization, even if you do give him 'bonus feats' (extra theme) and feat taxes.The problem with taking appart the fighter into multiple classes is, that would make a lot of classes.
I guess that would depend on whether or not the rules (or the DM) allows you to take more than one theme. (shrug) Multi-class, multi-theme, whatever.A no ability to customise them.
That means no Barbarian Slayer, no Paladin Guardian and no Ranger Archer.
So far, yes. But what if in the next playtest, both are expanded? Backgrounds could be expanded to include skills, bonus languages, and weapon proficiencies...Themes could be expanded to include feats and special abilities...I think that would be awesome. I'm going to keep my fingers crossed for it.Backgrounds are just what skills you have. Themes are just what feats you get. The fighter would continue to be the blandest class that can't do anything that anyone else couldn't.
I guess that would depend on whether or not the rules (or the DM) allows you to take more than one theme. (shrug) Multi-class, multi-theme, whatever.
You are right; there is no way that they can make everyone happy (just look at all of the "uproar" over the definition of hit points in this forum). Some people want only the iconic D&D classes in their games, some people want newer classes, others want to get rid of classes altogether, and some (like me) think D&D never needed more than 4 classes anyway. There will always be lots of loud demand no matter what they decide to do. I don't envy them.Even so, it still means that to play some 'Iconic' D&D classes, you have to use a Theme up that could have been used one something else.
Take all the people that complain about Feat Taxes, swap the word Feat for Theme and I think you will be able to approximate the scale of the issue for people. Even more so if to play a 'Ranger Archer' you have to wait for level six, while a 'Fighter Archer' can be done at level one.
I think it would just be a repeat of when 2e tried it, I.e. overturned pretty quickly due to lots of loud demand.
My point, though, isn't about making people happy...it's about efficient game design.
CleverNickName said:So I maintain that all we need is one "fighter class," with a variety of Backgrounds (skills, proficiencies, flavor) and Themes (special abilities, feats) to add as desired. This will allow us to build any of these other "classes" quickly and easily, and with one-tenth the page count.