Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Dungeons & Dragons
How does Surprise work in 5e?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="pemerton" data-source="post: 6471185" data-attributes="member: 42582"><p>Rereading Basic, p 69:</p><p></p><p style="margin-left: 20px">Any character or monster that doesn’t notice a threat is surprised at the start of the encounter.</p> <p style="margin-left: 20px"></p> <p style="margin-left: 20px">If you’re surprised, you can’t move or take an action on your first turn of the combat, and you can’t take a reaction until that turn ends.</p><p></p><p>So the constraint on surprise seems stricter than "1st turn only". It's "start of encounter" only.</p><p></p><p>There is no express statement that the unnoticed threat must activate itself as an element of the encounter, but that seems to be implied. Hence, to me, the most natural reading is that <em>when an unnoticed threat activates itself at the start of the encounter </em>, perhaps by initiating the encounter all on its own, perhaps by participating in conjunction with other noticed threats, then <em>those who failed to notice it are surprised, and hence can't move, take actions or react</em> until after their initiative count has been passed in that first round of the encounter.</p><p></p><p></p><p>That is how it seems to me: if the archers in the woods activate themselves at the start of the encounter (eg by shooting arrows at the PCs) and the PCs hadn't noticed them prior to this, then the PCs are surprised and hence will get beaten up in the first round of combat.</p><p></p><p></p><p>Basically, this.</p><p></p><p></p><p>I don't think so, because the goblins after the first one wouldn't be activating themselves at the start of the encounter.</p><p></p><p>To me this seems to break the rules. The encounter had already started when the wyverns attacked, so the PCs shouldn't have been able to be surprised by them.</p><p></p><p>This is weird, though, because those who roll better on initiative are actually worse off! (My Rolemaster players used to call this being "initiative purged" - especially costly in RM because it can mean you haven't had a chance to declare a defence, and hence can be fairly easily cut down in melee.)</p><p></p><p>A somewhat similar thing comes up in Perkins' example, where the encounter starts before the wyverns can act (presumably because they rolled lower on initiative). Assuming that you are applying the surprise rules in these situations, I think the solution in these sorts of cases is probably to take a bit more advantage, as a GM, of the fact that initiative is an abstraction and all the action is taking place simultaneously: let the archers attack, and then have the visible bandits go, and then roll initiative after that first round. And in the wyvern case, have the GM declare the cultist attacks, then announce the wyverns' presence also ("You also see wyverns that you hadn't noticed swooping in!") - hence the PCs are surprised. Then resolve the melee attacks in initiative order.</p><p></p><p></p><p>On this interpretation - which I think is the most natural reading of the rules as written - the surprise rules combine perception and morale into one gestalt whole. This is implicit in the phrase "unnoticed threat".</p><p></p><p>If a gnat is lurking in wait for me as I walk along the garden path, I probably won't notice it, but although unnoticed it is probably not an unnoticed <em>threat</em>. I think the sole goblin sniper with 30 obvious hobgoblins is in the same category: if the PCs are already gearing up to fight 30 hobgoblins one goblin is not a threat. Similarly, if your hidden bandits throw radishes at the PCs, the PCs might be surprised in the colloquial sense, but they have not been subjected to an unnoticed threat. (If the archers have carved the radishes in the shape of arrows - perhaps they are low on arrow heads but nevertheless want to give their visible comrades an advantage - that could be a different matter, perhaps determined by further perception or horticulture checks.)</p><p></p><p>To my mind, this question - what counts as a <em>threat</em> - is one of the places where the "rulings not rules" motif makes sense. (Whereas don't get me started on the syntactic and conceptual mess that is the hiding rules!) It reminds me a bit of Burning Wheel's Steel rules - a surprise attack can force a Steel check, with the possible consequence of being discombobulated and hence vulnerable to all comers. But the GM has authority to decide when a Steel check is triggered. A band of stout dwarves, facing a phalanx of hobgoblins, will not have to make a check just because one goblins jumps out and throws a spear at them!</p><p></p><p>This is an interesting case. As written, the surprise rules seem to assume that it is only at the start of an encounter that the failure of attention and morale that constitutes surprise can take place. That looks like a simplification to facilitate game play and remove the need for some more complex mechanic like BW's Steel.</p><p></p><p>Within the scope of that simplification, the traitor is better of striking in the same round as the goblins attack, rather than waiting to see which way the wind is blowing and then deciding to treach.</p></blockquote><p></p>
[QUOTE="pemerton, post: 6471185, member: 42582"] Rereading Basic, p 69: [indent]Any character or monster that doesn’t notice a threat is surprised at the start of the encounter. If you’re surprised, you can’t move or take an action on your first turn of the combat, and you can’t take a reaction until that turn ends.[/indent] So the constraint on surprise seems stricter than "1st turn only". It's "start of encounter" only. There is no express statement that the unnoticed threat must activate itself as an element of the encounter, but that seems to be implied. Hence, to me, the most natural reading is that [I]when an unnoticed threat activates itself at the start of the encounter [/I], perhaps by initiating the encounter all on its own, perhaps by participating in conjunction with other noticed threats, then [I]those who failed to notice it are surprised, and hence can't move, take actions or react[/I] until after their initiative count has been passed in that first round of the encounter. That is how it seems to me: if the archers in the woods activate themselves at the start of the encounter (eg by shooting arrows at the PCs) and the PCs hadn't noticed them prior to this, then the PCs are surprised and hence will get beaten up in the first round of combat. Basically, this. I don't think so, because the goblins after the first one wouldn't be activating themselves at the start of the encounter. To me this seems to break the rules. The encounter had already started when the wyverns attacked, so the PCs shouldn't have been able to be surprised by them. This is weird, though, because those who roll better on initiative are actually worse off! (My Rolemaster players used to call this being "initiative purged" - especially costly in RM because it can mean you haven't had a chance to declare a defence, and hence can be fairly easily cut down in melee.) A somewhat similar thing comes up in Perkins' example, where the encounter starts before the wyverns can act (presumably because they rolled lower on initiative). Assuming that you are applying the surprise rules in these situations, I think the solution in these sorts of cases is probably to take a bit more advantage, as a GM, of the fact that initiative is an abstraction and all the action is taking place simultaneously: let the archers attack, and then have the visible bandits go, and then roll initiative after that first round. And in the wyvern case, have the GM declare the cultist attacks, then announce the wyverns' presence also ("You also see wyverns that you hadn't noticed swooping in!") - hence the PCs are surprised. Then resolve the melee attacks in initiative order. On this interpretation - which I think is the most natural reading of the rules as written - the surprise rules combine perception and morale into one gestalt whole. This is implicit in the phrase "unnoticed threat". If a gnat is lurking in wait for me as I walk along the garden path, I probably won't notice it, but although unnoticed it is probably not an unnoticed [I]threat[/I]. I think the sole goblin sniper with 30 obvious hobgoblins is in the same category: if the PCs are already gearing up to fight 30 hobgoblins one goblin is not a threat. Similarly, if your hidden bandits throw radishes at the PCs, the PCs might be surprised in the colloquial sense, but they have not been subjected to an unnoticed threat. (If the archers have carved the radishes in the shape of arrows - perhaps they are low on arrow heads but nevertheless want to give their visible comrades an advantage - that could be a different matter, perhaps determined by further perception or horticulture checks.) To my mind, this question - what counts as a [I]threat[/I] - is one of the places where the "rulings not rules" motif makes sense. (Whereas don't get me started on the syntactic and conceptual mess that is the hiding rules!) It reminds me a bit of Burning Wheel's Steel rules - a surprise attack can force a Steel check, with the possible consequence of being discombobulated and hence vulnerable to all comers. But the GM has authority to decide when a Steel check is triggered. A band of stout dwarves, facing a phalanx of hobgoblins, will not have to make a check just because one goblins jumps out and throws a spear at them! This is an interesting case. As written, the surprise rules seem to assume that it is only at the start of an encounter that the failure of attention and morale that constitutes surprise can take place. That looks like a simplification to facilitate game play and remove the need for some more complex mechanic like BW's Steel. Within the scope of that simplification, the traitor is better of striking in the same round as the goblins attack, rather than waiting to see which way the wind is blowing and then deciding to treach. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
How does Surprise work in 5e?
Top