Poll: Should Smite spells become interrupt-only (like Shield/Counterspell)? #938
Replies: 3 comments 9 replies
|
I already voted but could you provide a bit more info on this? If the purpose of converting all the smites into interrupts is just for ease-of-use for the player, then I actually don't mind this. |
|
The RAW wording of 2024 makes them triggers on hit with no need to cast and concentrate like 2014. As long as the code only consumes the bonus action and spell slot it would be closer to RAW. |
|
i voted no because the existing build allows for a prompt asking if we want to divine smite on critical hit and implementation can no longer distinguish between critical vs non-critical. I can't see a situation where i would want to use a "utility" smite (wraithful, thunderous etc) on criical hit because the damage is lower than divine smite. If i want the utility, i would want it regardless if it would crit so i would manually cast it even if it fails to crit. Having to deal with a prompt asking if i want to smite on every non-crit hit would be very annoying in combat (which is the result we would get if i understand correctly) Part of the reason i save smite only for crit is because the spell slots are limited and i avoid resting too regularly. But i understand some players may enjoy to burn every slot and rest since bg3 allows so this is not a limitation they face. If i understand the original request, it is to benefit a specific multiclass to use blade cantrip with utility smite - which, if multiclass were done RAW (which bg3 doesnt check if a multiclass meets minimum requirements), it probably only really benefit the valor bard or heroic sorc multiclass (cha casters with war magic) unless they were planning a non RAW multiclass or really niche build that i cant really think of. As such, when i weigh up that
my vote is currently no ***edits for clarity & typos |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Following up on #827 (Smite spells as an interrupt).
Divine Smite and Eldritch Smite already work as interrupts — they're granted through a passive that makes them Always Prepared, so there's no "is this currently known/prepared" state to track.
The other Smite spells (Wrathful, Searing, Staggering, Blinding, Thunderous, Branding, Ballistic, etc.) are regular prepared spells, so whether a character has one in their spellbook — and whether it's currently prepared — varies per character and changes between rests. Dynamically wiring an interrupt to match that state for each of them gets complicated fast.
An alternative is converting those Smite spells to work only as an on-hit interrupt, similar to how Shield or Counterspell function, instead of being cast directly as an active spell. That's feasible, but it comes with a tradeoff: since each prepared spell maps to exactly one interrupt, there's no way to branch behavior on critical vs. non-critical hits the way the active-spell version currently can.
Vote below on which direction you'd prefer.
13 votes ·
All reactions