Just having bonuses, not managing them.I thought fighting styles in 5e were all about minor bonus management
Cool! I hadn't given half a thought to balance...Tony, I'm going to try a balance pass on your stuff.
Not really balance, and, you-grant-it has it's downsides, too.White Raven
Why: makes it your decision (you grant it).
Striking Viper
5e has opportunity attacks, so I figured it should otherwise conform to them.This makes the triggered attack not an opportunity attack (ie, it won't trigger sentinal), and simplifies wording.
Hammer & Anvil
Yeah, I was concerned about it being 'free,' too.I added in reaction costs here as well.
Bravura Spirit
I'd rather find some other way to ramp it down that going to reactions again. The idea is that your recklessness leaves you open, but taking advantage of it leaves the enemy open, so you're not reacting...I ramped this down from "every" in both cases. Now you get 2 ways to burn your reaction to grant single attacks. Still strong (reliably turning reactions into attacks is great), but not crazy strong.
Part of the problem is that there's too much use for reactions, already, they're a very limited resource compared to OAs in 4e or AoOs in 5e. I actually considered making one style grant you extra reactions for specific purposes, corresponding to Extra Attack, but I figured I'd leave that a separate issue...The theme I'm following is "it costs your reaction". This helps keep these from stacking insanely and making a Fighter 1/Ranger 2/Paladin 2 build into a super-strong one.
Well, it reduces mental load on allies and moves it to the Warlord. You say "hey, have a toy".Cool! I hadn't given half a thought to balance...
Not really balance, and, you-grant-it has it's downsides, too.
There are already powerful riders on opportunity attacks, like Sentinal. Granting an opportunity attack is more powerful than granting an attack.5e has opportunity attacks, so I figured it should otherwise conform to them.
By placing a constant reaction cost on the Warlord, I am trying to prevent these all from going off on a given turn if you stack them.I'd rather find some other way to ramp it down that going to reactions again. The idea is that your recklessness leaves you open, but taking advantage of it leaves the enemy open, so you're not reacting...
Breaking the action economy is very powerful in 5e.Part of the problem is that there's too much use for reactions, already, they're a very limited resource compared to OAs in 4e or AoOs in 5e. I actually considered making one style grant you extra reactions for specific purposes, corresponding to Extra Attack, but I figured I'd leave that a separate issue...
Not a Warlord, just a combat style.Well, it reduces mental load on allies and moves it to the Warlord. You say "hey, have a toy".
Cool.There are already powerful riders on opportunity attacks, like Sentinal. Granting an opportunity attack is more powerful than granting an attack.
Well, it does have to be adjacent to both you, but, the idea was that if it left only one of your zones, only that one would get the OA.Striking Viper in this model, you burn 1 reaction to grant two attacks, and do so even if they disengage (or even teleport!), and if they leave your allies zone (not only yours).
Nice. That was actually a synergy of the 4e Viper's Strike at-will when used with a Fighter ally.It doesn't, however, also trigger Sentinal on you or your ally, which could completely shut down an enemies ability to flee.
The possibilities of stacking Combat Styles are pretty limited. You'd need a Champion or a muti-fighter/paladin/ranger party for that, and compared to a multi-full-caster party layering concentration buffs, how bad could it be, really?By placing a constant reaction cost, I am trying to prevent these all from going off on a given turn if you stack them.
Another concern I had, and I've no real idea how to address it is that for most melee-oriented characters, a single attack doesn't really scale. It'll be quite good at low level, and, as Extra Attack provides more and more of the melee-types' DPR, it'll fall off.I'm trying to grant 1 melee weapon attack from the reaction (from someone), and have it be a more common trigger than usual, and some other bonus.
Seems like a feat issue, more than a reaction issue.And getting more reactions could be crazy strong. It multiplies with PAM and Sentinal, which in turn multiplies with tap +damage or warcaster.
The feats are out there and widely played. Fixing things so we don't multiply together just requires replacing "opportunity attack" with "as a reaction make a melee weapon attack".Seems like a feat issue, more than a reaction issue.
L 1 Fighter/L5 Paladin/L2 Ranger has 3 combat styles. A triple-classed spellcaster doesn't have 3 concentration slots.The possibilities of stacking Combat Styles are pretty limited. You'd need a Champion or a muti-fighter/paladin/ranger party for that, and compared to a multi-full-caster party layering concentration buffs, how bad could it be, really?
Scaling for a class with Extra Attack comes primarily from Extra Attack.So if I want the reaction damage to scale faster for balance reasons, instead of saying "you get a full attack routine" or whatever I'd make it deal more damage at higher levels.
For a low-level character who gets one attack, that's doubling his DPR, for a high-level one getting 4 attacks, it's +25%. I see a potential issue with that, but it's that it's dropping off in impact as you level.I mean, "every turn you can spend a reaction to get an attack" is already a ridiculously strong combat style compared to the existing ones.
Yeah it annoys me for some reason. Anti-heroic? For a fighter almost incongruous it seems this character can attack 4 bloody times moving in the middle between each even do an action surge to double down on the attacks, but he can react ummmm once...Part of the problem is that there's too much use for reactions, already, they're a very limited resource compared to OAs in 4e or AoOs in 5e. I actually considered making one style grant you extra reactions for specific purposes, corresponding to Extra Attack, but I figured I'd leave that a separate issue...