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
Modeling Uncertainty
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="Guest 6801328" data-source="post: 7001767"><p>Because it's the product of study and specialized knowledge, not intuition and hunches. </p><p></p><p>Or, to dive a little bit deeper, if you make a mistake building a bomb it's because you made a mistake. And the dice roll says you didn't make a mistake. The underlying principles are not bayesian or stochastic. </p><p></p><p>But if you're trying to intuit whether a guard is lying, even if you've been foolish enough to pay for a course in how to detect lies you're still applying probabilities, not certainties. "When people behave such-and-such a way it <em>probably</em> means they are lying."</p><p></p><p>So even if you apply those principles without making a mistake they still aren't guaranteed to produce the right answer.</p><p></p><p>How's that?</p><p></p><p></p><p></p><p>That reduces the chances, and also reduces the character's confidence that they will succeed, but has no change on their confidence that they have succeeded. Again, you may not want that sort of uncertainty in your game (which is understandable because it's not, as far as I'm aware, baked into <em>any</em> RPG) but I do, which is why I started the thread.</p><p></p><p></p><p></p><p>Yes, there are various ways to introduce the kind of uncertainty I'm talking about; the difference becomes the probabilities that are generated.</p><p></p><p></p><p></p><p>Also in this specific scenario, you could roll the check at the point of the wire cutting, so the PC is deciding solely on how good he is at the task in question. That does leave the PC without any interesting options to mitigate the effect of a poor roll though.</p><p></p><p>The only way I see this scenario as being interesting is this:</p><p>1. present it.</p><p>2. player makes a roll to see if he knows which wire to cut. Whether his roll is good or bad, he isn't likely to be confident in the answer unless you've done something like told him the DC up front.</p><p>3. optionally the DM rolls an opposed check to add some extra uncertainty, which could cause the bomb to fail despite the player botching his roll, or cause the bomb to explode despite him doing well at it.</p><p></p><p>I'm not sure how your extra rule would help here. If the PC is only just beating the DC of the device, there's already uncertainty. Heck, if your narrative is strong, he's not going to be confident that he has the device beat because he doesn't know the DC.</p><p></p><p></p><p></p><p>As noted previously that's an erroneous characterization. If you are good at something then on any given attempt you still have a higher probability of succeeding.</p><p></p><p></p><p></p><p>Almost. There are different kinds of uncertainty.</p><p></p><p></p><p></p><p>Seriously? Choosing Insight as one of your skills suddenly becomes a bad investment? Sheesh.</p><p></p><p></p><p></p><p>Oh, ok, so it was the first version. I don't know why you think this is hard. Remember that the fluff in this case is purely fluff. "You think he's lying because he won't make eye contact." "You think it's the left passage because you think you feel a slight draught." "You think it's the red wire because your bomb disposal instructor told you that 66% of the time it's the red wire." Whatever. Unlike the approach where the DM is trying to actually convey the probability with the rationale, in this case the believability of the rationale has no impact on the player's understanding of the probabilities. </p><p></p><p>DM: "You think it's the red wire because last night you had a dream where everything was red."</p><p>Player: "Yeah, whatever. I beat the TN by 7 so I have a 1/6 chance of being wrong."</p><p></p><p>Again, if that's the case, why does the skill apply to it at all? And why do all insight checks fall into the "just a hunch" bucket?</p><p></p><p></p><p></p><p>(Funny you mentioned 3 wires...see my next post, which is what I logged on to write.)</p><p></p><p>It's not impossible to get the duke's nickname wrong. The difference is that thinking somebody lying is a hunch (see above) not a retrievable fact. I mean, the duke's nickname COULD be a hunch and if, depending on the scenario, the DM decided that uncertainty would add to dramatic tension, this rule could still be used. Similarly (or conversely), whether or not the guard is lying might not really have much impact on the story, in which case I wouldn't bother with the uncertainty. </p><p></p><p>Why do I sense so much hostility from you toward this whole idea? Or is it hostility toward me personally?</p></blockquote><p></p>
[QUOTE="Guest 6801328, post: 7001767"] Because it's the product of study and specialized knowledge, not intuition and hunches. Or, to dive a little bit deeper, if you make a mistake building a bomb it's because you made a mistake. And the dice roll says you didn't make a mistake. The underlying principles are not bayesian or stochastic. But if you're trying to intuit whether a guard is lying, even if you've been foolish enough to pay for a course in how to detect lies you're still applying probabilities, not certainties. "When people behave such-and-such a way it [I]probably[/I] means they are lying." So even if you apply those principles without making a mistake they still aren't guaranteed to produce the right answer. How's that? That reduces the chances, and also reduces the character's confidence that they will succeed, but has no change on their confidence that they have succeeded. Again, you may not want that sort of uncertainty in your game (which is understandable because it's not, as far as I'm aware, baked into [I]any[/I] RPG) but I do, which is why I started the thread. Yes, there are various ways to introduce the kind of uncertainty I'm talking about; the difference becomes the probabilities that are generated. Also in this specific scenario, you could roll the check at the point of the wire cutting, so the PC is deciding solely on how good he is at the task in question. That does leave the PC without any interesting options to mitigate the effect of a poor roll though. The only way I see this scenario as being interesting is this: 1. present it. 2. player makes a roll to see if he knows which wire to cut. Whether his roll is good or bad, he isn't likely to be confident in the answer unless you've done something like told him the DC up front. 3. optionally the DM rolls an opposed check to add some extra uncertainty, which could cause the bomb to fail despite the player botching his roll, or cause the bomb to explode despite him doing well at it. I'm not sure how your extra rule would help here. If the PC is only just beating the DC of the device, there's already uncertainty. Heck, if your narrative is strong, he's not going to be confident that he has the device beat because he doesn't know the DC. As noted previously that's an erroneous characterization. If you are good at something then on any given attempt you still have a higher probability of succeeding. Almost. There are different kinds of uncertainty. Seriously? Choosing Insight as one of your skills suddenly becomes a bad investment? Sheesh. Oh, ok, so it was the first version. I don't know why you think this is hard. Remember that the fluff in this case is purely fluff. "You think he's lying because he won't make eye contact." "You think it's the left passage because you think you feel a slight draught." "You think it's the red wire because your bomb disposal instructor told you that 66% of the time it's the red wire." Whatever. Unlike the approach where the DM is trying to actually convey the probability with the rationale, in this case the believability of the rationale has no impact on the player's understanding of the probabilities. DM: "You think it's the red wire because last night you had a dream where everything was red." Player: "Yeah, whatever. I beat the TN by 7 so I have a 1/6 chance of being wrong." Again, if that's the case, why does the skill apply to it at all? And why do all insight checks fall into the "just a hunch" bucket? (Funny you mentioned 3 wires...see my next post, which is what I logged on to write.) It's not impossible to get the duke's nickname wrong. The difference is that thinking somebody lying is a hunch (see above) not a retrievable fact. I mean, the duke's nickname COULD be a hunch and if, depending on the scenario, the DM decided that uncertainty would add to dramatic tension, this rule could still be used. Similarly (or conversely), whether or not the guard is lying might not really have much impact on the story, in which case I wouldn't bother with the uncertainty. Why do I sense so much hostility from you toward this whole idea? Or is it hostility toward me personally? [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Modeling Uncertainty
Top