I have a paladin with Smite Level 4 and a Sorceress with Counterspell and Shield and a Rogue with Uncanny Dodge. Yes. It can get a little heavy on the prompts, but I still don't think it's that bad. Still, that's why I was considering the preset method and trying to maybe figure out a solution to make it work.
Some thought I was exaggerating about the prompt frequency, but some battles it is a bit much. That's again why I thought at least some sort of presets would at least cut down the frequency.
I remember one battle in particular. Sorak triggers AOO. Yes? With Smite? Sorak hits rogue. Uncanny Dodge? Yes. Another Sorak triggers AOO. Yes? With Smite? Sorak casts spell. Counterspell? No. Not wasting it on enemy's level 1 spell. Other Sorak casts spell. Counterspell? No. Another baby spell. I'd rather cast Fireball on my turn.
Even still. It wasn't that bad, and it wasn't like that happened every battle.
Which is why things that aren't reactions (e.g., Smite) and/or that would prompt on every single roll (e.g., Cutting Words) should probably not be prompts, because these
would result in an overabundances of prompts.
- Cutting words in BG3 is imo a great solution to this type of ability - modified to be a weaker pre-cast but with a broader area & longer time of effect.
- Smite should be a toggle that automatically adds the (player-chosen) slot level to your Paladin's
successful attacks. You'd still get prompted for AoOs, and would possibly be able to toggle Smite off while reacting to that attack, so you'd always have perfect control over when and how hard you Smite. You'd only lose on the ability to crit-fish Smites, which...too bad.
