Skip to content

AI horror game maker: a plan for your first one

By Eduardo Orellana · Updated

Horror is the genre most often attempted first and least often finished. This page is less about the tool and more about the order to do things in so yours gets made. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

The main page on this subject is What is an AI game maker that writes a real Godot project?.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

Pick a shape before you pick a monster

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.

What gets built for you, and what you judge by eye

Flockbay is a desktop app for Windows, macOS and Linux with Godot inside it. It reads 2D or 3D from your description of the game and settles it before it creates anything, then agrees a brief with you and builds the place: the building, the rooms, the fog and the light in 3D; a TileMapLayer and sprites in a flat game. In this genre the layout is a large part of the fear and it has to be judged by eye, so you walk it, and Godot's own editor is there in the Standard and Full views when a wall needs to move a metre.

Flockbay 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.

The tuning pass is the game

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 Flockbay 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.

Things that quietly ruin horror games

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.

What it needs from you

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

The download is free. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

Sound is half the game, and choosing it is yours

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 the choosing 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, and Flockbay can generate the sounds themselves, effects, loops and music. 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.

A starting project for this is the horror game templates. The design note that goes with it is whether a horror game is really a movie.

Questions

Do I need to code the monster behaviour?
No. Describe how it hunts, how it loses you and what happens when it catches you, and Flockbay writes the GDScript.
Is it 3D or 2D?
Both, settled before anything is created. A 3D project makes first-person horror a normal case. A 2D one is built from a TileMapLayer and sprites, which is how a side-on or top-down horror game gets made in the same app, with the same chat.
How long does a small horror game take?
That depends entirely on how much you tune it, and tuning is the part that makes it frightening. The building is the fast half.
Can I share it with friends to test?
Yes. The app's Export makes a Windows, macOS or Linux build you can hand to a friend, and the built game runs locally without a connection.
What does it cost?
Nothing. Free to download. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

Free for Windows, macOS and Linux. Build one building, one night, one thing.

Download Flockbay free