Can an Arcane Archer fighter use a Banishing Arrow to effectively get two surprise rounds?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
8
down vote

favorite












The Arcane Archer fighter (Xanathar's Guide to Everything, p. 28-30) gets a number of Arcane Shot options, allowing them to unleash special magical effects when they fire a longbow/shortbow. One of their Arcane Shot options is Banishing Arrow:




You use abjuration magic to try to temporarily banish your target to a harmless location in the Feywild. The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. While banished in this way, the target’s speed is 0, and it is incapacitated. At the end of its next turn, the target reappears in the space it vacated or in the nearest unoccupied space if that space is occupied.




If a creature gets banished in a group of enemies and no one sees the creature get banished, do the other creatures notice he is gone and are still surprised if you decide to attack them next round?



(Obviously before the creature comes back at the end of its next turn... although THAT might get tricky depending on initiative rolls and when the DM states "it's now this guy's next turn", but for the sake of simplicity, we'll say that because you don't act on a surprise round he doesn't get the first turn when he's hit.)



As far as I can tell this is really a matter of timing. If you hit a creature and it's able to do ANYTHING (even saying 'ow') before being banished, then it's obvious that this is your surprise round and you don't get to grab another one... On the other hand, if the creature is banished THEN gets to say 'ow', well, no one can hear him; and if no one saw him go "poof", then you're likely to be able to just get another round out next turn with people still not knowing you're there.










share|improve this question





























    up vote
    8
    down vote

    favorite












    The Arcane Archer fighter (Xanathar's Guide to Everything, p. 28-30) gets a number of Arcane Shot options, allowing them to unleash special magical effects when they fire a longbow/shortbow. One of their Arcane Shot options is Banishing Arrow:




    You use abjuration magic to try to temporarily banish your target to a harmless location in the Feywild. The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. While banished in this way, the target’s speed is 0, and it is incapacitated. At the end of its next turn, the target reappears in the space it vacated or in the nearest unoccupied space if that space is occupied.




    If a creature gets banished in a group of enemies and no one sees the creature get banished, do the other creatures notice he is gone and are still surprised if you decide to attack them next round?



    (Obviously before the creature comes back at the end of its next turn... although THAT might get tricky depending on initiative rolls and when the DM states "it's now this guy's next turn", but for the sake of simplicity, we'll say that because you don't act on a surprise round he doesn't get the first turn when he's hit.)



    As far as I can tell this is really a matter of timing. If you hit a creature and it's able to do ANYTHING (even saying 'ow') before being banished, then it's obvious that this is your surprise round and you don't get to grab another one... On the other hand, if the creature is banished THEN gets to say 'ow', well, no one can hear him; and if no one saw him go "poof", then you're likely to be able to just get another round out next turn with people still not knowing you're there.










    share|improve this question

























      up vote
      8
      down vote

      favorite









      up vote
      8
      down vote

      favorite











      The Arcane Archer fighter (Xanathar's Guide to Everything, p. 28-30) gets a number of Arcane Shot options, allowing them to unleash special magical effects when they fire a longbow/shortbow. One of their Arcane Shot options is Banishing Arrow:




      You use abjuration magic to try to temporarily banish your target to a harmless location in the Feywild. The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. While banished in this way, the target’s speed is 0, and it is incapacitated. At the end of its next turn, the target reappears in the space it vacated or in the nearest unoccupied space if that space is occupied.




      If a creature gets banished in a group of enemies and no one sees the creature get banished, do the other creatures notice he is gone and are still surprised if you decide to attack them next round?



      (Obviously before the creature comes back at the end of its next turn... although THAT might get tricky depending on initiative rolls and when the DM states "it's now this guy's next turn", but for the sake of simplicity, we'll say that because you don't act on a surprise round he doesn't get the first turn when he's hit.)



      As far as I can tell this is really a matter of timing. If you hit a creature and it's able to do ANYTHING (even saying 'ow') before being banished, then it's obvious that this is your surprise round and you don't get to grab another one... On the other hand, if the creature is banished THEN gets to say 'ow', well, no one can hear him; and if no one saw him go "poof", then you're likely to be able to just get another round out next turn with people still not knowing you're there.










      share|improve this question















      The Arcane Archer fighter (Xanathar's Guide to Everything, p. 28-30) gets a number of Arcane Shot options, allowing them to unleash special magical effects when they fire a longbow/shortbow. One of their Arcane Shot options is Banishing Arrow:




      You use abjuration magic to try to temporarily banish your target to a harmless location in the Feywild. The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. While banished in this way, the target’s speed is 0, and it is incapacitated. At the end of its next turn, the target reappears in the space it vacated or in the nearest unoccupied space if that space is occupied.




      If a creature gets banished in a group of enemies and no one sees the creature get banished, do the other creatures notice he is gone and are still surprised if you decide to attack them next round?



      (Obviously before the creature comes back at the end of its next turn... although THAT might get tricky depending on initiative rolls and when the DM states "it's now this guy's next turn", but for the sake of simplicity, we'll say that because you don't act on a surprise round he doesn't get the first turn when he's hit.)



      As far as I can tell this is really a matter of timing. If you hit a creature and it's able to do ANYTHING (even saying 'ow') before being banished, then it's obvious that this is your surprise round and you don't get to grab another one... On the other hand, if the creature is banished THEN gets to say 'ow', well, no one can hear him; and if no one saw him go "poof", then you're likely to be able to just get another round out next turn with people still not knowing you're there.







      dnd-5e class-feature fighter stealth surprise






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 10 at 22:01









      V2Blast

      15.5k235101




      15.5k235101










      asked Sep 10 at 15:00









      Pacattack

      1487




      1487




















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          21
          down vote



          accepted










          Your Attack Reveals You



          I am not sure whether a creature getting banished makes any noise. It's possible that the creature disappears without any sound, or that it vanishes in a flash of light screaming. Either way, that isn't what will give you away: it's the attack you needed to make to banish the creature.



          Banishing Arrow states that:




          The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. (XGtE, p. 29)




          Since you need to hit a creature to banish it, you needed to make an attack. However, the rules on unseen attackers and targets state that:




          If you are hidden—both unseen and unheard—when you make an attack, you give away your location when the attack hits or misses. (PHB, p. 195)




          Note that it doesn't say you give away your location only to the target of the attack. When you attack while Hidden, you lose your Hidden status. Naturally, you wouldn't become visible to someone miles away, but basically anyone who could have been alerted by an "ow" from your initial target has already been alerted by your attack. (You can't even get around this with the Skulker Feat, because your attack needs to have hit).






          share|improve this answer






















          • You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
            – Loren Pechtel
            Sep 11 at 0:38






          • 3




            Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
            – Gandalfmeansme
            Sep 11 at 3:01











          • You may want to add how this interact with persistent invisibility
            – Vylix
            Sep 11 at 3:16






          • 2




            Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
            – Hennes
            Sep 11 at 4:22










          • The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
            – Pacattack
            Sep 12 at 1:49

















          up vote
          4
          down vote













          They could still be surprised, but it depends on a number of things.



          One particularly important part about Surprise is that the DM has to be the one actively deciding each time it's applied. Unlike stealth, buffs, healing, or other calculations regarding how it works, Surprise isn't necessarily as simple as "I rolled high, so now they're Surprised".



          Generally, for Surprise to work, the people in question need to believe there is no active threat. This means that they shouldn't be doing guard duty, couldn't have heard or seen someone get banished, or have any reason to believe that combat has initiated.



          Surprise is not a type of round, it's a condition that nullifies their first action in combat. If they don't know there's combat, then they're not taking combat actions, and they aren't surprised yet. Since the surprise hasn't been ruined, they could easily be surprised in later rounds, when the players do get around to spooking the enemy out of their pants.



          To make this simpler, I'd roll initiative for the entire encampment + players, but if a combatant doesn't know there's any reason for alarm, they simply do not take combat-related actions until they do or until they're Surprised. Mechanically, though, it should be treated as a
          string of short fights, which are individually considered for Surprise Rounds.




          This is separate from being "hidden" which is just one way to avoid being detected to get a Surprise Round. Another method could be to simply start attacking someone who thinks of you as an ally. Even without a stealth check, Surprise can still be obtained.






          share|improve this answer


















          • 1




            There is no such thing as a "surprise round" in 5E. This needs rewording.
            – T.J.L.
            Sep 10 at 18:08










          • @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
            – Daniel Zastoupil
            Sep 10 at 18:10






          • 1




            You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
            – Gandalfmeansme
            Sep 10 at 18:11










          • Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
            – Gandalfmeansme
            Sep 10 at 18:12










          • @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
            – Daniel Zastoupil
            Sep 10 at 18:15


















          up vote
          -1
          down vote













          I thought the way a "surprise" round worked in 5th edition was that everyone rolls initiative as normal. Everyone who is surprised misses their standard, bonus and move actions and only gets their reaction after their turn comes up. The exception being certain barbarians who can act provided they rage immediately when their turn starts.



          In any case I'd say you could take out that initial target or any number of targets without starting combat provided you can justify the remaining enemies not noticing anyone vanish. If they are all sitting around a campfire chatting and one of them suddenly vanishes there is pretty much no way they aren't going to be alerted. If one of them got up to answer the call of nature and you managed to take them out such that the others couldn't see or hear the attack then combat would not have started. The DM could still call for initiative rolls but not have the other enemies do something since they wouldn't know anything is going on.






          share|improve this answer




















          • You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
            – V2Blast
            Sep 11 at 8:28










          Your Answer




          StackExchange.ifUsing("editor", function ()
          return StackExchange.using("mathjaxEditing", function ()
          StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
          StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
          );
          );
          , "mathjax-editing");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "122"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f131460%2fcan-an-arcane-archer-fighter-use-a-banishing-arrow-to-effectively-get-two-surpri%23new-answer', 'question_page');

          );

          Post as a guest






























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          21
          down vote



          accepted










          Your Attack Reveals You



          I am not sure whether a creature getting banished makes any noise. It's possible that the creature disappears without any sound, or that it vanishes in a flash of light screaming. Either way, that isn't what will give you away: it's the attack you needed to make to banish the creature.



          Banishing Arrow states that:




          The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. (XGtE, p. 29)




          Since you need to hit a creature to banish it, you needed to make an attack. However, the rules on unseen attackers and targets state that:




          If you are hidden—both unseen and unheard—when you make an attack, you give away your location when the attack hits or misses. (PHB, p. 195)




          Note that it doesn't say you give away your location only to the target of the attack. When you attack while Hidden, you lose your Hidden status. Naturally, you wouldn't become visible to someone miles away, but basically anyone who could have been alerted by an "ow" from your initial target has already been alerted by your attack. (You can't even get around this with the Skulker Feat, because your attack needs to have hit).






          share|improve this answer






















          • You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
            – Loren Pechtel
            Sep 11 at 0:38






          • 3




            Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
            – Gandalfmeansme
            Sep 11 at 3:01











          • You may want to add how this interact with persistent invisibility
            – Vylix
            Sep 11 at 3:16






          • 2




            Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
            – Hennes
            Sep 11 at 4:22










          • The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
            – Pacattack
            Sep 12 at 1:49














          up vote
          21
          down vote



          accepted










          Your Attack Reveals You



          I am not sure whether a creature getting banished makes any noise. It's possible that the creature disappears without any sound, or that it vanishes in a flash of light screaming. Either way, that isn't what will give you away: it's the attack you needed to make to banish the creature.



          Banishing Arrow states that:




          The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. (XGtE, p. 29)




          Since you need to hit a creature to banish it, you needed to make an attack. However, the rules on unseen attackers and targets state that:




          If you are hidden—both unseen and unheard—when you make an attack, you give away your location when the attack hits or misses. (PHB, p. 195)




          Note that it doesn't say you give away your location only to the target of the attack. When you attack while Hidden, you lose your Hidden status. Naturally, you wouldn't become visible to someone miles away, but basically anyone who could have been alerted by an "ow" from your initial target has already been alerted by your attack. (You can't even get around this with the Skulker Feat, because your attack needs to have hit).






          share|improve this answer






















          • You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
            – Loren Pechtel
            Sep 11 at 0:38






          • 3




            Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
            – Gandalfmeansme
            Sep 11 at 3:01











          • You may want to add how this interact with persistent invisibility
            – Vylix
            Sep 11 at 3:16






          • 2




            Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
            – Hennes
            Sep 11 at 4:22










          • The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
            – Pacattack
            Sep 12 at 1:49












          up vote
          21
          down vote



          accepted







          up vote
          21
          down vote



          accepted






          Your Attack Reveals You



          I am not sure whether a creature getting banished makes any noise. It's possible that the creature disappears without any sound, or that it vanishes in a flash of light screaming. Either way, that isn't what will give you away: it's the attack you needed to make to banish the creature.



          Banishing Arrow states that:




          The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. (XGtE, p. 29)




          Since you need to hit a creature to banish it, you needed to make an attack. However, the rules on unseen attackers and targets state that:




          If you are hidden—both unseen and unheard—when you make an attack, you give away your location when the attack hits or misses. (PHB, p. 195)




          Note that it doesn't say you give away your location only to the target of the attack. When you attack while Hidden, you lose your Hidden status. Naturally, you wouldn't become visible to someone miles away, but basically anyone who could have been alerted by an "ow" from your initial target has already been alerted by your attack. (You can't even get around this with the Skulker Feat, because your attack needs to have hit).






          share|improve this answer














          Your Attack Reveals You



          I am not sure whether a creature getting banished makes any noise. It's possible that the creature disappears without any sound, or that it vanishes in a flash of light screaming. Either way, that isn't what will give you away: it's the attack you needed to make to banish the creature.



          Banishing Arrow states that:




          The creature hit by the arrow must also succeed on a Charisma saving throw or be banished. (XGtE, p. 29)




          Since you need to hit a creature to banish it, you needed to make an attack. However, the rules on unseen attackers and targets state that:




          If you are hidden—both unseen and unheard—when you make an attack, you give away your location when the attack hits or misses. (PHB, p. 195)




          Note that it doesn't say you give away your location only to the target of the attack. When you attack while Hidden, you lose your Hidden status. Naturally, you wouldn't become visible to someone miles away, but basically anyone who could have been alerted by an "ow" from your initial target has already been alerted by your attack. (You can't even get around this with the Skulker Feat, because your attack needs to have hit).







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 10 at 22:04









          V2Blast

          15.5k235101




          15.5k235101










          answered Sep 10 at 15:04









          Gandalfmeansme

          12.5k24586




          12.5k24586











          • You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
            – Loren Pechtel
            Sep 11 at 0:38






          • 3




            Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
            – Gandalfmeansme
            Sep 11 at 3:01











          • You may want to add how this interact with persistent invisibility
            – Vylix
            Sep 11 at 3:16






          • 2




            Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
            – Hennes
            Sep 11 at 4:22










          • The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
            – Pacattack
            Sep 12 at 1:49
















          • You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
            – Loren Pechtel
            Sep 11 at 0:38






          • 3




            Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
            – Gandalfmeansme
            Sep 11 at 3:01











          • You may want to add how this interact with persistent invisibility
            – Vylix
            Sep 11 at 3:16






          • 2




            Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
            – Hennes
            Sep 11 at 4:22










          • The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
            – Pacattack
            Sep 12 at 1:49















          You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
          – Loren Pechtel
          Sep 11 at 0:38




          You're assuming someone can see you. There's a room with several creatures ahead. Someone has scouted and figured this out. You position yourself so that you only have line of sight to one creature and fire. Perhaps they will be alerted by the sound but they certainly won't see you.
          – Loren Pechtel
          Sep 11 at 0:38




          3




          3




          Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
          – Gandalfmeansme
          Sep 11 at 3:01





          Where did I assume that enemies could see you? The rules on unseen attackers do not specify that you give away your location if you can be seen and you attack (though that is certainly also the case). It says you give away your location when you attack, and it hits or misses.
          – Gandalfmeansme
          Sep 11 at 3:01













          You may want to add how this interact with persistent invisibility
          – Vylix
          Sep 11 at 3:16




          You may want to add how this interact with persistent invisibility
          – Vylix
          Sep 11 at 3:16




          2




          2




          Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
          – Hennes
          Sep 11 at 4:22




          Note that not only the creature you attack can make sound. You are firing a bow... Twang (sound of bow-string being released).
          – Hennes
          Sep 11 at 4:22












          The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
          – Pacattack
          Sep 12 at 1:49




          The last bit about firing a bow and it making a sound then has an interesting implication with the previously named Skulker feat because the way that would HAVE to work is that somehow you'd have to be able to make the sound of firing the bow inaudible ... and then the sound of hitting someone would be what actually alerts people. But based off the previous answer the hit does make a sound
          – Pacattack
          Sep 12 at 1:49












          up vote
          4
          down vote













          They could still be surprised, but it depends on a number of things.



          One particularly important part about Surprise is that the DM has to be the one actively deciding each time it's applied. Unlike stealth, buffs, healing, or other calculations regarding how it works, Surprise isn't necessarily as simple as "I rolled high, so now they're Surprised".



          Generally, for Surprise to work, the people in question need to believe there is no active threat. This means that they shouldn't be doing guard duty, couldn't have heard or seen someone get banished, or have any reason to believe that combat has initiated.



          Surprise is not a type of round, it's a condition that nullifies their first action in combat. If they don't know there's combat, then they're not taking combat actions, and they aren't surprised yet. Since the surprise hasn't been ruined, they could easily be surprised in later rounds, when the players do get around to spooking the enemy out of their pants.



          To make this simpler, I'd roll initiative for the entire encampment + players, but if a combatant doesn't know there's any reason for alarm, they simply do not take combat-related actions until they do or until they're Surprised. Mechanically, though, it should be treated as a
          string of short fights, which are individually considered for Surprise Rounds.




          This is separate from being "hidden" which is just one way to avoid being detected to get a Surprise Round. Another method could be to simply start attacking someone who thinks of you as an ally. Even without a stealth check, Surprise can still be obtained.






          share|improve this answer


















          • 1




            There is no such thing as a "surprise round" in 5E. This needs rewording.
            – T.J.L.
            Sep 10 at 18:08










          • @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
            – Daniel Zastoupil
            Sep 10 at 18:10






          • 1




            You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
            – Gandalfmeansme
            Sep 10 at 18:11










          • Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
            – Gandalfmeansme
            Sep 10 at 18:12










          • @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
            – Daniel Zastoupil
            Sep 10 at 18:15















          up vote
          4
          down vote













          They could still be surprised, but it depends on a number of things.



          One particularly important part about Surprise is that the DM has to be the one actively deciding each time it's applied. Unlike stealth, buffs, healing, or other calculations regarding how it works, Surprise isn't necessarily as simple as "I rolled high, so now they're Surprised".



          Generally, for Surprise to work, the people in question need to believe there is no active threat. This means that they shouldn't be doing guard duty, couldn't have heard or seen someone get banished, or have any reason to believe that combat has initiated.



          Surprise is not a type of round, it's a condition that nullifies their first action in combat. If they don't know there's combat, then they're not taking combat actions, and they aren't surprised yet. Since the surprise hasn't been ruined, they could easily be surprised in later rounds, when the players do get around to spooking the enemy out of their pants.



          To make this simpler, I'd roll initiative for the entire encampment + players, but if a combatant doesn't know there's any reason for alarm, they simply do not take combat-related actions until they do or until they're Surprised. Mechanically, though, it should be treated as a
          string of short fights, which are individually considered for Surprise Rounds.




          This is separate from being "hidden" which is just one way to avoid being detected to get a Surprise Round. Another method could be to simply start attacking someone who thinks of you as an ally. Even without a stealth check, Surprise can still be obtained.






          share|improve this answer


















          • 1




            There is no such thing as a "surprise round" in 5E. This needs rewording.
            – T.J.L.
            Sep 10 at 18:08










          • @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
            – Daniel Zastoupil
            Sep 10 at 18:10






          • 1




            You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
            – Gandalfmeansme
            Sep 10 at 18:11










          • Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
            – Gandalfmeansme
            Sep 10 at 18:12










          • @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
            – Daniel Zastoupil
            Sep 10 at 18:15













          up vote
          4
          down vote










          up vote
          4
          down vote









          They could still be surprised, but it depends on a number of things.



          One particularly important part about Surprise is that the DM has to be the one actively deciding each time it's applied. Unlike stealth, buffs, healing, or other calculations regarding how it works, Surprise isn't necessarily as simple as "I rolled high, so now they're Surprised".



          Generally, for Surprise to work, the people in question need to believe there is no active threat. This means that they shouldn't be doing guard duty, couldn't have heard or seen someone get banished, or have any reason to believe that combat has initiated.



          Surprise is not a type of round, it's a condition that nullifies their first action in combat. If they don't know there's combat, then they're not taking combat actions, and they aren't surprised yet. Since the surprise hasn't been ruined, they could easily be surprised in later rounds, when the players do get around to spooking the enemy out of their pants.



          To make this simpler, I'd roll initiative for the entire encampment + players, but if a combatant doesn't know there's any reason for alarm, they simply do not take combat-related actions until they do or until they're Surprised. Mechanically, though, it should be treated as a
          string of short fights, which are individually considered for Surprise Rounds.




          This is separate from being "hidden" which is just one way to avoid being detected to get a Surprise Round. Another method could be to simply start attacking someone who thinks of you as an ally. Even without a stealth check, Surprise can still be obtained.






          share|improve this answer














          They could still be surprised, but it depends on a number of things.



          One particularly important part about Surprise is that the DM has to be the one actively deciding each time it's applied. Unlike stealth, buffs, healing, or other calculations regarding how it works, Surprise isn't necessarily as simple as "I rolled high, so now they're Surprised".



          Generally, for Surprise to work, the people in question need to believe there is no active threat. This means that they shouldn't be doing guard duty, couldn't have heard or seen someone get banished, or have any reason to believe that combat has initiated.



          Surprise is not a type of round, it's a condition that nullifies their first action in combat. If they don't know there's combat, then they're not taking combat actions, and they aren't surprised yet. Since the surprise hasn't been ruined, they could easily be surprised in later rounds, when the players do get around to spooking the enemy out of their pants.



          To make this simpler, I'd roll initiative for the entire encampment + players, but if a combatant doesn't know there's any reason for alarm, they simply do not take combat-related actions until they do or until they're Surprised. Mechanically, though, it should be treated as a
          string of short fights, which are individually considered for Surprise Rounds.




          This is separate from being "hidden" which is just one way to avoid being detected to get a Surprise Round. Another method could be to simply start attacking someone who thinks of you as an ally. Even without a stealth check, Surprise can still be obtained.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 10 at 22:47

























          answered Sep 10 at 17:47









          Daniel Zastoupil

          5,3181156




          5,3181156







          • 1




            There is no such thing as a "surprise round" in 5E. This needs rewording.
            – T.J.L.
            Sep 10 at 18:08










          • @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
            – Daniel Zastoupil
            Sep 10 at 18:10






          • 1




            You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
            – Gandalfmeansme
            Sep 10 at 18:11










          • Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
            – Gandalfmeansme
            Sep 10 at 18:12










          • @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
            – Daniel Zastoupil
            Sep 10 at 18:15













          • 1




            There is no such thing as a "surprise round" in 5E. This needs rewording.
            – T.J.L.
            Sep 10 at 18:08










          • @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
            – Daniel Zastoupil
            Sep 10 at 18:10






          • 1




            You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
            – Gandalfmeansme
            Sep 10 at 18:11










          • Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
            – Gandalfmeansme
            Sep 10 at 18:12










          • @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
            – Daniel Zastoupil
            Sep 10 at 18:15








          1




          1




          There is no such thing as a "surprise round" in 5E. This needs rewording.
          – T.J.L.
          Sep 10 at 18:08




          There is no such thing as a "surprise round" in 5E. This needs rewording.
          – T.J.L.
          Sep 10 at 18:08












          @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
          – Daniel Zastoupil
          Sep 10 at 18:10




          @T.J.L. Duh, you're right. Surprise is a condition that lasts a round. I'll fix it.
          – Daniel Zastoupil
          Sep 10 at 18:10




          1




          1




          You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
          – Gandalfmeansme
          Sep 10 at 18:11




          You make a lot of accurate comments here, but I don't see them as applying to this situation. Your example of how characters could surprise enemies without Hiding is that the enemies might think they are allies (good example, as this is another way you could "not notice a threat"). But this particular question is about attacking one creature, who if they said "ow" would be perceived by their allies. And whether the others will then still be surprised. Won't attacking one creature reveal to its nearby (within earshot) allies that you are hostile?
          – Gandalfmeansme
          Sep 10 at 18:11












          Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
          – Gandalfmeansme
          Sep 10 at 18:12




          Also, although I absolutely agree that a creature can be surprised by an enemy which is not Hidden, I think you might want to cite some sources for that. Especially since the rules on surprise in the PHB compare Stealth with Perception rolls.
          – Gandalfmeansme
          Sep 10 at 18:12












          @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
          – Daniel Zastoupil
          Sep 10 at 18:15





          @Gandalfmeansme All great points, but since Banishing Arrow doesn't indicate what effects, if any, are present, and it says "when the creature is hit", not "When it takes damage", it could be read as being the first thing that occurs (with damage happening after). These particular aspects would have to be decided by the DM. I did try to address this in the second line, with "They [...] couldn't have heard or seen someone get banished".
          – Daniel Zastoupil
          Sep 10 at 18:15











          up vote
          -1
          down vote













          I thought the way a "surprise" round worked in 5th edition was that everyone rolls initiative as normal. Everyone who is surprised misses their standard, bonus and move actions and only gets their reaction after their turn comes up. The exception being certain barbarians who can act provided they rage immediately when their turn starts.



          In any case I'd say you could take out that initial target or any number of targets without starting combat provided you can justify the remaining enemies not noticing anyone vanish. If they are all sitting around a campfire chatting and one of them suddenly vanishes there is pretty much no way they aren't going to be alerted. If one of them got up to answer the call of nature and you managed to take them out such that the others couldn't see or hear the attack then combat would not have started. The DM could still call for initiative rolls but not have the other enemies do something since they wouldn't know anything is going on.






          share|improve this answer




















          • You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
            – V2Blast
            Sep 11 at 8:28














          up vote
          -1
          down vote













          I thought the way a "surprise" round worked in 5th edition was that everyone rolls initiative as normal. Everyone who is surprised misses their standard, bonus and move actions and only gets their reaction after their turn comes up. The exception being certain barbarians who can act provided they rage immediately when their turn starts.



          In any case I'd say you could take out that initial target or any number of targets without starting combat provided you can justify the remaining enemies not noticing anyone vanish. If they are all sitting around a campfire chatting and one of them suddenly vanishes there is pretty much no way they aren't going to be alerted. If one of them got up to answer the call of nature and you managed to take them out such that the others couldn't see or hear the attack then combat would not have started. The DM could still call for initiative rolls but not have the other enemies do something since they wouldn't know anything is going on.






          share|improve this answer




















          • You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
            – V2Blast
            Sep 11 at 8:28












          up vote
          -1
          down vote










          up vote
          -1
          down vote









          I thought the way a "surprise" round worked in 5th edition was that everyone rolls initiative as normal. Everyone who is surprised misses their standard, bonus and move actions and only gets their reaction after their turn comes up. The exception being certain barbarians who can act provided they rage immediately when their turn starts.



          In any case I'd say you could take out that initial target or any number of targets without starting combat provided you can justify the remaining enemies not noticing anyone vanish. If they are all sitting around a campfire chatting and one of them suddenly vanishes there is pretty much no way they aren't going to be alerted. If one of them got up to answer the call of nature and you managed to take them out such that the others couldn't see or hear the attack then combat would not have started. The DM could still call for initiative rolls but not have the other enemies do something since they wouldn't know anything is going on.






          share|improve this answer












          I thought the way a "surprise" round worked in 5th edition was that everyone rolls initiative as normal. Everyone who is surprised misses their standard, bonus and move actions and only gets their reaction after their turn comes up. The exception being certain barbarians who can act provided they rage immediately when their turn starts.



          In any case I'd say you could take out that initial target or any number of targets without starting combat provided you can justify the remaining enemies not noticing anyone vanish. If they are all sitting around a campfire chatting and one of them suddenly vanishes there is pretty much no way they aren't going to be alerted. If one of them got up to answer the call of nature and you managed to take them out such that the others couldn't see or hear the attack then combat would not have started. The DM could still call for initiative rolls but not have the other enemies do something since they wouldn't know anything is going on.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 11 at 5:13









          Allan

          1




          1











          • You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
            – V2Blast
            Sep 11 at 8:28
















          • You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
            – V2Blast
            Sep 11 at 8:28















          You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
          – V2Blast
          Sep 11 at 8:28




          You are correct about the surprise rules (though there's no "move action", just movement), but your answer would be improved by referencing the relevant section of the rules. However, the start of the second paragraph of your answer is a bit confusing, given that "taking out a target" is combat by definition. You might want to change "without starting combat" to "without other enemies expecting a threat", or something like it.
          – V2Blast
          Sep 11 at 8:28

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f131460%2fcan-an-arcane-archer-fighter-use-a-banishing-arrow-to-effectively-get-two-surpri%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?