Skip to content

Making a Steam game with AI: what the platform actually requires

By Eduardo Orellana · Updated

A Steam game is a native desktop build that people pay for and then play for hours. Flockbay produces the first part; the rest is your game being good enough, which no tool supplies. 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 A Steam game maker for people who bring their own Claude or ChatGPT plan.

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

Steam ships native executables, and Godot makes them

Steam distributes native desktop executables. Not web builds, not streamed sessions. A game that only exists inside a browser tool is not in a shape Steam accepts, which is why a lot of browser-based game makers are a dead end for this specific goal.

Flockbay builds on Godot, which is an engine that ships commercial PC games. Your project is a real Godot project on your disk, and the app's Export makes native builds from it for Windows, macOS and Linux, a single .exe on Windows. That is the right starting shape.

Being clear about what this page is not claiming: Flockbay does not upload your game to Steam for you. The app prepares the store page and makes the build. The Steamworks account, the upload, the review and the paperwork are yours.

More on this: GodotSteam: setting up Steamworks in a Godot 4 game

A paid game has to clear a far higher bar than a demo

People who buy a game expect hours from it, and they expect it not to break. That is a much higher bar than a jam game or a demo, and it is worth saying plainly because AI tools make the first thirty minutes of a game very easy to produce and the next ten hours exactly as hard as they have ever been.

The thing that usually kills a first commercial project is not code quality. It is that the game has one idea and runs out of it after twenty minutes. That is a design problem and it is solved by playing your own game a great deal and being honest about when you got bored.

You are the person who does that. Not writing the code or building the world does not exempt you from judging the game; it is the opposite, it is the whole reason you have time to.

The AI builds the game from a brief, and you judge every pass

It starts with a brief. Flockbay asks questions one round at a time, each with a recommendation, and writes down what gets built first, what comes after and what is not in this version. Nothing is built until you approve it.

On Steam the flat games are not a lesser tier: Stardew Valley and Hollow Knight are both sprites. In 2D, Flockbay paints a TileMapLayer, whose TileSet terrains give the edges and the collision, adds a backdrop behind it, and places sprites at an exact position, rotation and scale. In 3D it builds the player controller, characters and props, with terrain, water and a sky from a Godot plugin or nodes it writes. It writes the GDScript for everything that happens in either — movement, systems, progression, saving, settings menus, all the unglamorous parts that a commercial game needs and a demo does not — and plays the game to check it runs.

Then you play it and say what is wrong, and it changes it against the brief. When the call is pure taste, like where a platform sits or which way a path bends, Godot's own editor is there in the Standard and Full views, so you can make that one change by hand, and Godot's undo takes it back.

Put the unglamorous parts in the brief. Save systems, options, and key rebinding are the things people skip and then have to retrofit into a finished game, which is much worse than having them from the start.

The game runs locally on the copy of Godot bundled with the app, so you are testing on the same kind of machine your players will use.

More on this: How many screenshots does a Steam page need, and which ones?

Building is free to start, and so is getting ready for Steam

Flockbay is a desktop app for Windows, macOS and Linux. The app is free, and building is free to start. 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, generates pictures and sound, or uses your own files.

Building in Flockbay is free to start, and so is getting ready for Steam. In Publishing tools, the Steam page tab takes you through everything the store page asks for: capsules cut from a frame of your game, the description, tags, screenshots, price and system requirements. You fill it in or, on a plan, Flockbay's AI drafts it, and it exports as a .zip with a README naming the Steamworks page each part goes on. You upload it in Steamworks yourself, and the build from Publishing tools > Export goes up with SteamPipe. Flockbay sends nothing to Steam and takes no share of your sales. Steam's own fee of US$100 per app is Valve's.

Building needs an internet connection, since the chat and asset generation are network services. The finished game does not.

More on this: How to put a Construct 3 game on Steam

Make a small free game before the paid one

Make something small and free first, and let people play it. Not as practice in a vague sense — specifically to find out what your game is like in someone else's hands, which is always different from what you assumed.

Then build the paid one, and build it narrow. A short game that is completely solid sells better than a long one with a soft middle, and it is a project you can actually finish.

More on this: How to make a Steam store page, step by step

Every commercial game needs the same unglamorous list

Every commercial game needs a settings menu with resolution and volume, key rebinding, a save system that never loses progress, a pause that actually pauses, and sensible behaviour when the window loses focus.

None of these are interesting and all of them are noticed instantly when missing. They are also ordinary code, so they cost you a description rather than a week.

Ask for them early. Retrofitting a save system into a finished game is one of the genuinely painful jobs in game development, and it is entirely avoidable by doing it while the game is small.

Questions

Does Flockbay publish my game to Steam?
No. Flockbay prepares the Steam store page and exports it as a .zip, and its Export makes the Windows, macOS or Linux build. You upload both in Steamworks yourself.
Does it produce a native PC build?
Yes. Its Export makes a native Windows build, a single .exe, and macOS and Linux builds, from a real Godot project, the format commercial PC games ship from. A Web build is a separate export.
Is there a royalty or revenue share?
No. Flockbay is free to start and takes no share of your sales. The only cost of getting on Steam is Steam's own one-time fee of US$100 per app, paid to Valve, which Steam returns once the game has sold $1,000.
Can a non-programmer really finish a commercial game?
The code is not the barrier here: Flockbay writes it. Scope and design are, and those are the same for everyone. The brief helps with scope, since an idea too big for a first version gets the truth and a smaller one.
Do I need to be online?
To build, yes. To play the finished game, no.

Free to download for Windows, macOS and Linux.

Download Flockbay free