Make a Horror Game With AI: Less Monster, More Dread
Horror is made of waiting and not knowing, so build one dark corridor, one sound and one simple rule for the threat before you build any monster. Your AI can write the game, but only you can tell whether it is frightening.
Why can your AI not judge this genre?
It cannot sit alone in the dark. It has no idea whether a room is black enough, whether a sound is too loud, or whether a silence has gone on for the right length. It will tell you the atmosphere is chilling, and that sentence means nothing.
Worse, fear wears out. The same trick twice is a joke. A bang that made you jump on Monday will not work on Tuesday, and you will play your own game far more often than anyone else. Ask a friend to try it, because you have become immune.
So your job here is a director's job. The AI runs the machine. You decide when the lights go out.
What is the smallest version that can scare someone?
Three minutes in one place. Take a lift engineer on the night shift in an empty office tower. The corridor lights are on motion timers and go off behind you. Far away, a lift dings, and nobody else is in the building.
That needs a slow walk, a narrow torch beam, a low hum, your own footsteps and one wrong sound. No monster has appeared, and the player is already holding their breath.
In what sequence should the scare be built?
- Darkness, slow movement and the torch.
- Sound. Do this early, because sound does more of the work than pictures do. Start with hum and footsteps.
- One event, tied to a place: the lights behind you die.
- A threat with one rule the player can learn. Say it follows the sound of footsteps, so standing still keeps you safe, while the torch battery runs down.
- A safe spot, such as the lift. Fear needs relief, or it turns into numbness.
- An ending, which can be very short.
Think of it as breathing: calm, uneasy, threat, relief, and again, each round a little worse.
What ruins a horror game?
Showing the monster. Seen clearly and often, it stops being a horror and becomes a problem to solve. A chase every thirty seconds is an action game with the lights off. Keep it at the edge of the torch beam for as long as you can.
The other trap is real darkness. If players cannot see where they are going, they get annoyed, not frightened. Dark should mean they can see just enough to imagine the rest.
What about flickering lights?
They are a staple of the genre, so take care. W3C's web accessibility rules say content should not flash more than three times in any one second, because flashing can bring on migraines, dizziness, nausea and seizures. Use that as your limit, and add a warning at the start.
Paste this to your AI
Build a three-minute horror scene for the browser: one dark corridor, a narrow torch beam, slow walking, and no monster on screen.
Draw the tension loop first, as a state machine in a Mermaid diagram: calm, uneasy, threat near, hiding, safe again, caught. Beside each state, write what I see and hear, and name the one rule that moves the threat between states. Make sure calm can always return unless I am caught. Build from that.
Nothing may flash more than three times in any second.
You cannot see or hear this the way a player does, so never tell me a scene is scary or dark enough. Show me what sets off each sound and event, at which spot, after how long. For the feeling itself, tell me you do not know, then let me decide.
Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP
How to check it worked
- Play in the dark with headphones. Do it once, alone. Where did you slow down?
- Stand still for a minute. The game should keep working on you while you wait.
- Play it twice. If the second run does nothing, you have a surprise, and you want dread.
- Try it in daylight. You should still see where you can walk.
- Count the flicker. Slow it down if you can count more than three flashes in a second.
- Watch a friend. Note where they stop walking, not where they jump.