What an AI FPS generator can honestly hand you
You can have a walking, shooting, dying first person shooter in an afternoon. What you cannot have is a good one, and the gap between those two things is the whole project. 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.
The afternoon version
Describe a shooter, agree the brief, and Flockbay will build it: a first level, a first person controller, a hitscan or projectile weapon, ammo and reloading, health and damage, an enemy that chases and shoots back, a respawn, a score. That is a real playable loop and it takes very little time.
It is worth being clear that this is genuinely useful. Most people who want to make a shooter never get past the first weekend, and the first weekend is exactly the part that generates well. Skipping it is not cheating, it is skipping the part that is the same in every shooter.
What arrives is a shooter-shaped thing. It works. It is not yet a game anyone would play twice.
More on this: AI shooter maker: the genre that lives or dies on feel
Everything that is not in the generated version
A reason to be there. A level with a shape, rather than a box with enemies in it. Enemies that behave differently from each other. A weapon that feels distinct at the moment of impact. A difficulty curve. A sound design that tells you what is happening behind you.
None of those come out of a description because none of them have a default correct answer. They are decisions about your game, and a generator that guessed them would be guessing.
This is why the brief comes first: Flockbay asks about them before it builds anything, each question with a recommendation, rather than guessing. And it is why you walk the level it builds. What you cannot see from a description you can see immediately from inside the level, and when the fix is a matter of a metre, Godot's own 3D editor is there in the Standard and Full views, so you can move the cover yourself.
More on this: Godot FPS templates, and why the feel is most of the work
Generation as a starting point rather than an answer
The right way to use a generator is as a way to arrive at a working loop fast and then start disagreeing with it. Play it, notice the enemies are too accurate, say so, play it again. The generated code is in your project as ordinary GDScript, so changing it is a normal thing rather than a regeneration.
Regenerating the whole shooter because one thing is wrong is the failure mode, and it is why some tools never converge. Every reroll is a different game, not a better one.
You do not need to write the code to run that loop. You need to play the game and be honest about it, which is a thing you can already do.
Where it runs
Flockbay is a desktop app for Windows, macOS and Linux, downloaded and installed, with Godot bundled inside it. The game runs on your machine, not in a tab and not streamed.
For a shooter that matters twice: a browser build caps what your level can contain, and inconsistent frame timing makes aiming feel wrong in a way players blame on the game.
Building needs an internet connection. Playing does not. 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.
More on this: FPS game maker: the feel comes before the level
Difficulty is the part you have to make up
A generated shooter arrives at a default difficulty that means nothing, because difficulty is relative to a player, and no tool has watched yours play.
Worse, you are the worst possible judge of your own game difficulty, because you have played this level two hundred times and know where everything is. The version that feels right to you is usually far too hard.
There is no way round this except other people. Watching one person who has never seen your level play it for ten minutes will tell you more than a week of your own testing. That is true in every tool and it is the thing generation cannot shorten.
Making the generated version yours
The fastest way to stop a generated shooter feeling generic is not more generation. It is one strong decision applied everywhere: a setting, a restriction, a single weapon with a strange property.
Restrictions work particularly well here because a shooter has so many defaults. Take one away, ask for the code that replaces it, and the whole game reorganises around the absence.
That decision is not something a generator can supply, because it is the only part of the project that is genuinely about you rather than about the genre.
More on this: Make an FPS with AI: the feel is code, the map is judged on foot
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 long until I have something playable?
- A basic shooting loop comes together quickly. A shooter you would show someone takes as long as it takes you to make the level good.
- Does it generate the levels too?
- Yes. Flockbay builds the level from the brief. A shooter level is a looking problem, though, so you walk it and judge it, and any spot you want exact you can move by hand in the Godot editor.
- Can I change the generated code?
- Yes. It is plain GDScript in a normal Godot project. You can ask for changes or make them yourself.
- Is it online or a download?
- A download, for Windows, macOS and Linux. Building needs an internet connection; playing what you built does not.
Free to download for Windows, macOS and Linux. Start from a working loop.
Download Flockbay free