Every tabletop roleplaying game has its bread-and-butter scenes: the tavern rumor, the dungeon corridor, the tense conversation with someone who’s absolutely lying through their teeth. But sooner or later, the table wants something with a little extra spice. Someone wants to spring an ambush. Someone wants to flee across rooftops while goblins hurl insults and javelins. Someone wants to steal the duke’s jeweled owlbear statue during a masked gala without getting caught.
Ambushes, chases, and heists are wonderful because they change the rhythm of the game. They ask players to think fast, improvise, and work together. They also ask the Game Master to do a bit of careful handling, because these scenes can get messy if they’re too rigid or too random.
The good news? You don’t need a giant subsystem or a binder full of flowcharts. You just need clear stakes, active environments, and a willingness to let the players surprise you.
Ambushes: Make Surprise Feel Fair
Ambushes are tricky because no one likes feeling helpless. A good ambush should feel dangerous, not cheap. The players should think, “Oh no, we walked right into this,” not “Well, I guess the GM just wanted to hurt us.”
The key is foreshadowing. Before the arrows fly, give the party signs that something’s off. The forest has gone quiet. The road’s too clean. The old campsite still has warm ashes, but no footprints leading away. A flock of birds erupts from the trees ahead. None of these clues need to scream “ambush,” but they should give sharp players a chance to get suspicious.
If the party notices, reward them. Maybe they’re not surprised. Maybe they spot one hidden attacker. Maybe they get to choose better terrain before the fight begins. Even a small advantage makes their caution feel meaningful.
Also, think about what the ambushers want. Bandits may want valuables, not corpses. Predators may want to drag away one victim. Soldiers may want to capture a spy. This makes the scene more dynamic than “everyone fights to the death.” A group of highway robbers might open with a warning shot and a demand. Kobolds might attack, retreat, and attack again from another tunnel. Ghostly assassins might only target the character carrying a cursed relic.
Terrain is your best friend. An ambush in an open field is just a fight with a surprise round. An ambush in a ravine, a ruined market, a foggy swamp, or a crowded festival gives everyone toys to play with. Let wagons tip over, ropes snap, awnings collapse, horses panic, braziers spill, and statues topple. The more the battlefield moves, the more memorable the ambush becomes.
Finally, don’t make ambushes purely punitive. Sometimes the party should get ambushed because the enemies are smart. Sometimes they should get ambushed because they ignored clues. But if every road contains invisible murder archers, the players will stop engaging with the world and start poking every shrub with a ten-foot pole. Use ambushes like hot sauce. A little wakes up the meal. Too much ruins breakfast.
Chases: Keep Them Moving
Chases often sound exciting, then become weirdly slow at the table. Everyone checks movement speeds, counts squares, debates whether a bonus action dash works uphill in mud, and suddenly, the thrilling pursuit feels like filing taxes while wearing boots.
The trick is to focus on momentum. A chase isn’t just “who moves faster?” It’s a string of obstacles, risks, choices, and near misses.
Start by making the goal obvious. Are the heroes trying to catch a thief before he reaches the thieves’ guild? Escape guards before the city gates close? Reach the ritual chamber before the cult leader finishes chanting? A chase needs a finish line, even if that finish line changes.
Then build the chase in beats. In each round or scene, introduce a complication. A fruit cart blocks the street. A bridge is rising. A herd of goats floods the alley. The quarry dives through a gambling den. Rain turns the rooftops slick. A parade cuts across the road. The players should constantly choose how bold they want to be.
Safe option: slower, lower risk.
Risky option: faster, higher consequence.
For example, a character can follow the road around the burning wagon or leap through the flames and gain ground. They can push through the crowd carefully, or shove forward and risk angering bystanders. They can climb the wall or sprint through the guardhouse and hope nobody recognizes them.
This keeps everyone involved, including characters who aren’t built for speed. The barbarian can smash through a locked gate. The bard can misdirect the crowd. The druid can turn into something nimble. The wizard can block a street with fog. The rogue can take the terrifying shortcut across laundry lines because, of course, they can.
Don’t be afraid to zoom out. Not every chase needs exact distances. You can track progress with successes and setbacks. Maybe the party needs five successes before three failures to catch the target. Maybe each clever idea grants an advantage or counts as a success. Maybe a failure doesn’t end the chase, but adds a cost: lost gear, separated characters, damage, public attention, or the enemy reaching a stronger position.
Above all, describe motion. Wind in cloaks. Boots slipping on wet stone. A spell blast blows chimney soot into the air. A guard yelling, “Stop them!” from three streets back. Players will remember the chase because it felt like it had a heartbeat.
Heists: Let the Plan Matter, Then Let It Go Wrong
Heists are delightful because players love planning. They love maps, disguises, fake names, secret signals, and arguing for twenty minutes about whether the wizard should pretend to be a wine merchant. Let them have that fun. Planning is part of the heist fantasy.
But also, be careful. Too much planning can drain the energy from the session. If the group spends three hours preparing for a job that takes twenty minutes to play, the table may start to sag. Give them useful information, a few interesting unknowns, and then get to the action.
A good heist has three things: a target, security, and pressure.
The target is what they want. A jewel. A prisoner. A spellbook. A signed confession. A dragon egg in a velvet-lined warming box.
Security is what stands in the way. Guards, locks, wards, nosy servants, rival thieves, suspicious nobles, magical alarms, trained blink dogs, a floor that remembers footsteps.
Pressure is why they can’t just wait forever. The auction ends at midnight. The vault changes location at dawn. The target is being moved tonight. The gala only lasts four hours. The demon inside the mirror is getting chatty.
Once those pieces are clear, create multiple paths. Let sneaky characters sneak, social characters mingle, strong characters create distractions, and magical characters bend the rules. Don’t build a heist that depends on one exact solution. Players won’t find it, and even if they do, they may decide it’s boring and disguise the fighter as a pastry chef instead.
One useful trick is to separate the heist into phases: approach, infiltration, complication, grab, escape. You don’t need to announce these phases, but they’ll help you pace the session.
During the approach, the players get into position. During infiltration, they bypass the first layers of security. During the complication, something changes. A rival crew appears. The duke returns early. The “fake” idol starts whispering. During the grab, they reach the prize. During the escape, the whole thing becomes wonderfully loud.
Complications are important, but they shouldn’t erase the plan. If the players spent time getting guard uniforms, those uniforms should help. If they bribed the kitchen staff, that should matter. The fun comes when the plan works just long enough for everyone to feel clever, then breaks in a way that invites improvisation.
Also, embrace flashbacks if your table likes them. When a player says, “I knew this might happen, so earlier I planted a smoke bomb in the laundry cart,” you can allow it with a roll, a resource cost, or a limited number of flashback points. This keeps planning from becoming endless while still letting the characters feel like competent scoundrels.
The Shared Secret: Consequences Beat Failure
Ambushes, chases, and heists all shine when failure doesn’t simply stop the game. A failed perception check doesn’t mean instant doom. It means the ambush begins on enemy terms. A failed chase roll doesn’t mean the villain vanishes forever. It means the villain reaches the bridge first and cuts the ropes. A failed lockpick check during a heist doesn’t mean everyone goes home. It means the lock opens, but the alarm rune wakes up.
Think in terms of consequences, not dead ends. Keep the story moving, but change its shape. Put the characters in hotter water. Make the choices sharper. Give them a chance to recover in style.
The best scenes aren’t the ones where everything goes perfectly. They’re the ones where the ranger spots the ambush one second too late, the cleric tackles a fleeing assassin through a market stall, and the bard escapes the palace wearing the wrong noble’s hat.
So the next time your game needs a burst of energy, toss in an ambush with clues, a chase with wild obstacles, or a heist with just enough structure to go gloriously sideways. Your players will bring the chaos. You just need to give it somewhere fun to land.
Your Turn!
Let us know how your table handles these surprises in the comments below.
0 comments