# Godot city builder templates give you placement, not simulation

Dropping a building onto a grid with a camera that moves nicely is a solved and pleasant problem, and that is what a city builder starter solves. The economy that makes the city worth building is not in there. 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/templates/godot-city-builder-template/ · Updated 2026-10-01

## The one project people mean

Search for a Godot city builder template and you arrive at Kenney's Starter Kit City Builder. It is a 3D project with a top-down camera, and what it covers is placement: putting structures down on a grid, rotating them, removing them, describing them as reusable resources, and hooks for saving and loading what you built.

It is a good project and the scope is right for a starter kit. It is also, measured against [a finished city builder](/city-building-game-maker/), somewhere near a tenth of the game. Everything it does is the part that is fun to build and quick to finish.

A word on the art, since it is half of why the kit is popular. Kenney's asset packs are widely used and the look is instantly recognisable, which cuts both ways. It is the fastest route to a scene that reads as a city, and the fastest route to looking like every other prototype.

## Placement is the easy tenth

Grid placement has a shape that has been settled for thirty years. A ghost of the building follows the cursor, snapped to the grid. It turns red where it will not fit. A click commits it, a right click cancels, a key rotates. Removing is the same in reverse. There is craft in making it feel good, but there is no unsolved problem in it.

The camera is similar. Pan on the edges or with a drag, zoom on the wheel, rotate around a point, and keep the whole thing smooth enough that a two-hour session does not become tiring. This is genuinely worth inheriting, because getting [a city builder camera to feel unfussy](/blog/the-challenge-of-cameras/) takes longer than people expect and no player will ever notice you did it.

What that leaves you is a diorama. You can place forty buildings and take a screenshot, and nothing about the arrangement matters, because nothing is reading it.

## The simulation is the product

A city builder is a machine that turns the player's arrangement into consequences. Housing produces people, people want jobs, jobs want goods, goods want transport, transport wants roads, and every one of those wants space and money. The game exists in that loop and nowhere else. Take it away and you have a level editor.

This is why the genre is hard in a way that placing buildings is not. You are [balancing a feedback system](/blog/how-games-use-feedback-loops/) that runs for hours, where a number five per cent wrong compounds into a city that either stalls at twenty minutes or runs away at ninety. Balancing that means playing long sessions repeatedly, and it does not get faster because the placement code was inherited.

It also decides whether your game is a game. A player who can put a building anywhere and get the same result is arranging furniture. The decision needs a cost, a constraint and a consequence they can see, and designing those three things is the work the starter did not do.

## Two problems that arrive with scale

The first is movement. The moment citizens or delivery trucks travel between buildings you are running pathfinding for thousands of agents at once, which is a performance problem rather than a design one. Many city builders sidestep it entirely by simulating flow as numbers moving between zones and never drawing an individual at all. Make that decision deliberately and early, rather than at building number four hundred.

The second is readability. With three thousand structures the player cannot see what is wrong by looking at it. They need overlays: coverage, density, traffic, pollution, land value, whatever you actually track, drawn as colour over the map. Overlays are how a player forms a plan, which makes them [core gameplay rather than a UI nicety](/blog/the-power-of-video-game-huds/), and a city builder ends up far more interface than most people budget for.

Saving belongs alongside both. A city builder save is the entire simulation state, and it grows with the city rather than staying a fixed size. Getting the format right early is unusually valuable here, because every system you add later has to write itself into it.

## Prototype the economy in a spreadsheet

The central question is whether the economy produces interesting decisions across three hours, and you can answer much of that without an engine. Put your buildings in rows. Give each a cost, an upkeep, an output and a requirement. Step it forward turn by turn and see whether the player ever faces a choice they have to think about.

If the spreadsheet says every sensible player builds the same four things in the same order, no amount of placement polish fixes that, and you learned it in a day instead of a quarter. If it says three strategies trade off against each other, you know what you are building, and the starter becomes genuinely useful because you know which parts of it you will bend.

This is [the cheapest debugging in the genre](/blog/whats-the-point-of-prototyping/) and almost nobody does it, because placing buildings is more fun than filling cells.

## Where Flockbay fits

Flockbay's own templates, under New from template on Home, do not include a city builder, and a Godot project you have downloaded opens in it with Open Godot project. Its route here is a different one. What it offers is a brief first: Flockbay asks about the city one round of questions at a time, each with a recommendation, and writes down what gets built first, what comes after and what is not in this version. Once you approve it, Flockbay builds the world and writes the GDScript for the systems in your project, plays its own build, and hands it to you. You play the result and say whether it is right.

Whether the city is 2D or 3D is settled before anything is made, read from your description of the game and yours to change. Take 3D and Flockbay sculpts the terrain and places what stands on it. Take 2D and a top-down city is a first-class thing to make rather than the cheap version: Flockbay lays tile ground for streets and lots, and buildings go down as sprites at an exact position, rotation and scale, each sitting on its own drawn bottom-centre so it stands on the ground instead of floating above it. Whether ground stops a walker is declared per material, so the path your citizens use and the block they cannot cross are painted the same way and only one of them stops anybody.

This is one of the genres where the by-hand path earns its keep, because a city's layout is taste. The same world tools are buttons around Godot's own 3D and 2D view, acting on the live scene: nudge the town hall, redraw a street, flatten a hill, and Godot's undo takes it back if it was worse. A sentence gets you a district; your hand can get you the exact district. The limit is worth being straight about: [having the simulation code written for you](/ai-city-builder-maker/) does not make the economy interesting. Bring the spreadsheet to the brief, and play the long sessions that tell you whether it holds. It is a desktop app for Windows, macOS and Linux, the engine underneath is Godot, and your game runs locally on the bundled copy. Building needs an internet connection; playing what you built does not.

## Questions

### Is there a Godot city builder template?

Kenney's Starter Kit City Builder is the one people mean. It is a 3D project with a top-down camera covering structure placement, rotation and removal, structures defined as reusable resources, and hooks for saving and loading.

### Can I open it from inside Flockbay?

Not from New from template. Flockbay's templates do not include a city builder. The kit is a public GitHub repository, so you clone it yourself; once it is on your disk, Open Godot project opens it in Flockbay, or you open it in Godot directly.

### What does a placement starter leave me to build?

The simulation, the interface and the balance. Resource flows, growth, the constraints that make a placement decision matter, the overlays a player reads the city through, and a save format that holds all of it.

### Should a city builder be 2D or 3D?

Both work. 3D reads as a place and lets the player orbit and zoom into what they made, at the cost of art volume and camera work. 2D is far cheaper to produce and often clearer to read at high density. Pick for the art you can actually make.

### How do I know whether my economy is any good?

Model it in a spreadsheet before you build it. Step the turns forward by hand and look for a moment where the player has a decision they must think about. If there is not one on paper, there will not be one on screen.

Download Flockbay free: Flockbay is a free download for Windows, macOS and Linux. It builds the city and writes the code from a brief you approve. https://flockbay.com/

Related: [Godot 3D game templates](/templates/godot-3d-game-template/), [Godot tower defense templates](/templates/godot-tower-defense-template/), [Godot RPG templates](/templates/godot-rpg-template/), [Godot puzzle game templates](/templates/godot-puzzle-game-template/)