Sneaking Around In Tabletop RPGs

Stealth checks are a mess. I have yet to meet or hear of a GM that actually uses stealth checks in any deterministic way when it involves more than a single "sneaker." Party stealth is the most common kind of stealth check made, and as far as I have experienced, the party just needs to roll a rough average above the difficulty to avoid detection. Like a skill challenge a la 4E. How else could you actually do it?

From OOTS #90

If you determine stealth individually, then certain party members (read: cleric, fighter, etc.) will fail virtually every check, because the game assumes they are in super noisy scale or plate armor. This means that even if half of the party moved into position undetected, the enemy is no longer caught unaware, even if they are still surprised or sneak-attacked by the rogue and ranger, for instance. The game tries to go easy on the sneakier classes by still giving them damage bonuses for being stealthy, but the mechanics have made a completely reasonable tactic (stealth) entirely devoid of utility except for those who specialize in it.

This bears mentioning, because we have all snuck up on our parent, sibling, friend, etc. in real life, and scared the ba-jeezus out of them. Sneaking up on someone who is not paying attention to their surroundings is actually pretty easy. Even cats and dogs, with their superior animal senses, can be scared out of their furry wits by a sudden jump from around the corner.

So why does the game assume you will alert your enemies to your presence most of the time, if you let the fighter or cleric anywhere in their earshot? Surprising the enemy shouldn't be so much about silence as about timing.

Take the Siege of Osgiliath, for example. Regardless of how the build-up was shot (which I feel left a lot of tension to be desired), the great thing about this scene is that the Gondorian soldiers still manage to get the jump on the orcs by hiding just inside the entrance, despite half of them having plate armor. They get a surprise round, even though the orcs know full well that there are enemies inside the walls. In fact, a lot of the stuff about this scene that bugs people actually would make for great rules-of-thumb around the table.

Yes, plate mail rings like a bag of tin cans and wind-chimes when you fight in it.

But, there is always some kind of white noise going on that will lessen the odds that someone who isn't actively listening for sounds notices a person in plate mail walking carefully.

Yes, soldiers run across the orcs' line of sight like, a dozen times just before the boats dock.

But it is dark and misty and foggy and the GM has to be honest: the orc saw a shadowy figure dart across the entrance. They know that Osgiliath is occupied, but they haven't heard any war horns. Does that really give them enough information to avoid the ambush? I don't think so.

It is a strange vestige of incorporating perception and stealth checks into the game that many GMs and players operate under two very unrealistic and paradoxical assumptions:

1) That nearly every non-living, physical detail about the world is shrouded in some kind of impenetrable fog or obscurity until such time as a good perception check is rolled.

2) That nearly everyone is fully aware of each living creature within eyesight and earshot until such time as a good stealth check is rolled against them.

Those assumptions lead to this being part of every D&D session ever:

(GM) "You guys begin trekking through the woods"
(Players) "We all go stealthily" *rollrollrollroll*
(DM) "Uh...yeah, okay you go pretty quietly on your way"

How is this even a thing? You roll one stealth check each for a whole day of travel, when earlier that day the rogue had to roll a whole stealth check just to take two steps behind an orc without it noticing? That's like saying the fighter can get through a whole day of random encounters with one attack roll, but has to roll for every attack when he encounters a pre-planned fight.

Are your characters seriously checking behind every tree and around every hill and padding every footstep to avoid contact with sentient beings? Or are you just keeping your voices low and going slow? Cuz you shouldn't need to roll for going slow, bro. Slowing down and shutting up is easy.

Are your characters trying to move fast, but not alert anyone? Tough shit. You get one or the other, unless you have some bombdotcom spell you wanna blow for super quick silent movement, or you are a high level ranger with some class feature that gives you crazy stealth stride. It is a basic fact of life, and one that needs to be preserved to have an interesting and problem-solving oriented adventure game: the faster you go, the louder you are and the more likely someone will notice you. The slower you go, the easier it is to move about without drawing attention to yourself.

Stealth is probably one of the wonkiest mechanics simply because it exists as the veil between the free-range character action outside of combat, and the turn-based character action inside of an encounter. Some might think of initiative when I say that, but initiative is "Step One" of combat, not the connecty bit. If you fail your stealth check, typically, combat begins. Maybe the target starts running away, maybe they pull out an axe and start swinging, who knows. Either way, it's now a two-player contest, and turns start being taken. If you succeed on Stealth, you remain the only "turn-taker" in the game, which means it isn't even a contest yet. No combat. Yet.

What would happen if we relaxed the combat structure of hard turns in a specific order, and instead made use of stealth merely as a means of getting the element of surprise on your side? In movies, for instance, when the action hero gets the drop on the guard guy, the hero snaps his neck or muffles him and slips a blade betwixt his ribs and that's all she wrote. In D&D, anyone but the rogue has almost no chance of taking the unsuspecting guard out in one-shot, because once combat rules kick in, damage is supposed to happen in little chunks over a long period of time. I don't see why the fighter couldn't shove his longsword through a dude's back and take him out (perhaps not dead, but certainly down), regardless of his HP. But again, if your combat is very rigidly segregated from your "non-combat" play, then it will be hard to justify anyone but the rogue being capable of shanking a dude.

And so stealth also brings up trouble with regard to how hit points work. One of the primary benefits of sneaking up on an enemy combatant is the opportunity to quickly and quietly dispose of them. However, most enemies in D&D type games have more HP than a fighter can deal in damage in one round. This winds up being "role protectionism," for the rogue. Even if the monk, or ranger, or fighter, or paladin, etc. snuck up on the enemy, they would not be able to kill them quietly, or quickly, thus giving their little stealth operation a close to 0% chance of success (where success is taking the enemy dude out without alerting the other enemies).

But enough about the problems with stealth. How do we fix it?

Well, there are a number of things:

1. Stop screwing characters in heavy armor. Seriously. Give them penalties to swimming, give them a hard time when they try to run more than 50 yards, but stop forcing them to auto-fail stealth checks with your gratuitous penalties. Armor is heavy, armor is expensive, and those two things together are more than enough to counterbalance the bonus to a character's defense. In reality, D&D-type games have been biased toward not wearing much armor for a long time. If you are regularly in hand-to-hand combat, wearing no armor is suicidal. All those leather-pants-wearing thieves out there who have complained enough to be allowed into front-line fighting are messing things up for their armor-bearing allies. Reality checks should be used very sparingly when it comes to fantasy games, but this is a spot where one is sorely needed.
   
2. There are two types of "sneak attacks." Ones where you plan to eliminate your target, and ones where you plan to get in a solid first strike against a big evil guy like a dragon. Take that into consideration when you are stating up your NPCs and monsters. If the standard ol' city guards have 5d8+12 HP each, then only the rogue can ever hope to take them out with a surprise attack. Don't do that to your players. Let your player characters outrun the rest of humanity in terms of HP and bonuses and such as they level-up. That way, a normal city guardsman always has roughly 1-8 HP, and even the bard could kill him silently with a good stab in the back. If you were hoping for the city guard to put up a good fight against your magically equipped and time-tested PCs, you are designing your encounters wrong. Simple as that.
   
3. If a PC critically fails a stealth check, they should be seen, no question. However, a regular fail on a stealth check should be interpreted more loosely as "a complication is added to the scenario." The castle guards stop to chat, and the careful timing you did of their rounds is now totally useless. A new NPC shows up to speak to the guard, or give him some food, or something else. A third party, like a wild animal or a beggar or something, shows up and draws attention in a direction you didn't want it drawn. The dog smells you and starts to bark from his cage, but the guards are just telling it to shut-up for now. This way, when the party rolls stealth all together, there are three possible outcomes: everyone succeeds and no complications arise, some people fail and complications arise, everyone fails (or at least one critically fails) and the PCs are discovered before their plan can occur. Now, the fighter and cleric can come along just like everyone else, but each additional person is another chance for a crit-fail to show up. Bigger party = harder to go unnoticed = perfectly reasonable to me.
   
4. Be real about how aware the enemy really is. A small camp of orcs that is feasting and wrestling are essentially unaware of their surroundings unless they have posted a lookout (which should not always be the case, unless its wartime or something). Assuming there is no lookout, the PCs should be able to sneak around their camp (in the trees) without rolling anything. If they want to foot-pad into the camp, enter tents, steal food or gold, etc., then stealth checks are needed to see how well that goes, since a stray orc could easily befall them as they reach into the chests of treasure in the middle of the camp.
   
5. Allow the players to solve the problem without rolling. If a rock thrown in the opposite direction of the entrance can draw the lookout away from his position long enough for the party to slip inside, then the party shouldn't need to roll stealth at all so long as they figured that out and did it. An invisibility spell + slow walking should allow a character to move through an open doorway without a problem, even with a guard a few feet away. Maybe a dexterity check might be needed if someone was to almost bump into them, but you get the drift.

Those are my best pieces of advice. If you have any other tips, or you've got the ultra-genius way of resolving stealth that I could never have conceived in a million years, please leave them in the comments. Pretty please?

The Force is Strong with this Villain...

Darth Vader was awesome because he was the Chosen One before Luke was the Chosen one.

Vader knew secrets and wisdom about the Force that Luke had barely scratched the surface of when they first fight. He was more highly skilled than Luke in all the areas that Luke had been training in. Not only that, but he had his own plans. Plans to overthrow the SAME GUY that the good guys wanted to overthrow. Vader's option was a kind of Option #3, where a different part of the dark side ruled the galaxy.

GMs should do this in their tabletop RPGs. Have villains be older, morally failed versions of the PCs. Have villains that are working against, or tangentially to, another villain. If you have a wizard in the party, have a villain that is a VERY OLD wizard who specializes in the same kind of magic. That way, the evil wizard isn't just an evil wizard, but a master of something close to the party's heart as well.

Evil monks? Evil monks are badass. How about Zaheer from Legend of Korra? He is a far more memorable villain than, say, Fire Lord Ozai, because his philosophy and point of view had merit. They were taken to extremes, and used to hurt people, thus making him a villain, but he could still teach the avatar a thing or two about air bending, and herself.

Your campaigns need villains like this. Villains that react to changes in the world, and make use of them for their own ends, rather than villains that spur on changes in the world.

Have a meteor that will destroy the world in 1 week? Well, there should probably be a group of cultists who use it's intergalactic presence to bolster their magic and try to take over. But once the PCs defeat them, it should be clear that the meteor wasn't summoned by them, they were just opportunists. Maybe now, the PCs need to work together with the cult's knowledge to stop the impact.

Make your PCs begrudgingly respect some of your villains. Not because they're so cool, or suave, or powerful, but because they are actually talented and intelligent in a way that even the PCs must acknowledge. Have the villain complement your PCs during the fight.

The end of that Star Wars clip is thematically perfect, because this first major interaction with Vader forever changes Luke, emotionally. He will never look at himself, or the Force, or his master Obi Wan the same. AND, he lost a freakin arm as a metaphor for that change.

So I guess the moral of the story is have your villains chop off more of your PCs arms.

2 Things to Use in your Campaign

1: Sea Monsters

For the love of gods, why aren't sea serpents used more in games like D&D? I don't own the 5e Monster Manual, but I am pretty sure there is roughly one kind of giant sea monster: the kraken.

Don't get me wrong, I love me some krakens. I've used them. I've had them attack ships. I've had them attack subterranean Aboleth cadres in Pacific Rim-type cave-lake encounters. Super fun.

But there is SO MUCH MORE sea monster mythology out there to be used. Hell, you can throw anything underwater and make it cooler.

How about aquatic hobgoblins? No, not sahuagin (or whatever they are called). As soon as you put a fish face on something, it looks stupid. Big dumb eyes and wide toothless mouths. That is not scary. Why not more aquatic mammals or reptiles that need to breath air, but not very often.

Like a crocodile. Sweet mother of Thor crocodiles are scary. Stealth killers that get you at the watering hole?

Terrifying.

Also: water. No need to add all those ridiculous terrain changes and traps and whatnot. Deep water is scary enough as is.

2: Battle Formations

Smart enemies fight in formation. Maybe not a straight line, or a tortuga, or whatever that roman thing was with all the shields and spears and such, but they know where they are supposed to be to make things as bad as possible for the PCs.

This means you can't just sprinkle the hobgoblins on the random forest map and expect it to end up like a real fight. And I don't mean "real" as in "like the real world," I mean real as in "dramatic and requiring strategy."

Let's see some regrouping and battle chants and (for the bigger battles) war drums and horns and such. Opportunity attacks make this needlessly difficult, which is why I hate them.

But at least consider allowing the monsters or PCs to pull back and reestablish positions on higher ground or better terms.

Shadow of Mordor: Video Games Improving the Hobby

I don't want my pen & paper games to be replicas of my video games. I firmly believe, however, that it is crucially important to study all rpgs and story-driven games to better understand what works and doesn't work about them, and which of those qualities that work can be translate into other mediums.

Enter the much-less-than-a-year-old LotR licensed game Shadow of Mordor.

Like all creative works, SoM has plenty of stuff that DMs can steal for their game: interesting plot twists, unique creatures, names, etc.. But there are two significant pieces of the game that make it excellent (in my humble opinion), and we need to examine them to see if we can add them to our tabletop repertoire.

The Combat

Video game combat is very different from pen & paper combat. No matter how complex and visually exciting it is, it does boil down to pushing one or more buttons repeatedly. That kind of monotony cannot be allowed to sneak its way into our tabletop games.

But if we take a look at more than just the boilerplate, we find a very interesting system. SoM uses the Batman Arkham combat engine (essentially), which has two major parts: a few plain but well-animated basic attacks, and then a plethora of extremely satisfying finishing moves, all of which use the same button activation, but have a varied appearance. The game camera also goes into slow-motion and zooms in for every single finisher the player does.

As most players of SoM will tell you, this leads to extremely satisfying and dynamic encounters, even sans the god-like superpowers your character eventually gets later in the game. So, what is the takeaway for the table?

1. If you (the DM) aren't narrating how the characters defeat enemies in great detail, you are missing out on a great opportunity to increase immersion. Remember, camera slow-mo, zooooooom in.
2. If the players are encouraged to narrate their hits and near misses (or really, all of their actions) in good detail, everyone is missing out on the immersion.
3. Combat feels better when it goes smooooooooothly. There are a number of ways to do this, each way is better or worse depending on the group. Some quick examples:
1. Initiative around the table clockwise instead of by roll, so everyone knows exactly when they go right from the start.
2. Roll attack and damage at the same time, and just ignore the damage roll if you miss.
3. Monster swarms/mobs instead of individuals.
4. Minion/mook monsters with "hits-to-down" instead of a hit point pool.
4. Lastly, SoM shows us an example of a game without a huge number of combat options (at the beginning, at least), that remains satisfying and dynamic. It isn't about having 100 things to do with each attack, but rather having at least one thing cool to do when the moment is right. Consider the following house rule I just made up (and sort of stole from Risus, now that I think about it):
1. Whenever one combatant (player or otherwise), would reduce another combatant to 0 HP, the victorious combatant may do whatever they like to the defeated one, keeping them alive if they so choose. This could include: knock downs, trips, chokes, slams, pins, interrogations, aerial decapitations, brow-beatings, humiliations, scarring, and so on.

The Enemies

SoM's Nemesis System is a program for randomly generating, designing, and promoting boss Orcs during the game to replicate the ebb and flow of Mordor's chain of command. It was the biggest draw for the game's release, and rightfully so: this was the first time a video game could even attempt to mimic the creative potential of a DM. I think the developers did an excellent job with it.

Of course, no program could ever come up with more, or more creative enemies than a human DM could, but there is one thing the computer has on all of us behind the screen:

The computer never forgets to do its job.

DMing is a LOT of work, so who can blame us for forgetting to come up with a unique name, voice, appearance, and stat write-up for every big-baddy that trudges toward the party in a blind fury? It's almost impossible, but there are ways to cut yourself some slack and still save face, story-wise.

1. SoM only gives enemies titles and personalities when they do significant things (like kill the player character, or get assigned as a bodyguard to an important Orc captain). DMs can do the same. When one of your Orcs or giants or whatnots deal a PC a grievous wound, or catch them sneaking around the camp, or escapes a battle with them, that enemy needs to be important and unique for later on.
2. Get yourself some random voice, appearance, and surname/title tables and use them! Using the SoM method, this stuff writes itself. "Zaku the Handsome" is an Orc captain with terrible face boils and deformities. His name is ironic, memorable, and gives you 90% of his necessary description right off the bat.
3. Keep a one-page log of the relations between named and reoccurring NPCs, so that when one dies or is displaced, or switches sides, etc., you have a reference for how the other guys will react. 

Let me know if there are any other games/movies/etc. that you want me to distill for the table!