Make a horror game with AI: the fear is in the level, not the code

Sightlines. How far you can see, what is around the corner, whether the corridor turns left or right, how long the walk back is. A room that is frightening and a room that is not can have identical contents and different geometry.

Light, and the absence of it. Not darkness everywhere — a screen that is entirely black is boring. Fear lives in the bit of the room you can nearly see.

And pacing, which is a level layout problem too: how long you go without anything happening, and whether the player has started to relax when it does.

None of that is code. All of it is the part you build with your hands, which is why horror suits this tool particularly well.

You lay out the space in the builder and walk it constantly. This is the whole job. A corridor that feels fine in an overhead view can be completely toothless from eye level, and the only way to know is to stand in it.

Fog and weather are properties of the world you set, and they are your main instrument. Pulling the fog in changes what the player can see, which changes what they fear, and it costs you one adjustment rather than a lighting rebuild.

Interiors get built from placed geometry, generated assets, sourced models, or your own files. Horror is forgiving about asset fidelity and unforgiving about layout, so put the time into the layout.

The systems. A torch with a battery that drains. A pursuer that hunts by sound and loses you if you break line of sight for long enough. A door that locks behind you. A sanity meter, a save point, an inventory of four items and no more.

You describe these in plain sentences and the GDScript appears in your project. Then you play, and the first version is nearly always too easy or too cruel, and you say which and it gets tuned.

That tuning loop is where horror is actually made. The distance at which the monster notices you is a number that has to be found by playing, not reasoned about.

Stage Engine is a desktop app for Mac and Windows, and your game runs on your own machine through the bundled open-source Godot. Nothing streams.

Horror depends on frame consistency and audio timing more than most genres. A stutter at the wrong second turns a scare into a bug. Running locally is what makes that controllable.

Building needs an internet connection. Playing the game you built does not.

They are the easiest thing to ask for and the fastest thing to exhaust. A player learns the trick in about four repetitions and then your game has nothing left.

The durable stuff is slower: a sound you cannot place, a room that is different when you come back, a resource that is running out. Those are also systems Director 1 can write, and they hold up over an hour of play in a way a loud noise does not.

Horror is carried by audio more than any other genre. A silent room with a good visual is unsettling for about four seconds. A room with the wrong sound in it stays unsettling for as long as you are in it.

Most of what you need is quiet: room tone, footsteps that change with the surface, a distant noise that has no visible source. The loud sounds get all the attention and do the least work.

Triggering all this is code, so it gets described and written like everything else. Choosing the sounds and deciding when silence is better is yours, and it repays more attention than almost anything you could add visually.