AI map generator for games: a real Godot world you can keep editing

Ask an image model for a volcanic island and you get a beautiful one in seconds. Then try to put a character on it. There is no ground to stand on, no collision, no shoreline the player can wade into, nothing for a camera to follow. It is a picture of a map, and a picture is the end of the road.

A game map is data an engine runs: heights or tiles, collision, water you can fall into, somewhere to spawn. It is also the thing you will change fifty times while the game works out what it wants to be. The valley is too wide. The mountain hides the view from the start. The lake should be somewhere the player passes early. None of that is knowable before you walk it.

So the useful question about any AI map generator for games is what you are holding afterwards, and whether you can still change it. Flockbay’s answer is a real Godot project on your own disk, on the official Godot 4.7.2 engine rather than a fork, with every part of the map still editable by hand and by AI.

A 3D world is built from six parts. Each one is a working Godot system that Flockbay sets up and keeps consistent with the others, and each has its own button in the builder.

The ground. It starts from one of four places: a real spot on Earth, the one you name or one that fits what you describe, whose elevation data is downloaded for that patch; a real spot picked at random, kept only if you would be standing above the sea on ground with some relief in it; an island that is not anywhere, with a raised interior and a shore; or flat ground. A world covers 0.5 to 50 km edge to edge. Up to about 8 km across there is a height sample every 2 metres, fine enough to paint a footpath; wider worlds space the samples out. The terrain material, whether sand, moss, rock or snow, is set by height and slope rules, from textures the app ships or from your own.

The water. Water is one level for the whole world: every patch of ground below it is under water and everything above it is dry. Coasts and lakes come from the shape of the land, so a lake is a hollow you dig below the level. The look is a choice of shaded surfaces, from a deep ocean to ice, and the player can wade and swim.

The sky. A sky dome with a sun, a moon and a clock: the time of day, where on Earth the world stands (which decides the sun’s path), how long a day lasts, whether time runs in Play, how cloudy and how hazy.

The weather. Rain or snow, how hard it falls, how much snow lies on the ground and how wet surfaces look. The wind belongs to the sky, so the clouds and the rain agree about which way it blows.

The player. A character who walks, runs, crouches, jumps and swims, with a camera behind them or a fixed high-angle view. Every feel number is a control you can turn: walk speed, the time it takes to reach a run, jump height, gravity, the slope that stops them.

Placed objects. Anything from the library, put at an exact spot: the models Flockbay ships, files from your own project, the catalogue, or 3D models generated for this game. A placed prop keeps its spot when the terrain under it is rebuilt, because it is your decision rather than generator output. Foliage is painted onto the terrain with a brush of its own.

More on this: A sandbox game maker built around systems that keep running

A 2D world has four of the six parts. There is no water and no weather in 2D.

The ground is painted tiles. The world stores one thing, which cells are ground, and draws everything else from that: the tiles, the edges, the corners and the collision. Nine pictures, a centre, four edges and four corners, cover every shape you can paint, because the tiles are matched on a grid offset by half a cell, where sixteen combinations cover everything and none can be missing. Ground can be solid, like a platformer’s blocks, or something you walk on, like a top-down path.

The backdrop is a sky colour and one band of scenery along the horizon. The colour is read off the band’s own top row, so swapping the picture swaps the sky and the join cannot be wrong. There is no parallax yet.

The player is a 2D character. Side-on or top-down is not a setting: give the world gravity and it is a platformer with a jump; take gravity away and the character steers in every direction. What the camera shows, the dead zone the player moves in before it follows, and how far it may travel are three rectangles you drag in the 2D view.

Props are sprites, placed on the tile grid where you click.

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

Everything above lives in the project on your disk. Flockbay’s own screen is the Godot editor it bundles, and the world is live in that editor’s 3D or 2D view: the real terrain, water, sky and player, not a preview of them.

The builder is a column of buttons around that view. In 3D they are Select, Sculpt, Paint, Plants, Place, Water, Sky, Weather, Characters and Camera; in 2D, Select, Paint, Place and Characters. Sculpt raises, lowers, smooths, flattens and slopes, and Slope runs between two points you click, which is how a road bed gets made. Paint sets the terrain material, its colour and how wet it looks. Water is one slider for the level and a choice of looks. A tool is on the column only when the world has what it drives, so a world with no water has no Water button.

Navigation is Godot’s own: hold the right button and fly with WASD, scroll to zoom. Every finished stroke, placement or change is one step of Godot’s undo, so Ctrl+Z takes it back. The Game screen only plays: you build in the editor, and Play (or F5) runs the game fresh.

The rest of the project is ordinary Godot. Your scenes, scripts and resources are yours to open, read and change, in the editor or in any code editor. The files Flockbay generates for the world are its own: change the world with the builder or by asking, and leave those files alone, because the app rewrites them. A game you export carries the world with it and none of the builder.

More on this: Plugins: where the manual controls live

Install Flockbay on Windows and sign in with a free account. Make a new game and answer the one question it asks up front: 2D or 3D.

Describe the place in your own words: “a volcanic island at dusk, with a village on the east shore”, or “the Isle of Skye, in the rain”. Flockbay reads the idea back, asks a round of questions with a recommendation for each, and writes a brief. Nothing is built until you approve it.

It then builds the first playable: the terrain, the water, the sky, the weather and a player controller, plus anything else the brief needs as ordinary GDScript. Press Play and walk it.

Then change it. Sculpt the valley narrower, pull the water up, set the hour to dawn, put the village where the path crests the hill. Or tell Flockbay what is wrong and let it make the change.

If you already work in Claude Code, Codex or Cursor, your own agent can do all of this instead. In Flockbay, open Connectors, press Set up on Another agent, press Turn on, and paste the line it gives you into your agent. It gets the same world tools, plus the Godot editor and the running game, for free. The walkthrough is in making games from Claude Code.

Flockbay runs on Windows today; a Mac release follows later. Building needs an internet connection, because the AI, the art and the elevation data come over the network. Playing what you built does not.

Water is one level per world. A river that runs downhill, a waterfall, or a lake high in the mountains above the sea is not something the water can be yet. You can dig a channel below the level, but its surface sits at that level.

You cannot import your own heightmap. It comes from a real place, a random real place, an invented island or flat ground, and you sculpt it from there.

Bigger is not better. At a real walking pace of 1.4 metres a second, crossing a 12 km map takes about two and a half hours. If that is too long, the fix is a smaller map or a way to travel, not a faster walk, because a fast walk is what makes a big world feel like a corridor.

Dungeons, rooms and levels laid out by rules are code, not a world part. Flockbay writes that code into your project as GDScript (more in the AI level generator), but there is no button for it.

Generated art costs something. Pictures and sound come with a Flockbay plan, or run on your own keys when you build on your own AI. 3D models are made on your own Tripo key either way.

The download is free, and so is every builder button: sculpting, painting, planting, placing and every slider.

The AI that builds the map runs on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds it in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices: Indie at $20, Pro at $60 or Ultra at $200 a month, each opening a band of hosted models, with generated pictures and sound on that plan. Your own agent over MCP, or your own API key from OpenAI or Anthropic, stays free. Every new account also gets Demo, a small free allowance, to try the app first.

We read every tool below on its own site on 29 September 2026. Most of what comes up when you search for an AI map generator for games draws a picture. Spriteflow is honest about it: its own page says the output is “not an engine-ready Tilemap, collision layer, navigation mesh, or gameplay-validated level”. A picture is useful for a pitch or a tabletop session. It is not a level.

Summer Engine’s map generator is the other AI tool that promises a playable map. Its page says it builds terrain with elevation, biome regions, water and paths, spawn locations and points of interest, as 2D tile maps or 3D landscapes, in “standard, editable nodes with collision and navigation already set up”. We have not run it, so read those as its claims. It works inside Summer’s own desktop app, built on a Godot 4.7.2 base, with hosted AI from $20 a month; the two are compared in Flockbay vs Summer Engine.

Ludo.ai makes tiles rather than maps: each tile comes back as its own transparent image, and you assemble them “in your engine’s tilemap or in Tiled”. Useful art, and the map is still yours to build.

The free tools that produce real game data use rules, not AI. Wave function collapse grows a map that looks like a sample you drew, and the godot-constraint-solving add-on writes the result straight into a Godot TileMapLayer or GridMap. Gaea is a node-graph generator for Godot 4.4 and up, in 2D and 3D, with version 2.0 still in early development. Tiled is the standard hand-made 2D map editor, with rule-based automapping, and it exports Godot 4 scenes and TileSets. Sprite Fusion is a free browser tilemap editor with a native Godot export. Godot’s own TileMapLayer terrains autotile as you paint.

For 3D ground, World Machine simulates erosion and exports heightmaps; its free Basic edition is for personal use at up to 1K. A heightmap reaches Godot through the Terrain3D add-on, which imports EXR, R16 and RAW. What you get is ground, not a level: no water, sky, player or objects until you add them.

Flockbay’s place in that list is the AI answer that hands you the whole playable world, on the official Godot, where the rule-based tools hand you parts to assemble. The table has every row, with the pages each was read from.

More on this: An RPG Maker alternative that keeps the tiles and loses the event editor