Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="SBMC" data-source="post: 2433203" data-attributes="member: 30040">I have been playing martial characters my whole career as a gamer. What I can tell ya is this: If Power Attack is "to powerful" in your game then I would say that what you are facing is far to weak. Sure maybe your EL's look fine - but I can get an EL 20 and still have a target with a 10 AC - making it perfect for Power Attack use.  As far as combat goes - a fighter should be able to outmaneuver a foe (using the right feats at the right time), and a Barbarian should be able to dish out more damage than most others - that is what a Barbarian is = a damage machine. If someone is a rouge/fighter you should not complain about not being as good at combat as a pure fighter or barbarian; you picked an additional class that isn't!  If the party all starts taking up two handed weapons and taking the Power Attack feat then I would say they are all dead - keep in mind using a two handed weapon means you don't have the use of a shield or buckler of any kind. It also means your going to have to get in close and get dirty - something that d8's and below are not optimized with when wielding two handed weapons (or at all fo that matter!). Rangers are an exception but they, by necessity, also TEND TO have higher Dex AND Str scores versus rouges, for example, that focus on Dex and Int. A ranger is still not optimized using Power Attack by an means; if your using TWF then Power Attack negates the benefit of the additional attacks in most cases. If he has archery what is he doing standing there with a greatsword?  Power Attack is not meant to be a "bonus" per se like Weapon Focus and Weapon Specialization but a trade off. It only becomes a "bonus" in specific circumstances (like the vast majority of feats). It is a Maneuver (noting fighters per the PHB are experts at maneuver's; not damage or BAB or anything else)  The BAB penalty can be explained in various ways in "reality". However as a game mechanic I would think that this is done (BAB versus Damage) as an equal trade off in melee. Mechanically using Power Attack you have less of a chance of hitting but when ya do you do more damage. That same logic is, in part, what drives the Barbarian class. He can rage but when he does he gives up certain things - and he gets the Rage instead of piles of feats.  Your idea messes up the whole mechanic here you see - when you reduce AC you are taking the mechanic elsewhere. Using Combat expertise - your ability to hit is reduced at the same time your AC increases (equal tradeoff - you can hit them less; they can hit you less; same mechanic at work). Your idea gives you an internal increase in damage and a decrease entirely dependant on the outside.   Regarding Attacking - BAB is related to AC (overcome AC or not). BAB is related to Damage (Overcome AC and do Damage)- Damage is NOT RELATED to AC (Once AC is overcome by BAB damage is independent of that). Look at class builds and feats; note how this seems to hold true (at least IMO)  In the case of the "Shock Trooper" feat from Complete Warrior - the Heedless Charge maneuver - it is VERY situational: useable in a charge. This is the balance; it can only be used in certain circumstances but the mechanic above still plays out.   Anything that changes BAB, AC or Damage in combat needs to be carefully scrutinized. And don't look at the PC's first; look at what you are facing first. If the party constantly fights 20th level Hobgoblin fighters dressed in loincloths; well Power Attack will work pretty well here regardless of those Hobgoblins' BAB. The EL may look great…but is it really? You can max your Power Attack every attack and hit with every attack. Fighting say a 10th level Hobgoblin Fighter in +2 Breastplate would actually be harder! P.S. I think Oversized TWF is the most unbalanced feat out there and do not allow it in my game! Same with Monkey Grip (the Munchkins favorite feat I would think)</blockquote>

Verification