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

Try describing a place you know well in enough detail that a stranger could rebuild it. Where the ridge line falls, how far the treeline is from the water, which way the road bends, how the ground rises behind the house. It takes hundreds of words and the result is still wrong.

Now imagine correcting it. Move the hill slightly left is not a sentence with a meaning. Space is continuous and language is not, so every correction costs another paragraph and lands somewhere near where you meant.

This is the actual reason prompt-to-3D tools feel like a slot machine. The failure is not model quality. It is that the interface guesses at everything the sentence left out, and then has no way to express a small spatial adjustment.

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

Behaviour is the opposite. The wolf should stop chasing once it loses sight of you for four seconds is precise, complete and unambiguous. There is nothing to point at and nothing that would be faster to demonstrate.

Game logic is made almost entirely of statements like that. Damage falls off past ten metres. The door needs three keys. The shop restocks at dawn. Saying them is the fastest possible way to specify them, and being able to say them without knowing a language is the real unlock.

So text is not the wrong interface. It is exact for behaviour, and for space it needs two things a prompt box lacks: questions before anything is built, and a way to make a small adjustment without another paragraph.

More on this: Chat to game, and the part chat is bad at

It asks first. Questions come one round at a time, each with a recommendation and a line on why, and end in a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it. That is where the guess goes away: the ridge, the treeline and the road are decided with you, not for you.

Then it builds the world with world tools, as nodes and resources in your scene tree: terrain sculpted and painted, water, sky, weather, plants, the player controller, characters and props. It writes the behaviour as GDScript inside your project, and you never have to open the file. It runs the game itself, sends input events, reads the debugger and captures the viewport. Then you play it and say what is wrong, and it revises.

Moving the hill slightly left is still not a sentence with a meaning, so the same world tools are buttons around the Godot editor's own 3D view: Sculpt, Paint, Plants, Place, Water, Sky, Weather, Player controller, NPCs and Camera. That adjustment is a drag, and Godot's undo takes it back. A sentence gets you a valley; your hand gets you the exact valley.

That is why the app is not a chat box with a viewport attached. The editor around the chat is Godot's own, with the Scene dock, the Inspector and the Script editor.

More on this: Who writes the code in Flockbay?

A place you can walk around in, and one or two behaviours that work: the first thing the brief said to build. Not a finished game, and not a genre in a box. It will look like your idea rather than like a template, because the brief was about your idea.

You will also find that your idea was less specific than you thought. Almost everyone does. The brief's questions are where that starts, and playing the first version is mostly how you discover what you actually wanted. That discovery is not something a prompt can do on your behalf.

The descriptions that work are the ones with a condition and a consequence. When the player is seen, the guard shouts and the others come. After four seconds without line of sight, it goes back to patrolling. Those get built correctly the first time.

The ones that go wrong are adjectives. Make the guard smarter, make the combat feel better, make it more fun. Those are judgements about a result rather than descriptions of behaviour, and there is nothing in them to build.

When you find yourself typing an adjective, the useful move is to work out what the adjective would look like on screen and say that instead. That translation is the skill, and it is one that pays off in every part of the project.

Flockbay is a desktop app for Windows and Linux. It is downloaded and installed, not run in a browser, and it ships with Godot inside it so your game runs locally at your machine's framerate.

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

The platform is free, the world tools included. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

More on this: Create a game with AI, and keep the part that makes it yours