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="clearstream" data-source="post: 6699014" data-attributes="member: 71699"><p>Arial's surprise (what we're calling <strong>surprise version 1</strong>) adds words to RAW and ignores RAW in several places, but I will focus first on one example. Specifically, it adds the words "<em>surprise ends on noticing a threat</em>" to RAW. Those words do not appear in RAW. And in adding those words, <strong>surprise version 1</strong> ignores other RAW that makes it clear that surprise confers to individual combatants. It instead necessitates that surprise is tracked to pairs of combatants. (Working through multi-way combats demonstrates that. Multiple assassins can lose surprise at various times to various targets.)</p><p></p><p><strong>Surprise version 1</strong> benefits ranged-assassins and increases the power of the Skulker feat, while penalising melee-assassins who will need to close without being noticed. The streamlined base rules of 5th edition don't include facing, so a DM might decide to adopt the optional Facing rules from the DMG to mitigate that. Albeit any melee-using creature closing from behind will then get advantage, making the first part of Assassinate meaningless for melee-assassins.</p><p></p><p>A possible defence for adding "<em>surprise ends on noticing a threat</em>" to RAW is if we decide that the first-turn effects of surprise expressed on PHB189 are not synonymous with being surprised. If so, then RAW does not tell us when surprise ends so we require additional words. Whatever words we choose can't be justified by our wanting surprise to continue past its first turn effects in order to serve as a handshake for features such as Rogue Assassinate and Kenku Ambusher. Because that commits the fallacy of begging the question (our premises directly or indirectly include the claim that the conclusion is true). Additionally, ending surprise on noticing a threat can result in surprise ending <em>prior </em>to its first turn effects completing, necessitating that we launch those effects before participants start taking turns! A baroque addition to the mechanic that falls afoul of Occam's Razor.</p><p></p><p>Conversely, if we decide that the first-turn effects of surprise are synonymous with being surprised, then all of RAW is sustained without added complexity.</p></blockquote><p></p>
[QUOTE="clearstream, post: 6699014, member: 71699"] Arial's surprise (what we're calling [B]surprise version 1[/B]) adds words to RAW and ignores RAW in several places, but I will focus first on one example. Specifically, it adds the words "[I]surprise ends on noticing a threat[/I]" to RAW. Those words do not appear in RAW. And in adding those words, [B]surprise version 1[/B] ignores other RAW that makes it clear that surprise confers to individual combatants. It instead necessitates that surprise is tracked to pairs of combatants. (Working through multi-way combats demonstrates that. Multiple assassins can lose surprise at various times to various targets.) [B]Surprise version 1[/B] benefits ranged-assassins and increases the power of the Skulker feat, while penalising melee-assassins who will need to close without being noticed. The streamlined base rules of 5th edition don't include facing, so a DM might decide to adopt the optional Facing rules from the DMG to mitigate that. Albeit any melee-using creature closing from behind will then get advantage, making the first part of Assassinate meaningless for melee-assassins. A possible defence for adding "[I]surprise ends on noticing a threat[/I]" to RAW is if we decide that the first-turn effects of surprise expressed on PHB189 are not synonymous with being surprised. If so, then RAW does not tell us when surprise ends so we require additional words. Whatever words we choose can't be justified by our wanting surprise to continue past its first turn effects in order to serve as a handshake for features such as Rogue Assassinate and Kenku Ambusher. Because that commits the fallacy of begging the question (our premises directly or indirectly include the claim that the conclusion is true). Additionally, ending surprise on noticing a threat can result in surprise ending [I]prior [/I]to its first turn effects completing, necessitating that we launch those effects before participants start taking turns! A baroque addition to the mechanic that falls afoul of Occam's Razor. Conversely, if we decide that the first-turn effects of surprise are synonymous with being surprised, then all of RAW is sustained without added complexity. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Assassinate
Top