Sorry, it sounded snippier than intended on a second reading. I think the designers chose main roles in the PHB based on most likely. The average paladin would be the shining defender, not a heavy-hitting striker.
Oh, I get that... what I was moreso saying was that I don't think they should have connected explicit combat roles with archetypes... In other words the Paladin shouldn't have been a Defender... he should have been an archetype with a Defender build, a Striker Build and maybe even a Leader build. IMO, that would've covered the roles I've seen a Paladin take on in previous editions and fit more in tune with the varying examples of the Paladin archetype.
Nor do I. But I do think it is possible to achieve, especially as the game expands. Each edition of D&D has expanded to include more and more archetypes mechanically. You could say you were a barbarian and make some (suboptimal?) choices in 1E, but until UA came out (or the Dragon article) you weren't really supported mechanically.
Oh, I agree... but I'm not speaking of expanding the archetypes... 4e created another axis to that when it went with eplicit roles for archetypes. Now not only did it have to include archetypes but it had to include a role for said archetype (which I feel was a mistake, especially since I think way too much effort, early on and even now, was/is put into creating builds that have the same role for the same archetype and thus further pigeonholing archetypes. Now I can have a striker fighter, without a feat tax or multi-classing... but this should have, IMO, been the direction in the first place.
They could have done alot with the first book, as evidenced by multiple players handbooks and additional support material. But I think it's unreasonable to expect all that from the get go.
I think you're still confusing what I mean by archetype. In my mind an archetype is the fighter... but I don't feel the archetype of the fighter should have been initially constrained to the role of Defender... it leaves out too many iconic examples of fighters that weren't "defenders". It was role diversity within archetypes that I feel 4e should have focused on earlier in the game. Even now there are at most a couple of archetypes that aren't still pigeonholed into particualr roles... even if that role doesn't cover iconic concepts of said archetype.
[Note: You accidentally attributed part of my post to Walking Dad]
Whoops, sorry about that...
I don't consider adding the ability to heal and gain training in another skill a 'tax' unless it diminished my current abilities. I could see the 'feat tax' argument for the armor proficiency. And needing PHB2? Definitely. I don;t think the archetype you describe is that common. Strikers before 4E were basically rogues. Their high damage came from Sneak Attack. Not something paladins are well-known for (despite the running joke in our group about one player's 'sneaky paladin.')
See and that's the problem, a paladin already has all these things... all I want to do is make him a striker as opposed to a defender. So it is a feat tax since I don't want the extra stuff... just a role change. The Slayer is a fighter who doesn't have to spend any feats to be a striker... yet to get a paladin striker I do...
As to your second point... I'm going to disagree I don't think the roles were as hardcoded and especially not in 3.x.
Fighters weren't always tanks... they could easily be tweaked as strikers... Cleric's could tank or lead, Wizards could focus on particular spells to make themselves strikers, controllers, or defenders but probably not leaders in the 4e sense... and so on. So no, I don't agree with that
The designers started to expand on that role in the PHB with the Ranger and the Warlock. Again, they could have kept going, but there was only so much space you can devote to the core books before you need to get them out there.
See maybe this is the disconnect... I don't feel they should have expanded archetypes based on roles... I feel they should have expanded the roles within archetypes. Something they're finally getting around to doing... though this could just be test material like Bo9S.
Hindsight is 20/20. I've had my own thoughts in this direction since the mention of shared power lists in Ro3. But I don't have the time to design my own perfect game system. You can only hope the designers learn and continue down a path you enjoy. To expect that they should have gotten it right for you the first time around is unreasonable, IMO.
I don't know if it's totally hindsight... I remember quite a few complaints along the lines of... "Why can't my fighter be a striker as opposed to a defender?". These questions tended to be met with the answer of "Go play a Ranger.". When in actuality I feel the answer (which funnily enough it is now) should have been go play the striker build for the fighter.
[sblock="Hybrid Paladin/Barbarian"]====== Created Using Wizards of the Coast D&D Character Builder ======
Arjhan, level 1
Dragonborn, Barbarian/Paladin
Hybrid Paladin Option: Hybrid Paladin Will
Hybrid Talent Option: Paladin Armor Proficiency
Dragonborn Racial Power Option: Dragonfear
Redeemer of the Desecrated (+2 to Religion)
Theme: Knight Hospitaler
FINAL ABILITY SCORES
STR 20, CON 10, DEX 10, INT 8, WIS 11, CHA 16
STARTING ABILITY SCORES
STR 18, CON 10, DEX 10, INT 8, WIS 11, CHA 14
AC: 18 Fort: 16 Ref: 10 Will: 14
HP: 25 Surges: 9 Surge Value: 6
TRAINED SKILLS
Athletics +8, Intimidate +10, Religion +6
UNTRAINED SKILLS
Acrobatics –2, Arcana –1, Bluff +3, Diplomacy +3, Dungeoneering +0, Endurance –2, Heal +0, History +1, Insight +0, Nature +0, Perception +0, Stealth –2, Streetwise +3, Thievery –2
POWERS
Basic Attack: Melee Basic Attack
Basic Attack: Ranged Basic Attack
Knight Hospitaler Utility: Shield of Devotion
Dragonborn Racial Power: Dragonfear
Paladin Feature: Divine Challenge
Barbarian Attack 1: Howling Strike
Paladin Attack 1: Strike of Hope
Barbarian Attack 1: Avalanche Strike
Barbarian Attack 1: Life Thane Rage
FEATS
Level 1: Hybrid Talent
ITEMS
Plate Armor x1
Greatsword x1
Adventurer's Kit
Trail Rations
====== End ======[/sblock][/QUOTE]
Cool, though my Paladin now has the primal power source and rages and a host of other things that don't necessarily fit with the archetype I'm picturing... especially depending on the god or ideals I want him to follow.