NOW LIVE! Today's the day you meet your new best friend. You don’t have to leave Wolfy behind... In 'Pets & Sidekicks' your companions level up with you!

Reply to thread

Message: <blockquote data-quote="Maxperson" data-source="post: 9190075" data-attributes="member: 23751">If I have to explain that to you...  I mean, at this point you are literally arguing that you can only be forced to take a death save once ever if you get hit while at a 0, because it doesn't say, "Each time you take damage while at 0 hit points you suffer a death save failure." <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f644.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":rolleyes:" title="Roll eyes    :rolleyes:"  data-smilie="11"data-shortname=":rolleyes:" /> I can absolutely determine an order.  I am the DM and fully capable of making a ruling to cover a hole in the rules.No. There will pretty much always be time in-between simultaneous events here in the real world, because there will be .000000000000001 second or something in-between.  We use simultaneous, because we either cannot determine the time or because it's so close as to not matter. People will describe a bunch of things happening with very small, but often discernable amounts of time in-between as simultaneous, because the very small amount of time just doesn't matter.I mean, how often have you seen in a war/action movie the protagonists or antagonists plotting simultaneous attacks in different locations?  How many of those do you think happen with 0 time in-between?Which isn't the same as all at once, as I showed with my examples. It also doesn't mean with 0 time in-between, as I also showed above.  It just means close enough together to be considered "at the same time."It isn't applied at the same time. It's applied 1d4+1 at a time until all d4s have been rolled.  If the player wants to total the damage and deduct it all at once, that's okay, but that doesn't mean that it's applied all at once.If they don't count as a single hit, then they are discreet instances of damage even if they are simultaneous. That triggers the death save with each discreet instance of damage.We get that. We aren't stupid and you've been quite clear about that. The problem is that you are conflating "all at once" with "simultaneous" and "simultaneous" with "0 time at all in-between events."  Neither of those mean the other.I'm still not sure how I will play it.  It has not yet come up in my game for us to even think about, but I'm certain that all 4 of my players will agree with everyone here(excepting you) and agree that it should as written cause multiple death save failures.I mean, there's literally no difference.  If as written it causes 3 death save failures for 3 missiles, then it does the same when you are not at 0, but can be bought to 0 with few missiles than hit you.  This again is a hole in the rules and needs a DM ruling to figure out how to determine which missiles hit first.  And again, simultaneous =/= here in the real world mean 0 amount of time has occurred in-between instances. So it doesn't mean that in the game, either.</blockquote>

Verification