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
Community
General Tabletop Discussion
*Dungeons & Dragons
"Run away! Run away!" ... what if they don't?
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="hawkeyefan" data-source="post: 7452607" data-attributes="member: 6785785"><p>I don't think that any single one of them is bad, really, but I generally do see a TPK as a bad thing. Sure, there may be examples that folks can provide where a TPK was fun and rewarding, and perhaps even furthered the story. This is why I'm not saying that a TPK should absolutely never happen. I question it as advice given to a DM who asks how to handle a situation where his players have foolishly gone up against an encounter that is too tough for them. </p><p></p><p></p><p></p><p></p><p>Who made the list that you rolled from? Who placed the area that list pertains to? </p><p></p><p>Setting aside the whole "neutral DM" aspect of the discussion, the DM has still made several choices in regards to this. So even if ultimately, a die is used to randomize the encounter....the die is randomizing from details chosen by the DM. </p><p></p><p>Even if it's a list in a published game book, the DM has chosen that list. And this is fine....I am not saying this is a bad thing, or a bad way to handle it....but the DM has made choices about these things. He is not absolved of responsibility for them. </p><p></p><p></p><p></p><p>This is not about keeping the PCs safe. It's about letting them know that the danger may be too great. For example, naming the hills the Giant Hills and having the PCs hear of giant attacks, and maybe speaking to a veteran NPC missing an arm who tells them if they ever see a giant, they should run. Those are the kinds of things I am talking about. Now, those seem to be reasonable warning signs. However, since this is a game, the players may actually see things like that as a dare. This is why I say that the DM is responsible to make sure things are clear....because different players may pick up on different cues, and what's an "obvious warning" to one player is seen differently by another. </p><p></p><p>So I have to disagree that this is not your job. The DM has to try and portray the world to the players so that they can make informed decisions. It's not about keeping them safe....it's about letting them make as informed a decision as possible.</p><p></p><p></p><p></p><p>Glad we agree here!</p><p></p><p></p><p></p><p>In this case, I mean more about the decisions of monsters/enemy NPCs. When the tide of the combat seems to turn against the PCs, the DM is able to ease off a bit....there's no reason that he has to continue to run the bad guys as perfectly efficient killing machines who will not take a moment to gloat, or waste an action in some other way. There can be plenty of story related reasons for this. Yes, a lot of this depends on the reason for the combat and the creatures involved, but my point is that this is another decision point where the DM has the ability to influence the likelihood of a TPK. </p><p></p><p></p><p></p><p>What about when PCs flee? That's what I was taking about. Again, I think it depends on the context of the fight, and the enemy motivation for the combat, but in most instances it would be pretty easy to justify letting PCs run away. Or if it's not, then the pursuit can be resolved with skills rather than continuing the combat, or the chase mechanics in teh DMG (weak as they may be) can be used to mitigate the results. </p><p></p><p></p><p></p><p>"Far too many factors" is what I am talking about. Any of those factors may allow the DM an opportunity to mitigate the deadliness of the encounter. The Bullette drags off the downed PC to eat rather than chase the other fleeing PCs, etc. </p><p></p><p>Even once all PCs are down....unless they've all failed 3 death saves, I don't see this as a TPK. Once the last goes down, I'd stop combat and then narrate what happens. They could be taken prisoner or wake up with their gear stolen or any other option we can come up with. </p><p></p><p></p><p></p><p>People also like stories where there is definitely no chance that the main character will die. And such stories are not inherently weaker. </p><p></p><p>(Also, Robb Stark was clearly an NPC, so no the RW was not a TPK <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":p" title="Stick out tongue :p" data-smilie="7"data-shortname=":p" />)</p><p></p><p>Having said that, I agree, I prefer that my game has the risk of PC death. There have been two from our current group. Stuff happens and sometimes there are bad results. But I don't think that's the same as going for a full on TPK. They don't happen by accident, despite the examples provided. A TPK has to have DM approval. </p><p></p><p>And that's fine if that's the game you're playing and that your players expect.....but as general advice? I think it's probably not a good idea.</p></blockquote><p></p>
[QUOTE="hawkeyefan, post: 7452607, member: 6785785"] I don't think that any single one of them is bad, really, but I generally do see a TPK as a bad thing. Sure, there may be examples that folks can provide where a TPK was fun and rewarding, and perhaps even furthered the story. This is why I'm not saying that a TPK should absolutely never happen. I question it as advice given to a DM who asks how to handle a situation where his players have foolishly gone up against an encounter that is too tough for them. Who made the list that you rolled from? Who placed the area that list pertains to? Setting aside the whole "neutral DM" aspect of the discussion, the DM has still made several choices in regards to this. So even if ultimately, a die is used to randomize the encounter....the die is randomizing from details chosen by the DM. Even if it's a list in a published game book, the DM has chosen that list. And this is fine....I am not saying this is a bad thing, or a bad way to handle it....but the DM has made choices about these things. He is not absolved of responsibility for them. This is not about keeping the PCs safe. It's about letting them know that the danger may be too great. For example, naming the hills the Giant Hills and having the PCs hear of giant attacks, and maybe speaking to a veteran NPC missing an arm who tells them if they ever see a giant, they should run. Those are the kinds of things I am talking about. Now, those seem to be reasonable warning signs. However, since this is a game, the players may actually see things like that as a dare. This is why I say that the DM is responsible to make sure things are clear....because different players may pick up on different cues, and what's an "obvious warning" to one player is seen differently by another. So I have to disagree that this is not your job. The DM has to try and portray the world to the players so that they can make informed decisions. It's not about keeping them safe....it's about letting them make as informed a decision as possible. Glad we agree here! In this case, I mean more about the decisions of monsters/enemy NPCs. When the tide of the combat seems to turn against the PCs, the DM is able to ease off a bit....there's no reason that he has to continue to run the bad guys as perfectly efficient killing machines who will not take a moment to gloat, or waste an action in some other way. There can be plenty of story related reasons for this. Yes, a lot of this depends on the reason for the combat and the creatures involved, but my point is that this is another decision point where the DM has the ability to influence the likelihood of a TPK. What about when PCs flee? That's what I was taking about. Again, I think it depends on the context of the fight, and the enemy motivation for the combat, but in most instances it would be pretty easy to justify letting PCs run away. Or if it's not, then the pursuit can be resolved with skills rather than continuing the combat, or the chase mechanics in teh DMG (weak as they may be) can be used to mitigate the results. "Far too many factors" is what I am talking about. Any of those factors may allow the DM an opportunity to mitigate the deadliness of the encounter. The Bullette drags off the downed PC to eat rather than chase the other fleeing PCs, etc. Even once all PCs are down....unless they've all failed 3 death saves, I don't see this as a TPK. Once the last goes down, I'd stop combat and then narrate what happens. They could be taken prisoner or wake up with their gear stolen or any other option we can come up with. People also like stories where there is definitely no chance that the main character will die. And such stories are not inherently weaker. (Also, Robb Stark was clearly an NPC, so no the RW was not a TPK :p) Having said that, I agree, I prefer that my game has the risk of PC death. There have been two from our current group. Stuff happens and sometimes there are bad results. But I don't think that's the same as going for a full on TPK. They don't happen by accident, despite the examples provided. A TPK has to have DM approval. And that's fine if that's the game you're playing and that your players expect.....but as general advice? I think it's probably not a good idea. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
"Run away! Run away!" ... what if they don't?
Top