Make a game with AI and no coding, without a closed toolbox
You can make a game with AI and no coding in Flockbay: you approve a brief, and its AI builds the world and writes real GDScript you never have to read, in a Godot project you own. Real code is why it does not run out of ideas the way a block editor does. 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.
The main page on this subject is Make a game with AI without giving up the game.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
Two very different meanings of no coding
The first meaning is a closed system: blocks, behaviour menus, a fixed list of things that can happen. Nothing to learn, and a hard ceiling. When your game needs a rule the menu does not contain, there is no move available. You are not stuck because you lack skill; you are stuck because the option does not exist.
The second meaning is that code gets written and it is not written by you. The ceiling then is not the menu, it is what can be expressed in a programming language, which for practical purposes is everything.
Flockbay is the second kind. Flockbay writes GDScript in your project. You never open it.
More on this: An AI game studio in the sense of a workshop, not a company
How you actually specify behaviour
In sentences. "Torches burn out after two minutes and you can relight them from a brazier." "The boat only moves if both crew are aboard." "The music changes when you cross the bridge."
None of those are on any behaviour menu, and all of them are ordinary code. You get them by asking, playing, and saying what is wrong.
The part that surprises people is how much of the work is the third step. First attempts are usually close and rarely right, because rules interact in ways nobody predicts until they are playing. That iteration is the design work, and it is yours.
The world is built from a brief, not guessed from a sentence
Before anything is built, Flockbay asks what it needs to know, one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. You approve it, and then it builds the scenes, as real nodes in the scene tree. In a 3D game: the player controller, characters and props, with terrain, water, sky or weather from a Godot plugin when the game needs them. In a 2D one: a TileMapLayer whose TileSet terrains give the edges and the collision, Parallax2D layers behind it, and sprites at an exact position, rotation and scale. You judge it by playing it.
This is why the tool does not need to guess at your game. And the parts a description would butcher, like exactly where a doorway sits, are the parts you can do by hand if you want to: Godot's own editor is there in the Standard and Full views, and Godot's undo takes a change back. No code is involved either way.
More on this: Text to game, taken apart into the four things a game is made of
The honest constraints
It is a desktop app for Windows, macOS and Linux. Downloaded, installed, no browser version. In exchange, your game runs locally on the bundled open-source Godot, on your own hardware.
Building requires an internet connection. Playing what you built does not.
Free to download. 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.
More on this: What is a no-code game engine?
Not coding is not the same as not deciding
The uncomfortable version of "no coding" implies you also hand over the judgement. You do not. Flockbay plays its own work to check it runs, but nobody else can tell whether your game is fun, and no model has an opinion about it worth trusting over yours.
You play everything. You reject plenty. Handing work back is the normal loop here, not a sign the tool failed. If anything, the people who get the most out of this are the ones with the strongest opinions about what is wrong.
More on this: What is vibe coding?
The code exists, and that is part of the offer
There is a version of no-code where the code does not exist at all, and your game is a configuration file interpreted by a runtime you do not control. Nothing can be inspected because there is nothing to inspect.
Here the GDScript is written into your project as ordinary files. You are not expected to read them. But they exist, which means a friend who does program can help, a problem can be diagnosed, and the project has a life beyond this app.
That difference costs you nothing while things are going well and matters enormously the first time something is wrong in a way you cannot describe.
Questions
- Is this block-based or visual scripting?
- Neither. Real GDScript is written for you by Flockbay, which is why there is no fixed list of behaviours.
- Will I ever have to open a script?
- No. The code is there in your project if you or anyone else wants to look, but nothing requires it.
- What if the AI writes something wrong?
- You play it, say what is wrong in plain language, and it gets revised. That loop is the intended way to work.
- Does it run in a browser?
- No. Desktop app for Windows, macOS and Linux, with the game running locally on bundled Godot.
- What does it cost?
- Free to download. 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.
Free to download for Windows, macOS and Linux.
Download Flockbay free