How to Run a Horror RPG Campaign Without Any Visuals
Horror might seem like the hardest genre to pull off without visuals — no flickering lights, no monster designs, no sudden cuts to a terrifying face. But in practice, audio horror is some of the most effective horror that exists. Radio dramas in the 1940s, podcasts in the 2010s, horror audiobooks across decades, and now AI-narrated audio RPGs have all produced fear responses that visual horror struggles to match. The classic radio adaptation of "The War of the Worlds" caused mass panic in 1938 not despite the lack of visuals but because of it. Listeners' imaginations filled in details no special effects budget could ever afford.
This post is a craft guide for building and running horror campaigns in EchoQuest. Some of the techniques apply to any audio storytelling; others are specific to running interactive horror, where the player's own choices determine how deep the dread goes. If horror isn't your genre, the underlying principles — about pacing, withheld information, and the power of suggestion — generalise to any tense scene in any campaign.
Why Audio Horror Works
Fear lives in the imagination. The monster you can't see is almost always scarier than the one on screen. When a horror film shows you the creature, your brain categorizes it: "CGI wolf, cost $3 million, actors were on a set." The fear deflates. The thing has been resolved, given dimensions, made into a known entity. Once it's known, it's manageable. Once it's manageable, it isn't terrifying anymore.
When the narration says "you hear something large moving in the dark beyond the reach of your lantern," your brain generates the monster. And it generates exactly the version you personally find most terrifying, drawing from your own fears and imagery. No film budget could match that. A million-dollar prosthetic monster looks the same to every viewer; an unseen audio monster looks different to every listener and is custom-tailored, by your own subconscious, to scare you specifically.
This is why blind horror enthusiasts often have a nuanced vocabulary about audio horror that sighted critics lack. They've been listening to fear that the imagination assembles for them their whole lives. The sighted players who eventually fall in love with audio horror often describe the experience as "discovering they were missing something." They were. The thing they were missing was their own imagination's contribution to the fear.
The Craft of Audio Horror
Sound design is your biggest tool. A cave drip. A long silence. The sound of something wet. These ambient details create dread before anything narratively threatening happens. Set the sound environment early and let it do work before the story catches up. EchoQuest's automatic ambient layer handles much of this — when the location switches to a horror-tagged scene, the soundscape changes accordingly. But you can also explicitly call for sound cues in your Game Bible: "this scene begins with two seconds of silence, then a single dripping sound."
Withhold information deliberately. Horror is the gap between what your player knows and what they suspect. Don't reveal too much. Let them hear something without explaining it. Let them find evidence of something terrible without showing the event itself. The blood on the wall is scarier than the killing it implies. The empty room with three plates set for dinner is scarier than the people who used to live there. The AI GM is naturally inclined to over-explain — a tendency you can correct by telling it explicitly, in the world's tone notes, that horror in this world reveals itself through implication, not exposition.
Make the mundane wrong. The most effective horror isn't about monsters — it's about familiar things behaving incorrectly. An NPC who knew the player's name without being told. A room that's slightly larger on the inside than the outside. A child's laughter from a place where no child could be. A clock that ticks at the wrong rhythm. A road that turns differently each time you walk it. The wrongness should be small enough that the player isn't sure they're imagining it. Doubt is the texture of horror.
Use silence. Narrate a scene ending with something alarming, then go quiet. Let the player decide what to do. The silence after "you hear it stop moving" is more frightening than any follow-up description. EchoQuest's GM can be told to sit on a silent beat — "after this line, leave the player in silence until they take their next action." Many of the most memorable horror moments in our test campaigns came from a deliberately held silence right after a partial reveal.
Escalate slowly. The player should feel a slow creep of wrongness for several scenes before anything overtly threatens them. By the time the danger is explicit, the dread is already deep. The classic structure is: scene 1 establishes the world as normal; scene 2 introduces a single small wrong thing; scenes 3-5 layer more wrongness while the player tries to rationalise; scene 6 is when something undeniable happens. The audience should be ahead of the player by scene 4 — they know something is terribly wrong, but the player character is still trying to convince themselves there's a normal explanation.
Use the player's name. Once your character has been named, the GM saying that name in a scene where it shouldn't be said — by an NPC who shouldn't know it, in a place where it shouldn't be heard, in a tone that doesn't feel right — is one of the most effective horror moves available. The name is the player's hook. Twist that hook and you twist the player.
Don't be afraid of dark endings. Horror that always resolves cleanly isn't really horror. The best horror campaigns are willing to end in something other than triumph. A pyrrhic victory, a cost the character carries forever, a survival that feels worse than the alternative. Tell the GM up front that this campaign has darker possible endings; the world will lean into them when the choices warrant it.
Building a Horror World in EchoQuest
When writing your Game Bible for a horror campaign:
- Define the central horror clearly for yourself, but reveal it to players gradually. Write down what the threat actually is, what it wants, what its rules are. The AI GM needs to know to be consistent. The player does not, and shouldn't, until the moment is earned
- Write specific sensory details for each location — horror lives in specifics. "The hospital corridor" is generic; "The hospital corridor where the linoleum has buckled in places that make you walk slightly off-rhythm, the fluorescents flicker every 14 seconds, and there's a faint smell of formaldehyde that gets stronger near the locked door at the end" is a place
- Give your primary antagonist or threat a distinctive sound (before the player ever "sees" it). The player should learn to dread that sound across multiple scenes. The first time they hear it, they shouldn't recognise it. The third time, they should know they're in trouble before anything else has happened
- Establish what's normal in this world so deviations register as wrong. Horror requires a baseline. If everything is creepy from scene one, the player calibrates to that and nothing escalates
- Set content rating to Teen or Mature to allow genuine darkness. Family-rated horror exists, but it sits at a lower ceiling
Example opening:
"You've been assigned to document the decommissioned hospital on the edge of town. The front door is already open, which the records say it shouldn't be. Inside, the smell of antiseptic has been replaced by something older and wetter. Your torch throws shadows that seem to resolve into shapes a half-second after you look away. Your radio is playing static, and you don't remember turning it on."
That's a complete horror opening with no monsters and no jump scares — just wrongness, accumulating. Notice the specific sensory details: the door, the smell, the shadow timing, the radio. Each one is a small wrong thing. By the time the player decides what to do, they're already deep inside the dread.