An AI game maker that writes real code

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 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.

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 before you plan a year around it.

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 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.

Director 1 writes GDScript into your project. Real files, real script, in a normal Godot project in a folder on your disk. 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. 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 Mac and Windows. The game runs locally on that copy of Godot. Building needs an internet connection; playing what you built does not.

If you already write code, an AI coding assistant with an engine you know is more precise and gives you more control. That is a straight recommendation.

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, a phone or a shareable link in two minutes, none of this applies — this is a desktop download and the world is built by hand.