# Text to game, taken apart into the four things a game is made of

The phrase "text to game" hides how much a game is. Split it into four parts and it becomes obvious which ones a sentence can carry, which need questions, and which stays with you. Flockbay is free, AI included: free hosted AI every day, or your own Claude, ChatGPT, agent or API key. It runs on Windows, macOS and Linux, on the official Godot engine.

Source: https://flockbay.com/text-to-game/ · Updated 2026-10-01

## One good sentence is about two per cent of a game

Take a real sentence: "a game where you run a lighthouse on a cold coast and something is wrong with the boats". That is a good idea and it is roughly two per cent of a game.

Underneath it there is a coast, which has a shape. There is a lighthouse, which has an interior and a stair and a light that has to do something. There are boats, which arrive on a schedule and behave in a way that is meant to be unsettling. There is a night length, a fuel supply, a reason to sleep and a consequence for not.

None of that is in the sentence, and none of it can be deduced from it, because a different person writing from the same sentence would build a different game. [The sentence is the seed](/ai-game-idea-generator/), not the specification.

## Four parts, and the AI builds three of them

World: the coast, the rocks, the light on the water, where the cottage sits relative to the tower. Built by Flockbay from the brief you approved, with world tools, as nodes in your scene tree. In a 3D project that means terrain sculpted and painted, water, sky and weather; in a 2D one it means tile ground, where the tiles, the edges and the collision follow from which cells are ground, and sprites at an exact position. When you want the cottage exactly somewhere, the same tools are buttons in the Godot editor, and moving it is a drag.

Systems: the fuel, the schedule, the light's rotation, whether a boat that gets too close does something. Described in words, written by Flockbay as GDScript inside your project. Words are the best possible instrument for this and always were.

Content: what the boats look like, what the radio says, the lines you wrote. Flockbay builds from [a library of ready-made objects](/asset-store/), generates pictures and sound (effects, loops, music), or uses your own files, and Godot's own shapes stand in when that is the honest fastest route to playing.

Feel: whether the night is long enough to be dreadful, whether the stairs take too long to climb, whether the light is bright enough. Flockbay plays the game to check it runs; whether it feels right is judged by you playing it, and it stays with you throughout.

## The brief comes before the build, so the game stays yours

It would be easy to sell a chat box that produces a whole game from a paragraph. The problem is that the result is always someone else's: a template with your nouns in it, and the moment you want it to be specifically yours you have no instrument except more paragraphs.

Flockbay asks instead. Questions come one round at a time, each with a recommendation and a line of why: how long a night lasts, what the boats do, what happens when the fuel runs out. Then a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it, so the first build is your game, small, rather than a template, large.

After that, every change is held against the brief, and the small spatial ones do not have to go through words at all. [The by-hand world tools](/no-code-3d-game-maker/) sit around the Godot editor's own view, so moving the cottage is a drag instead of a negotiation, and Godot's undo takes it back.

That is the argument. Use text to say what you want, let the questions turn it into a brief, and use your hand only where your hand is exact.

## The loop is a conversation with a game you keep going back into

Flockbay builds a stretch of coast and the tower, makes the light rotate and the fuel drain. You play it, and the fuel drains too fast, so you say so. You play again and the night is boring, so you ask for a boat.

It is not a generation step followed by a result. It is a conversation with a game you keep going back into, and the useful thing you bring to it is impatience with what is not right yet. Handing the work back is the normal loop rather than a failure.

## People get stuck on ideas, not on code

The code is rarely where it stops. The two common stopping points are having no second idea after the first thing works, and having a first idea so large that nothing works for weeks.

The first is solved by playing what you made and noticing what is missing. A world you can walk around generates its own next questions, and they are better questions than the ones you had before it existed.

The second is solved by cutting. One place, one mechanic, one reason to be there. The brief does some of that cutting with you: an idea too large for a first version gets the truth and a smaller start, with the rest written down as what comes after. The full game does not go away by being postponed, and [the small version](/blog/whats-the-point-of-prototyping/) is what tells you whether the full one is worth building.

## It is an ordinary Godot project on your own disk

Flockbay is a desktop app for Windows, macOS and Linux. It is downloaded and installed, and it ships with Godot inside it, so your game runs locally on your own machine rather than in a tab or on a server.

Your project is [an ordinary Godot project](/what-is-godot/) on your disk. Godot is open source, so the folder opens without this app.

Building needs an internet connection, because the chat, asset generation and world data all come over the network. Playing what you built does not. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

## Questions

### Can I type one sentence and get a finished game?

No. One sentence starts the questions, and the questions end in a brief. Once you approve it, Flockbay builds that first version, world and behaviour, and plays it to check it runs. Finishing it is a loop of you playing and saying what is wrong.

### How long until something is playable?

A place you can walk around with a working behaviour or two is an evening. A game with a shape is considerably longer, and that is true in every tool.

### Do I need to know how to code?

No. Flockbay writes GDScript into your project. You can read it, since it is a normal Godot project, but nothing asks you to.

### Is it 2D or 3D?

Either. Say which your game is and the world tools follow. A 3D world is terrain, water, sky, weather, plants and props. A 2D one is tile ground, where the tiles, the edges and the collision follow from which cells are ground, a band of scenery behind it, and sprites at an exact position, rotation and scale. Terrain and weather have no meaning in a flat world, so a flat world gets its own tools.

### Does it run online?

The app is a desktop download for Windows, macOS and Linux. Building needs a connection because the AI and asset generation are online; playing what you built does not.

Download Flockbay free: Flockbay is free to download for Windows, macOS and Linux. https://flockbay.com/

Related: [Text to 3D game](/text-to-3d-game/), [Make a game from text](/make-a-game-from-text/), [Prompt to game](/prompt-to-game/), [Story to game](/story-to-game/), [Idea to game](/idea-to-game/), [Voice to game: what talking can and cannot build](/voice-to-game/)