AI adventure game maker, with the AI in the right place

The AI here writes the machinery of an adventure game — dialogue state, inventory, flags, triggers — and stays out of the two things that make an adventure good: the places and the words.

Adventure games fail in the plumbing

Ask anyone who abandoned an adventure project what stopped them and it is rarely the story. It is that the dialogue system got out of hand. A conversation that branches, remembers, re-enters at the right node, gives a different line on the second visit, and unlocks a flag that a door three rooms away is watching.

That is not creative work. It is bookkeeping with a lot of edge cases, and it is exactly the kind of thing Director 1 writes well. You describe the behaviour and it writes the GDScript in your project.

The result is that the parts of an adventure game that are actually about being a writer stay in your hands, and the parts that are about being a programmer stop being your problem.

The places you build yourself

Adventure games are about being somewhere. A study with the curtains drawn. A ridge where the path forks. A corridor that is deliberately too long. You build these by hand in the builder, and which tools the builder hands you depends on the pick you made when the project was created: 2D or 3D, two pictures, no default.

In a 3D world that is terrain, interiors, light, weather and time of day. In a flat one it is tile ground you drag into place, a sky colour with one band of scenery along the horizon behind it, and sprites positioned, turned and sized by hand. Top-down rooms in painted tiles is a first-class way to make an adventure here, not the thing you fall back to.

This is spatial judgement rather than technical skill, which is why it is the half you keep. A room reads correctly or it does not, and only you can tell.

Worlds can be small and dense or large and open. A twelve-room house is as reasonable a project as a valley, because the game runs on your machine rather than inside a hosted preview that quietly prefers small.

What the AI writes, specifically

Interaction: looking, taking, using one thing on another, and the refusal lines when it does not work. Inventory with combination and state. Conversations with conditions and memory. Journals that update. Triggers that fire once. Save files that restore all of it correctly, which is the part nobody thinks about until it breaks.

It also writes the movement and camera, because an adventure game where walking feels bad is an adventure game nobody finishes.

None of this requires you to read a script. It requires you to play the game and say when a conversation repeats itself or a door gives the wrong reason for being locked.

Puzzle fairness is not automatable

The tool will implement any chain of conditions you describe. It cannot tell you whether step three is a leap that nobody will make, because that is a fact about players rather than about code.

So you play your own puzzle, notice the leap, and change it. Being non-technical has nothing to do with this. You are the person best placed to judge whether your puzzle is fair, and handing the work back with a note is the normal rhythm here.

There is one more thing only you can judge, which is whether a puzzle belongs in this story. A mechanically fair puzzle can still be a mechanically fair puzzle that has wandered in from another game, and that is a tonal judgement rather than a design one.

The setup

Flockbay is a desktop app for Mac and Windows with Godot bundled inside it. Your game runs locally when you press play. There is no browser version and no streaming.

Building needs an internet connection, since Director 1, asset generation and world data all come over the network. Playing the finished game does not.

Where AI is a bad fit for this genre

Worth being direct. Generated prose is recognisable, and adventure games are made of prose. A description of a room written by a model reads as a description of a room, whereas a description written by you reads as a description of that room by someone who has an attitude about it. The second is why anyone plays these.

Generated puzzle design has the same problem in a less obvious way. A model will produce puzzles that are structurally valid and unmemorable, because the memorable ones depend on a specific joke or a specific piece of world knowledge that only exists in your game.

So the honest position is that the AI here is infrastructure. It writes the dialogue system, not the dialogue. It writes the inventory, not the joke about what is in it.

If what you wanted was a tool that writes the adventure for you, this is not it, and the ones that claim to be are producing something you would not want to put your name on.

Questions

Does the AI improvise dialogue while the player plays?
No. Director 1 writes the code at build time. The dialogue that ships is the dialogue in your project.
Can I make a text-heavy adventure with almost no world in it?
Yes, and 2D is often the honest pick for one. You choose 2D or 3D when the project is made. A painted room, a few sprites and a lot of words is a whole game.
Do I write the story?
Yes, and that is the intent. The tool removes the systems work so the writing is what you spend time on.
Do I need to code?
No. The GDScript is written for you inside a normal Godot project.
What does it cost?
Free to download, and the builder is free to use. Indie at $10 a month unlocks the AI assistance: Director 1 writing the gameplay logic, and generated textures, sounds, props and rigs. You can try the AI features on the free plan first.
How large should an adventure be?
Smaller than you think. Two hours that are well made beat eight that thin out, and finishing the short version teaches you more than half-finishing the long one.