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
*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
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Dungeons & Dragons
Running away...
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="pming" data-source="post: 6614005" data-attributes="member: 45197"><p>Hiya!</p><p></p><p></p><p></p><p> The first thing you need to do is realize there <em>is no spoon</em>. What that means is you need to stop approaching 5e "rules" from a 3.x/4e/PF mentality. Stop looking for "absolutes" in the game rules. You will be sorely disappointing and constantly annoyed by the simple fact that there are very little of these absolutes in the game. </p><p></p><p> You can't just say "forcing past foe = DC 15" and be done with it. That just does not make any sense at all from a "realism" side of things, and definitely not from a 5e rules side of things. There are a hundred and one things that could all affect the DC...and your DM can guesstimate all of them in a couple of seconds. This is FAR superior to spending three and a half minutes leafing through pages of charts and tables with modifiers, adding them all up, and adding that to some "set in stone" DC that was in all likelihood arbitrarily decided on anyway by the designers.</p><p></p><p> Your DM can use the standard DC's and just pick one that fits for the base (DC 5, 10, 15, 20, 25, 30). Or, he can base it on the opponents Dexterity score. Or average of Dex + Int. Or maybe on 30 - base AC. Or any number of other factors that could be coming into play during that particular situation. The point is...the DC will be based on the situation. And trying to dumb everything down to an absolute "DC = X in situation Y" is a loosing battle and one that will make for a much more bland and poorer game experience....IMHO, of course. A base "DC = X, modified by whatever" is a MUCH better solution.</p><p></p><p>Oh, and me? I'd probably choose the 30 - base AC route, modified by situation (slippery floor, damage done to foe, type of weapon foe has, ...all those hundred-and-one things that go through a DM's mind when thinking about this kind of thing)...if my players had to have something carved into stone for some reason. Luckily I don't have players like that. Sometimes I may just pick a DC and say "Dex Save at X" just to keep things moving or when it really isn't all that important. Sometimes I might make it based on and average of Str + Con. And sometimes I'd just say "No" or "Yes". The situation is the key to the whole thing and a good DM will learn what "feels right" the more they DM.</p><p></p><p>^_^</p><p></p><p>Paul L. Ming</p></blockquote><p></p>
[QUOTE="pming, post: 6614005, member: 45197"] Hiya! The first thing you need to do is realize there [I]is no spoon[/I]. What that means is you need to stop approaching 5e "rules" from a 3.x/4e/PF mentality. Stop looking for "absolutes" in the game rules. You will be sorely disappointing and constantly annoyed by the simple fact that there are very little of these absolutes in the game. You can't just say "forcing past foe = DC 15" and be done with it. That just does not make any sense at all from a "realism" side of things, and definitely not from a 5e rules side of things. There are a hundred and one things that could all affect the DC...and your DM can guesstimate all of them in a couple of seconds. This is FAR superior to spending three and a half minutes leafing through pages of charts and tables with modifiers, adding them all up, and adding that to some "set in stone" DC that was in all likelihood arbitrarily decided on anyway by the designers. Your DM can use the standard DC's and just pick one that fits for the base (DC 5, 10, 15, 20, 25, 30). Or, he can base it on the opponents Dexterity score. Or average of Dex + Int. Or maybe on 30 - base AC. Or any number of other factors that could be coming into play during that particular situation. The point is...the DC will be based on the situation. And trying to dumb everything down to an absolute "DC = X in situation Y" is a loosing battle and one that will make for a much more bland and poorer game experience....IMHO, of course. A base "DC = X, modified by whatever" is a MUCH better solution. Oh, and me? I'd probably choose the 30 - base AC route, modified by situation (slippery floor, damage done to foe, type of weapon foe has, ...all those hundred-and-one things that go through a DM's mind when thinking about this kind of thing)...if my players had to have something carved into stone for some reason. Luckily I don't have players like that. Sometimes I may just pick a DC and say "Dex Save at X" just to keep things moving or when it really isn't all that important. Sometimes I might make it based on and average of Str + Con. And sometimes I'd just say "No" or "Yes". The situation is the key to the whole thing and a good DM will learn what "feels right" the more they DM. ^_^ Paul L. Ming [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Running away...
Top