Make an FPS with AI: the feel is code, the map is judged on foot
A first person shooter is two crafts: the feel of moving and shooting, which is code, and the map, which is architecture. Flockbay builds both from a brief you approved, and you judge both by playing. 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.
Feel is a stack of small numbers
Mouse sensitivity and acceleration. How fast you get to full speed and how fast you stop. Whether you can strafe at full speed. How much the camera moves when you fire, and how quickly it returns. How long between shots, how long to reload, and whether the reload can be cancelled.
Every one of those is a number, none of them can be reasoned out in advance, and all of them are code. Flockbay writes them as GDScript in your project and you tune them by playing, which is the only way anyone has ever tuned them.
The single most valuable thing you can do early is spend an hour walking around an empty box, adjusting movement until it is pleasant with nothing to shoot. If moving feels good, a mediocre map is playable. If it does not, a brilliant map is not.
More on this: Make a platformer with AI: getting the jump right is the whole job
The map is architecture, and you judge it at eye level
Sightlines, cover, height differences, how many ways there are into a room, how long you are exposed crossing a space. This is the design work of the genre and it is spatial, which means it is judged by walking it rather than by reading about it.
Flockbay builds the first version of the map from the brief and play-tests it itself, but whether a sightline is fair is your call, so you playtest constantly too. A map that reads well from above can be miserable at eye level, and the only way to find out is to be in it. When a piece of cover is in the wrong spot, say so, or move the crate yourself: Godot's own 3D editor is there in the Standard and Full views, and Godot's undo takes a change back.
Outdoor spaces get terrain from a Godot plugin, with water, a sky and weather from a plugin or nodes Flockbay writes. Interiors get built from Godot's own shapes, ready-made objects from the library, or your own files.
More on this: Make a horror game with AI: the fear is in the level, not the code
Enemies, and being honest about them
Enemy behaviour is code and Flockbay writes it: patrol, notice, take cover, flank, retreat when hurt. You describe the behaviour you want in sentences and tune it by playing against it.
What is worth knowing is that good enemy behaviour is mostly about readability, not intelligence. A player needs to see the enemy decide something. An enemy that plays perfectly and invisibly just feels unfair. So the tuning you will do is usually making enemies more legible rather than smarter.
Local performance is not optional here
Flockbay is a desktop app for Windows, macOS and Linux, and your game runs on your own machine through the bundled open-source Godot. This matters for a shooter more than for anything else, because input latency and frame consistency are the genre.
A shooter running through a browser tab is a compromised shooter, and no amount of clever engineering changes that. Running locally is the reason this is a download.
Building needs an internet connection. Playing what you built does not.
More on this: AI shooter game maker: the level and the code, built from one brief
What to leave until later
Multiplayer. Networked shooters are one of the hardest things in the field and starting there is how first projects die. A single player or wave-based shooter teaches you the feel and the map craft, which is what transfers.
Also: an arsenal. One weapon that feels excellent beats six that feel approximate, and you will learn more tuning one properly.
One weapon, tuned properly
A weapon is about eight numbers and every one of them changes how it feels. Fire rate, damage, spread, recoil amount, recoil recovery, reload time, magazine size, and how long the shot sound lasts.
Change any of them and the weapon becomes a different weapon. This is why a single gun tuned over an evening beats an arsenal assembled in an hour, and it is the fastest way to develop a sense for what you are actually adjusting.
Feedback matters as much as the numbers. What sells a hit is the response: the sound, the flash, the reaction of the thing you hit. A weak weapon with good feedback feels better than a strong one without.
More on this: AI FPS game maker: the weapon first, then everything else
A starting project for this is the shooter game templates.
Questions
- Do I need to code the shooting mechanics?
- No. Describe how it should behave and Flockbay writes the GDScript. You tune it by playing.
- Can I make the map without modelling software?
- Yes. Terrain, water and weather come from Godot plugins in the Plugins panel, and structures come from Godot's own shapes, the library of ready-made objects, or your own files. 3D models are generated only on your own Tripo key.
- Is multiplayer supported?
- A standalone Godot project does not give you networked multiplayer for free, and it is a hard first project. Single player is the sensible starting point.
- Will it run well?
- It runs locally on your own hardware through bundled Godot, which is the right setup for a genre that depends on frame consistency.
- What does it cost?
- Free to download. 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.
Free to download for Windows, macOS and Linux.
Download Flockbay free