An FPS maker that runs the shooter on your own machine
Shooters are the genre where the hardware you are running on shows up in the game. Flockbay is a desktop app and your shooter runs locally, which is why the levels do not have to be small. 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.
The main page on this subject is FPS game maker: the feel comes before the level.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
Why the shooter runs locally, and why that decides things
Flockbay is a desktop app for Windows, macOS and Linux with a copy of Godot inside it. Pressing play runs your shooter on your own machine, at your machine framerate, using your machine memory and graphics card.
Browser-based makers cannot do this, and the consequence is not abstract. It is why their example projects are small, why the draw distance is short, why there are rarely more than a handful of active enemies, and why the lighting is baked flat. A tab is a budget.
If what you want is a shooter with a long sightline, a real skybox, dynamic shadows and twenty things happening at once, running locally is not a preference. It is the requirement.
More on this: Make an FPS with AI: the feel is code, the map is judged on foot
The build loop
Flockbay builds the level from a brief you approved: terrain, buildings, cover, props, light, all as nodes in the scene tree of a Godot project. Then it runs the game and captures the viewport to check what it built.
Flockbay writes the code: the controller, weapons, damage, enemy behaviour, objectives, the pause menu, the save. GDScript, inside your project, where you can see it. You describe what should happen and then check by playing.
The check is the important half. Play the level, notice you always approach from the left, and say so, or move the cover yourself in Godot's 3D view. Nobody can tell you that from a description and no generator can predict it.
More on this: Making a twin stick shooter without writing the controller
You are the one who says it is wrong
The app does not assume you write the code. It does not assume you cannot tell a bad shooter from a good one either. Those are different things and most tools in this space confuse them.
So the loop is: describe, play, disagree, describe again. Handing work back because the recoil is too heavy is the normal state of the project, not a fault in the process.
What you will not do is spend the first two weeks getting a character controller to stop clipping through walls before anything is fun.
Practical answers
It is a download and an install, on Windows, macOS or Linux. The project it produces is a real Godot project, so it is not locked to this app.
Building needs an internet connection, because the chat and asset generation come over the network. The finished game runs without one.
The download is free. 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. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.
More on this: AI shooter generator: what you get in the first hour
What a local build lets you attempt
Long sightlines with things worth seeing at the end of them. Dynamic shadows that move. A skybox and weather that change the read of a level between the start and the end. Twenty enemies active rather than five.
None of those are exotic. They are ordinary shooter features that a constrained runtime makes into a fight, and running on your own hardware makes into a default.
It also means your performance testing is real. What you see when you press play is what someone on a similar machine will see, rather than a number filtered through a shared server and a browser tab.
More on this: No-code 3D game maker for worlds, not just scenes
Performance is a design tool
Because you are testing on your own hardware, you find out early what your level can afford, and that is useful information rather than bad news.
Knowing you have headroom lets you commit to a long sightline or a heavier lighting setup. Knowing you do not lets you design around it while the level is still cheap to change.
Either way it is a real measurement of the machine your player will use, taken during the work rather than at the end. That is not something a shared or browser runtime can give you honestly.
A starting project for this is the shooter game templates. The design note that goes with it is the four Ps of Doom’s combat.
Questions
- How big can a level be?
- Large enough that your machine is the limit rather than the tool. Running locally on bundled Godot is what makes that true.
- Can I import my own models?
- Yes. Your own files, objects from the library, and generated pictures and sound all sit in the same Godot project. Generated 3D models come only from your own Tripo key.
- Does it work on Mac?
- The app runs on 64-bit Windows 11, on Macs with Apple Silicon and on Linux as an x86_64 AppImage.
- Is there a browser version?
- No. It is a desktop app, deliberately, because a shooter is the genre a browser handles worst.
- Does it cost anything?
- No. Every account gets free hosted AI to start, with no sign-up, or you build on 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.
- Can I test performance properly?
- Yes, because you are running on your own hardware rather than a shared runtime. What you see when you press play is what a player on a similar machine sees.
Free to download for Windows, macOS and Linux. Your machine runs the shooter.
Download Flockbay free