Skip to content

Building with Flockbay needs a connection. Playing what you built does not.

By Eduardo Orellana · Updated

There is no offline mode. Building needs an internet connection, because the chat and asset generation come over the network, and the game you built runs locally on your own machine and needs nothing at all. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. 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 WindowsDownload for Linux

Both halves of the answer

Building a game with Flockbay needs an internet connection. Playing the game you built does not. Those two sentences are the entire answer, and this page exists because people get it wrong in both directions.

One wrong picture has the whole thing running somewhere else: a server rendering your game and sending you the pixels, the way a cloud gaming service does. That is not what happens. Flockbay is a desktop app for Windows, macOS and Linux with a copy of Godot inside it, and when you press play the game runs on your own processor and your own graphics card.

The other wrong picture has it working on a plane, on the grounds that it is a download rather than a website. It will not. Without a connection you cannot build, and no amount of having already installed it changes that.

More on this: Online AI game maker: the AI is online, the app is on your machine

What actually goes over the network

Three things. Flockbay, who writes the GDScript for your game on your own AI. Asset generation, when you ask for something that does not exist yet. And Godot plugins, which come from the Asset Library when you install one.

Your project is not one of those things. It lives in a folder on your own disk as an ordinary Godot project. It is not uploaded for the game to run and it is not being held on our side. The connection is carrying requests and results, not your game.

More on this: Online 3D game maker: the 3D is the reason this one installs

What runs on your machine

The app and the engine. Godot ships inside Flockbay, so pressing play starts a real game process on your computer at whatever framerate your computer manages. No render queue, no streaming, no browser tab in the middle of it.

That is why a large world is a reasonable thing to attempt here. Terrain, weather and a few hundred characters moving about are not things a browser tool runs smoothly, which is why browser tools quietly steer you towards whatever fits comfortably in a tab and rarely say why. The limit they are working around is scale, not dimension: a wide painted 2D world with a screen full of sprites runs into the same tab as readily as a hillside does.

It is also why the game you finish is a normal program. Somebody you give it to installs it and plays it, with no account, no connection and no copy of Flockbay anywhere on their machine.

More on this: A no-code game engine that is still a real engine

Why there is no offline mode

The models that write your code and generate your assets run on hardware that cannot be shipped inside a desktop app. An offline mode would have to be something much smaller wearing the same name, or a promise that fails quietly at the exact moment you were relying on it.

So there is not one. If a dependable connection is not something you have while you work, this is the wrong tool, and it costs you nothing to find that out before you install it rather than after.

Without a connection, building stops and says why, rather than half working and leaving you wondering whether the problem was your idea.

More on this: A no-code game maker where the code still gets written

When the connection drops

You stop being able to build. Asking Flockbay for a change needs the network, and so does generating an asset. That is the practical shape of it, and it is worth planning around if your connection is unreliable rather than absent.

What does not stop is everything already on your disk. Your project is a folder of files, Godot is free and open source, and a build you already made is a program that runs without checking in with anything. A dropped connection does not put your work out of reach or hold it hostage.

The two questions worth keeping separate are whether the tool needs the internet and whether the game does. The tool does. The game does not, unless you deliberately build a game that does.

Questions

Can I build a game on a plane?
No. The chat and asset generation come over the network, so building needs a connection.
Does the game I built need the internet to run?
No. It runs locally on the copy of Godot that ships with the app, and the build you hand to a player runs on their machine with no connection.
Is there an offline mode?
No. The models that write your code and generate assets do not run on a laptop.
Is my game streamed from a server?
No. Nothing is streamed or rendered remotely. Press play and the game runs on your own hardware at your own framerate.
Are my projects stored in the cloud?
Not unless you ask. They are ordinary Godot projects in folders on your own disk, and Flockbay keeps no copy of them. A game you publish to GitHub goes to your own repository.
What exactly needs the connection?
The AI that writes your code, and asset generation. Everything else is local.

Flockbay is a free download for Windows, macOS and Linux. Building needs a connection; playing does not.

Download Flockbay free