Skip to content

AI stealth game maker: the guard has to be readable

By Eduardo Orellana · Updated

Stealth is a genre about information. The player needs to know what the guard knows, and building that legibility is the whole design problem. 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 What is an AI game maker that writes a real Godot project?.

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

The rule that governs the genre

A stealth game is only fair if the player can model the guard. Where he is looking, how far he can see, what he heard, what he will do about it. When that model is accurate, being caught feels like a mistake and the player tries again. When it is not, being caught feels arbitrary and the player quits.

Everything else in stealth design follows from that. Vision cones exist so seeing is legible. Alert states are staged so escalation is visible. Sound has a radius so the player can reason about noise. These are not conventions for their own sake; they are the genre solving its information problem.

Building a stealth game therefore means building a system a player can read, and then building levels that make reading it worthwhile.

The systems, written for you

Perception with distance, angle and line of sight. Alert states with entry and exit conditions and a search behaviour between them. Patrol routes with waits and glances. Noise from footsteps, doors and objects you throw. Hiding, cover and the light level that decides whether cover works. Detection meters, if your design shows them.

Flockbay writes these into your Godot project as GDScript. You then play, and the useful feedback is exactly the kind a player gives: he saw me through a wall, he gave up too fast, I could not tell he had noticed me. Each of those is a change.

You are not required to read the code. Being non-technical does not make you a worse judge of whether a guard is behaving sensibly; if anything it makes you a better one, because you are watching the game rather than the implementation.

Levels are the puzzle, and the puzzle is tuned by sneaking through it

Flockbay builds stealth levels from the brief you approved, and this is where the game exists. Patrol paths that cross at an inconvenient moment. A vent that offers a route at the cost of information. A courtyard with two guards whose cones leave a gap that closes every twelve seconds.

That timing has to be arranged by someone who knows what they are arranging, and the arranging happens in the playing. Flockbay runs the level and captures the viewport to check it; you sneak through it, say the gap is too generous, and it changes. When the fix is one crate of cover, Godot's own editor is there in the Standard and Full views, so you can move it yourself and Godot's undo takes it back.

Light matters enough here to plan around. So does verticality, and so does the sight line from the balcony you thought was decorative.

The app itself

Flockbay is a desktop app for Windows, macOS and Linux. It installs on your machine and bundles Godot, so the game runs locally. Your project is an ordinary Godot project.

An internet connection is needed to build, because the chat and asset generation come over the network. Playing what you built does not need one.

The download is free, and so are the editor, your own art, playtesting and export. 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.

Failure has to be survivable

The oldest argument in stealth design is what happens when you are caught. Instant failure and a reload makes the game a series of restarts, and players start save-scumming rather than playing. Full combat makes stealth optional, and once it is optional most players stop bothering with it.

The answer most good stealth games arrive at is a middle state: being spotted is expensive but recoverable. You can break line of sight, guards search and eventually give up, and the level continues in a worse condition than before. That keeps the tension without turning the game into a checkpoint simulator.

Getting that middle state right is a tuning job. How long guards search, how far they spread, how much they remember, whether the alert decays fully or leaves them jumpy. Each is a number, each changes the whole game, and each is found by being caught on purpose and seeing what happens next.

Questions

Can I make a top-down stealth game?
Yes. Camera perspective is a design decision. Top-down actually makes the information problem easier because vision cones are readable at a glance.
How sophisticated can guard behaviour get?
As far as you take it through iteration, since it is code written for your game rather than a fixed behaviour set. Guards that coordinate searches are a normal thing to ask for.
Do I need to write code?
No. Flockbay builds the levels and writes the GDScript. You judge the behaviour.
Does it work in a browser?
No. It is a desktop app for Windows, macOS and Linux, and the game runs locally on the bundled Godot.
What does it cost?
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.
Should being spotted end the mission?
That is a design decision rather than a setting we impose. Most players prefer a recoverable failure, because it keeps them playing instead of reloading.

Free to download for Windows, macOS and Linux. Build a guard the player can read.

Download Flockbay free