A few years ago, researchers in Denmark did something wonderfully cruel. They strapped heart-rate monitors onto 110 people, sent them through a haunted house, and asked two questions. How scared were you? How much fun was that?

Guess what? Fun went up with fear. Then, past a certain point, fun crashed. Too little fear, and people got bored. Too much, and it stopped being fun at all. The researchers called the peak a “sweet spot” (Andersen et al., Psychological Science, 2020).

That curve is your whole job as a horror GM. Get players to the top of the hill and keep them there. And the fastest way to fall off the far side? Take away their choices.

I learned this the hard way. My first Call of Cthulhu one-shot ended at 10:40 p.m. sharp, because I wrote it that way. Cultists win. Sanity gone. Everybody dies. I thought it was bleak and brilliant. Then my friend Marcus folded his arms and said, “So nothing we did mattered?”

He wasn’t scared. He was annoyed. At me.

Did that one-shot scare anybody? Nope. Well, actually, it scared one person pretty badly. Me. Out of running horror for a full year.

So let’s fix that. This post covers how to tell fear from frustration, why your players’ characters can be doomed while your players still feel free, and a seven-step method I call Scared, Not Stuck.

Why Getting Horror Right Is Worth It

Horror isn’t a side quest in this hobby. It’s a main questline.

Back when Roll20 published its Orr Reports, Call of Cthulhu sat at number two, played by about 13% of users in Q3 2019, right behind D&D 5e (Andrew Hooks). The same data showed Call of Cthulhu games averaged 11.9 hours of total play, compared to 40 hours for other systems (Bell of Lost Souls). Horror runs short. One-shots. Mini-arcs. That means every single session needs to land, because you don’t get a dozen more to recover.

And the indie scene is on fire. The Mothership sci-fi horror boxed set raised $1.4 million on Kickstarter in 2021 (Rascal). People want horror. They want it to work. So what breaks it?

Fear vs. Frustration: The Blame Test

Look, horror needs helplessness. Justin Alexander of The Alexandrian lists it alongside danger, anxiety, and mystery as a core piece of the genre (The Alexandrian). But he draws a hard line: never railroad players into danger. When the helplessness comes from the GM rather than the world, players stop caring, and fear turns into anger.

The haunted-house research backs this up. Mathias Clasen, who runs the Recreational Fear Lab at Aarhus University, describes the sweet spot as a place where “you feel you have a certain amount of control over the situation,” with a baby bit of unpredictability on top (Genetic Literacy Project).

Control. That’s the secret ingredient. Scary is fine. Powerless at the table is not.

So here’s the fastest diagnostic I know. Call it the Blame Test. After something awful happens in your game, ask yourself: who is the player mad at?

1. The monster. Perfect. The horror is working.
2. Themselves. (“I KNEW we shouldn’t open that crate!”) Even better. That’s guilt, and guilt is rocket fuel for dread.
3. You. Uh oh. That’s frustration. Fix it before the next scene.

If a player glares at you and not at the thing in the walls, the fear has left the building. What stayed behind is a grudge.

Doomed Is Fine. Stuck Is Not.

Blogger Ludovic Chabant makes a split that clears up a ton of confusion: loss of agency for the character is different from loss of agency for the player (The Stochastic Game).

Think about a Souls-style boss fight. You get flattened fifteen times. Is that frustrating? Kind of. But every death is your fault, and every retry is your choice. Now think about a cutscene where the game grabs the controller and walks your hero into the obvious trap. That’s the one people rage about.

Your players’ characters can be doomed. Cursed, infected, hunted, down to their last match. Your players should never be stuck watching a cutscene with dice.

Here’s a real example. On the blog Roleplay Letters, a GM ran a scripted sci-fi horror module where infections triggered on a schedule. One player complained that nothing they did mattered, since everyone was getting infected anyway. The GM’s verdict? The complaint was correct (Roleplay Letters).

Fixed threats are fine. The monster can be unkillable. Fixed outcomes for player choices? That’s the rail. Lay those rails and, sorry, nobody likes you.

The Scared, Not Stuck Method

Seven steps. Think of them as save points on the way to a good horror night.

1. Get Buy-In for the Kind of Fear

“Want to play a horror game?” is the wrong session zero question. Lots of people say yes to Cthulhu because tentacles sound cool. Fewer signed up to feel anxious for real.

So ask the better question. Do you want to feel scared, or do you want to play characters who feel scared? The Mothership Warden’s Operations Manual is blunt here. Actually scaring your players, it says, “is not a measure of a successful game night” (via James Maliszewski). Most players want to eat chips while their characters panic. That’s fine!

Then set up lines, veils, and an X-card. Here’s the part people miss: safety tools are agency tools. A player who knows they can stop a scene is a player brave enough to walk into one.

2. Threaten What the Players Care About

Players can’t fear losing something they don’t care about. Alexander points out that the target doesn’t need to be a PC at all. Their horse, their home, their favorite NPC all count.

At my table, the party adored Old Bett, a baker who slipped them free pies. In session four, Bett stopped answering her door. Nobody rolled a single sanity check. Everybody was terrified anyway.

Your job before the scares start: learn what they love. Then put it near the monster.

3. Signal Danger Before It Lands

Horror movie audiences yell “Don’t go in there!” Your players get to be the audience and the idiot with the flashlight. Let them know the risk.

Try open-information horror. Say it out loud: “You, the player, know those basement stairs are rotten. Your character has no clue.” Now the player picks. Go down anyway? Hunt for another way? Send the dog?

Screen Rant’s horror tips put a neat rule on it: deceive the character, never the player (Screen Rant). Lie to a player and they stop trusting your descriptions. Lie to a character, with the player in on the joke, and you get delicious dread.

4. Make Every Bad Outcome Traceable to a Choice

This is the big one. Before anything terrible happens, ask: “Which choice caused this?” If the answer is “my script,” rewrite it.

It doesn’t need to be a dumb choice. It can be a brave one. The player who stayed behind to hold the door made a choice. Her character dying there is tragic, not unfair. The player who got eaten because you decided Act 2 needed a death? That’s a naughty boy move, and your table will notice.

5. Swap Instant Death for Clocks

A fair point from The Alexandrian’s comment section: an out-of-nowhere PC death often deflates the scene. That player sits out, and the dread leaks away.

So use a countdown clock. Draw a circle with six slices and label it “The Thing in the Walls Finds You.” Every loud action fills a slice. Players can see it. Players can slow it. Players can gamble on it. When it fills, something awful happens, and everyone at the table knows exactly why.

And yes, there are fates worse than death. Delta Green co-creator Dennis Detwiller gives GMs a cold rule: “Do not protect the characters” (Detwiller Design). But losing a character to infection, possession, or a slide into madness keeps the player in the game longer and hurts way more.

Bonus trick from Detwiller, and it’s my favorite piece of lazy genius. He kept describing one player’s awful, squealing brakes. The player chose to take the car to a mechanic, who found a GPS tracker in the wheel well. No markings. No trace. Detwiller never followed up. He didn’t need to. The player stayed paranoid for the rest of the game, all on his own. Zero rails. Maximum dread.

6. Let Players Write Their Own Breakdowns

Old-school fear checks work like a stun lock. You fail a roll, you lose your turn, you sit there. Gnome Stew went as far as arguing that most games built on fear checks would be better off without them (Gnome Stew).

Newer games put fear on the table as something visible. Mothership tracks Stress and Panic. Daggerheart, which launched in May 2025, rolls Hope and Fear dice together on every check (ScriptoriumGM).

You can steal this idea for any system. When a character faces something horrible, give the player a menu:

• Keep it together, and take a mechanical penalty.
• Crack, and describe what your character does. In exchange, they gain an edge, like a burst of adrenaline or a desperate idea.

Fear the player writes feels like play. Fear the dice impose feels like a lost turn.

7. Pace Spike and Release

Remember the heart-rate data? The same study found enjoyment linked to “just right” swings in heart rate, while big, long-lasting swings often turned unpleasant (ScienceDaily).

Survival horror video games nailed this decades ago. Resident Evil gives you save rooms with calm music. Alien: Isolation gives you lockers to hide in. You get a breather, you choose when to step back out, and the fear hits harder because of it.

Build save rooms into your sessions. Every 30 to 45 minutes, offer a safe-ish scene: a locked church, a warm diner, a quiet car ride. Let players plan. Then let them decide when to leave.

One Scene, Three Rewrites

Let’s put the method to work on the most horror-movie scene ever: the basement door.

The rails version: “The door slams behind you. You’re trapped. The creature attacks. Roll sanity.” Four sentences, zero choices. Somebody at your table is checking their phone.

Rewrite A, signal the danger: Scratching comes from below. Chalk tally marks line the doorframe, and a new one appears each time someone makes noise. The players know something is counting. They choose whether to go down.

Rewrite B, add a dilemma: The missing kid’s voice calls from the basement. Also, the lantern has maybe ten minutes of oil left. Go now, or go back for supplies and risk the kid? Every option costs something.

Rewrite C, let the player author it: Ask, “What does your character hear down there that they really, really hope is a rat?” Now the player built the fear. You just deliver it.

(I just counted, and this post says “basement” way too much. I choose to curse myself and move on.)

Quick Fixes for Common Table Problems

“My players joke through everything.” Check what kind of joke it is. Alexander separates jokes that help players cope with the danger from jokes that push the game away. Coping jokes are fine. Nonstop distancing jokes mean the group isn’t bought in, so talk about it.

“A PC death felt like a screwjob.” Did you signal the danger first? If not, use step 3 next time. If yes, and the player chose the risk, that death belongs to them.

“They’re stuck on the clues.” Stuck is not scared. Stuck is homework. Give every key conclusion three clues, a rule The Alexandrian calls the Three Clue Rule, so the dread keeps moving.

“Sanity rules keep stealing characters.” Turn lost turns into hard choices, like in step 6.

Keep the Monster, Lose the Rails

Horror at the table is a balancing act on a curve. Too little fear, and your players snack their way through a spooky story. Too much helplessness, and they stop feeling scared and start feeling cheated. The haunted-house science and a pile of veteran GMs point in one direction: fear works best when players feel some control.

So hold onto the core idea. Characters can be doomed. Players should never be stuck.

At your next horror session, run the Blame Test after every awful moment. Watch who the players glare at. If it’s the monster, pat yourself on the back. If it’s you, pick one step from the Scared, Not Stuck method and try it the very next scene.