An AI dungeon generator that hands you a dungeon you can edit

Generators are very good at the boring half of a dungeon. Room counts, corridor connections, making sure the exit is reachable from the entrance, spreading loot so it is not all in one corner. That work is arithmetic. Doing it by hand for the twentieth room is how people abandon projects.

They are bad at the half that makes a dungeon memorable. The room you turn a corner into and stop. The corridor that is too long on purpose so the footsteps get uncomfortable. The moment the layout lies to you about where you are. None of that comes out of a seed, because none of it is a property of the graph.

So the honest design is to let the generator do the arithmetic and treat what it hands back as a draft. Flockbay writes the generator, keeps the layout you like as an ordinary scene, and then edits it the way a level designer would — widen this room, reroute that corridor, drop a set piece in the middle of it — from the brief and from what you say after playing it. Nothing about the generated result is locked, and every wall can be moved by your own hand too.

More on this: Best AI game generator, and the difference between a demo and a game

Editing here means changing the dungeon you have, not regenerating the whole thing when you dislike one room. Say a junction feels wrong and Flockbay moves that junction. Say a room wants to be twice as tall and that room gets twice as tall. When it is quicker to do than to say, the same scene is open in the Godot editor, and you can drag the wall yourself.

This matters because regenerating is not editing. A tool that answers every complaint by rolling a new seed will never converge on the level you had in mind. It will just keep offering you different levels. The second one is not closer than the first.

Regeneration is still there when you want it, and it is genuinely useful early, when you are looking for a shape rather than refining one. The difference is that it is one option rather than the only lever.

Doors that need keys. Enemies that patrol a route and notice you. A boss room that locks behind you. Traps that reset. Loot tables that do not hand you the best sword in the first chest. That is code, and Flockbay writes it, in GDScript, inside your project.

You describe the rule you want in a sentence, play the dungeon, and say whether it felt right. Not writing the code does not mean not having a view on whether the key placement is fair. That judgement is yours and it is the part the tool cannot do.

Because the output is a real Godot project, the generated dungeon, every correction to it and the scripted rules all end up in the same place, as ordinary scenes and scripts. There is no separate proprietary dungeon format that only this tool can read.

Flockbay is a desktop app for Windows, macOS and Linux. You download and install it, and it ships with a copy of Godot. Press play and the dungeon runs on your own machine at your own framerate.

That is the reason a dungeon with dynamic lighting, real shadows and thirty active enemies is a reasonable thing to attempt here. Browser tools are quiet about it, but the reason their examples are small and flat is that a tab is a hard performance ceiling.

Generating and building do need an internet connection, because the AI and the world data come over the network. Playing what you built does not.

The download is free and every world tool is free. Flockbay is free, AI included: free hosted AI every day, or your own Claude or ChatGPT, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

Generating layouts is cheap. Asking for a lot of code and a lot of art is where the day's free usage goes fastest, and it comes back the next day. Demo, free each day is a reasonable way to find out whether the tool suits you, and your own Claude or ChatGPT is one press away when you want more.

A generator is only useful if you can get back to a result you liked. Roll twenty layouts, decide the eleventh had the right shape, and then be unable to find it again, and the tool has cost you an hour and given you nothing.

So treat generated layouts the way you would treat sketches. Keep the ones with a shape you responded to, drop them into the project, and let the ones you dislike go. Because the output is an ordinary scene in an ordinary Godot project, keeping one is just keeping a file.

That also changes how freely you can explore. When a promising result is cheap to save, you stop being careful with the reroll button, and being careless with the reroll button early is how you find a shape you would not have designed on purpose.