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
Explain Bounded Accuracy to Me (As if I Was Five)
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="EzekielRaiden" data-source="post: 9286433" data-attributes="member: 6790260"><p>Considering I don't actually believe 4e did the thing you describe, yes, I certainly do believe there are ways to do that. You'll have to be much more specific about what you mean in order for me to meaningfully answer the question, since I doubt this answer is all that productive.</p><p></p><p></p><p>I don't see the "actively tries to negate their impact" thing. At all. So I can't really respond to this.</p><p></p><p></p><p>The "One D&D" playtest demonstrates that it does not--and Crawford, very early on in that playtest process, explicitly said how the rules <em>don't</em> do that. For example, the fact that players simply <em>do not</em> take short rests nearly as often as the game's design expects them to, which shafts any characters dependent on short rests or numerous combats (e.g. Warlocks/Battle Masters or Champions, respectively) and supercharges the classes that depend on long rests and were already somewhat above the curve (mostly full casters and especially Wizard).</p><p></p><p>Given I do not share your opinion, and in fact have highlighted various ways in which the text both actually does fail to tell people what they're supposed to do, or does tell them but somehow gets ignored, I just don't agree with your absolute hardline "there cannot be mechanical changes, sorry" position.</p><p></p><p></p><p>Bolded: No, it won't necessarily have that impact. That's exactly the assertion I refute. Doing so <em>poorly</em> has such effects, specifically as a result of being a poor implementation. This is not a trade-off; we can in fact have both things.</p><p></p><p></p><p>Exactly. It is a story of growth, of exceeding one's limits (or, indeed, transcending mortal limits entirely), which is a pretty friggin' big part of fantasy narratives in general. There's a reason fiction of all kinds, not just novels but games and film and TV shows etc. almost always feature epiphany and training, where opponents who used to be a terrible danger (sometimes even to the point of "nope, can't fight those, <em>just run away</em>") become absolute chump change over time. Avatar: the Last Airbender, for example, presents ordinary firebenders as a pretty serious threat during the first season. By the middle of the third, even without the Day of Black Sun, Team Avatar can <em>easily</em> defeat ordinary firebenders and really only fear folks like Combustion Man, Azula, or Ozai.</p><p></p><p></p><p>I'm not sure I entirely understand what you mean by "the fiction of paragon tier in mechanically heroic tier terms." Do you mean that, in a sense, the <em>fiction</em> sweet-spot gets expanded to cover a different level range? Or do you mean something else? If that is what you mean, I personally would say that it's really a difference of setting the "scaling factor" of a game. Heroic is small-time, Paragon is big leagues, and Epic is world-shaking, but choice of campaign setting and focus can change what those things mean. Neverwinter, being an FR game, is heavily trafficking in otherworldly stuff (much as Planescape does), and thus its scale has only a very brief period in early heroic for totally mundane challenges, and tops out in high epic with the theoretical potential to not just slay gods but fundamentally rewrite the rules of existence--effectively shifting <em>everything</em> up by around half a tier. DS, meanwhile, shifts everything in the other direction by half a tier or a bit more--early on it really is the case that fighting random (relatively) mundane desert creatures is a risky move, like how random sewer rats in an RPG can be a terrifying early threat, and you top out fighting beings who are attempting to ascend to the level of something like a demigod and maybe, <em>maybe</em> finding a way to heal the wounds of the world...or at least make the region you live in suck less.</p><p></p><p></p><p>Again, not seeing that, so I can't answer the question.</p><p></p><p></p><p>They aren't changed arbitrarily. They are changed for very specific reasons. There isn't a static benchmark because <em>the benchmark is the player experience, which is dynamic</em>. Mechanical representation is not the master, driving player experience before it and callously indifferent to how those mechanics will be experienced through play. <em>If</em> you choose to do this (and you do not have to! You can quite easily use monsters even within a +/- <em>8</em> level range if you feel like it, the rules even say so!), the mechanical representation changes specifically because mechanics are there to encode and represent the player experience, not to be some imperious objective reality and <em>hope</em> that that reality actually produces the experience so intended.</p><p></p><p>For someone who so thoroughly espouses the "the rules are not the master, I am" philosophy as far as I can tell, your desire for this static benchmark to be your master, to which you must adhere no matter what, is genuinely baffling.</p><p></p><p>Designing a 4e monster is thus a matter of genuinely thinking about what the creature is, and what the experience of fighting it should be. At level 1, a frost giant isn't even a solo--it's a <em>force of nature</em>, something the party has no hope whatsoever of <em>defeating</em> in battle, and must either flee from it, entrap it, or outsmart it, aka, a skill challenge.</p><p></p><p>But you shouldn't be designing a fight, or a combat, or whatever else, from the starting point of "I need to have a level X fight because my players are level X." You should come up with the concept of what the fight <em>actually is</em>, the fiction, and then develop mechanics which suit that fiction. Sometimes, that will mean that the best mechanical representation of a creature is a minion, even though the players have fought a creature like that before and it wasn't a minion. That's fine--because the objective fiction reality is still there, you're just adjusting how that manifests in mechanics in order to accurately portray whatever that thing is <em>now</em>, in <em>this</em> context.</p><p></p><p>This is not "undermining" anything. It is simply recognizing that mechanics are always an abstraction, and that we can (and, I argue, should) adapt that abstraction so that it invites the desired experience of play, rather than hoping to luck into (or brute-force) an experience of play by throwing utterly unchanged abstractions against a party with slightly different numerical values.</p><p></p><p></p><p>NO. THEY. ARE. NOT.</p><p></p><p>This is a pernicious <em>falsehood.</em> The books <em>explicitly reject doing this</em>. Repeatedly. I have dug up the quotes before, I can do it again.</p><p></p><p>Enemies are NOT "always level appropriate." I'm certain you've read the 4e DMG, so you should know better. And if you haven't, why are you staking such strident claims on the basis of nothing better than hearsay?</p><p></p><p></p><p>That is not the culture of play. That is WotC. WotC is making revisions, yes. And if you hadn't noticed, those revisions are not exactly the most popular thing! We have a poll <em>right now</em> asking whether people will adopt 5.5e, and it's currently 54% yes, 46% no. I wouldn't call that a ringing endorsement of new stuff!</p><p></p><p>But what I was actually talking about was 3PP and genuinely <em>new</em> mechanics, not just additional options for classes or feats or the like. I stand by what I said with regard to that. The culture of play for 5e--what the actual people running it tend to do--is the most hidebound I've ever seen D&D be. Far moreso than any edition first published during my lifetime (which would be 2e and up.)</p><p></p><p></p><p>Not at all. It is representing the fact that these things <em>do</em> still pose some challenge, but the kind of challenge they pose is different now. It is the same creature. The fictional reality has not changed. The mechanics have. Because mechanics are not fictional reality, and cannot be--the map is not the territory.</p><p></p><p>You are asking for every globe to have precise-to-the-meter topographical maps and street-view data. That is not productive nor useful for any globe, even a dynamically flexible one like Google Earth. The types and manners of information presented to the viewer <em>should</em> change as the scale and perspective change. The physical reality--the Earth itself--is not changing in any way. But the data furnished to you from a scale of 500 miles to the inch (or 300 km per cm, or whatever you prefer) <em>should</em> be different from the data furnished to you from a scale of 100 feet to the inch, even if in both cases you are centered on the same latitude and longitude. Some details that are essential at the 500 mile scale are utterly meaningless at the 100' scale and vice-versa.</p><p></p><p></p><p></p><p>The text of 4e's DMG explicitly says you should not do this, and in fact it adds (again, explicitly) that it is sometimes wise to have players truly face the exact same monster--no mechanical changes at all--so they can see how much their characters have grown.</p><p></p><p></p><p>Those would in fact be <em>different</em> creatures. Not the same creatures. If you're fighting an actually-more-powerful creature in an area you've been to before, it's because something there has changed and more powerful creatures have shown up.</p><p></p><p></p><p>Correction: A minion ogre is the same <em>creature</em>, but its mechanics have changed, because mechanics are contextual. In the context of "we have had one adventure together rescuing the miller's daughter," a single ogre is a dangerous and risky opponent which should not be underestimated. In the context of seasoned adventurers who have visited other planes and dealt with the servants of fey ladies and kings of shadow, an ogre is a nuisance, albeit still a danger. In the context of demigods who regularly show the deities themselves that they're not to be trifled with, a single ogre doesn't even rise to the level of <em>nuisance</em> anymore.</p><p></p><p>That shift from "terrifying" to "nuisance" to "non-entity (in isolation)" is represented with mechanics. Because mechanics are an abstraction, and that abstraction should serve us, not command us.</p><p></p><p></p><p>I mean, potentially it <em>could</em> be the same ogre. That could even be good fun; you fight <em>literally</em> the same ogre (say) six times from level 1-ish to level 18ish, initially as a skill challenge, then progressively a solo, an elite, a standard, a minion, and finally as a single soldier amongst a squad. A direct and palpable representation of how far the characters have come--literally a threat they <em>couldn't</em> threaten at the start of the campaign is now a puny nothing before them.</p><p></p><p></p><p>As stated: the 4e DMG explicitly, repeatedly, instructs the DM to <em>not</em> do things like this. It could not possibly be more clear that this is a thing you shouldn't do, without writing in large, friendly letters "DO NOT DO THIS THING."</p><p></p><p></p><p>4e's encounter design sections (there's a few of them, looking at encounter design from different perspectives) consistently state that you should use a variety, not just in flavor terms but in mechanical terms as well. What one might call "typical" fights are usually in the level +/- 2 range, but it explicitly suggests including <em>at minimum</em> some fights +/- 4, potentially up to +/- 8 on occasion as spice, with the +8 side giving the players a real nasty problem, and the -8 side giving them a cakewalk that highlights their strengths. The use of these things is, as stated, always focused on what kind of player-experience they're designed to produce.</p><p></p><p></p><p>And they aren't "not in the world anymore" in 4e either. "Weak" creatures would become one of the following, depending on context:</p><ul> <li data-xf-list-type="ul">Minions (creatures that can still do damage and are still non-trivial to hit, but which die as soon as they take any amount of damage; some homebrew ideas added the idea of "mooks," which are effectively <em>two-hit</em> minions, they must take damage from two different sources to fall)</li> <li data-xf-list-type="ul">Swarms (a collection of creatures that are not dangerous alone, but are dangerous collectively, e.g. a swarm of insects or vampire bats or the like)</li> <li data-xf-list-type="ul">A skill challenge (fighting them isn't productive. you want to get rid of the problem for good; e.g. if you have an ant problem, squishing a thousand ants isn't going to make the problem go away, even though the ants might be genuinely incapable of harming you)</li> <li data-xf-list-type="ul">A "trap"/obstacle/feature/etc. rather than a creature proper (because, again, for particularly weak creatures, <em>killing</em> them isn't productive, you must eliminate the underlying problem)</li> </ul></blockquote><p></p>
[QUOTE="EzekielRaiden, post: 9286433, member: 6790260"] Considering I don't actually believe 4e did the thing you describe, yes, I certainly do believe there are ways to do that. You'll have to be much more specific about what you mean in order for me to meaningfully answer the question, since I doubt this answer is all that productive. I don't see the "actively tries to negate their impact" thing. At all. So I can't really respond to this. The "One D&D" playtest demonstrates that it does not--and Crawford, very early on in that playtest process, explicitly said how the rules [I]don't[/I] do that. For example, the fact that players simply [I]do not[/I] take short rests nearly as often as the game's design expects them to, which shafts any characters dependent on short rests or numerous combats (e.g. Warlocks/Battle Masters or Champions, respectively) and supercharges the classes that depend on long rests and were already somewhat above the curve (mostly full casters and especially Wizard). Given I do not share your opinion, and in fact have highlighted various ways in which the text both actually does fail to tell people what they're supposed to do, or does tell them but somehow gets ignored, I just don't agree with your absolute hardline "there cannot be mechanical changes, sorry" position. Bolded: No, it won't necessarily have that impact. That's exactly the assertion I refute. Doing so [I]poorly[/I] has such effects, specifically as a result of being a poor implementation. This is not a trade-off; we can in fact have both things. Exactly. It is a story of growth, of exceeding one's limits (or, indeed, transcending mortal limits entirely), which is a pretty friggin' big part of fantasy narratives in general. There's a reason fiction of all kinds, not just novels but games and film and TV shows etc. almost always feature epiphany and training, where opponents who used to be a terrible danger (sometimes even to the point of "nope, can't fight those, [I]just run away[/I]") become absolute chump change over time. Avatar: the Last Airbender, for example, presents ordinary firebenders as a pretty serious threat during the first season. By the middle of the third, even without the Day of Black Sun, Team Avatar can [I]easily[/I] defeat ordinary firebenders and really only fear folks like Combustion Man, Azula, or Ozai. I'm not sure I entirely understand what you mean by "the fiction of paragon tier in mechanically heroic tier terms." Do you mean that, in a sense, the [I]fiction[/I] sweet-spot gets expanded to cover a different level range? Or do you mean something else? If that is what you mean, I personally would say that it's really a difference of setting the "scaling factor" of a game. Heroic is small-time, Paragon is big leagues, and Epic is world-shaking, but choice of campaign setting and focus can change what those things mean. Neverwinter, being an FR game, is heavily trafficking in otherworldly stuff (much as Planescape does), and thus its scale has only a very brief period in early heroic for totally mundane challenges, and tops out in high epic with the theoretical potential to not just slay gods but fundamentally rewrite the rules of existence--effectively shifting [I]everything[/I] up by around half a tier. DS, meanwhile, shifts everything in the other direction by half a tier or a bit more--early on it really is the case that fighting random (relatively) mundane desert creatures is a risky move, like how random sewer rats in an RPG can be a terrifying early threat, and you top out fighting beings who are attempting to ascend to the level of something like a demigod and maybe, [I]maybe[/I] finding a way to heal the wounds of the world...or at least make the region you live in suck less. Again, not seeing that, so I can't answer the question. They aren't changed arbitrarily. They are changed for very specific reasons. There isn't a static benchmark because [I]the benchmark is the player experience, which is dynamic[/I]. Mechanical representation is not the master, driving player experience before it and callously indifferent to how those mechanics will be experienced through play. [I]If[/I] you choose to do this (and you do not have to! You can quite easily use monsters even within a +/- [I]8[/I] level range if you feel like it, the rules even say so!), the mechanical representation changes specifically because mechanics are there to encode and represent the player experience, not to be some imperious objective reality and [I]hope[/I] that that reality actually produces the experience so intended. For someone who so thoroughly espouses the "the rules are not the master, I am" philosophy as far as I can tell, your desire for this static benchmark to be your master, to which you must adhere no matter what, is genuinely baffling. Designing a 4e monster is thus a matter of genuinely thinking about what the creature is, and what the experience of fighting it should be. At level 1, a frost giant isn't even a solo--it's a [I]force of nature[/I], something the party has no hope whatsoever of [I]defeating[/I] in battle, and must either flee from it, entrap it, or outsmart it, aka, a skill challenge. But you shouldn't be designing a fight, or a combat, or whatever else, from the starting point of "I need to have a level X fight because my players are level X." You should come up with the concept of what the fight [I]actually is[/I], the fiction, and then develop mechanics which suit that fiction. Sometimes, that will mean that the best mechanical representation of a creature is a minion, even though the players have fought a creature like that before and it wasn't a minion. That's fine--because the objective fiction reality is still there, you're just adjusting how that manifests in mechanics in order to accurately portray whatever that thing is [I]now[/I], in [I]this[/I] context. This is not "undermining" anything. It is simply recognizing that mechanics are always an abstraction, and that we can (and, I argue, should) adapt that abstraction so that it invites the desired experience of play, rather than hoping to luck into (or brute-force) an experience of play by throwing utterly unchanged abstractions against a party with slightly different numerical values. NO. THEY. ARE. NOT. This is a pernicious [I]falsehood.[/I] The books [I]explicitly reject doing this[/I]. Repeatedly. I have dug up the quotes before, I can do it again. Enemies are NOT "always level appropriate." I'm certain you've read the 4e DMG, so you should know better. And if you haven't, why are you staking such strident claims on the basis of nothing better than hearsay? That is not the culture of play. That is WotC. WotC is making revisions, yes. And if you hadn't noticed, those revisions are not exactly the most popular thing! We have a poll [I]right now[/I] asking whether people will adopt 5.5e, and it's currently 54% yes, 46% no. I wouldn't call that a ringing endorsement of new stuff! But what I was actually talking about was 3PP and genuinely [I]new[/I] mechanics, not just additional options for classes or feats or the like. I stand by what I said with regard to that. The culture of play for 5e--what the actual people running it tend to do--is the most hidebound I've ever seen D&D be. Far moreso than any edition first published during my lifetime (which would be 2e and up.) Not at all. It is representing the fact that these things [I]do[/I] still pose some challenge, but the kind of challenge they pose is different now. It is the same creature. The fictional reality has not changed. The mechanics have. Because mechanics are not fictional reality, and cannot be--the map is not the territory. You are asking for every globe to have precise-to-the-meter topographical maps and street-view data. That is not productive nor useful for any globe, even a dynamically flexible one like Google Earth. The types and manners of information presented to the viewer [I]should[/I] change as the scale and perspective change. The physical reality--the Earth itself--is not changing in any way. But the data furnished to you from a scale of 500 miles to the inch (or 300 km per cm, or whatever you prefer) [I]should[/I] be different from the data furnished to you from a scale of 100 feet to the inch, even if in both cases you are centered on the same latitude and longitude. Some details that are essential at the 500 mile scale are utterly meaningless at the 100' scale and vice-versa. The text of 4e's DMG explicitly says you should not do this, and in fact it adds (again, explicitly) that it is sometimes wise to have players truly face the exact same monster--no mechanical changes at all--so they can see how much their characters have grown. Those would in fact be [I]different[/I] creatures. Not the same creatures. If you're fighting an actually-more-powerful creature in an area you've been to before, it's because something there has changed and more powerful creatures have shown up. Correction: A minion ogre is the same [I]creature[/I], but its mechanics have changed, because mechanics are contextual. In the context of "we have had one adventure together rescuing the miller's daughter," a single ogre is a dangerous and risky opponent which should not be underestimated. In the context of seasoned adventurers who have visited other planes and dealt with the servants of fey ladies and kings of shadow, an ogre is a nuisance, albeit still a danger. In the context of demigods who regularly show the deities themselves that they're not to be trifled with, a single ogre doesn't even rise to the level of [I]nuisance[/I] anymore. That shift from "terrifying" to "nuisance" to "non-entity (in isolation)" is represented with mechanics. Because mechanics are an abstraction, and that abstraction should serve us, not command us. I mean, potentially it [I]could[/I] be the same ogre. That could even be good fun; you fight [I]literally[/I] the same ogre (say) six times from level 1-ish to level 18ish, initially as a skill challenge, then progressively a solo, an elite, a standard, a minion, and finally as a single soldier amongst a squad. A direct and palpable representation of how far the characters have come--literally a threat they [I]couldn't[/I] threaten at the start of the campaign is now a puny nothing before them. As stated: the 4e DMG explicitly, repeatedly, instructs the DM to [I]not[/I] do things like this. It could not possibly be more clear that this is a thing you shouldn't do, without writing in large, friendly letters "DO NOT DO THIS THING." 4e's encounter design sections (there's a few of them, looking at encounter design from different perspectives) consistently state that you should use a variety, not just in flavor terms but in mechanical terms as well. What one might call "typical" fights are usually in the level +/- 2 range, but it explicitly suggests including [I]at minimum[/I] some fights +/- 4, potentially up to +/- 8 on occasion as spice, with the +8 side giving the players a real nasty problem, and the -8 side giving them a cakewalk that highlights their strengths. The use of these things is, as stated, always focused on what kind of player-experience they're designed to produce. And they aren't "not in the world anymore" in 4e either. "Weak" creatures would become one of the following, depending on context: [LIST] [*]Minions (creatures that can still do damage and are still non-trivial to hit, but which die as soon as they take any amount of damage; some homebrew ideas added the idea of "mooks," which are effectively [I]two-hit[/I] minions, they must take damage from two different sources to fall) [*]Swarms (a collection of creatures that are not dangerous alone, but are dangerous collectively, e.g. a swarm of insects or vampire bats or the like) [*]A skill challenge (fighting them isn't productive. you want to get rid of the problem for good; e.g. if you have an ant problem, squishing a thousand ants isn't going to make the problem go away, even though the ants might be genuinely incapable of harming you) [*]A "trap"/obstacle/feature/etc. rather than a creature proper (because, again, for particularly weak creatures, [I]killing[/I] them isn't productive, you must eliminate the underlying problem) [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Explain Bounded Accuracy to Me (As if I Was Five)
Top