Skip to content

AI city builder maker: simulation you can watch

By Eduardo Orellana · Updated

A city builder is a simulation with a view on top. Flockbay writes the simulation in GDScript and builds the map, the starting buildings and the view from your description. Godot's own editor is there in the Standard and Full views, so you can move a building or a road piece by hand. 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 City building game maker: terrain first, then the simulation.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The genre is an economy in disguise

What makes a city builder good is not the buildings. It is the set of pressures between them: this needs power, power needs fuel, fuel needs a road, the road takes land you wanted for housing. Play is about resolving those pressures and the feeling of a city that is nearly working.

Building that means writing a simulation. Resource flows on a tick, demand that propagates, pathfinding for supply, agents with needs, and a save file that captures all of it. Every one of those is a real piece of programming and together they are the reason city builder projects are so often abandoned.

Flockbay writes them in GDScript inside your project. You describe the pressures you want and get a simulation you can run.

The land is half the genre, so it is built with the pressures in it

The map is the other half of the genre. In three dimensions that is terrain with real relief, a river that constrains where bridges go, a coast, a mountain pass that makes one route obviously valuable. Flat, it is the same argument made with a coastline and a band of tiles nobody can cross. Flockbay builds it from the brief, with those constraints written in.

This is the difference between a city builder with interesting decisions and a flat grid where every tile is the same. Judging it is purely spatial judgement, which is exactly the kind of decision that does not need a technical background: you play a few years of the city and say where the land is too generous.

On the 3D side Flockbay builds the map as scenes and places whatever should already be there before the player arrives, with terrain, water or weather from a Godot plugin when the city needs them. Godot's own 3D editor is there in the Standard and Full views, so when you want a building a little further from the river you can move it yourself.

A top-down city builder in 2D is the same half of the genre with different tools, and it is a choice the app reads from your first message rather than a compromise you settle for. Ground is a TileMapLayer, and its TileSet's terrains give the edges while its physics layer gives the collision. Whether a tile stops anybody walking is set per tile, so a road and a field can be laid with identical strokes and only one of them turn anyone back. Buildings are sprites from the library, placed at an exact position, turn and size — and with Y-sort on, a tower lower down the screen draws in front of the one behind it without anyone arranging it. Godot's TileMap panel and 2D view are there when you want to lay a square or move a tower yourself.

More on this: A no-code RPG maker that does not come with an RPG in it

Watching a simulation is how you debug it

The interesting failures in a city builder are visible ones. The trucks all take the same road. Nobody ever visits the second market. The population plateaus at four hundred for a reason nobody can see.

You find these by running the game and looking, which is why running locally matters. Flockbay bundles Godot inside the app and your city runs on your machine, so a few thousand agents and a full map are a normal load rather than the thing that kills the preview.

When you spot something wrong you say so in plain words. Trucks are queueing at the junction and never taking the second route. That is a complete bug report and it does not require knowing what pathfinding is.

More on this: A tower defense game maker where the balance is the whole job

No template city

There is no menu of city builder presets here. A preset encodes somebody else's economy, and the economy is the game. If your city builder is about water in a desert, or about a colony ship, or about a medieval town with one road out, a preset is in your way.

You describe the rules you want. If a rule is missing the tool asks for it rather than inventing a default, because an invented default is a decision you did not make.

A real heightmap, imported through a terrain plugin, is worth a mention here specifically, because a real landscape carries constraints nobody would think to invent. Rivers in awkward places, a plain that is slightly too narrow, a ridge that makes one approach obvious. Those constraints are free design.

Practical facts

A desktop app for Windows, macOS and Linux. Godot ships inside it and your game runs locally. There is no browser version and no streaming.

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. Building needs an internet connection; playing what you built does not.

More on this: AI isometric game maker: a camera decision, not an art style

The readability problem

City builders have a specific failure that is worth designing against from the start: the player cannot see why anything is happening. The population drops, and there is no way to find out that it is because one road is congested, so the player stops making decisions and starts guessing.

The fix is in the presentation layer rather than the simulation. Overlays that show flow. A building you can click that tells you what it is waiting for. A chart of the last hundred ticks. These are all code and all worth asking for early, because a simulation you cannot see into is one you cannot design.

It also helps you enormously as the developer, because the same tools that let a player understand the city let you find out why your economy collapses at minute forty.

This is the sort of thing that gets deferred forever when you are writing the code yourself, and it is the thing most responsible for whether the genre works.

More on this: Godot city builder templates give you placement, not simulation

A starting project for this is the simulation game templates.

Questions

How many agents can it simulate?
The game runs natively on your machine rather than in a browser, so the practical limit is your hardware.
Do I have to design the economy myself?
Yes, and that is the game. Flockbay asks about it while writing the brief, with a recommendation for each question, but the resources and pressures are your call, and it writes the simulation you settle on.
Grid or free placement?
Your choice. Placement rules are code, so they are written to what you ask for.
Can I use real world terrain?
In a 3D project, yes, from a heightmap of your own: a terrain plugin installed from the Plugins panel, such as Terrain3D, imports it, and its own sculpt tools reshape it by hand afterwards. Flockbay does not download elevation data. A 2D map is a TileMapLayer, painted cell by cell rather than sourced.
What does it cost?
The platform is free. 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. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.
Can the player build outside a grid?
Yes if you want that. Placement rules are code, so a free-form or organic layout is a request rather than something the tool decides for you.

Free to download for Windows, macOS and Linux.

Download Flockbay free