Reply to thread

Message

<blockquote data-quote="Merlin the Tuna" data-source="post: 3931146" data-attributes="member: 55638">Something that bears mentioning regarding DR slowing down the game...DR is just a simple check and a single subtraction operation.&nbsp; In a computer, this step would be completely negligible.&nbsp; &quot;Attack --&gt; Hit --&gt; Damage --&gt; DR.&quot;&nbsp; Not a big deal.&nbsp; In my experience though, that isn't what happens at the table.&nbsp; The DM rarely says &quot;He hits you with his claw for 8 damage, his other claw for 4 more damage, his bite for 13 damage, and his tail for 2 damage.&quot;&nbsp; &nbsp; Rather, it tends to be &quot;He [blah blah description].&nbsp; You take 27 damage.&quot;&nbsp; At that point, the player needs to cut in to ask the DM how many attacks that was and the damage of each one.&nbsp; (You can't just multiply the DR by 4, because in the case of DR 3/-, doing so would actually heal the tail's damage.)&nbsp; The DM, whose mind has already started to move on to the next task, then needs to jump back, figure out whether he's moved his dice yet, and relay it back to the player, who can THEN do the simple calculation.And even in situations that don't involve multiple attacks, the player is always going to ask &quot;Did you factor in my damage reduction yet?&quot; because the DM will remember it some times and forget it other times.&nbsp; Again, if all of this were being done in the same context (such as a computer processor), there'd be nothing to take care of here.&nbsp; A single DR sequence might only take 10 seconds even with all of these problems at their worst, but making an attack roll isn't a huge time-waster either, and we still make sure that players take care of that before their turns, too.</blockquote>

[QUOTE="Merlin the Tuna, post: 3931146, member: 55638"] Something that bears mentioning regarding DR slowing down the game... DR is just a simple check and a single subtraction operation. In a computer, this step would be completely negligible. "Attack --> Hit --> Damage --> DR." Not a big deal. In my experience though, that isn't what happens at the table. The DM rarely says "He hits you with his claw for 8 damage, his other claw for 4 more damage, his bite for 13 damage, and his tail for 2 damage." Rather, it tends to be "He [blah blah description]. You take 27 damage." At that point, the player needs to cut in to ask the DM how many attacks that was and the damage of each one. (You can't just multiply the DR by 4, because in the case of DR 3/-, doing so would actually heal the tail's damage.) The DM, whose mind has already started to move on to the next task, then needs to jump back, figure out whether he's moved his dice yet, and relay it back to the player, who can THEN do the simple calculation. And even in situations that don't involve multiple attacks, the player is always going to ask "Did you factor in my damage reduction yet?" because the DM will remember it some times and forget it other times. Again, if all of this were being done in the same context (such as a computer processor), there'd be nothing to take care of here. A single DR sequence might only take 10 seconds even with all of these problems at their worst, but making an attack roll isn't a huge time-waster either, and we still make sure that players take care of that before their turns, too. [/QUOTE]

Verification