Prompt to game, with the part nobody mentions

Rules. Logic. Behaviour. "The lantern goes out if you stand in the rain for more than ten seconds" is a sentence that carries all the information needed to implement it, and Flockbay will write the GDScript for it in your project.

Anything with a shape is different. "A village at the foot of a mountain, with the path from the north running through it" is a sentence that leaves out everything that matters: how steep, how far, where the houses sit relative to the road, where you can see the mountain from. A tool that builds straight from it is guessing, and you get its guess.

So Flockbay does not build straight from it. It asks, one round at a time, with a recommendation and a line of why on each question, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it. Then it builds the village, the mountain and the path, and writes the code that runs them.

For the one call that is pure taste, your hands can take over. The world tools Flockbay uses are also buttons in the Godot editor, so moving one house is a drag, and Godot's undo takes it back. A sentence gets you a village; your hand gets you the exact one. You never have to use them.

More on this: Vibe coding a game, and the part vibe coding is bad at

Prompt-to-game demos are usually short because short is where they work. One sentence, one scene, something moves. It is a real capability and it is also the easiest possible case.

The hard case is hour four, when the game has twelve interacting systems, you want the eleventh changed, and the change must not break the other ten. That is where a tool either holds up or does not, and it is not a thing a demo can show you.

What helps at hour four is that the code lives in a real Godot project on your disk, visible and editable, rather than in a hidden state somewhere. Changes are made to a thing that exists. And Flockbay plays its own work after a change: it runs the game, sends input events, and reads stdout and the debugger, so a GDScript parse error is its problem to catch before it is yours.

More on this: Can AI make a video game from a prompt?

Say what should happen. Play it. Notice it is wrong. Say what is wrong. Play it again.

That fourth step is the one people underestimate. "The enemy should notice me sooner" is more useful than any first prompt, because it is a correction against something real rather than a guess about something imaginary. Flockbay makes the change and holds it against the brief you approved. The best results come from people who play a lot and are specific about what bothers them.

You do not need to write code to be specific. Not writing code has nothing to do with not knowing what feels wrong.

Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside it. Press play and the game runs on your own hardware, locally. There is no browser preview and nothing is streamed to you.

Building needs an internet connection, since the chat, asset generation and world data all come over the network. Playing what you built does not.

Free to download, and the world tools are free. Flockbay is free, AI included: free hosted AI every day, or 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.

More on this: The easiest game maker to actually finish something in

Name the trigger and the outcome. Something happens, and then something else follows. That is the shape Flockbay can turn into code, and it is a much better opening than an adjective. The brief's questions will push you toward it anyway.

Give numbers when you have them. Ten seconds, three hits, twice as fast. If you do not have a number, say so and pick one to try, because a number you can adjust is more useful than a vague word you cannot.

Keep one change per request once the game exists. Asking for six things at once makes it hard to tell which of them landed badly, and hard to undo just the bad one. Small requests, played after each one, get you somewhere faster even though they feel slower.

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