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
Assassinate
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="Arial Black" data-source="post: 6682962" data-attributes="member: 6799649"><p>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. <em>They</em> could be surprised, because even though it is not <em>the</em> first turn of combat, it is <em>their</em> first turn of combat, therefore the effects of surprise for those guys is that they can't move or take an action on <em>their</em> 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).</p><p></p><p>Second, 'surprised' has TWO effects:-</p><p></p><p>* you are vulnerable to auto-crits from Assassinate all the while that you don't notice a threat, and are <em>not</em> vulnerable to auto-crits all the while that you <em>do</em> 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</p><p></p><p>* you may not move or take actions on YOUR first turn of this combat (whether or not <em>your</em> first turn is <em>the</em> 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, <em>this remains the case whether or not you notice a threat before your first turn</em>. 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!</p><p></p><p></p><p></p><p></p><p>Er...yeah, exactly! Assassinate doesn't <em>define</em> surprise, but it only works on someone who <em>is</em> surprised at the moment the attack hits. Therefore, one of the <em>effects</em> of 'surprise' it that you are vulnerable to Assassinate.</p><p></p><p></p><p></p><p>As explained above, <em>if</em> you were surprised at the start of <em>your</em> 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.</p><p></p><p></p><p></p><p>Yes, I'm stating the obvious. That doesn't make it untrue.</p><p></p><p></p><p></p><p>No. Just because surprise was determined at the start doesn't mean it isn't true later also.</p><p></p><p>'Haven't noticed a threat' = 'surprised. Therefore, if you <em>have</em> 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.</p></blockquote><p></p>
[QUOTE="Arial Black, post: 6682962, member: 6799649"] 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. [I]They[/I] could be surprised, because even though it is not [I]the[/I] first turn of combat, it is [I]their[/I] first turn of combat, therefore the effects of surprise for those guys is that they can't move or take an action on [I]their[/I] 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 [I]not[/I] vulnerable to auto-crits all the while that you [I]do[/I] 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 [I]your[/I] first turn is [I]the[/I] 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, [I]this remains the case whether or not you notice a threat before your first turn[/I]. 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! Er...yeah, exactly! Assassinate doesn't [I]define[/I] surprise, but it only works on someone who [I]is[/I] surprised at the moment the attack hits. Therefore, one of the [I]effects[/I] of 'surprise' it that you are vulnerable to Assassinate. As explained above, [I]if[/I] you were surprised at the start of [I]your[/I] 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. Yes, I'm stating the obvious. That doesn't make it untrue. 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 [I]have[/I] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Assassinate
Top