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
Do you let PC's just *break* objects?
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="Charlaquin" data-source="post: 9047945" data-attributes="member: 6779196"><p>It’s cool, sorry if I came across as obtuse, I just feel like the benefit of asking for additional clarity was self-evident in the case under discussion in this thread, in which the OP explicitly stated that the player may have had a different goal that the DM assumed or forgotten to mention details of their approach, and that those facts were the specific reasons they would rule the way they do.</p><p></p><p>To your Message example, “I cast message and say [whatever]” is a complete action declaration in my mind. It clearly communicates what you want to happen (for the target of the spell to receive the intended message) and what your character does to try and make that happen (cast the <em>message</em> spell). No further detail is necessary. Likewise, in the example that started this whole tangent, the action declaration “I try to destroy the warship with one punch” is also a complete action declaration in my mind. It includes both a goal (destroy the warship) and an approach (punch it once). That’s everything I need to know to determine how to resolve the action. It would, at my table, fail without a roll of any kind being called for, because at least in the kinds of worlds I like to run in D&D, even the strongest playable character would not be able to destroy a warship by punching it a single time. Maybe it would be more plausible in a game using the genre conventions of superhero comics, but not my D&D games.</p><p></p><p>For an example of an action declaration that <em>isn’t</em> complete to my mind, look at the “I smash the vase” one from earlier in this thread. As I said in my response to that post, that tells me what the player wants to happen as a result of their action (for the vase to be broken), but not what their character is doing to try and accomplish that. Are they picking it up and throwing it against the wall? Are they pushing it over and allowing it to fall to the floor? Are they bringing the pommel of their sword down on it? Are they squeezing it between their hands as hard as they can? The reason this information matters is that it might be relevant in how I resolve the action. For example, maybe the vase contains valuables that could be damaged or lost when it’s thrown. Or maybe it’s coated with a contact poison*. Or maybe it’s sitting on a pressure-sensitive plate like the idol in the opening scene of <em>raiders of the lost arc</em>. There are all sorts of reasons I might need to know how the character is going about trying to smash the vase in order to determine the possible results of that action and make the best call as to what rules (if any) need to be invoked to resolve any uncertainty in the possible results.</p><p></p><p>And as [USER=29398]@Lanefan[/USER] pointed out, in a post that you liked, if I were to accept “I smash the vase” alone as a general rule and only asked for additional detail when it’s relevant, asking for additional detail would indicate to the player that it is relevant, and may impact their decision making. Maybe they were imagining squeezing the vase between their hands, but the fact that I asked them how they try to smash it makes them suspicious, so instead they decide to nudge it off its platform with a 10-foot pole instead. And certainly if I simply assume how they go about trying to smash the vase, there’s a high likelihood that the player will take issue with my assumptions, especially if the action has any negative outcomes they think they might have been able to avoid had they gone about it a different way (whether or not they had any action intentions of doing it in the hypothetical way they imagine would have prevented those consequences).</p><p></p><p>Better, in my mind, to make the general rule that action declarations must always include both goal and approach. Excessive detail is not necessary - as we’ve seen “I cast message and say [whatever]” and “I try to destroy the warship in one punch” are perfectly sufficient action declarations by this standard. The suggestion I give if anyone is unsure whether an action declaration includes the necessary information is, if you can phrase it as “I try to <strong>__ </strong>by<strong> __</strong>,” it will in almost all cases be sufficient. And the nice thing is, by setting this standard, I can always ask for clarification if needed, without making the player think there’s something specific about <em>this</em> action that they need to be cautious of. Because that information is a requirement for <em>all</em> actions.</p><p></p><p>*For the record, I don’t actually use contact poison as a trap, because it doesn’t make a lick of sense. It’s just a convenient example of a reason it might be relevant whether or not a character touches a vase.</p></blockquote><p></p>
[QUOTE="Charlaquin, post: 9047945, member: 6779196"] It’s cool, sorry if I came across as obtuse, I just feel like the benefit of asking for additional clarity was self-evident in the case under discussion in this thread, in which the OP explicitly stated that the player may have had a different goal that the DM assumed or forgotten to mention details of their approach, and that those facts were the specific reasons they would rule the way they do. To your Message example, “I cast message and say [whatever]” is a complete action declaration in my mind. It clearly communicates what you want to happen (for the target of the spell to receive the intended message) and what your character does to try and make that happen (cast the [I]message[/I] spell). No further detail is necessary. Likewise, in the example that started this whole tangent, the action declaration “I try to destroy the warship with one punch” is also a complete action declaration in my mind. It includes both a goal (destroy the warship) and an approach (punch it once). That’s everything I need to know to determine how to resolve the action. It would, at my table, fail without a roll of any kind being called for, because at least in the kinds of worlds I like to run in D&D, even the strongest playable character would not be able to destroy a warship by punching it a single time. Maybe it would be more plausible in a game using the genre conventions of superhero comics, but not my D&D games. For an example of an action declaration that [I]isn’t[/I] complete to my mind, look at the “I smash the vase” one from earlier in this thread. As I said in my response to that post, that tells me what the player wants to happen as a result of their action (for the vase to be broken), but not what their character is doing to try and accomplish that. Are they picking it up and throwing it against the wall? Are they pushing it over and allowing it to fall to the floor? Are they bringing the pommel of their sword down on it? Are they squeezing it between their hands as hard as they can? The reason this information matters is that it might be relevant in how I resolve the action. For example, maybe the vase contains valuables that could be damaged or lost when it’s thrown. Or maybe it’s coated with a contact poison*. Or maybe it’s sitting on a pressure-sensitive plate like the idol in the opening scene of [I]raiders of the lost arc[/I]. There are all sorts of reasons I might need to know how the character is going about trying to smash the vase in order to determine the possible results of that action and make the best call as to what rules (if any) need to be invoked to resolve any uncertainty in the possible results. And as [USER=29398]@Lanefan[/USER] pointed out, in a post that you liked, if I were to accept “I smash the vase” alone as a general rule and only asked for additional detail when it’s relevant, asking for additional detail would indicate to the player that it is relevant, and may impact their decision making. Maybe they were imagining squeezing the vase between their hands, but the fact that I asked them how they try to smash it makes them suspicious, so instead they decide to nudge it off its platform with a 10-foot pole instead. And certainly if I simply assume how they go about trying to smash the vase, there’s a high likelihood that the player will take issue with my assumptions, especially if the action has any negative outcomes they think they might have been able to avoid had they gone about it a different way (whether or not they had any action intentions of doing it in the hypothetical way they imagine would have prevented those consequences). Better, in my mind, to make the general rule that action declarations must always include both goal and approach. Excessive detail is not necessary - as we’ve seen “I cast message and say [whatever]” and “I try to destroy the warship in one punch” are perfectly sufficient action declarations by this standard. The suggestion I give if anyone is unsure whether an action declaration includes the necessary information is, if you can phrase it as “I try to [B]__ [/B]by[B] __[/B],” it will in almost all cases be sufficient. And the nice thing is, by setting this standard, I can always ask for clarification if needed, without making the player think there’s something specific about [I]this[/I] action that they need to be cautious of. Because that information is a requirement for [I]all[/I] actions. *For the record, I don’t actually use contact poison as a trap, because it doesn’t make a lick of sense. It’s just a convenient example of a reason it might be relevant whether or not a character touches a vase. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Do you let PC's just *break* objects?
Top