Making a game with no experience: what you skip and what you do not

By Eduardo Orellana · Updated

You can skip learning a programming language and an engine interface. You cannot skip having taste, playing your own game, and deciding what is wrong with it. That is the honest deal. Flockbay is free, AI included: free hosted AI every day, or your own Claude, ChatGPT, agent or API key. It runs on Windows and Linux, on the official Godot engine.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for Windows

What normally stops people, in order

First the engine. You download something large, open it, and are looking at fourteen panels with no idea which one is the game. Most people quit here and it has nothing to do with talent.

Second the language. You find a tutorial, copy some code, it works, and then you want to change one thing and cannot, because copying is not understanding.

Third the world. Even if you get past both, you now need a place for the game to happen, and modelling software is a whole second career.

None of those three is the game. They are the tax on getting to the game, and it is a heavy tax paid in advance by people who do not yet know whether they will enjoy the thing they are paying for.

What Flockbay removes

The language, entirely. Flockbay writes GDScript in your project. You describe what should happen in normal sentences and never open a script.

Most of the engine, and the world with it. You describe the game in a sentence; the app reads it and preselects 2D or 3D, and Flockbay asks a few questions, one round at a time, each with a recommendation, then writes a brief: what gets built first, what comes after, what is not in this version. Once you approve it, Flockbay builds the world itself. In a 3D project that is terrain, water, sky and weather, and the buildings, props and characters standing in it. In a 2D project it is tile ground and sprites from the library. The editor around it is Godot's own, and you do not have to learn its panels to get a game.

And the wait between the idea and the jump. Flockbay plays its own work before you do: it runs the game, sends input events, reads the debugger and captures the viewport, so the first thing you do is not setup, it is having an opinion about the jump.

And a good deal of the asset problem, since things can be generated, sourced, brought from your own files, or built directly as geometry, depending on what is honest for the case.

What it does not remove, and should not

Judgement. You are the person who plays the game and decides it is boring, or too dark, or too slow at the start. No tool supplies that and you would not want one that tried.

Iteration. First versions are wrong. That is not a defect in the AI, it is what making anything is like. The work is the second, fifth and twentieth pass.

Scope discipline. Beginners with no engine friction can start something enormous very quickly, which is a new way to fail. A small finished thing teaches you more than a large unfinished one.

A first project that actually finishes

One room, or one small outdoor space. One thing the player wants. One obstacle between them and it. Ten to fifteen minutes of play at most.

Put that in the brief, so the space comes first and there is somewhere to stand. Get walking working. Then add the want and the obstacle, playing after every change. When it works, stop and start a second one rather than expanding the first, because the second one is where you get good.

The practical facts

Flockbay is a desktop app for Windows and Linux. It installs on your machine and bundles open-source Godot, so your game runs locally rather than streaming from anywhere.

You need an internet connection to build, because the chat, asset generation and world data all come over the network. You do not need one to play what you have made.

The download is free, world tools included. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

More on this: A game maker for education, and what it actually teaches

What you will pick up anyway

Not syntax, but a feel for how games are put together. After a few weeks you will find yourself thinking in terms of states and triggers without having been taught the words, because that is genuinely how games work and building one teaches it.

You will also get much better at describing what is wrong. Beginners say a game feels bad; people who have iterated a few times say the acceleration is too slow and the hit reaction is too long. That precision is the skill that compounds.

None of it requires a course. It comes from playing your own work and paying attention to your own reactions, which is available to anyone.

More on this: A free game engine for beginners, counting the real cost

Questions

I have never used a game engine. Is that a problem?
No. Flockbay does the building from a brief you approve, and you play and say what is wrong. Godot's editor is there when you want to change something yourself, and you do not have to learn it first.
Do I need to learn GDScript later on?
No. Flockbay writes it. The code is in your project if you ever want to read it, and nothing depends on you doing so.
How long before I have something playable?
Something you can walk around in comes quickly. Something you would want a friend to play takes as long as any first project takes, because that part is design.
Is it free to try?
Yes. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.
Does it work in a browser?
No. It is a desktop app for Windows and Linux, and your game runs locally on bundled Godot.