A horror game maker for people who understand pacing

What makes a horror game work is not the monster. It is the four minutes before the monster, where nothing happens and the player becomes certain something is about to. Get that wrong and no amount of design on the creature saves it. Get it right and a corridor with a dripping pipe is terrifying.

That means the craft is in timing, restraint and the shape of a space. How long the player is alone. How far they can see. Whether the sound stops or continues when something goes wrong. These are decisions you make by walking through the thing and feeling it, and then changing it because it was too slow or not slow enough.

None of it requires you to write code. All of it requires you to iterate fast enough to feel the difference between eight seconds of silence and twelve.

In Flockbay you build the world by hand. Creating a project asks whether you are making a 2D or a 3D game, and everything in this section is the 3D side of that answer, because fog and the way light falls are 3D tools and a corridor you walk down is a 3D place. That suits horror particularly well because the place is the mechanism. You shape the ground, put fog in the low parts, place the buildings, decide where the sightlines break and where a corner hides the rest of the corridor.

Weather and sky are part of the toolkit rather than decoration. A world where the light actually falls, where fog thickens, where rain covers the sound of footsteps, gives you the vocabulary horror runs on. A flat evenly-lit room does not, which is why so many first horror games feel like a well-lit warehouse with a jumpscare in it.

Because the game runs locally on the copy of Godot bundled with the app, the world can carry real terrain, weather and things moving in it without the compromises a browser tool has to make. That is what makes a dark forest an option rather than an ambition.

Flockbay writes the behaviour. You describe it: the thing follows sound rather than sight, it loses you if you stand still for six seconds, it does not enter lit rooms, it gets faster the longer you have survived. That becomes GDScript inside your Godot project.

Then you play it in the dark, which is the only way to know. Almost always the first version is wrong in an instructive way — it is too fast, or too obvious, or it kills you before the dread has anywhere to go. You say what is wrong and it changes, and you go again.

That cycle is where the game gets made. Nobody designs good horror on paper. They design it by being frightened by their own build, or failing to be, and adjusting.

Build one corridor and one room. Make the corridor long enough to be boring. Put a sound at the far end that stops when the player gets close. Do not add a monster yet. Play it, and see whether you tense up. If you do not, the problem is the space, and adding a creature will not fix it.

Then add something that reacts to the player rather than a scripted event. Reactive fear lasts and scripted fear works once, and the difference is worth learning early on a small scene rather than late on a big one.

Building needs an internet connection because the chat, asset generation and world data come over the network. Playing what you built does not. The app and the whole builder are free. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.