Teflon Billy said:
TB, while I love contructive replys and all, that wasn't one of them. Are we not on a d20 discussion board right now? That 'question' was a bit un-called-for, don'tcha think?
Teflon Billy said:
That said, there is a reason why the Prestige Class creation guideliens made the final cut. The reason the Battlemage isn't in the core classes is because--well--then where does that leave the plain old mage?
It leaves him where he was, obviously. A "plain old mage" would obiously be a more competent spellcaster than a battlemage could ever be; that's how balance works, right? If I give one class everything, then it's not balanced, and therefor not acceptable, thus you need to reduce its power. So a battlemage has to give up something for gaining it's niche, to continue our shared example of the fighter-battlemage-wizard spectrum.
Also consider that PrCs where originally intended to fill a special niche in every world where very powerful and specific roles need to be - like Red Wizards, Purple Dragon Knights, and Spellfire Channelers in FR. Just because there are 600 PrCs doesn't mean that they
belong in your game or your world.
If your campaign setting has a high magic focus, then maybe a battlemage is appropriate as a base class, with some more specific PrCs as well. If your campaign is a low-magic setting, then maybe a generic Fighter/Wizard PrC is not appropriate at all. It's all about the fulff and crunch and crunch and fluff, and PrCs are entirely optional in that, and are infact dictated by the Dms own preference of those two elements.
Psion said:
I think classes that can be fairly represented by multi-classes of existing classes are redundant and often inflexible (since you can't vary degrees of each class with your "combo class"; it's hardwired) and thus don't deserve to be part of the core rules.
Fair enough, but don't you think that, if properly designed, a Battlemage would fill a niche a fighter/wizard combo couldn't fill? As above, I think that with the proper reasoning, one could make a case for all sorts of archetypes in their campaign setting, depending on the fluff and the crunch therein.
Multiclassing also has that unnice sideeffect of gimping classes in a number of ways (spellcasters and bad saves) while really helping out full-BABers and shared-good saves. This is hardly what TB was talking about when he spoke of how 3e was designed with goals to get rid of class-discrepincies (sp?) in power. A Fighter/Wizard is going to have an abomidable Ref Save, and decent Fort/Will. His BAB and spellcasting will be all over the place, since the 'degrees' of your combo will dictate them. Would not this be the case for a base class?
Psion said:
Making existing classes more general (e.g., making the monk into a martial artist that could be another unarmed fighter type like a pugilist) or realizing concepts that can't be fairly realized by existing classes (a PC noble class) are moves I can get behind.
My thoughts exactly
Scribble said:
What do you ll think some clear guidelines would be for whether or not something should be a base class?
Well, whereever the holes are in the rules, of course; see my list above.
I also agree in making several packages availiable for different classes; one sugesstion I made in a thread about fighters was in order to make a swashbuckler, take away medium and heavy armour profs, all shields, and all martial weapons except those which are finessable, and give Balance, Tumble and some other few skills as class skills, and give +4 SkP/level. Weapon Finesse is a seet 1st level feat. Works nicely, IMO.
Just one example of what you were going for, but not a truel solution, IMO.
There's also the side of fluff; if you need a holy man who's non-combative, where's the 1/2 BAB priest class in the core rules? Nowhere.