Reply to thread

Message

<blockquote data-quote="CleverNickName" data-source="post: 8761504" data-attributes="member: 50987">Maybe we're doing it wrong, but at my table, &quot;Immune to an effect or damage type&quot; is not the same thing as &quot;don't roll a save throw.&quot;&nbsp; First we resolve the effect, then we apply resistance or immunity.Mage casts fireball on the red dragon and her tiefling cultists.All targets roll their Dexterity save throws.Player rolls the damage spell damage.Targets that made the save take half damage.Resistance reduces that damage further.Immunity reduces that damage to zero.Why do we bother rolling for the red dragon?&nbsp; Well, there are a number of reasons at my table, but I'll give you the top three.&nbsp; The biggest reason is because certain spells and abilities might have other effects that trigger on a failed save throw, we fell into the habit of always rolling.&nbsp; (shrug)Another reason:&nbsp; rolling the dice is a more satisfying action resolution than just a deadpan announcement from the DM.&nbsp; It's just more fun, and things flow better...until the save throw is rolled, the spellcasting action feels unfinished or incomplete.&nbsp; It also helps keep the players from asking &quot;but what about the dragon?&quot; for the rest of the scene.A third reason: most VTT macros are configured to automatically roll saves on the target(s) selected, and it would be more work to disable that feature for certain tokens and actors.&nbsp; The save throw is right there in the chat window, and the players can see that the fire damage was reduced to zero.&nbsp; Click, click, done.There are other reasons too, but these are the biggest ones at my table.</blockquote>

[QUOTE="CleverNickName, post: 8761504, member: 50987"] Maybe we're doing it wrong, but at my table, "Immune to an effect or damage type" is not the same thing as "don't roll a save throw." First we resolve the effect, then we apply resistance or immunity. Mage casts [I]fireball[/I] on the red dragon and her tiefling cultists. All targets roll their Dexterity save throws. Player rolls the damage spell damage. Targets that made the save take half damage. Resistance reduces that damage further. Immunity reduces that damage to zero. Why do we bother rolling for the red dragon? Well, there are a number of reasons at my table, but I'll give you the top three. The biggest reason is because certain spells and abilities might have other effects that trigger on a failed save throw, we fell into the habit of always rolling. (shrug) Another reason: rolling the dice is a more satisfying action resolution than just a deadpan announcement from the DM. It's just more fun, and things flow better...until the save throw is rolled, the spellcasting action feels unfinished or incomplete. It also helps keep the players from asking "but what about the dragon?" for the rest of the scene. A third reason: most VTT macros are configured to automatically roll saves on the target(s) selected, and it would be more work to disable that feature for certain tokens and actors. The save throw is right there in the chat window, and the players can see that the fire damage was reduced to zero. Click, click, done. There are other reasons too, but these are the biggest ones at my table. [/QUOTE]

Verification