Tag Archives: perception

The One Best Way to Make Perception Checks Doesn’t Exist. Here’s Your Toolkit

When players make Wisdom (Perception), Spot, Search, Insight, and other rolls to gain information, the number on the die reveals things: A low roll with no discovery suggests the character missed something; a high roll without a discovery confirms nothing to find. Unlike the players, their characters never see the die roll, so they lack the same insight.

In the early days of Dungeons & Dragons, dungeon masters avoided revealing such metagame clues by rolling secretly. To see if someone spotted a secret door, Gary Gygax rolled a 6-sided die behind a screen. Elves locate hidden passages on a roll of 1-4.

But when a die roll affects the characters’ fate, players like throwing their own dice. We all feel like if we want a certain roll strongly enough, we might sway the outcome. Sure, those of us who play D&D rather than Las Vegas recognize that sense of control for a lie, but we feel it all the same. Plus, dungeon masters see player rolls bring other benefits: Die rolls grab the players’ attention and keeps them physically engaged. (See How to Wring Maximum Drama from a Roll of the Dice.)

Fifth edition D&D skips the roll with the innovation of passive checks. Just compare the DC against a passive score. In theory, passive checks speed play, avoiding all those secret die rolls to spot hidden doors. The DM simply decides in advance what hidden doors the party will find, and then sets the DCs accordingly. Phrased like that, the procedure seems like no fun at all. Die rolls add surprise, uncertainty, and even a sense of fairness to our games. (See D&D and the Role of the Die Roll, a Love Letter.)

Aside from secret rolls (less fun) and passive checks (no fun), gamers account for the metagame insights that come from seeing the die roll in different ways:

  • The players roll, and then roleplay as if they didn’t see the die.
  • The players roll, but the DM sometimes asks for red-herring checks.

Over the years, I’ve gone through periods where I’ve favored each of those approaches. When I asked folks on twitter for their favorite techniques, I even learned a new one thanks to Alyssa Visscher.

  • The players roll, but the DM doesn’t tell what the roll is for.

For this technique, the DM has to know the characters’ perception bonuses. Just ask for a d20 roll, add the bonus, and go with the outcome. This lets players roll and grabs attention. For advantage or disadvantage, ask for two rolls.

I used to hope for a perfect method that brought player engagement without revealing metagame clues, but I’ve given up that search. Now I see a toolkit of methods, each with advantages.

How should you choose the right fit for a situation?

One situation always leads to a best approach. If a roll for initiative or damage would immediately follow a perception check, just let the player roll. Even players with imperceptive PCs immediately learn what t hey missed, so DMs gain nothing from a passive check or from metagame-thwarting tricks. (See How to Run an Ambush So Sneaky Monsters Bring More Than Claw/Claw/Bite.)

Other situations offer nearly as much clarity. If the players have to find something like a clue or a secret door for the adventure to continue, just let them find it without a roll. Or play the odds and let everyone roll. Someone will nearly always succeed. I’ve used both tricks to guarantee success, but I’m never proud of it. Checks that require success hint at fragile adventures that require a dash of railroading. (See In D&D, Letting Everyone Roll Certain Checks Guarantees Success, So Why Bother Rolling?.)

Also, specific actions can eliminate any need for die rolls. The characters leading the party might need to make a perception check to notice a hidden pit, but if they probe the floor with their 10-foot pole, the discovery becomes automatic.

Choosing from the other methods calls for more judgment.

DM rolls secretly. Aside from depriving players of the fun of rolling, secret rolls suffer from a second disadvantage: In today’s roleplaying games, characters bring extra abilities likely to affect their chance of making a particular check. DMs can never expect to learn them all.

Still, for high-stakes insight checks that steer the course of an adventure, I ask players for their insight modifier and roll in secret. (See Insight Played Wrong Can Become the Most Unrealistic Thing In D&D, a Game With Djinns In Bottles Who Grant Wishes.)

Instead of rolling, use passive checks.  Despite my distaste for how passive checks rob players of rolls in favor of a mechanic uncomfortably close to DM fiat, I sometimes account for passive scores during low-stakes descriptions. Characters with high perceptions may notice clues or interesting details that deserve extra attention. When using this technique, mention that the character’s keen perception led to the discovery. Players deserve to know that their character choices paid off.

Players roll and roleplay as if they didn’t see the die. This method works best for low-stakes situations where the players have little fear of overlooking something dangerous or valuable. In perilous situations, the technique forces players into an uncomfortable conflict between risking their characters and playing their role. Also, by eliminating some natural uncertainty, instead of truly feeling unease and a sense of mystery, players just pretend to feel.

Players roll but the DM sometimes asks for red-herring checks. Every DM intuits one bluff: If characters search a door for traps, then someone rolls even if the door has no traps. But characters can notice hidden doors even when no player asked to look, which means asking players to roll checks. To add extra uncertainty, ask for checks at times when nothing important can be found. This camouflages the important checks and heightens the tension that comes from knowing peril might hide nearby.

For extra misdirection, respond to every knowledge check with some information, even something familiar. So if the players fail a check to spot the spy following them through the market, tell them about the smell from the fishmonger, the buskers playing at the fountain, or the urchin looking for pockets to pick.

When players gain such information, they feel unsure of whether they missed their check or successfully learned something unremarkable.

Players roll, but a table rule adds uncertainty. Years ago, I proposed letting players make their own information checks, but occasionally overriding their due based on a secret roll. Whenever a player makes a check for information, secretly roll a d6 and a d20. If the d6 comes up 1, substitute your d20 result for the player’s.

In life, people tend to get a sense of how well they accomplish a task. Likewise, using this method, players gain a sense of whether their character succeeded, but as in life, that intuition may sometimes prove false.

Players must know about this uncertainty in advance, or they will suspect their DM of overriding rolls to hurt the characters. So this technique requires a rule of the table that everyone accepts.

What‘s your favorite method?

How to Run an Ambush So Sneaky Monsters Bring More Than Claw/Claw/Bite

Dungeons & Dragons includes lots of sneaky creatures proficient in Stealth, from Abominable Yeti to Yeti. That alphabetical range somehow fails to make my point, but more than 500 creatures fit in between. The game includes creeping monsters who work as ambush predators like spiders (Stealth +7), crafty ambushers like goblins (Stealth +6), as well as potential jump scares from wights, and jumping oh-shit surprises from bulettes.

When these creatures get some chances to lie in wait or to sneak up for surprise, they show the traits that make them more interesting than a claw/claw/bite sequence. Combat scenes feel more varied. Plus the barbarian gets to show off Feral Instinct. However, I have almost never run sneaky monsters for surprise, and based on countless convention games virtually every other DM plays sneaky wrong too.

Part of the blame rests on the fifth edition rule for hiding before an attack. “Compare the Dexterity (Stealth) checks of anyone hiding with the passive Wisdom (Perception) score of each creature on the opposing side. Any character or monster that doesn’t notice a threat is surprised at the start of the encounter.” In the highly technical jargon of game design, this rule is rubbish.

The worst check among the hiders determines surprise, so with multiple foes and checks, the chance of success veers quickly toward impossible. Based on real life, you might suppose that ambushes often work. Based on the D&D rules, the word “ambush” describes a imaginary event that can never happen, at least for groups of sneaky monsters. (For a look at the reverse of this dynamic, see In D&D, Letting Everyone Roll Certain Checks Guarantees Success, So Why Bother Rolling?.)

To fix the rule so ambushers can surprise, skip the roll to hide. As a dungeon master, you can set the difficulty class to spot an ambush just as you set DCs for other checks. Then, compare each character’s passive Wisdom (Perception) score against the DC to determine if the character is surprised. This matches the procedure you might use for a trap.

As a technique for setting the DC to detect an ambush, just add 10 to the ambushers’ Stealth bonus, so hiding goblins with Stealth +6 require a DC 16 to spot. If the sneaky creature has advantage, add 5 to the DC. For disadvantage, subtract 5 from the DC. A group setting an ambush has the edge of planning, preparation, and familiarity with the location, so a DM focused on realism might allow advantage and enable many surprises, but not the kind players favor. More entertaining ambushes probably lead to a mix of surprised characters and characters who act immediately. Such situations reward characters with high perception.

This approach boosts sneaky monsters and perceptive characters, but it eliminates die rolls and the fun uncertainty that dice add. By choosing a DC, the DM essentially decides who becomes surprised, and it’s always the same, oblivious characters. The D&D designers favor passive perception because it avoids slowing the game for rolling Wisdom (Perception) checks. In dungeons that encourage players to look frequently for traps, passive checks can speed past a lot of rolls. But lurking monsters deserve a different procedure: Just have players roll a Wisdom (Perception) check before the likely roll for initiative. The characters who fail their check begin surprised.

In an ambush, initiative can start at one of two times:

  • When the monsters attack.
  • When one or more characters notice the potential ambush.

This second case leads to judgement calls from the DM, but can also lead to interesting scenes. How the realization plays depends on how the perceptive characters react to spotting the attackers.

If the ranger draws a sword and yells, “To Arms!” then initiative starts and the less perceptive players begin surprised. Meanwhile, the monsters are already aware of their foes, so they start without surprise.

If the ranger plays it cool and tries to alert the party, then the scene turns on whether the ambushers happen to attack immediately. Does the ambushers’ insight reveal that the archer spotted them? If so, they strike and may surprise some characters. Can the ranger deceive the ambushers into waiting just a moment longer while covertly signaling the party? Ask what the alert characters do, and then call for checks to play the scene.

Distance factors into the situation too. In daylight, if the eagle-eyed ranger spots a group of yuan-ti hiding among desert rocks a half-mile ahead, then any surprise hardly matters. During that first round, no one without meteor swarm is in range to attack. The players can select the best angle of approach or can just avoid the monsters. Since yuan-ti have darkvision to 120 feet, they surely wait until night when most adventurers with darkvision see 60 feet and still suffer disadvantage to Wisdom (Perception) checks unless they carry a light source. Such scenes allow characters to show their special traits, like the drow character’s enhanced night vision that lets the party turn the tables.

For that ambush in darkness, you must judge how close the party will approach the yuan-ti before any characters can detect the snakes. Perhaps at 60 feet, allow the ranger leading the party one check at disadvantage due to dim light. At 30 feet, in the moment the monsters spring their attack, allow a second check for the entire party.

Ultimately, many ambush attempts lead into situations that demand DMs ready to balance distance, skills, and traits to create fun and exciting situations. An ’80s roleplaying game might have included a table that factored Stealth scores, Perception scores, terrain and lighting into a roll that revealed encounter distance. The authors of the Player’s Handbook skipped all that complexity in favor of simplicity. The approach relies on a DM’s judgement, but isn’t that part of what makes being a dungeon master fun?

To Find the Fun in Traps, Did D&D Miss the Search Check?

Traps add fun to Dungeons & Dragons when players can (a) make choices that help uncover them or (b) interact with them. Interaction includes crawling to evade scything blades or stuffing the mouth of the green dragon statue to block a jet of poison gas. Fun interaction favors discovery over die rolls and certainly doesn’t include just subtracting damage from hit points.

The standard routine for traps in fifth edition skips all the entertainment. The game’s example goes like this: A character’s passive perception reveals a trap, then a player rolls a Intelligence (Investigation) check to discover how the trap works, and then someone tries a Dexterity (Thieves’ Tools) check to disable the thing. This rote mostly dodges any potential fun. Passive perception just skips any engagement, and a trap’s discovery leads to zero choices. The only activity comes from die rolls. The only decisions come during character building. I daresay the procedure’s designer dislikes traps, but dutifully includes them based on D&D tradition.

Because the fun of traps comes from finding and interacting, dungeon masters can watch players evade them all and rate the session a success. Still, characters may overlook a few gotchas. Unnoticed traps that spring on characters serve three purposes:

  • To make careless and reckless choices lead to consequences.
  • To set a mood of peril.
  • To warn of more dangerous traps ahead.

For setting the mood and as a signal of more traps, the devices players do find work just as well. Even spent traps and their victims’ remains serve the purpose.

When players spot traps and use ingenuity to evade them, they gain the pleasure of figuring things out and feel clever. But even traps where the interaction goes wrong can prove fun. On the Mastering Dungeons podcast, Teos “Alphastream” Abadia says, “I recall an adventure that had a series of traps that were engaging enough that my party activated all of them after spotting all of them, and we were all laughing and having a great time. At one point a player found this pressure plate, and somehow, she concluded that this was the safe spot, so she jumped on it.” Later in the gauntlet, the group found a pit that dropped to a strange growth that hit the bottom, so someone dropped a torch to see. The growth was brown mold, which grows with fire.

The advice in the Dungeon Master’s Guide for running traps favors using passive Wisdom (Perception) scores to decide when characters notice traps. This advice aims to speed play by skipping time wasted looking for non-existent traps. But passive perception also loses the surprise and fun of rolling the dice. (See D&D and the Role of the Die Roll, a Love Letter.) Also, passive checks eliminate decisions that lead to uncovering traps, except for choices during character creation. Sure, no one wants a game slowed by fruitless checks for traps, but traps work best where players expect them—preferably past the spiked and burned corpses of previous explorers in dungeons with words like “horrors,” “death,” and “Tucker’s” in the name.

Passive perception can fill a role in a dungeon master’s trap game. Perception enables characters to notice things that simply require keen senses, such as a trip wire strung across a corridor. Passive perception can feel like a rule where the DM just chooses whether someone finds a trap. After all, the DMs who set DCs often know their group’s perception scores. But when only the characters at the front get close enough to spot traps, the choice of marching order factors into success. Sometimes the choice to light a torch also leads to success by eliminating the -5 penalty darkvision suffers in total darkness.

If someone observant leads and that character inevitably spots a trip wire, then the incident still sets a mood and signals more traps to come. Plus, players who chose the Observant feat feel rewarded for their choice.

Even the highest passive perception score falls short of trap radar. Totally concealed traps such as a pressure plate buried under dust require a search to uncover. For searching, choose Intelligence (Investigation) checks. Someone skilled at Investigation spots ordinary but significant details such as the residue around the gaping mouth of the dragon statue or the scratch left by the swing of scything blades. When players must ask for searches, they make the choice that a uncovers a trap. Plus, the roll for success adds the uncertainty that passive checks lack, and that roll adds surprise for the DM.

Traditionally, the D&D rules granted thieves and rogues a special knack for finding traps. Arcane tricksters aside, fifth edition’s rogue class fails to reward the Intelligence scores needed for skilled investigation or the Wisdom scores needed for keen perception. Not even the so-called Mastermind archetype requires brains. Even a rogue who chooses to pair Perception or Investigation with expertise will probably fall short. This makes either clerics or wizards best at finding traps, depending on how the DM runs the process of looking. (Hint: Wizards.) The rules for tool proficiency in Xanathar’s Guide to Everything help rogues meet expectations. Characters proficient in thieves’ tools gain advantage when they use Investigation or Perception to find traps. This amounts to a +5 to passive perception. Perhaps the thief can lead the marching order.

If I were to redesign a rogue class, I would consider more abilities that reward a high Intelligence. This would yield thieves more apt at spotting traps and spies more capable of investigation. Character optimizers call classes that require high scores in more than one attribute multi-ability dependent or MAD. Such requirements weaken classes a bit. Fortunately, MAD paladins bring power to spare. Sorry, MAD rangers. A hypothetical MAD rogue would get a small boost to compensate. My dream rogue would also become a capable backstabber, unlike the current version where daggers only rate as a strategy for players seeking the roleplaying challenge of playing an inferior character.

Stop Favoring Perception for Searches in D&D

When Dungeons & Dragons characters search, what check should players make? Based on my experience playing with a hundred or so fifth-edition dungeon masters, most answer Wisdom (Perception). Nonetheless, many DMs ask for Intelligence (Investigation) checks instead.

So what character should search a door for traps? Based on the Dungeon Master’s Guide, pick the wise cleric. Based on the skill descriptions, pick the clever wizard. Based on tradition, pick the thief and—if you play fifth edition—run for cover because they can’t spot anything. Besides initiative checks, search checks rate as the second most common in the game, so you would think everyone would agree. We don’t.

All this uncertainty means that as a DM making a call for your table, you decide. I’m here to help.

Some players like to call for their own checks. A character enters a room and the player announces something like, “I use perception and roll a 17. What do I find?” Rolling a check that the DM didn’t request counts as a small lapse of table decorum. Only the DM decides whether a situation merits a check, whether the character can succeed, what check suits the circumstances, and which characters deserve the roll. If a player just announces such a check, say “First, tell me what you’re examining. Do you touch it?” That question grabs attention.

To complement Perception, D&D’s fifth-edition playtest included a Search skill. So during exploration, PCs “make a Wisdom (Perception) check to detect hidden creatures and an Intelligence (Search) check to detect hidden objects (such as traps and secret doors)”. This makes the difference between Perception and Search seem like noticing creatures versus spotting objects—surely not the intended distinction, and perhaps one source of confusion that led the designers to drop Search in favor of Investigation. At least everyone could agree to use Search for searching.

The game rules for Investigation explain, “When you look around for clues and make deductions based on those clues, you make an Intelligence (Investigation) check.” The bit about looking around for clues makes Investigation seem like a more useful superset of Search. Aside from treasure, clues rank as the most common thing for a search to uncover. Even traps only prove fun when players find clues to their presence. Falling down a pit: no fun. Investigating a puddle and finding an edge where the liquid meets a seam in the floor: fun.

For searches, opt for Intelligence (Investigation) checks. Investigators notice clues and uncover things outside of plain sight. Investigators know where to look, so they check under a drawer to find the envelope tucked in the joint. Most characters ignore the scuffs on a stone floor, but an investigator notices them because the marks show where the statue slides to reveal a trap door. Someone skilled at Investigation spots the ordinary but significant details that the keen-sensed barbarian overlooks because such details seem insignificant. Sometimes players know where to look too, so if a player asks to peer under drawers, they spot that letter.

In contrast, perception enables characters to notice things that simply require keen senses, for example the sounds of an invisible creature, the master rogue Waldo in a crowd, or the cat obscured by shadows. “Your Wisdom (Perception) check lets you spot, hear, or otherwise detect the presence of something. It measures your general awareness of your surroundings and the keenness of your senses.” Perception can reveal the obscure, but it can’t expose something hidden from all the senses.

Many D&D fans, including me, tend to think of Investigation and searching as active in contrast to passive Perception. While this pattern frequently holds, don’t rely on it to distinguish the skills.

Such thinking leads players to make two checks to look around, one for percieving and one for investigating. Better to avoid such repetition. See How to Avoid Boring Rerolls of D&D’s Ability Checks. Players who make one check to find nothing in an empty room feel disappointed. Why invite a second, time-wasting check?

Freelance designer Teos “Alphasteam” Abadia explains how a distinction between active and inactive skills leads players to game the system. “Spycraft did that, with one skill for actively looking and another for possible noticing. It led to absurd behavior. You would enter an enemy camp, but state you were not looking around. That way, your better Notice skill would kick in.”

Sometimes the difference between Investigation and Perception blurs. Typically, when characters pause to examine and interact as they look, call for an Investigation check. This tends to reinforce the distinction of an investigator noticing the details in the mundane, plus it balances the value of the overvalued Wisdom (Perception) check with the undervalued Intelligence ability and Investigation skill.

D&D is a team game and when different character architypes skills and abilities contribute to a group’s success. By using the Intelligence ability and the Investigation skill, players who excel at those less pervasive knacks gain a chance to shine.

This approach amplifies the importance of not completely blocking a group’s progress with an Intelligence (Investigation) check. Fifth edition minimizes the value of the Intelligence ability so much that unless a party includes a Wizard, then no character may have a score higher than 10. In an essential investigation, give any required information, and then reward the sleuths with additional insights.

As for all those 8 and 10 Intelligence characters played by smart D&D players, they show the changing fashions of tabletop roleplaying. In the hobby’s early days of random ability scores, players who valued character immersion often felt obligated to play a low intelligence character as a knucklehead, complete with dangerously foolish decisions. Now, I rarely see such a commitment.

In D&D, Letting Everyone Roll Certain Checks Guarantees Success, So Why Bother Rolling?

As a dungeon master, I rarely ask everyone in the party to make perception, investigation, or knowledge checks, because someone almost always rolls high. With these checks, just one high roll yields the information the players want. Why bother rolling for a virtually certain outcome?

I asked this question of Dungeons & Dragons fans and gained hundreds of responses.

Many comments mentioned that passive checks—especially passive Wisdom (Perception) checks—fit most times everyone might roll.

So why roll instead?

Even though DMs realize that saying “everyone roll” almost guarantees success, they ask because players enjoy rolling. For many players, the game only begins when the dice fly.

Plus, “everyone roll” is D&D theater. You know the outcome but asking grabs attention and spurs the players into real-world action. Jamie LaFountain writes, “Everyone rolling is a nice smoke-and-mirrors trick when you want to get a piece of information out to the group and give the illusion of risk of failure.”

Sometimes everyone rolls without a request from the DM. One person makes a check, and all the other players snap to attention and try too. For example, the character at the dungeon door looks it over, muffs a perception check, and then everyone else starts rolling and calling numbers. What should a DM do?

First, you might gently remind your players that rolling a check that the DM didn’t request counts as a slight lapse of table decorum. “When I’m a player I loathe that everyone at the table feels the need to also roll a check,” Sam Witkowski writes. Such piling on robs the active player of their moment—their chance to be rewarded for their action. Checks should happen when a DM decides that a character’s action in the game world merits a check.

Ask the other players what their characters do. If nobody approaches to spot the door’s faded inscription, ignore their checks. If everyone takes a turn up close, consider any time pressure, but let everyone roll (and maybe a wandering monster opens the door from the other side).

Actions prompt checks, so making a perception check typically means taking a closer look. If the party just crosses a room and you want to see if someone notices a trap door, D&D’s rules suggest using passive Wisdom (Perception) rather than calling for a roll. You can limit passive checks to those closest to the trap door, so players benefit from letting the perceptive character lead. (And remember in dim light, the check is at disadvantage, a passive -5. Darkness counts as dim light for characters relying on darkvision.)

Players pile on lore checks too. These are checks against skills like History, Arcana, and Religion to discover if a character brings some knowledge to a situation. Everybody rolling for knowledge typically assures success. Such group rolls often show that the most unlikely character knows some bit of obscure lore.

Group knowledge rolls diminish the choices of players who invested proficiency in knowing things. If you always let everyone roll for an inevitable success, the value of knowledge skills drops to almost nothing. Success comes from making five rolls rather than from proficiency.

When everyone rolls, the one sage proficient in a skill will seldom roll a better success than the four know-nothings in the party. Still, some DMs enjoy the surprise of seeing the barbarian beat the wizard’s arcane knowledge. Such occasions can reveal character.

The next time every character wants to pile on a knowledge check, consider letting them, but ask players to roll only if they think their character might know something. Then if the barbarian lucks into a 20, say, “I’ll tell you about the enchantment on the door, but first can your tell me how someone fostered by wolves knows about wards forged on the plane of Mechanus?” Asking “how can this be so?” fuels creativity. “The barbarian may not know what that symbol means is or what civilization used it, but they remember seeing something similar 10 years ago on a crypt outside of Blahland,” writes Jonathan Hibberd. Either players add interesting bits of background to their characters, or they admit to knowing nothing.

Letting everyone roll a lore check works best when you have lots of information to offer. Every success yields a fun fact. By granting information for good rolls, you can make an information dump feel like a series of rewards.

For extra value, try to make the tidbits feel unique to each character’s background, nature, and outlook. D.W. Dagon writes, “A Religion check from a cloistered scholar is going to be resolved very differently to the same check from an outlander. It’s a great opportunity to bring forth each character’s unique backstory in a way which forwards story.”

DMs who want to see if a character discovers a secret may ask for everyone to roll. The player who succeeds gains confidential information. Don’t do this if you expect players to share the information. Players tend to guard secrets, even when they have no reason to.

Everyone roll almost guarantees success, but sometimes no one rolls better than a 6—including the character starting with a +5. If you call for everyone to roll, expect success, but be ready for a fail. If the adventurers must know something, then just tell them.

Some DMs keep track of characters’ proficiencies for this purpose. “If I can prepare,” Thomas Christy writes, “I love to find out who is trained in pertinent skills, and then feed their players information ahead of the session.” During the game, the players can reveal their knowledge in-character. When players remember their knowledge, Tom rewards inspiration.

You can treat knowledge skills as passive. Without a roll, tell players what their character knows based on, say, their Intelligence (Religion) bonus. I often reveal lore based on characters’ proficiencies and background. For instance, the druid knows of the cursed trees surrounding the grove, while the dwarf knows about the flooded mine. This technique works especially well for the information players must learn to continue. Essential backstory feels like a reward for a character’s choices. Players won’t know what knowledge comes from their characters’ aptitude and what you had to reveal to advance the plot.

If you want to make checking for a bit of obscure lore into a real test, allow fewer characters to roll.

  • Limit the check to characters with proficiency. This rewards the cleric proficient in religion even if their knowledge is hampered by low Intelligence.

  • Limit the check to the active character, possibly just the person who asked, and then grant advantage based on the party’s advice and assistance. This encourages action.

  • Limit the check to the most knowledgeable character, and then grant advantage based on the party’s help. I love when this enables a quiet player to gain the spotlight based on their character’s aptitude.

You can impose similar limits on investigation. Limit Intelligence (Investigation) rolls to the best detective or to the active character, and then grant advantage based on the help from other characters.

Wisdom (Insight) checks commonly lead to pile-on checks. If you want any intrigue and deception in your game, then more than one person should never roll a Wisdom (Insight) check. Next week, I’ll explain how to cope with Insight.

Is it found? How to handle a search

Speed through the obvious by summarizing simple search efforts

Game masters often speed past the uninteresting parts of the game—the parts with few decisions or obvious decisions—with a simple summary of activity. Most game masters will use a summary to skip past a search of a place containing nothing of interest, but the technique also works during the players’ first examination of a cluttered laboratory or dusty crypt.

When you conduct the routine parts of a search, summarize the obvious actions the party might take to perform a quick, initial search. This summary from the game master brings two advantages:

  • You, as the game master, and the characters in the game world have a clearer picture of the location than the players.
  • You can summarize the results of the most simple, obvious search efforts without slowing play with back-and-forth discussion as the players describe their actions.

In your summary, mention the obvious items in the location and any simple steps required to search around and inside them. You might also mention things the characters don’t do, either because the actions could be risky or time consuming. For example, “As you look, you leave the books on the shelves and the furniture in place.”

Parable of the Hidden Treasure by Rembrandt

Hidden Treasure

Avoid giving the results of this summary, in case the players wish to change some the actions that you outline. For example, “No, none of us go near the dark altar.”

This description will give the players a more vivid picture of the contents of the room, and will suggest things that deserve further checking.

Once you finish a summary of an initial search, the players can agree to proceed, you can share the outcome, and then the players can describe anything they want to do to take a closer look.

This method only works if you limit your description of the party’s search to obvious efforts. Do not make the players feel usurped by the game master. If the players enter the Garden of a Thousand Stings, where any misstep brings painful death, have them spell out every action. If the players enter Acererak’s throne room, and they prefer to describe every nuance of their search, they can—they should.

Search procedure

When the players ask to search a location, and they have limited time to search, use the following method:

  1. Ask if the characters will touch, move or open things as they search. If traps seem plausible, ask how the characters divide the responsibilities of opening and moving. If the room appears on a battlemap, you can ask the players to place their figures in the region they intend to search. During this step, you establish which characters could possibly trigger any traps or hazards that may exist.
  2. Summarize the obvious actions the party might take to perform a quick, initial search. This description will give the players a more vivid picture of the contents of the room, and will suggest things that deserve further checking.
  3. If the players have no objections, then tell the result of their initial search. The characters might find the keys on the bodies, coins in the sofa, and the monsters under the bed. They will find anything in plain view. If they open and move objects, they will also find anything not carefully hidden.If you feel uncertain whether something hidden would be noticed in this first, quick search, call for a search check from the entire group, but only consider the result from the character searching the area with the hidden object. Many things in the location may still need a closer look or more actions to find.
  4. If the players think some features deserve more thorough investigation, let them describe closer checks. For example, “I want to check that empty chest for hidden catches or compartments.”“I wonder what’s behind the bookcase. Is it built into the wall?”
“In most cases, you need to tell the DM where you are looking in order for him or her to determine your chance of success. For example, a key is hidden beneath a set of folded clothes in the top drawer of a bureau. If you tell the DM that you pace around the room, looking at the walls and furniture for clues, you have no chance of finding the key, regardless of your Intelligence (Search) check result. You would have to specify that you were opening the drawers or searching the bureau in order to have any chance of success.” – Dungeons &Dragons Next playtest

In step 4, the characters’ specific search actions may call for search checks, or they may yield discoveries without a roll. As the characters’ search actions grow more specific, they may make some or all search rolls irrelevant. If the ceiling contains a hidden trap door and someone starts rapping the ceiling with a 10′ pole, just tell about the hollow-sounding spot that reveals the door.

Searching and tedium

This search procedure typically applies when the characters face some time constraints, when they must decide whether to keep searching, or whether to press on before, say, a patrol comes or the dark ritual begins.

When characters can search without time pressure or risk, but you, as the game master, make the players either roll or narrate their search process, you can introduce frustration. The players know if they waste enough real-world time rolling checks or describing how their characters probe, sift, and break down every object, they will eventually find everything that can be found. The search’s success hinges on the players’ patience for drudgery.

In the classic dungeon expedition, the threat of wandering monsters discouraged this sort of grind. In original Dungeons & Dragons, searching a 10 foot section of wall for a secret door required a 10-minute turn. Each turn, the referee checked for wandering monsters, and the players faced a 1 in 6 chance of attack. Players focused their searches on the most promising features, and then moved ahead. See “Three unexpected ways wandering monsters improve D&D play” for more.

Third edition acknowledged the tension between tedious play and exhaustive searches by introducing the option to take 20. Taking 20 allows players to find everything the characters could possibly find, without testing anyone’s patience.

Searching without game-world time limits

Fourth edition and D&D Next both dropped the rule for taking 20, while old-school games include no rules for checks at all. However, the players don’t need to say, “We take 20,” for you to cut past tedium.

Anytime players can search without time pressure, they will find everything that can be found.

If players search without time constraints, and they’re determined to finding whatever can be found, let them find it. Skip the rolls and skip the rote recitals of how and where they look. Just tell the players everything they’re capable of finding.

Although this guideline lets you provide a search’s outcome in seconds, the guideline applies when the players wish to invest what could be hours of game-world time in an exhaustive search. If the players show no particular interest in a thorough investigation, then just summarize the outcome of a simple search and let them follow up as they choose.

In unusual cases, the characters may not be capable of finding everything. For example, a perfectly concealed door may require a search DC higher than 20 plus the search skill of the party’s best searcher.

Time and search

Most versions of Dungeons & Dragons tend to leave the time demanded by a search to the discretion of the dungeon master. Advanced Dungeons & Dragons offers the best guidelines: “mapping, and casually examining a 20’×20’ area” requires a 10-minute turn, and then thoroughly searching the 20’×20’ area after the initial examination requires another 10 minutes. Actual time varies depending on the amount of stuff in the area. Characters must spend much more time to finish an exhaustive search that finds everything that can be found, and rules out any possibility of missing something.

Newer versions of the game calculate search times with an interest in making searching feasible during combat. Third edition lets you search a 5’×5’ area as a full-round action. Pathfinder lets you search it as a move action. I can’t even find my keys in a 5×5 inch basket that fast. These times only seem applicable to a relatively empty battlefield square, and not a wizard’s junk drawer.

“Time spent searching for anything (secret passages, hidden treasure, etc.), loading treasure, listening, ESPing, hiding, will be adjudged by the referee as to what portion of a turn will be used by the activity.” –Dungeons & Dragons Underworld and Wilderness Adventures p.8

In play, when time matters, keep a rough accounting of the time characters invest in a search, and share the totals with the players. You may need to keep them appraised of the risks of spending more time.

How to run listen.

This one is easy. Everyone forms a line and takes turns putting an ear to the door, and then rolling. Meanwhile, the dungeon master rolls to see who is listening when something awful comes through the door. For instance, Beholders can drift soundlessly and open doors with telekinesis.

How to run an ambush

Group checks and the ambush

In “How D&D Next almost made knowledge count” and in “Is it noticed? How to run alertness,” I discussed the inevitable success that comes when a group rolls to gain one success. The reverse of this phenomenon appears when a group makes a check and just one failure can drag down the effort. The designers of d20 role-playing games mostly ignore these issues.

Credit the fourth edition Dungeon & Dragons designers for introducing a group-check rule for some tasks. From a game-play perspective, I like 4E’s group-check rule because it makes some group tasks possible. From a realism perspective, I fail to understand how three stealthy party members cover the racket from the clanking dwarf and paladin. In this post, I ignore the 4E rule, which I’ve never seen applied to perception anyway.

No situation highlights the problems of group checks more than the ambush. Using the simplest interpretation of the rules, everyone in a group setting an ambush must roll to hide, giving all a chance to doom the effort with a single bad roll. When the targets of the ambush arrive, every target gets a chance to spot that worst hider.

Based on real life, you might suppose that ambushes typically work. The group setting the ambush has the advantage of planning, preparation, and surprise. They just sit out of sight until their targets arrive. Unless someone sneezes or the targets have x-ray vision, the ambush works.

Based on the game, the word “ambush” describes a imaginary event that can never happen.

In “Is it noticed?” I suggested a fix. I advised assuming that the targets of an ambush take-10 to spot it. In effect, you set the DC for the ambushers’ hide check based on the targets’ lowest take-10 to spot. While this enables one creature to set an ambush, it still fails when a group prepares an ambush and everyone must roll to hide. My method only gives a group a chance of setting an ambush if the GM either (a) requires just a single hide check from the worst hider or (b) relies on 4E’s group check rules for the attempt to hide.

In a comment, Sr. Rojo suggested a method for handling ambushes that I like better.

How to run an ambush

To run an ambush, follow these two steps:

  1. Allow the group setting the ambush to take-20 in their effort to hide.This reflects their time advantage, which lets them pick a good site and then arrange themselves for maximum concealment. When you set an ambush, you have time to work out the best hiding place you can muster.
  2. When the targets reach the ambush site, ask them to roll to spot. The DC to spot the enemy equals 20 plus the ambushers’ worst hide bonus.Unless the ambushers stink at hiding, the DC to spot the ambush may be unattainable for some targets, and will present a challenge to the rest. Unlike most group spot checks, this check presents a reasonable chance of failure. Rather than assuming the targets of the ambush take 10 on their spot check, you can let them roll, and still give the ambushers a fair chance.

As with any spot check, you can limit the check to those characters keeping watch and in position to notice. If the party wants to an ambush a company, only the few soldiers on watch get a spot check, not all 100 enemies.

Take 20 and the rules

“When you have plenty of time, you are faced with no threats or distractions, and the skill being attempted carries no penalties for failure, you can take 20.” – Pathfinder Roleplaying Game Core Rulebook, p.86

Some rules lawyers might argue that the hide attempt does not qualify for a take-20, because it carries a penalty for failure. I disagree. Unlike climbing or disabling a trap, the act of perfecting a hiding spot carries no penalty for failure. Your best hiding place may not be good enough, but that comes later.

Dungeons & Dragons fourth edition and fifth edition both lack a take-20 rule, so this method requires some latitude with the rules as written. In practice, if the players set an ambush and you tell them they automatically roll a 20 on their hide check, no one will gripe.

If the players walk into an ambush, you, as the game master, set the DC they must reach to spot the ambush. Even in a game without a take 20 rule, a DC equal to the ambushers’ worst hide bonus plus 20 makes a good target.

Next: Is it found? How to handle a search

Is it noticed? How to run alertness

Introducing the spot check

In this post, I cite “spot checks” to refer to third edition’s Spot checks, Next’s Wisdom (Perception) checks, and tests of awareness made with 4E and Pathfinder’s Perception skill.

The Spot skill and its descendents rate a character’s ability to notice something while doing other things like traveling, fighting, or resting. Before Spot entered the game, unless you searched, you noticed the things the game master decided you noticed. A thief might hide from you, but their success depended on their roll to hide, not on your ability to spot.

Spot the spider

Can you see me?

When the game master simply decides what the characters perceive, the game plays fine. After all, the game master adds things to an adventure to enrich the adventure. If you let the dice say that the PCs fail to catch a scent of brimstone, or fail to spot the cloud of bats erupting from the cliffside, then the game suffers.

Nonetheless, when Spot skill entered the game, game masters and designers dutifully worked spot checks into every situation. Whenever the party opened a door or topped a hill, everyone made a new round of spot checks. At some game tables, every bit of information had to be earned with a spot check.

I will explain why you should skip many spot rolls, reserving the spot check for a small number of specific circumstances.

Passive perception and taking 10

Fourth edition attempted to rein in spot rolls by introducing passive perception. In principle, a dungeon master could skip perception rolls and use the characters’ passive perception to determine just what they notice as they explore.

“Passive perception checks help you set the scene. They tell you right away how much of the details of a room or encounter area the characters notice.” – Fourth edition Dungeon Master’s Guide p.26

Passive perception extends the mechanic of taking-10. Instead of players stating that they take 10, the game master assumes it.

Passive perception avoids putting the players on alert by asking for a roll when they see nothing. And it avoids interrupting the narrative for all those rolls.

What’s not to like?

The problem with passive perception

Passive perception forces the dungeon master to do the extra work of tracking all the passive perception scores and of setting perception DCs. Typically, this extra effort only yields a process that amounts to the DM deciding in advance what the PCs will notice. Seem familiar?

Most DMs running for regular groups know the approximate perception bonuses of the PCs. If you bother to create something interesting or something that advances the adventure, would you hide it behind a DC that prevents the group from ever seeing it? Never. Not even authors of published adventures will hide things that enrich the adventure beyond the perception of a typical party.

Secrets add fun to the game, but only when uncovered. If the players overlook the secret door, it’s just another wall. – Monte Cook, “Dungeoncraft” in Dungeon 137

But suppose a virtuous DM devises an adventure that gives keen-eyed parties a significantly different experience than unwary parties. The players still never know that their keen-senses paid off. The work of managing perception stays in the DM’s head, its effects unnoticed by the players, extra work, arguably for nothing.

If you would set the DC required to spot something within the reach of the PCs’ passive perception or take-10 value, then skip the DC. They spot it. The players will not ask you to show your work.

As a diceless method of resolving spot checks, passive perception falls short, but it still works as a way to set a difficulty class. More on that later.

The play value of rolling to spot

None of this means that you must always decide in advance what the players see. Random rolls can add an element to the game.

  • Unpredictability makes role-playing games interesting, mainly for the game master. The printed adventure cannot surprise the GM. Only the players actions and the random luck of the die add surprises to the game.
  • Randomness helps the game master keep some distance from the characters’ fates. The players should see the course of the game determined by their choices and by the luck of the die, not by the GM’s whims and mood.

Ask for spot checks (a) when success is uncertain, and (b) success hinges on keen senses in the game world.

Group perception checks almost always succeed

The outcome of group perception checks is rarely uncertain enough to merit a check.

Anytime every player can attempt a spot check, someone will succeed. Suppose a party of five adventurers, all with +0 to their check, passes something that requires a spot DC of 15, what D&D Next considers a moderate DC. If one person rolls, the chance of success is 30%. If everyone rolls, each has a 30% chance of success, which means the odds of someone succeeding grows to 83%. This supposes that no one is particularly good at spotting—everyone has a +0. One alert character pushes the chance of success closer to 90%.

When the odds of everyone missing something amounts to a rare fumble, does stopping the action to roll make sense? With some groups, absolutely. In particular, younger players love to roll, so group rolls create excitement despite the minimal chance of failure. Let them roll.

“Listen or Spot checks can get repetitive and dull if players have to make them over and over, especially when it usually only takes one success out of the whole group to succeed, making their success typically a foregone conclusion. Think twice before asking for such checks. They’re interesting when the PCs are trying to find a hiding or invisible foe, but get dull fast when they’re walking through the woods and you ask for them for every hour of travel.” – Monte Cook, “Dungeoncraft” in Dungeon 137

For most groups, you can consider any ordinary group perception check an automatic success. Skip the pointless activity, tell them what they see, and move on.

When you devise adventures, never mistake a group perception task difficulty for a challenge. On the rare occasions a group fails to spot something, they fumbled. This certainty is not a bad thing. In most cases you want the players to spot the “hidden” things in your adventure, either because these interesting things enrich the adventure, or because they advance the plot.

Hard checks change the equation. These checks impose DCs so high that only one or two members of the party can even hope to succeed. That’s the water elemental stirring the reeds under the bridge, or the key glimmering below the school of silvery fish. In these cases, allow a roll. You must be comfortable with the likelihood that no one will spot the ambush or the key.

If your players have become accustomed to calling for group perception checks, you can tell them not to waste their time, or you can let them have their fun, knowing that their success is virtually certain.

Individual perception checks may merit a roll

Of course, many spot checks can only be attempted by a character or two. This gives you a chance to add an element of uncertainty, and gives your players a potential reward for investing in perception.

Sometimes a spot task may be limited to the characters…

  • leading the party in marching order.
  • with darkvision or another requisite ability
  • spending an action the heat of battle to look
  • with applicable talents such as the ability to spot traps or arcane phenomena
  • taking the role of lookout

The D&D Next exploration system turns some of these limitations into specific rules: “When a character chooses to keep watch as an exploration task, the character makes a Wisdom (Perception) check to detect hidden creatures and an Intelligence (Search) check to detect hidden objects (such as traps and secret doors) as the group travels during the current exploration turn.”

D&D Next writes this as a rule, but it applies to other games too. In many situations, only a few members of the party can make perception checks. Their skills pay here. Keeping watch is a task akin to mapping or tracking.

“Don’t be afraid, in some cases, to only allow one or two characters to make the check. It’s with in your prerogative to rule that most of the party is preoccupied in other activities while one character is more or less ‘keeping watch.’ This isn’t covered in the rules, but in a case-by-case basis, you can decide that only a character who’s trying to listen or keep an eye out has a chance of making a check.” – Monte Cook, “Dungeoncraft” in Dungeon 137

Group perception checks guarantee success, so individual checks like these represent a chance for players who invested in perception skills to reap benefits.

Even if only one or two characters can possibly notice something, you might ask all the players to make the roll, and then only consider the checks from those able to notice. This avoids giving clues about, say, the location of the breeze coming from the unseen exit.

Favor search over spot

Before you ask for a spot check, consider whether a search makes more sense. In most cases, this comes down to the circumstances, see “Choosing which type of perception check fits a situation.” Sometimes, you may be tempted to give someone a chance to spot something hidden, but hypothetically visible to spot. Favor making the players search. Searching plays better than spotting for a couple of reasons:

  • Searching engages the characters in action, forcing them closer for a look.
  • Searching invites the players to make decisions about when, where, and how to search, and how much time to risk.

If someone steps into a room, aces a die roll, and sees the key at the bottom of the fountain and the odd scratches on the floor behind the chest, you have replaced the interaction and decision making demanded by a search with an abstract roll.

Hiding and sneaking

When one creature attempts to hide from others, do not ask for spot or listen checks. Instead, use passive perception or take-10 scores to set the DC to sneak or hide. Pit the active creature’s stealth check versus the highest applicable take-10 score. In the case when a group could roll to spot, this method makes hiding possible, because group perception checks virtually always succeed.

In combat, if someone chooses to look for a hiding creature, they can spend an action and roll versus the hiding creature’s check. In Pathfinder and 3E, active looking takes a move action. In 4E, active looking takes a standard action.

The same system works for ambushes. If someone hides to ambush, they roll to hide. Later, when the ambush springs, compare the hide check against the highest passive perception or take-10 score of the targets.

While this procedure may not follow your game’s written rules, it makes sense because the targets of the ambush are busy traveling and, by default, taking 10 on perception.

Five questions to ask before calling for a Spot check

The game master almost always asks players to make spot checks, except when players take an action in combat to look for something.

As a game master, before you ask for a check, consider these five questions:

  1. Is something sneaking or hiding? Skip the spot check. Instead, use the party’s best take-10 (passive perception) scores to set the DC for the hide or sneak attempt.
  2. Can the thing to spot be noticed from the character’s vantage? If not, wait for the players to search.
  3. Does noticing something fall within the take-10 value of the most perceptive PC? Do not roll. Something is noticed.
  4. Does everyone in the party have a chance to notice something? Do not roll. Something is noticed.
  5. Are only one or two characters in position to notice something? Ask for a perception check.

Next: How to run an ambush

Secrecy, metagaming, and perception checks

When players roll their own perception checks, they learn something from the number on the die roll. Players with bad rolls know that their search may have missed something; players with great rolls may trust the game master’s report that they found nothing.

As a game master, you can make perception checks in secret, but players hate this. Some of the fun of the game comes from rolling dice. If the GM rolls for your character, you start to feel a loss of ownership. You feel like a bysander watching the game rather than participating.

Who should roll perceptions checks?

Clear box for dice rolling

Clear box for dice rolling

Many players take pride in running their character without relying on any metagame information. These players can roll, obviously blow their check, and press ahead knowing that if a trap awaits, they missed it. If you have such players at your table, let them roll their own checks. Still, even for these players, knowing the rolls can rob the adventure of some sense of peril and mystery.

Some players take the unearned information that comes from the number on the die and they use it to make choices. For them, remind them that their characters don’t know they blew a search check, so the characters lack any reason to repeat the search. If they keep searching anyway, roll the second check for them, out of their view. And if you simply ignore the second roll, no one will know.

Roll substitution

If you want a game that emphasizes a sense of challenge and risk—or you have a table of unrepentant metagamers, I suggest an occasional roll substitution.

Tell the players, “Whenever you make a perception check, I will secretly roll a d6 and a d20. If I roll a 1 on the d6, the information I tell you will be based on my d20 roll rather than on yours.”

With this approach, most of the players’ rolls still apply, so players remain connected with the game. The visible roll gives the players a fair sense of how their characters performed, just as you might have a sense of your performance on a real-world test. But players can never feel certain that a 19 on the die means they found everything to find. And when someone rolls a 1, but sees a glimmer on the horizon, it may be more than a mirage.

Misdirection

If you only ask for perception checks when something can be noticed, the checks will put players on alert. Once or twice a session, when nothing can be found, you should call on players to make a Spot or Perception check. No matter what the roll, frown, shake your head, and tell them nothing. Not only will this unnerve the players, but it trains them to avoid assuming that they must have missed something.

Next: Is it noticed? How to run alertness

Choosing which type of perception check fits a situation

Both fourth edition Dungeons & Dragons and Pathfinder apply a single Perception skill to all observation tasks. This cuts any confusion about which skill applies. Both D&D Next and third edition split the single skill into two or three.

3E D&D check 4E & Pathfinder check D&D Next check
Search Perception Intelligence (Search)
Spot Perception Wisdom (Perception)
Listen Perception Wisdom (Perception)

Magnification specs

For more on the advantages of multiple observation skills, see “A short history of perception in Dungeons & Dragons.”

In this guide, I sometimes refer to the perception tasks as Search, Spot, and Listen. In your game, apply the skill or check that fits the task.

Choosing which type of check fits a situation

D&D Next offers two types of observation checks, Intelligence (Search) and Wisdom (Perception), raising questions about which applies to a situation.

Spot and alertness checks

Wisdom (Perception) could have almost been called Alertness as these checks cover general awareness. When choosing whether to make these checks, consider the following observations:

  • Characters usually make Wisdom (Perception) or Spot checks to notice something while they’re busy doing something else: traveling, fighting, and so on.
  • Characters usually make Wisdom (Perception) or Spot checks because the game master calls for the check. The characters are busy, but the game master wants to determine if they notice something unusual. Characters make Wisdom (Perception) rolls when they look but don’t touch.
  • Wisdom (Perception) and Spot match with Tarzan’s alertness.
  • Wisdom (Perception) checks show keen senses too, but this typically only applies in one situation: Characters listening at a door make Wisdom (Perception) checks.

Search checks

Intelligence (Search) checks apply when characters spend time to examine and investigate.

Characters make Intelligence (Search) checks when players call for the check by asking to search.

Intelligence (Search) matches with Sherlock Holmes’ use of intellect of observe.

If you spend a moment to scan the surrounding trees, or press your ear to a door to hear what might lurk beyond, you’re relying on Wisdom (Perception) rather than Intelligence (Search). As a rule, if you’re not positive that Intelligence is the right choice, then Wisdom is the ability to use.” – D&D Next playtest rules

Listen checks

Third edition included a Listen skill as a nod D&D’s long tradition of characters putting their ears to doors. Aside for listening at doors, Listen skill frequently overlaps with Spot. When characters might both see and hear something like the monsters sneaking close to ambush, just roll to spot. Allowing characters to use both Listen and Spot to notice one thing makes stealth too difficult and adds excessive die rolling. Reserve Listen for cases where nothing can possibly be seen.

Next: Secrecy, metagaming, and perception checks