...why not just bump up the damage die he rolls with weapons by one step? If they're already doing that for racial classes, it's not a big deal to do it again. Obviously, they'd have to be careful about stacking this effect (the dwarven fighter would go from 2d6 to 2d8 damage), but I'm not seeing how it's going to bust the game wide open to make sure the fighter is mowing through enemies.
If people are super worried about damage on the fighter...
- Thread starter B.T.
- Start date
Lwaxy
Cute but dangerous
In my view, the fighter shouldn't mow through enemies, at least not until later levels. Our fighter was already kinda outdoing the rest, including the wizard.
I'd prefer some sort of exhaustion rule where you are more likely to hit with your first strikes and then lose the boni for every additional hit.
The auto-damage of the playtest fighter could be, for example, 4 points for first strike, 3 for next, then 2 and then 1 until he has rested.
But I keep getting crazy ideas like that
I'd prefer some sort of exhaustion rule where you are more likely to hit with your first strikes and then lose the boni for every additional hit.
The auto-damage of the playtest fighter could be, for example, 4 points for first strike, 3 for next, then 2 and then 1 until he has rested.
But I keep getting crazy ideas like that
The fighter's damage on a hit doesn't seem to be a problem. Heck, so far, against kobolds and goblins the damage has been utter overkill (we were making jokes by the end of the night that on a miss he kills a kobold but on most hits he cuts the head clean off!).
Even against the high hitpoint Ogre the fighter was doing more than enough damage.
Killing one minor enemy per round is hardly mowing through enemies! Even at second-third level the fighter only "mowes" through minor stuff.
And "outdoing the wizard?" Certainly not in my group! The fighter killed his share of stuff (then again, so did the rogue) but between sleep, burning hands and magic missle he wasn't even close to the wizard.
And that's just in combat - where the fighter is supposed to shine. Outside of combat the fighter couldn't hold a candle to all the neat stuff the rogue and the wizard could do.
Take away the fighter's one advantage of consistant, not limited (eg spell dependant) damage? I'd like to see if that can be avoided this time around.
Lwaxy
Cute but dangerous
Our wizard's spells got either interrupted, or she had no line of sight to the target, and the foes managed the sleep saves 
The rogue had really bad dice rolls, and the clerics weren't that much behind. The fighter was the best contributor by far.
One enemy per round is ok at first, but hey, your arm will eventually tire.
The rogue had really bad dice rolls, and the clerics weren't that much behind. The fighter was the best contributor by far. One enemy per round is ok at first, but hey, your arm will eventually tire.
I keep seeing grumping about the fighter's damage per round and how the cleric can buff up and be as good as him for a short period of time.
Our wizard's spells got either interrupted, or she had no line of sight to the target, and the foes managed the sleep saves
Our mage staid out of melee at all costs,and the kobolds were much to preoccupied to shoot at him!
Plus the mage's use of his cat familiar coupled with comprehend languages (sneaking in to scout) gave the group a massive initial advantage against the kobolds.
And against the ogre - ray of frost is, to put it mildy, overpowered against a single opponent! Especially coupled with a lack of AoOs.
The rogue took full advantage of his lurker theme - and rolled 2d20 to hit more often than not - he rarely missed. And when he hit, since he often had advantage (and therefore did an additional d6) he was doing damage almost comparable to the fighter (with the added advantage of being out of melee!)
The dwarven cleric did suffer from horrible die rolls, but his use of defender (from the guardian feature) was so prominently useful that his presence was far from a failure!
Rounds are 6 seconds, a battle trained fighter should be able to go much longer than it matters (realistically he'll either get mobbed and pinned or his hit points will expire long before he gets tired).
Again, the fighter has a pretty limited schtick, limiting it further is something I don't want to see.
Lwaxy
Cute but dangerous
Our wiz is still at 1st level, so no familiar. Not that we like the way the familiar is set up, we need familiars to be normal animals, not something that emulates an eidolon. So we might not use it as written. If we ever get to 2nd level, we seem to have missed out on lots of XP potential. GM said he'll level us up sooner probably.
Oh yeah, our wiz tried to sneak into the hobgoblin cave to see what they were up to but there was this heap of trash she fell over and caused a ruckus
Yeah the ray of frost would have been a killer but our wiz was stuck in the underbush vines... But the ogre died anyway, after almost stomping the rogue.
You are right with the round duration though, kinda miscalculated that. I loved the way the fighter plays out, really. I don't often enjoy playing fighters.
Oh yeah, our wiz tried to sneak into the hobgoblin cave to see what they were up to but there was this heap of trash she fell over and caused a ruckus
Yeah the ray of frost would have been a killer but our wiz was stuck in the underbush vines... But the ogre died anyway, after almost stomping the rogue.
You are right with the round duration though, kinda miscalculated that. I loved the way the fighter plays out, really. I don't often enjoy playing fighters.
My group was 1st level too, and I totally missed that !?!
I trusted the players to play their characters correctly (they're all quite experienced). And it seems the player of the mage gave himself a familiar at 1st level!
I thought it seemed a bit too much, but we were moving things along quickly and it didn't even register at the time.
It only mattered in 2 instances - but still.
Similar Threads
D&D 3E/3.5
Homebrew Content
