• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

D&D 5E Assassinate

Right, but that's also the maximum range of the weapon, and no other weapon can shoot that far, at least none on the weapons list. For the sake of simplicity, I like to assume that, within that range, noises are generally audible.



I agree that the audibility of noise is entirely left to the subjective discretion of the individual DM. It would have been nice, however, to have some general guidelines as to range of hearing included in the rules, along the lines of what was provided in the DMG for range of vision. I don't see any reason not to have done so. There are a number of factors involved that might have dissuaded the designers from doing so, namely the ability of the environment to absorb or dampen sound, and the speed and direction of wind. I like to put all that down to the die roll, however, and would have liked a simplified list of common sources of sound and distances over which they can be heard in typical adventuring environments. I can only assume they didn't do this because of the complications that would arise when people started asking things like, "What if the sound is twice as quiet, but can still be heard?" or, "What about intervening noise?" They obviously didn't want to produce a long list of modifiers to apply to any Stealth roll. That's what advantage/disadvantage is for anyway.

As it is, I've compiled a list of four sound levels: quiet whisper, whisper, normal conversation, and loud singing, just what I've been able to find decibel measurements of on the internet. I've then applied a sound level drop of 6dB per doubling of distance. I'm not an expert in acoustics, however, so I'm not sure if I've done the calculations correctly. What it tells me, however, is that a whisper approaches becoming inaudible at about 6', normal conversation at about 100', and loud singing at about 600' or more. The sound of combat I would generally expect to be louder than any of these, but keep in mind these figures would apply only under ideal conditions. If anyone has more accurate numbers, I would love to hear about them.
You're conceptually off there. Sound drops by the square of the distance, not doubling of the distance. While the dB scale is logarithmic and so takes that into account (again, roughly), by applying the drop over doubled instead of fixed distances you're negation much of the purpose of using the db scale. I'd halve the distances you have calculated and that should be a decent ballpark.

Generally, if you get the result that you can hear someone singing loudly without amplification clearly from two football fields away, you've done something wrong. On a dead calm day with the wind in the right direction and no other sounds, you could probably hear something, but not tell what it was.
 

log in or register to remove this ad

OK, so the player of my bard assassin asked my a question over the weekend that made me think of this thread. If he had an illusion up to look like an NPC (in this case a lover of the local warlord) and got passed the guards, and got into the warlord's keep and to her, would any attack be a assassinate... it would be a surprise, since she would think him her lover.

Now I jumped to yes without really thinking about it, but then he added "can I make multi attacks?"

now this at first was an "Ok, you have the surprise," but I realized an effort of magic item combos could give him a lot of attacks... I wondered what you guys would say...


In the game world Chanla the warlord is a big problem, she is the off spring of a Aasimar (child of a celestial and an elf) and a tanarukk (offspring of a demon and an orc) and she is prophesied to end the world. Because she has a large army and controls the whole city state, no one has even tried to fight her yet...
 

Yes, if he gets next to her undetected, he should get his crit(s). If you don't want her to die yet, run the numbers on his maximum damage and make sure she has more hit points than that, or position an acolyte nearby with Healing Word and Spare the Dying. If you're ok with her being killed, then the adventure becomes the challenge of getting the assassin out of the keep after the warlord gets shanked.
 

OK, so the player of my bard assassin asked my a question over the weekend that made me think of this thread. If he had an illusion up to look like an NPC (in this case a lover of the local warlord) and got passed the guards, and got into the warlord's keep and to her, would any attack be a assassinate... it would be a surprise, since she would think him her lover.

Now I jumped to yes without really thinking about it, but then he added "can I make multi attacks?"

now this at first was an "Ok, you have the surprise," but I realized an effort of magic item combos could give him a lot of attacks... I wondered what you guys would say...


In the game world Chanla the warlord is a big problem, she is the off spring of a Aasimar (child of a celestial and an elf) and a tanarukk (offspring of a demon and an orc) and she is prophesied to end the world. Because she has a large army and controls the whole city state, no one has even tried to fight her yet...

By RAW no. There is no stealth, without stealth there can not be surprise.

The DM determines who might be surprised. If neither side tries to be stealthy, they automatically notice each other. Otherwise, the DM compares the Dexterity (Stealth) checks of anyone hiding with the passive Wisdom (Perception) score of each creature on the opposing side. Any character or monster that doesn’t notice a threat is surprised at the start of the encounter.

I allow my players to make Charisma (deception) vs Wisdom (insight) is such face to face, surprising like situations though.

If they do get surprise, both roll initiative, you can apply advantage/disadvantage as you see fit to these checks.

If the warlord wins initiative then by the time the assassin has their turn they don't benefit from their class ability. Unless something is giving them advantage they won't even be able to sneak attack.

Also remember even if the assassin wins initiative and can use their ability only one of the attacks if they have multiple attacks can benefit from sneak attack, any that would hit of course are still critical hits.
 

So that would be a "no" to my question, which leaves me feeling a bit confused since you just said that surprise is not limited to the start of combat, but can actually apply throughout combat. Now you seem to be saying that if you are "in combat", you can't be surprised at all.

There's a couple of things here. First, imagine that the combat has been raging for several rounds when you suddenly burst into a room whose inhabitants knew nothing about any combat. They could be surprised, because even though it is not the first turn of combat, it is their first turn of combat, therefore the effects of surprise for those guys is that they can't move or take an action on their first turn, and are vulnerable to auto-crits from Assassinate until they notice a threat (which should be fairly soon if the warriors burst in but may be a while if they snuck in).

Second, 'surprised' has TWO effects:-

* you are vulnerable to auto-crits from Assassinate all the while that you don't notice a threat, and are not vulnerable to auto-crits all the while that you do notice a threat. If you start combat surprised then you become 'un-surprised' when you notice a threat, but as soon as you notice a threat (whether at the start of combat or later) then you can't become surprised while that combat rages, i.e. while in combat time/initiative order

* you may not move or take actions on YOUR first turn of this combat (whether or not your first turn is the first turn) and cannot take reactions until your first turn is over. Note that once your 'surprise' has mandated that you can't act etc. on your first turn, this remains the case whether or not you notice a threat before your first turn. If you start combat 'surprised', then notice a threat (because the attacker/assassin runs into the open) before your first turn, you still can't do anything on your first turn even though you are no longer surprised!


I wouldn't look to the text of Assassinate to define the effect of surprise. It only tells you what effect a successful attempt to Assassinate has on someone who is surprised.

Er...yeah, exactly! Assassinate doesn't define surprise, but it only works on someone who is surprised at the moment the attack hits. Therefore, one of the effects of 'surprise' it that you are vulnerable to Assassinate.

You defined "in combat" above as having noticed, or believing there is, a threat. I agree that having done so makes it so you cannot be surprised. It does not follow, however, that once you are surprised, noticing a threat will make you unsurprised. This would in fact contradict the rule that says that if you are surprised you can't take actions or move until your first turn is over, because if you start the encounter surprised, then notice a threat before the end of your turn, becoming thus unsurprised by your reading, you would suddenly be able to take actions and move on your turn. What then did it mean to have been surprised?

As explained above, if you were surprised at the start of your first round of this combat, then you suffer the 'cannot act' penalty on your first turn, and that penalty has already been caused at that point. That 'cannot act' penalty doesn't go away if you notice a threat in the meantime; no rule says that! But you are only vulnerable to auto-crits if you are surprised (i.e. haven't noticed a threat) at the moment that attack hits you. Why? Because no rule says that 'being able to react' = 'no longer surprised', but 'surprised' does mean that the hit auto-crits if the attacker has the Assassinate ability.

Do you see how this is circular? "You are surprised for as long as you are surprised."

Yes, I'm stating the obvious. That doesn't make it untrue.

Who is vulnerable to the assassin's auto-crits? Anyone who is surprised, right? But how do we know they are still currently surprised? Surely once having been unaware of their opponents doesn't make creatures permanently surprised. I know you aren't saying that. When the assassin strikes, however, the cause of surprise is most certainly in the past because surprise was determined at the beginning of the encounter

No. Just because surprise was determined at the start doesn't mean it isn't true later also.

'Haven't noticed a threat' = 'surprised. Therefore, if you have noticed a threat then then the condition for 'surprised' has not been met. Since the default condition of creatures is 'not surprised' then there is no excuse for applying those penalties.
 


OK, so the player of my bard assassin asked my a question over the weekend that made me think of this thread. If he had an illusion up to look like an NPC (in this case a lover of the local warlord) and got passed the guards, and got into the warlord's keep and to her, would any attack be a assassinate... it would be a surprise, since she would think him her lover.

Now I jumped to yes without really thinking about it, but then he added "can I make multi attacks?"

now this at first was an "Ok, you have the surprise," but I realized an effort of magic item combos could give him a lot of attacks... I wondered what you guys would say....

The DM determines surprise. How he determines surprise is entirely up to him. He can just rule, by fiat, that a creature is surprised in these circumstances.

However, the DM usually uses opposed rolls (or a roll versus a score) to determine surprise. The nature of adventuring usually means that as soon as you see a creature you assume you are enemies and attack, therefore if you see him before he sees you, you could surprise him. This is modelled by an opposed Stealth/Perception check.

But that is not always the case. Just because you see another living creature doesn't mean you'll each try to kill the other. Going shopping would be a nightmare!

In a situation where the presence of a creature is obvious but their hostile intent is not, then Stealth/Perception doesn't do the job. In such a case, Deception/Insight is the answer. Can you detect, through body language or whatever, that the person you think of as a friend/lover is about to attack you? The better your Insight, the better your chance to realise their hostile intent. The better their Deception, the better they fool you.

'Surprised' = 'not noticed a threat'. In this case, seeing your 'lover' doesn't mean you recognise a threat, therefore a sudden attack from 'her' may well be a threat you didn't notice and may well cause you to be 'surprised'.

That being said, the moment your 'lover' stabs you in the guts, you absolutely do notice a threat! You still reacted slowly, so you still don't get to act on your turn, but after that first attack hits you, subsequent attacks do not auto-crit. Unless the DM rules that you somehow didn't notice the 80 points of damage and the dagger in your gut!
 

isn't using an illusion a type of stealth?

Of course it is. Some people seem to have a problem with the idea that "stealth" can apply to more than simply a dexterity (Stealth) check opposed by a passive wisdom (Perception) score. You can sometimes spot them by their references to "RAW."
 



Into the Woods

Remove ads

Top