AI horror game maker: a plan for your first one

Horror splits into shapes that play completely differently. There is the hunted game, where something is looking for you and you have nowhere to fight from. There is the exploration game, where the threat is mostly implied and the tension is not knowing. There is the resource game, where fear comes from having four bullets and a decision.

People usually start by designing the monster, which is the least load-bearing part. Pick the shape first, because it determines everything else: whether you need combat, whether you need hiding, whether a map even helps you.

Then choose the smallest version of it. One building. One night. One thing in it. Finished small horror is frightening; unfinished large horror is a folder.

Stage Engine is a desktop app for Mac and Windows with Godot inside it. You build the place by hand — the building, the ground, the fog, the light — in the builder, because in this genre the layout is a large part of the fear and it has to be judged by eye.

Director 1 writes the code. The thing that hunts you, the hiding mechanic, the torch battery, the door that will not open until you have found three things, the moment the music stops. You describe the behaviour and it writes GDScript into your project.

You then play it in the dark and find out that nothing is scary yet. That is the normal state of a horror project at this stage and it is where the actual work starts.

Almost everything frightening in a finished horror game is a number that someone sat and adjusted. How far the sound carries. How long the corridor is. How many seconds of silence before the second noise. How fast it moves when it sees you, and whether that is faster than you.

You will change these dozens of times, and each change is a sentence to Director 1 rather than a script edit, which is what makes dozens of times practical.

Test with other people early. You cannot be frightened by your own game after the fourth run, so your judgement about the scares expires quickly and someone else's face is the only reliable instrument you have.

Showing the creature too clearly and too early. Fully lighting a scene so nothing is hidden. Music that announces a scare before it lands. A death that costs the player ten minutes, which converts fear into irritation faster than anything else.

And frame drops. A stutter at the exact moment of a scare removes the scare entirely. The game running locally on the bundled Godot rather than in a browser tab is a genuine advantage here rather than a technicality.

A Mac or Windows machine. An internet connection to build, because Director 1, asset generation and world data are all online. The finished game runs locally, so you can hand it to someone on a laptop anywhere.

The download is free and there is a free plan. Indie is $10 a month and Pro is $50 for more usage.

Everything above is about systems and space. The thing that will do the most work in your finished game is audio, and it is worth saying plainly that this is your job.

Where sounds come from, how far they carry, whether the player can tell direction — those are systems and they get written for you. Choosing the actual sound, and choosing silence, is taste.

Silence is the underused one. A stretch with no music at all, after ten minutes of ambient noise, does more than any sting. Most first horror games have far too much sound in them.