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
*Pathfinder & Starfinder
Sneak Attack Resistance
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="Li Shenron" data-source="post: 5802999" data-attributes="member: 1465"><p>I see three options (here the example is Sneak Attack, but it can be applied to mostly any resistance or immunity):</p><p></p><p>a) tie resistance to Sneak Attack to creature type [the 3e core method]</p><p></p><p>Pro is simplicity, you just know that "all undead are immune to SA" which is very easy to remember, and doesn't need to be reprinted every time in a MM.</p><p></p><p>Con is that when an ability carries over to everything which has that "type" including PC/NPC using spells or earning class abilities that grant such type, you may have a lot of baggage to carry over and remember, and it may generate nonsense cases. Example fomr 3.0 SRD: "Elementals <em>have no clear front or back</em> and are therefore not subject to critical hits or flanking." WTF? There are pretty many creatures of the Elemental type that <em>do </em>have a front and back... in this case I want to point out that it is the immunity to <em>flanking</em> here that makes no sense to apply.</p><p></p><p>b) tie resistance to Sneak Attack to another ability/feature [your suggestion]</p><p></p><p>Pro is that it that probably you can avoid more nonsense cases.</p><p></p><p>Con is that it sounds more complicated to keep track of if you allow more than one feature to tie into SA, and IMHO it also makes monster design more difficult. You may also get some new extra nonsense cases as a by-product.</p><p></p><p>c) make resistance to Sneak Attack specific for each creature, untied to everything else</p><p></p><p>Pro is that there are no nonsense cases.</p><p></p><p>Con is that you have to rewrite the ability into each MM entry.</p><p></p><p>---</p><p></p><p>Personally I think the best solution would be a) + c), i.e. let creature Type dictate a series of abilities (when they are believed to be <em>really </em>iconic and thus very frequent), but then include the magic word <strong>usually</strong>, and then feel free to make some creatures an exception.</p><p></p><p>Also, put a line in the DMG/MM saying that a DM can decide to modify/remove some monster abilities of these kinds if the group finds it more "realistic".</p></blockquote><p></p>
[QUOTE="Li Shenron, post: 5802999, member: 1465"] I see three options (here the example is Sneak Attack, but it can be applied to mostly any resistance or immunity): a) tie resistance to Sneak Attack to creature type [the 3e core method] Pro is simplicity, you just know that "all undead are immune to SA" which is very easy to remember, and doesn't need to be reprinted every time in a MM. Con is that when an ability carries over to everything which has that "type" including PC/NPC using spells or earning class abilities that grant such type, you may have a lot of baggage to carry over and remember, and it may generate nonsense cases. Example fomr 3.0 SRD: "Elementals [I]have no clear front or back[/I] and are therefore not subject to critical hits or flanking." WTF? There are pretty many creatures of the Elemental type that [I]do [/I]have a front and back... in this case I want to point out that it is the immunity to [I]flanking[/I] here that makes no sense to apply. b) tie resistance to Sneak Attack to another ability/feature [your suggestion] Pro is that it that probably you can avoid more nonsense cases. Con is that it sounds more complicated to keep track of if you allow more than one feature to tie into SA, and IMHO it also makes monster design more difficult. You may also get some new extra nonsense cases as a by-product. c) make resistance to Sneak Attack specific for each creature, untied to everything else Pro is that there are no nonsense cases. Con is that you have to rewrite the ability into each MM entry. --- Personally I think the best solution would be a) + c), i.e. let creature Type dictate a series of abilities (when they are believed to be [I]really [/I]iconic and thus very frequent), but then include the magic word [B]usually[/B], and then feel free to make some creatures an exception. Also, put a line in the DMG/MM saying that a DM can decide to modify/remove some monster abilities of these kinds if the group finds it more "realistic". [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Pathfinder & Starfinder
Sneak Attack Resistance
Top