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
*Dungeons & Dragons
How do you prep/run stealth missions?
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="Imaculata" data-source="post: 7827910" data-attributes="member: 6801286"><p>I designed a dungeon once where the players had to bypass an army of skeleton pirates. Stealth was encouraged, but not mandated, because you can never force your players to do what you want them to do.</p><p></p><p>Instead, what I prefer to do is offer a lot of options to my players. This means including branching paths in the dungeon, and making stealth the easiest approach for them. For this to work there should be an initial opportunity for the players to get a glimpse of what they're up against, without immediately getting caught. So the first encounter with the guards requires <strong><u>no check</u></strong>, the players can simply see the guards from a safe position, without being spotted. This allows the players to get an idea what the positions of the guards are, how to stay out of sight, what their patrol routes are, and form a plan.</p><p></p><p><strong>Patrols</strong></p><p>I try to make guard patrols very simple and easy to understand. While a real guard would not be this predictable, I tend to wave realism away in favor of gameplay. I treat this like a computer game, by having every guard behave predictably and simple. Some guards may stay in one place constantly, and merely face different directions every now and then. While other guards simply move from A to B and back again. This allows the players to clearly state an approach, such as: "<em>I wait till the guard on the tower is looking away from us</em>", or "<em>I wait till the guard walks towards us, and then grab him as he turns around</em>".</p><p></p><p><strong>Cover spots</strong></p><p>You'll want to include plenty of cover for the players, so they have things to hide behind. And they should be able to take out some of the guards without being spotted by the rest. The players may want to wait for one guard to be alone, and then quickly drag him behind cover to quietly take him out.</p><p></p><p><strong>Height differences</strong></p><p>I also tend to include lots of height differences, because this provides more ways for the players to stay out of the line of sight of guards. For example, a guard on a bridge will probably not notice a player swimming underneath it, or swimming entirely underwater. Where as a guard on a balcony will be able to see very far, but will have a blindspot underneath the balcony it is standing on.</p><p></p><p><strong>Not too many checks</strong></p><p>The more rolls the players need to make, the higher the chance their stealth fails, despite their best efforts. Unlucky rolls are always lurking, so try not to force too many rolls on your players if you want them to consider stealth a valid option. Because statistically, they are eventually going to make a bad roll. For example, if a player has to cross an area without being noticed by guards, that should require just one stealth check, even if there are multiple guards. You could even decide that only one party member makes all the stealth checks, and he then helps the other players cross unnoticed. This simplifies the stealth a lot, and makes the stealth not hinge on the weakest link of the party.</p><p></p><p><strong>Failure conditions</strong></p><p>But as a DM you need to have a plan regarding what happens when the stealth fails. Is the entire dungeon alerted? Or is only a small section alerted? Can the players perhaps intercept a guard who runs for an alarm bell? I tend to be rather lenient in this regard, because the players aren't perfect. They make mistakes, and they can have an unlucky roll.</p><p></p><p><strong><span style="color: rgb(184, 49, 47)">Most importantly:</span></strong> One failed stealth check should not immediately alert all the guards, it may just draw their attention to a suspicious noise, leading to an exciting challenge where the players must hide from sight, kill the guard quietly or distract the guard. <span style="color: rgb(0, 0, 0)">As long as the guards are unaware of the presence of the players, one strange sound is no reason to sound the alarm... yet.</span> <span style="color: rgb(0, 0, 0)">Use this as an opportunity to build suspense, rather than punish the players for making a bad roll.</span></p><p><span style="color: rgb(0, 0, 0)"></span></p><p><span style="color: rgb(0, 0, 0)"><strong>Drunk, stupid and talking guards</strong></span></p><p><span style="color: rgb(0, 0, 0)">These are best to teach your players how to use stealth, so use them early. Drunk/stupid guards are easy to bypass and easy to fool. They don't pay a lot of attention and can add a bit of humor to your stealth challenge. I also like to give my guards dialogue that my players can overhear. Guards that are talking are an easy tool for exposition, giving the players information about the dungeon and the guards themselves, plus a talking guard is distracted, so easy to bypass. </span></p><p></p><p><strong>Monster guards</strong></p><p>Lastly, if the players need to sneak past monsters, this may be easier or harder, depending on the monsters. A dragon could easily sniff out any intruders and has excellent hearing, while skeletons possibly can't hear any sounds at all. Orc guards could be stupid and easy to fool with a simple distraction. Undead will probably not follow up on a false alarm, and resume their usual patrols unaware of the player's presence. Plus they usually can't communicate with each other. Give some thought to the level of intelligence of your guards and how this affects their behavior.</p></blockquote><p></p>
[QUOTE="Imaculata, post: 7827910, member: 6801286"] I designed a dungeon once where the players had to bypass an army of skeleton pirates. Stealth was encouraged, but not mandated, because you can never force your players to do what you want them to do. Instead, what I prefer to do is offer a lot of options to my players. This means including branching paths in the dungeon, and making stealth the easiest approach for them. For this to work there should be an initial opportunity for the players to get a glimpse of what they're up against, without immediately getting caught. So the first encounter with the guards requires [B][U]no check[/U][/B], the players can simply see the guards from a safe position, without being spotted. This allows the players to get an idea what the positions of the guards are, how to stay out of sight, what their patrol routes are, and form a plan. [B]Patrols[/B] I try to make guard patrols very simple and easy to understand. While a real guard would not be this predictable, I tend to wave realism away in favor of gameplay. I treat this like a computer game, by having every guard behave predictably and simple. Some guards may stay in one place constantly, and merely face different directions every now and then. While other guards simply move from A to B and back again. This allows the players to clearly state an approach, such as: "[I]I wait till the guard on the tower is looking away from us[/I]", or "[I]I wait till the guard walks towards us, and then grab him as he turns around[/I]". [B]Cover spots[/B] You'll want to include plenty of cover for the players, so they have things to hide behind. And they should be able to take out some of the guards without being spotted by the rest. The players may want to wait for one guard to be alone, and then quickly drag him behind cover to quietly take him out. [B]Height differences[/B] I also tend to include lots of height differences, because this provides more ways for the players to stay out of the line of sight of guards. For example, a guard on a bridge will probably not notice a player swimming underneath it, or swimming entirely underwater. Where as a guard on a balcony will be able to see very far, but will have a blindspot underneath the balcony it is standing on. [B]Not too many checks[/B] The more rolls the players need to make, the higher the chance their stealth fails, despite their best efforts. Unlucky rolls are always lurking, so try not to force too many rolls on your players if you want them to consider stealth a valid option. Because statistically, they are eventually going to make a bad roll. For example, if a player has to cross an area without being noticed by guards, that should require just one stealth check, even if there are multiple guards. You could even decide that only one party member makes all the stealth checks, and he then helps the other players cross unnoticed. This simplifies the stealth a lot, and makes the stealth not hinge on the weakest link of the party. [B]Failure conditions[/B] But as a DM you need to have a plan regarding what happens when the stealth fails. Is the entire dungeon alerted? Or is only a small section alerted? Can the players perhaps intercept a guard who runs for an alarm bell? I tend to be rather lenient in this regard, because the players aren't perfect. They make mistakes, and they can have an unlucky roll. [B][COLOR=rgb(184, 49, 47)]Most importantly:[/COLOR][/B] One failed stealth check should not immediately alert all the guards, it may just draw their attention to a suspicious noise, leading to an exciting challenge where the players must hide from sight, kill the guard quietly or distract the guard. [COLOR=rgb(0, 0, 0)]As long as the guards are unaware of the presence of the players, one strange sound is no reason to sound the alarm... yet.[/COLOR] [COLOR=rgb(0, 0, 0)]Use this as an opportunity to build suspense, rather than punish the players for making a bad roll. [B]Drunk, stupid and talking guards[/B] These are best to teach your players how to use stealth, so use them early. Drunk/stupid guards are easy to bypass and easy to fool. They don't pay a lot of attention and can add a bit of humor to your stealth challenge. I also like to give my guards dialogue that my players can overhear. Guards that are talking are an easy tool for exposition, giving the players information about the dungeon and the guards themselves, plus a talking guard is distracted, so easy to bypass. [/COLOR] [B]Monster guards[/B] Lastly, if the players need to sneak past monsters, this may be easier or harder, depending on the monsters. A dragon could easily sniff out any intruders and has excellent hearing, while skeletons possibly can't hear any sounds at all. Orc guards could be stupid and easy to fool with a simple distraction. Undead will probably not follow up on a false alarm, and resume their usual patrols unaware of the player's presence. Plus they usually can't communicate with each other. Give some thought to the level of intelligence of your guards and how this affects their behavior. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
How do you prep/run stealth missions?
Top