A sandbox game maker built around systems that keep running
By Eduardo Orellana · Updated
A sandbox game is not a level with the walls removed. It is a handful of systems that keep running whether or not the player is watching, and it is mostly a question of what interacts with what. 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.
The genre is defined by what happens when you stand still
In a linear game, nothing happens until the player does something. In a sandbox, the fire spreads, the animal wanders, the weather turns, the crop grows. Take those away and you have an empty level, no matter how big it is.
So the work splits into two very different jobs. One is making a place worth standing in: in 3D the terrain, the water, the light, the way a valley reads from the ridge above it; in 2D the shape of the ground you paint and the band of scenery sitting behind it. The other is making the rules that tick along inside it.
Flockbay does both, from a brief you approve: it builds the place with world tools and writes the rules as GDScript inside your project. The third job, finding out whether any of it is fun, is yours.
More on this: Building a farming game, which is mostly a calendar problem
The place gets built first, and you walk it
Before anything is built, Flockbay asks what the sandbox is, one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. A sandbox needs that more than most genres, because the honest first version is far smaller than the one you are picturing. Nothing is built until you approve it.
In 3D it then sculpts and paints the terrain, lets a lake fill, sets the weather and the time of day, plants the trees, and puts buildings and characters where the brief says. In 2D it paints tile ground, and the tiles, the edges and the collision all fall out of which cells are covered, so the floor is one the player can stand on the moment it exists. Behind it goes a sky colour and one band of scenery along the horizon; on top of it go sprites, each at an exact position, rotation and scale. All of it is real Godot data, nodes and resources in the scene tree.
This matters more in a sandbox than anywhere else, because a sandbox player spends their attention on the place itself. A ridge that hides the valley until you crest it is a design decision, and so is the gap in a flat world's floor that turns a shortcut into a commitment. You judge both by walking them. When the ridge is a few metres too low, Sculpt is a button around the Godot editor's own 3D view, so you can raise it yourself, and Godot's undo takes it back. A sentence gets you a valley; your hand can get you the exact valley.
The app ships with Godot inside it, so pressing play runs the world locally on your own machine. That is what makes a large world reasonable to attempt at all — no streaming, no tab, no render queue between you and the framerate.
More on this: An AI walking sim maker where the world is the mechanic
Every rule is a sentence, so you can afford the eleventh
Then you start saying what interacts. Rain puts out fire. Wolves avoid the village during the day. Wood can become a wall. Cold drains stamina above the treeline. Each of those is a sentence to Flockbay and a piece of code in your project afterwards.
The interesting part of a sandbox is almost always the combination nobody planned. That only happens if the rules are cheap enough to add that you add more of them than you strictly need. When you are not writing the code yourself, adding the eleventh rule costs about what the second one did.
Flockbay runs each change itself first, sending input events and reading the debugger, so a rule that breaks the game is caught before you see it. The combination nobody planned only turns up when you play, though. Finding it is the part of the work that stays yours, and it is the reason the loop is described as: you judge, it revises.
Scope is the real difficulty
Sandbox games fail from ambition more than from technique. A world with thirty systems in it is not thirty times better than a world with four; it is usually worse, because none of the thirty are tuned.
A useful discipline: pick three systems, make them interact in both directions, and play for an hour before adding a fourth. If the hour is boring, the fix is almost never a new system. It is that one of the three is not doing enough.
Flockbay pushes back on this up front. The brief it writes before building names what gets built first and what is not in this version, and a thirty-system world gets the truth and a smaller first version rather than a fake yes. After that the judgement is yours: whether the fourth system earns its place is something you only find out by playing.
In 3D, weather and time are systems rather than scenery
A day-night cycle changes what the player can do, not just how the screen looks. Things that only happen at night, work that can only be done in daylight, a temperature that drops when the sun goes: each turns the clock into a resource the player manages.
Weather does the same. Rain that makes a slope unclimbable, wind that carries sound, fog that shortens sight. Once weather changes a decision, the player starts watching the sky, and watching the sky is a large part of what makes a sandbox feel alive.
In a 3D project both are world tools rather than effects added at the end. Flockbay sets them from the brief, Sky and Weather are buttons in the Godot editor if you want to change them yourself, and the rules that make them matter are GDScript like everything else. Play a full in-game day before deciding whether either is doing enough work.
This is where the principle breaks in a flat world, and it is worth knowing before you spend an afternoon asking for it. There is no 2D weather and no sun to move — those tools have nothing to describe without depth. What a flat sandbox does have is rules that keep running, because Flockbay writes them the same way there. So its clock is something the systems track rather than something the light announces, and it has to be legible in what the player can actually see: what comes out at night, what the crop has done since you last looked, which door is shut.
More on this: AI survival game maker with real terrain and weather
What you need and what it costs
It is a desktop app for Windows, macOS and Linux. You download and install it, and your project sits on your own disk as an ordinary Godot project. Godot is open source, so there is no format here that only one company can open.
Building needs an internet connection: the chat, asset generation and world data all come over the network. Playing what you built does not.
The download is free, and so is the AI. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.
More on this: A game maker for kids, with the grown-up details up front
A starting project for this is the simulation game templates.
Questions
- Can I do voxel or block building?
- Placing and removing blocks at runtime is code, so Flockbay writes it. Describe the rules you want for placement and destruction and play what comes back.
- How big can the world be?
- Large enough that your machine is the limit rather than a server. The game runs locally on the bundled Godot, so the ceiling is your own hardware.
- Does a sandbox have to be 3D?
- No. A flat sandbox gets painted tile ground, a sky colour with one band of scenery behind it, and sprites at an exact position, rotation and scale. What it does not get is a water or weather tool, so systems that would have leaned on those have to be built out of the rules instead.
- Do I need to write code?
- No. Flockbay builds the world and writes the GDScript, and you play it and judge it. You can read the code if you want, since it is a normal Godot project.
- Does this work offline?
- Playing does. Building does not, because the AI, asset generation and world data all come over the network.
- Is there a multiplayer sandbox option?
- Networking is code like anything else, but it is the hardest thing to get right in any engine, and a first sandbox is far easier to finish as a single-player world.
Related
- AI sandbox game maker
- AI open world game maker
- Survival game maker
- AI voxel game maker
- Make a 3D game
- Make a 2D game
- Prompt to 3D game: questions first, then the world and the systems
- A 3D game maker for people who bring their own Claude or ChatGPT plan
- A no-code game engine that is still a real engine
- An AI game builder that builds the world, and leaves you the controls
- What is an AI game maker that writes a real Godot project?
Flockbay is free to download for Windows, macOS and Linux.
Download Flockbay free