Open worlds are a scale problem before they are a design problem

By Eduardo Orellana · Updated

The reason solo creators do not finish open worlds is not ambition, it is square kilometres. Flockbay builds the terrain, water, sky, weather and props as real Godot data and writes the systems in GDScript, from a brief you approve. Its world tools are also buttons in the Godot editor, so you can reshape or repopulate any part by hand. 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.

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

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for Windows

The genre that punishes small teams

An open world sets an expectation the moment the player sees the horizon: you can go there. Meeting that expectation means content everywhere, and content everywhere is why this genre belongs to studios with hundreds of people.

Two costs dominate. The first is the landscape itself, which used to mean sculpting terrain by hand for months. The second is systems: traversal, day and night, weather, saving, a map, inventory, interaction — a large block of code that exists before your game has a single interesting moment in it.

Flockbay goes after both. The landscape comes from heightmaps, real elevation data and drawn water outlines. The systems come from Flockbay as GDScript in your project.

More on this: No-code 3D game maker for worlds, not just scenes

Terrain, water and sky are already there

Terrain is heightmap-driven, which is what keeps it editable after it is created. Flockbay raises the ridge, cuts the pass, flattens a plateau for the town and paints materials across it, and every one of those strokes can be redone later. Real-world elevation data is available, and terrain shaped by actual geology reads as somewhere in a way that noise does not.

Water follows the shape it is given. A lake, a coastline, a river valley: it gets an outline and fills to it, rather than being a plane that happens to be blue.

Sky and weather are a layer of the world, not a post-process you bolt on. The same terrain at dusk in fog is a genuinely different place from the same terrain at noon, and for an open world that variety is doing a lot of the work.

More on this: City building game maker: terrain first, then the simulation

A landmass becomes a place when someone judges it

A generated landmass is not yet a place. Places are made by decisions: the ruin visible from the road, the pass that reveals the valley, the village positioned so that you arrive at it from below. Flockbay makes the first round of those decisions from the brief, places the props as nodes in your scene tree, then runs the game and captures the viewport to check what it built.

Then you walk it and decide what is in the wrong place. Say the ruin belongs on the next ridge and it moves. Or, when the call is pure taste, press Place in the Godot editor and drag it there yourself; Sculpt, Paint, Plants, Water, Sky and Weather sit beside it, and Godot's undo takes any of it back. A sentence gets you a valley. Your hand can get you the exact valley.

Characters and creatures live on top: patrol routes, schedules, animals that flee, settlements that behave differently at night. Describe the behaviour, get the code, play it, correct it.

More on this: How to make a 3D game when you build on your own Claude or ChatGPT plan

Running locally is what makes the scale possible

Flockbay is a desktop app for Windows, macOS and Linux with Godot bundled inside. Press play and the world runs on your own machine, using your own GPU, at your own framerate.

This is the reason the genre is even on the table. Browser tools push you toward small flat scenes because that is what a tab can serve, and no amount of clever engineering changes what a streamed frame costs. A local build with real terrain, weather and a few hundred simulated characters is an ordinary thing to attempt here.

Building needs an internet connection, since the chat, asset generation and world data come over the network. Playing does not. The download is free and building the world costs nothing. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

More on this: An AI voxel game maker that runs on your own machine

Density is the decision that defines your world

Every open world sits somewhere on a line between full and empty. Full means something to do every thirty seconds and a map covered in icons. Empty means long stretches of travel where the landscape is the content.

Neither is wrong and both can be excellent, but the choice has to be deliberate, because it decides everything else: how fast the player moves, how big the map should be, whether fast travel exists, whether the weather matters. A world that is accidentally empty is a world where the creator ran out of time.

Deciding this early saves months. If you are one person, an intentionally sparse world at a walking pace is far more achievable than a dense one, and it is also the thing several of the most admired games in the genre chose on purpose.

A starting project for this is the adventure game templates. The design note that goes with it is how Zelda’s open world stays readable.

Questions

How large can the world be?
There is no fixed size in the tool. The practical ceiling is your machine, which is a much higher ceiling than a browser tab.
Is the terrain editable after generation?
Yes. It stays heightmap terrain in your Godot project, so raising, lowering, smoothing and repainting are all still available, whether you ask Flockbay or use Sculpt and Paint yourself.
Do I have to write GDScript?
No. Flockbay writes it inside your project and builds the world around it. You judge the game by playing it.
Does it work offline?
Building needs a connection because the chat, asset generation and world data come over the network. The game you built runs locally without one.
What engine is under it?
Godot, open source, bundled with the app. Your project is a normal Godot project.