Skip to content

Describe a game, then reach by hand what description cannot

By Eduardo Orellana · Updated

Description is an excellent instruction for behaviour and a rough one for space. Flockbay builds the code and the world from your description, and hands you direct controls for the exact spot. 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 AI game generator: what one sentence can generate, and where it runs out.

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

Two kinds of sentence

Compare two instructions. "When the player steps into water, they slow down and the camera drops closer." And: "the rocks along the shore should be a bit more scattered, and that one is too big."

The first is precise. It has a trigger, a condition and two effects, and a machine can turn it into code that does exactly that. The second is not an instruction at all; it is a gesture pointed at a screen. Read it back in a week and you cannot reconstruct which rock.

Almost every disappointment with describing a game to an AI comes from that second category. The tool is fine at behaviour and rough at arrangement, and the last metre of arrangement is where a world becomes yours.

More on this: Make a game from text: where writing works and where it stops

What you describe

In Flockbay you describe the game, and the AI turns it into a brief, one round of questions at a time with a recommendation for each. Once you approve the brief, it builds the scenes and writes the GDScript for the behaviour into your project. Rules, systems, states, consequences. What happens when you pick the thing up. What the guard does when it loses you. How the day changes the world. What a save file contains.

You can be as detailed as you like or start rough and correct by playing. Rough is usually faster: get the mechanic in the game, hold it in your hands, and then say the actual thing you want, which you normally cannot articulate until you have felt the wrong version.

The code lands in your own project, and the project is a real Godot project. You are not asked to read the script. You are asked to run the game and say whether the water felt right.

More on this: Text to 3D game: the part text is good at, and the part it is not

What you move instead of describing

Flockbay builds the scenes too: buildings and characters in 3D, with a lake or weather from a Godot plugin when the game needs one; painted tile cells and sprites in 2D. What description cannot reach is the gesture: the rock that is too big, the crate a little too far left. For those, Godot's own editor is there in the Standard and Full views, so you shrink the rock by shrinking it and move the crate by dragging it, and Godot's undo takes it back. Neither requires code, and neither goes through a text box.

Direct control is simply the right instrument for that kind of spatial call, in the same way a text description is the right instrument for a rule. Flockbay builds and writes the code, or you use the same tools by hand, and a description never silently rearranges your scene.

More on this: Voice to game: what talking can and cannot build

What happens after you describe it

The game runs locally. Flockbay is a desktop app for Windows, macOS and Linux and it ships with Godot inside, so pressing play starts your game on your machine at your machine's framerate. No streaming, no browser tab, no waiting for a queue.

That short loop is what makes description workable at all. You say a thing, you play it within a minute, and you know immediately whether the sentence you wrote meant what you thought it meant. The revision is the work, not the failure.

Building needs an internet connection because the chat and asset generation come over the network. Playing what you already built does not.

Writing a description that gets you somewhere

Name the trigger, the actor and the outcome. "When the player enters the cave, the torch lights and the ambient sound drops" is buildable. "Make the cave spooky" is a mood. It gets you a first attempt, and then the mood is yours to tune, with sentences about the light, the sound and the pacing, or with the Inspector in the editor.

Ask for one behaviour at a time. A paragraph containing six systems produces six things you cannot individually judge. One thing, play it, then the next.

And describe the effect, not the implementation. You do not need to know how a state machine works to say that the enemy should hesitate before charging.

When your description keeps being wrong

It happens, and it is almost never because the words were unclear. It is because you asked for the implementation you imagined instead of the outcome you wanted.

If you say the enemy should have a three second cooldown, you get a three second cooldown, and the fight is still boring. What you actually wanted was a gap where you feel safe enough to move. Say that, and the number becomes a thing to tune rather than a guess you have committed to.

The habit worth building is to describe the feeling you are chasing alongside the mechanic. You have every right to that judgement, and it is the input nobody else can supply.

Questions

Can I just describe my whole game and get it back?
Not in one go, and nothing can. Your description becomes a brief you approve, then Flockbay builds the world and writes the code. Exact arrangement is the part a sentence specifies worst, so you judge it by playing and move things by hand when that is quicker.
What language do I describe things in?
Plain English about what should happen. You do not need to know the names of engine features or write anything that looks like code.
Do I need to be able to read the code that comes out?
No. It is a normal Godot project so you can, but the loop is play it and say what is wrong.
Is it a browser tool?
No. It is a desktop app for Windows, macOS and Linux, and the game runs locally on the bundled Godot.
What does it cost?
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.

Free for Windows, macOS and Linux. Describe the game, then move the rock yourself.

Download Flockbay free