# An AI game maker that writes real code

Some AI game makers write real script into a real engine project. Others assemble behaviour from a fixed internal list and describe that as AI. Both are sold with the same words, and the difference decides what you can build in month two rather than in week one. 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.

Source: https://flockbay.com/ai-game-maker-that-writes-code/ · Updated 2026-10-01

## The two things "AI writes your game" can mean

The first: a model produces source code, in a language the engine runs, in files that live in your project. If you opened the folder you would find text you could read, edit or hand to a developer.

The second: a model chooses from [behaviours the tool already implements](/how-do-ai-game-makers-work/) and configures them. Nothing new is written. The output is a configuration, and the vocabulary is fixed at whatever the authors built.

Both are marketed identically. The second is often faster and more reliable inside its range, which is a genuine advantage. What it cannot do is exceed its range, and no phrasing of your request changes that.

## How to tell which one you have

Ask for something specific and slightly odd. Not "add an enemy" — something like "when the player stands still for ten seconds, the music changes and the birds stop". A tool writing code will attempt it. A tool with a menu will produce the nearest thing on the menu, or say it is not supported.

Then ask where the code is. If there is a folder with source files in it, you have the first kind. If the answer is a project view with no files behind it, you have the second.

Neither answer is disqualifying. The point is to know [which product you bought](/blog/ai-game-maker-comparison-guide/) before you plan a year around it.

## What writing real code costs

Reliability per attempt. A configuration from a fixed list either works or is unavailable. Written code can be almost right, and the loop is describe, play, say what was wrong, go again. That is normal and it is not free.

Structure over time. [Code accumulated sentence by sentence](/vibe-coding/) over weeks develops a shape nobody chose. Everything works, each change costs slightly more, and there is no single moment where it went wrong. Being able to open the project in a standard engine is what keeps that fixable rather than terminal.

What it buys is the absence of a wall. The limit becomes what the engine can do, which is very far away, instead of what somebody anticipated, which is not.

## Where Flockbay sits

Flockbay writes GDScript into your project. Real files, real script, in a normal Godot project in a folder on your disk. It builds the world the same way, as nodes and resources in the scene tree. There is no behaviour list, no allowlist, and no genre template anywhere in the product, which is deliberate rather than incidental.

You are not required to read any of it. Flockbay runs the game first, sends input events and reads the debugger, so a GDScript parse error is caught before you see it. You describe what should happen, play the result, and say whether it is right. You can read it, and the fact that you could is what makes the project portable — a developer can open it, and so can Godot.

The engine is Godot, open source, bundled inside a desktop app for Windows, macOS and Linux. The game runs locally on [that copy of Godot](/what-is-godot/). Building needs an internet connection; playing what you built does not.

## Where it is not the right answer

If you already write code and want line-by-line control, an AI coding assistant in an editor you know is more precise. That is a straight recommendation, with one note: your own agent, such as Claude Code or Codex, can connect to Flockbay over MCP and use the same scene tools and play-testing from there.

If you want maximum reliability inside a narrow range and do not care about the ceiling, a menu-based tool will frustrate you less. And if you want [a browser tool](/browser-game-maker/), a phone or a shareable link in two minutes, none of this applies: this is a desktop download, and the world is built from a brief you agree first.

## Questions

### What language does Flockbay write?

GDScript, the scripting language built into Godot, placed directly into your project.

### Can I edit the code myself?

Yes. It is a normal Godot project in a folder. Nothing requires you to, and nothing stops you.

### Can a developer take over my project?

Yes, it is standard Godot. That is one of the practical reasons real code matters.

### Is written code less reliable than a menu?

Per attempt, often yes. Over a project, it has no ceiling, which is the trade being made.

### Do I have to review what it wrote?

No. You judge the game by playing it. Reading the source is available and optional.

Download Flockbay free: Free to download for Windows, macOS and Linux. Real GDScript in a real Godot project. https://flockbay.com/

Related: [What is GDScript](/what-is-gdscript/), [What is a no-code game engine](/what-is-a-no-code-game-engine/), [AI game maker comparison](/ai-game-maker-comparison/), [What is an AI game maker](/what-is-an-ai-game-maker/)
