Making a Steam game with AI: what the platform actually requires
By Eduardo Orellana · Updated
Flockbay is free on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds a real Godot project in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices. Windows today. The engine is the official Godot release. 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.
What Steam is, from a build point of view
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, producing native builds. 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, and there is no button here that handles a store page, a build pipeline, or the paperwork. Those are yours.
The bar a paid game has to clear
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 does not exempt you from judging the game; it is the opposite, it is the whole reason you have time to.
How the work divides
A new project asks 2D or 3D before it will create anything, and on Steam the flat ones are not a lesser tier: Stardew Valley and Hollow Knight are both sprites. In a 2D project you build the world by dragging ground into place a cell at a time and putting each sprite at the position, turn and size you chose. In a 3D one you shape terrain, outline water, set the weather, and place every building, prop and character. Flockbay 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.
Ask for the unglamorous parts early. 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: Make a game without coding, and without a ceiling
The practical terms
Flockbay is a desktop app for Windows. The app and the whole builder are free. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.
The monthly plan is for building. Publishing to Steam through the app is priced separately, and the fee and any share of sales are shown on the submission screen before you commit to anything.
Building needs an internet connection, since the chat, asset generation and world data are network services. The finished game does not.
More on this: Mobile game maker: the desktop kind, and why that is normal
A realistic route
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.
The 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.
More on this: What you build is an ordinary Godot project, which is the shape a game gets sold in
The design note that goes with it is what releasing a game on Steam is actually like.
Questions
- Does Flockbay publish my game to Steam?
- No. It builds the game. Getting it onto a store is separate work that you handle.
- Does it produce a native PC build?
- Your project is a real Godot project, which is the format commercial PC games ship from. It is not a web build.
- Is there a royalty or revenue share?
- Your monthly plan is a flat price for building and carries no share of your sales. Publishing to Steam through the app is a separate, paid step, and it does have a share of revenue above a threshold. The exact figures are shown on the submission screen at the time you submit rather than quoted here, because they can change.
- Can a non-programmer really finish a commercial game?
- The code is not the barrier here. Scope and design are, and those are the same for everyone.
- Do I need to be online?
- To build, yes. To play the finished game, no.