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: 9286487" data-attributes="member: 6790260"><p>Which means the abstraction can, and should, change if doing so gets closer to the actual state of affairs.</p><p></p><p></p><p>Not at all. It follows that the rules should prioritize efficacy and functionality. "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines." Consistency is not an unalloyed good. It has many benefits, and thus we should not dismiss a <em>wise</em> consistency. I myself am an advocate for a wide variety of particular kinds of consistency, e.g. unified resolution mechanics, not on the brute fact that they are consistent, but rather because their consistency leads to something else that is valuable in itself, such as making it easier, simpler, and more natural to adjudicate, or to speed up the learning process (which is, was, and always will be the single greatest hurdle to getting people into the hobby.) Requiring that the rules rigidly produce only and exactly <em>one</em> description of something, when that thing's value is <em>necessarily</em> relative to the context in which it appears, is a foolish consistency, pulling us away from efficacy and functionality.</p><p></p><p></p><p>But that was exactly my point...?</p><p></p><p></p><p>But it <em>does</em> change. By definition! You don't get street view data when you're looking at the whole Earth. It isn't just too small to see, it is in fact <em>not there</em>. And once you zoom in to see the street view, geographic data like contour lines <em>isn't there</em>. It's genuinely <em>not displayed</em>. Because that's not what is useful or relevant in that context.</p><p></p><p>The globe itself remains what it is. Main Street is always <em>there</em>, in terms of the territory. But when we look at states and continents, we do not render Main Street. When we look at Main Street, we do not render states and continents. The data isn't simply "currently out of view." It is genuinely <em>not present on the map</em> until it is called up--and other data is necessarily put away when one does this. That's the whole point.</p><p></p><p>The map is not the territory--and different maps actually do have different information on them. The territory always remains whatever it is (I assume you grant that we're looking at the territory only in one particular moment.) But which parts of the territory are in fact on the map, and which ones are intentionally left off the map, varies by context. It is precisely the same with the level 2 solo ogre and the level 14 (or whatever) minion ogre. Different data has been represented in the abstraction, because we have proverbially "zoomed out."</p><p></p><p></p><p>You have simply made the argument circular. It is consistent because it must be; it must be consistent because it is.</p><p></p><p>I'm saying that it is <em>useful</em> to allow non-consistency in this context, because the thing we wish to represent--the danger posed by this threat--IS different today than it was six months ago. The creature is the same, but the context is different, and the context is always what matters.</p><p></p><p></p><p>Except that there <em>is</em> a reason. The 88-HP ogre <em>cannot</em> produce the kind of experience you intend with this. It just can't. That's the whole point. You are hoping and praying that coincidence will fall in your favor. We can do better; we can <em>design</em> better.</p></blockquote><p></p>
[QUOTE="EzekielRaiden, post: 9286487, member: 6790260"] Which means the abstraction can, and should, change if doing so gets closer to the actual state of affairs. Not at all. It follows that the rules should prioritize efficacy and functionality. "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines." Consistency is not an unalloyed good. It has many benefits, and thus we should not dismiss a [I]wise[/I] consistency. I myself am an advocate for a wide variety of particular kinds of consistency, e.g. unified resolution mechanics, not on the brute fact that they are consistent, but rather because their consistency leads to something else that is valuable in itself, such as making it easier, simpler, and more natural to adjudicate, or to speed up the learning process (which is, was, and always will be the single greatest hurdle to getting people into the hobby.) Requiring that the rules rigidly produce only and exactly [I]one[/I] description of something, when that thing's value is [I]necessarily[/I] relative to the context in which it appears, is a foolish consistency, pulling us away from efficacy and functionality. But that was exactly my point...? But it [I]does[/I] change. By definition! You don't get street view data when you're looking at the whole Earth. It isn't just too small to see, it is in fact [I]not there[/I]. And once you zoom in to see the street view, geographic data like contour lines [I]isn't there[/I]. It's genuinely [I]not displayed[/I]. Because that's not what is useful or relevant in that context. The globe itself remains what it is. Main Street is always [I]there[/I], in terms of the territory. But when we look at states and continents, we do not render Main Street. When we look at Main Street, we do not render states and continents. The data isn't simply "currently out of view." It is genuinely [I]not present on the map[/I] until it is called up--and other data is necessarily put away when one does this. That's the whole point. The map is not the territory--and different maps actually do have different information on them. The territory always remains whatever it is (I assume you grant that we're looking at the territory only in one particular moment.) But which parts of the territory are in fact on the map, and which ones are intentionally left off the map, varies by context. It is precisely the same with the level 2 solo ogre and the level 14 (or whatever) minion ogre. Different data has been represented in the abstraction, because we have proverbially "zoomed out." You have simply made the argument circular. It is consistent because it must be; it must be consistent because it is. I'm saying that it is [I]useful[/I] to allow non-consistency in this context, because the thing we wish to represent--the danger posed by this threat--IS different today than it was six months ago. The creature is the same, but the context is different, and the context is always what matters. Except that there [I]is[/I] a reason. The 88-HP ogre [I]cannot[/I] produce the kind of experience you intend with this. It just can't. That's the whole point. You are hoping and praying that coincidence will fall in your favor. We can do better; we can [I]design[/I] better. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Explain Bounded Accuracy to Me (As if I Was Five)
Top