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
*TTRPGs General
Monte Cook On Fumble Mechanics
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="pemerton" data-source="post: 7695387" data-attributes="member: 42582"><p>My apologies. I took you to be saying that when you said that such a conception of fumbles is overly narrow.</p><p></p><p>See, here, you seem to be agreeing with Monte Cook also - because you are just repeating what Charles Ryan has said is the whole point of the blog - that treating nat 1 as a major-screw-up is not a good approach, and is too narrow a conception of what might happen on a (so-called) "fumble".</p><p></p><p>I'm having trouble following this.</p><p></p><p>You seem to be saying that Charles Ryan actually disagrees with Monte Cook. Whereas Charles Ryan presents his post as an explanation and defence of the blog.</p><p></p><p>As I read it, Monte has written a blog saying that a nat 1 shouldn't be a major-screw-up-style fumble. Charles Ryan has weighed in agreeing with him, saying that a nat 1 can be broader than that, including encompassing events that (in the fiction) are not causally related to the action that (at the table) had an outcome determined by rolling a d20 that came up 1.</p><p></p><p>The key issue in both Monte's blog and Charles Ryan's post is a question about game design and game play (what to do on a nat 1), not a question of semantics (about the best use of the word "fumble"). Clearly there can be multiple uses of the word "fumble", but I think it's very clear how Monte was using it, and this clear sense in which he was using it has been confirmed by Charles Ryan's post. </p><p></p><p>So, to focus on the key issue: do you think Monte Cook and Charles Ryan are right, or wrong, when they say that nat 1=major-screw-up is not a good rule?</p><p></p><p>I think that Monte Cook's claim (and Charles Ryan's agreement) is probably about what is <em>typically</em> or <em>generally</em> enjoyable, rather than to what is <em>universally</em> fun and enjoyable.</p><p></p><p>As for the relationship between GM intrusions and imagined, ingame causation: I am relying on Monte Cook's and Charles Ryan's account of the system they design. I don't own it and don't play it. The posts I was engaging with were discussing GM intrusion as a device for introducing fictional events that are not, in the fiction, causally downstream of the PC's failure (eg following a missed bow shot, the arrival of reinforcements). This is also the sort of thing that the two designers were talking about. For instance, the blog says:</p><p></p><p style="margin-left: 20px"></p> <p style="margin-left: 20px">In a combat situation, a GM intrusion can range from the opposing creature gaining an additional chance to attack for a round, to reinforcements for the opposition showing up. It could mean that the character accidentally shoots a friend, or drops her weapon, or slips and falls, but those should be rare. Far more often, it should be some external circumstance that arises, and not something “wrong” that the character did.</p><p></p><p>Personally, I think it's fairly clear why Monte Cook and Charles Ryan make this suggestion: if the idea is that a nat 1 result should, in some way, <em>stand out</em> from a typical failure, then something <em>bigger</em> and more distinctive has to happen on a nat 1. But if that is not going to be a major-screw-up (which the designers think it shouldn't always, or even typically, be) then what is it going to be? And the natural answer is that it something that, within the fiction, is causally independent of the PC's action that fails. (As an aside: I assume that by "character driven" you mean <em>an event in the fiction that, in the fiction, is caused by the PC's failing at his/her action</em>.)</p><p> </p><p>If, in fact, there is an interesting and expansive set of fictional events that are:</p><p></p><p style="margin-left: 20px">(1) Distinctive from ordinary failure;</p> <p style="margin-left: 20px">(2) Not major screw-ups;</p> <p style="margin-left: 20px">(3) Able to be imagined, in the fiction, as caused by the PC's failed action;</p><p></p><p>then Monte Cook is wrong (and so is Charles Ryan in agreeing with him). Do you think there is such a set of fictional events?</p><p></p><p>But if there really were no such reason, then why would Monte Cook write a blog saying that "Far more often, it should be some external circumstance that arises, and not something “wrong” that the character did"?</p><p></p><p>One possibility is that he misunderstands his own system and the possibilities inherent in it.</p><p></p><p>But what I think is more likely is that he is reasoning more-or-less along the lines I've just set out: that he wants a nat 1 to be a <em>big</em> event, but <em>not</em> a major screw-up, and that there are simply not enough infiction possibilities that satisfy both these desiderata while nevertheless being causally downstream of the failed character action.</p><p></p><p>Anyway, I think the question about whether Monte Cook and Charles Ryan are correct about this is much more interesting than arguing over what the canonical use of the word "fumble" should be.</p></blockquote><p></p>
[QUOTE="pemerton, post: 7695387, member: 42582"] My apologies. I took you to be saying that when you said that such a conception of fumbles is overly narrow. See, here, you seem to be agreeing with Monte Cook also - because you are just repeating what Charles Ryan has said is the whole point of the blog - that treating nat 1 as a major-screw-up is not a good approach, and is too narrow a conception of what might happen on a (so-called) "fumble". I'm having trouble following this. You seem to be saying that Charles Ryan actually disagrees with Monte Cook. Whereas Charles Ryan presents his post as an explanation and defence of the blog. As I read it, Monte has written a blog saying that a nat 1 shouldn't be a major-screw-up-style fumble. Charles Ryan has weighed in agreeing with him, saying that a nat 1 can be broader than that, including encompassing events that (in the fiction) are not causally related to the action that (at the table) had an outcome determined by rolling a d20 that came up 1. The key issue in both Monte's blog and Charles Ryan's post is a question about game design and game play (what to do on a nat 1), not a question of semantics (about the best use of the word "fumble"). Clearly there can be multiple uses of the word "fumble", but I think it's very clear how Monte was using it, and this clear sense in which he was using it has been confirmed by Charles Ryan's post. So, to focus on the key issue: do you think Monte Cook and Charles Ryan are right, or wrong, when they say that nat 1=major-screw-up is not a good rule? I think that Monte Cook's claim (and Charles Ryan's agreement) is probably about what is [I]typically[/I] or [I]generally[/I] enjoyable, rather than to what is [I]universally[/I] fun and enjoyable. As for the relationship between GM intrusions and imagined, ingame causation: I am relying on Monte Cook's and Charles Ryan's account of the system they design. I don't own it and don't play it. The posts I was engaging with were discussing GM intrusion as a device for introducing fictional events that are not, in the fiction, causally downstream of the PC's failure (eg following a missed bow shot, the arrival of reinforcements). This is also the sort of thing that the two designers were talking about. For instance, the blog says: [indent] In a combat situation, a GM intrusion can range from the opposing creature gaining an additional chance to attack for a round, to reinforcements for the opposition showing up. It could mean that the character accidentally shoots a friend, or drops her weapon, or slips and falls, but those should be rare. Far more often, it should be some external circumstance that arises, and not something “wrong” that the character did.[/indent] Personally, I think it's fairly clear why Monte Cook and Charles Ryan make this suggestion: if the idea is that a nat 1 result should, in some way, [I]stand out[/I] from a typical failure, then something [I]bigger[/I] and more distinctive has to happen on a nat 1. But if that is not going to be a major-screw-up (which the designers think it shouldn't always, or even typically, be) then what is it going to be? And the natural answer is that it something that, within the fiction, is causally independent of the PC's action that fails. (As an aside: I assume that by "character driven" you mean [I]an event in the fiction that, in the fiction, is caused by the PC's failing at his/her action[/i].) If, in fact, there is an interesting and expansive set of fictional events that are: [indent](1) Distinctive from ordinary failure; (2) Not major screw-ups; (3) Able to be imagined, in the fiction, as caused by the PC's failed action;[/indent] then Monte Cook is wrong (and so is Charles Ryan in agreeing with him). Do you think there is such a set of fictional events? But if there really were no such reason, then why would Monte Cook write a blog saying that "Far more often, it should be some external circumstance that arises, and not something “wrong” that the character did"? One possibility is that he misunderstands his own system and the possibilities inherent in it. But what I think is more likely is that he is reasoning more-or-less along the lines I've just set out: that he wants a nat 1 to be a [I]big[/I] event, but [I]not[/I] a major screw-up, and that there are simply not enough infiction possibilities that satisfy both these desiderata while nevertheless being causally downstream of the failed character action. Anyway, I think the question about whether Monte Cook and Charles Ryan are correct about this is much more interesting than arguing over what the canonical use of the word "fumble" should be. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
Monte Cook On Fumble Mechanics
Top