Looks like the Avenger is super-lightly armored, actually.Want to be a heavily armored striker? Avenger.
Then there's no issue. Grab a big weapon and go to town.I guess it comes to me disagreeing with the designers on what the fighter role should be. I don't see fighters at defenders, but as defenders and or strikers.
...and fighters are still trained warriors? With a better-than-normal attack bonus, to boot (via the fighter weapon talent).I actually loved the old 3E fighter because they were feat monkeys with large base attack bonuses. For me this fit the concept of the fighter; someone who was a trained warrior.
Looks like the Avenger is super-lightly armored, actually.
Then there's no issue. Grab a big weapon and go to town.
...and fighters are still trained warriors? With a better-than-normal attack bonus, to boot (via the fighter weapon talent).
Rogue 1 daily + sneak attack = 5d6+dex damage.but the strikers are still better at dishing out big damage than they are.
And if you don't want to be a tough warrior, then why are you looking at the fighter?
The fighter is inherently tough by virtue of armor and hit points. That's how the fighter has always been, in every edition of D&D, independant of one's CON score.Because being a fighter doesn't have to mean being a slab. Remember that constitution is one of four possible prime stats.
Because being a fighter doesn't have to mean being a slab. Remember that constitution is one of four possible prime stats. You could just as easily make a fighter that relies primarily on dexterity and wisdom, which would make him neither tough, nor strong(but no less effective).
I think that you are looking at this too much from the role perspective, and not enough from the character concept perspective. A fighter is not someone who is tough. He is not someone who is strong. A fighter is someone who fights. That is his primary function. If I make a swashbuckler, then a rogue just might fit the bill. But if I want to make a duelist, then I don't care about thievery skills. I don't care about sneak attacks. I care about swordsmanship. Skill with a weapon. Fighting. And yeah, I could pretend that my character's sneak attack is really some sort of sword maneuver. I could pretend that the fluff for all of the abilities means something else. Or I could play a fighter, a class already designed for my character concept with the only exception being that the word "defender" was typed into the Class Traits block. So which is easier for me to get around? A single word or several pages of fluff and slightly off flavored mechanics?
Except that's not accurate at all. Almost all of the fifteen or so pages of powers and class abilities for fighters are designed around the 'defender' role, not just the word 'defender' in the class description.
It's concept -> combat role (or possibly roles; multi-class feats, paragon multi-classing, and paragon paths that help bridge roles all exist) -> class. Fighter is character class. It's at the bottom of the chain. The class name may be more generic than the class actually is (fighter and wizard suffer from this, to some degree), but a D&D4 character class is a pretty specific thing, to the point where the two-classes-in-one Ranger really ought to have been broken up, except that would have given us 4 strikers in PH1.
Spatula said:The fighter is inherently tough by virtue of armor and hit points. That's how the fighter has always been, independant of one's CON score.

(Dungeons & Dragons)
Rulebook featuring "high magic" options, including a host of new spells.