# How I ditched scripted jumpscares and built a dynamic "tension director" in UE5 (Breakdown in comments) — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/ab7489c17243e261

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-10-11 13:20 ingested 2026-10-12 02:37

[original source ↗](https://www.reddit.com/r/gamedev/comments/1x382ms/how_i_ditched_scripted_jumpscares_and_built_a/)

## retained text



```
I'm developing **Fear: Nightmare Citadel** — a psychological horror game with a unique gothic castle aesthetic. For a long time, scaring the player just didn’t feel right. Everything was tied to static trigger zones, which meant zero replayability on a second run, and the timing often felt completely random on the first.



So I scrapped the old system and built a lightweight solution I call a "tension director."



The core idea: The game tracks the player's approximate stress level instead of just firing events at fixed coordinates.



What gets tracked:

 Time passed since the last scare event

 Player state (light sources, equipped items, health)

 Spatial context (is the player in a safe zone or trapped in a narrow corridor?)



How it actually works:

 Dynamic Pacing: If the tension stays flat for too long, the system queues up something subtle: distant footsteps, a flickering light, or a creaking door. Conversely, if the player barely survived a high-stress situation, the system intentionally dials back the intensity so the following calm moment feels even more unnerving.

 Out-of-Sight Spawns: Major events never occur directly in the player's field of view. Everything impactful happens behind them or just around the corner—the player's imagination creates a far worse picture than any asset I could ever make.

 Audio Over Visuals: What surprised me most was that audio had a much higher impact than visual scares. Audio sources occluded by walls (like movement in an adjacent room) proved to be way scarier than anything shown on screen.



What I'd do differently: Initially, I set the rules to be too strict, making the game feel almost predictable—like it was blatantly reading the player's inputs. I had to ditch strict timers and reintroduce a healthy layer of randomness.



Everything is implemented in Unreal Engine 5 using MetaSounds and a standard line-trace audio occlusion setup, driving around 20 procedural ambient events.



If you're curious to see how this plays out, our free demo drops on Steam on October 19th for Steam Next Fest:

https://store.steampowered.com/app/5244810/Fear\_Nightmare\_Citadel\_Demo/



I’d love to hear how other devs handle horror pacing! Do you hand-craft every single trigger, build systemic rulesets, or go with a hybrid approach? And if you give the demo a try and notice the tension director acting weird or breaking the atmosphere—please let me know!
```



document fetched 2026-10-12 00:24 · canonical https://reddit.com/r/gamedev/comments/1x382ms/how_i_ditched_scripted_jumpscares_and_built_a
