Do you need to code to make a game?

Pick from a menu. The tool ships with a set of behaviours and you assemble a game out of them. Fastest to start, and it has a hard ceiling shaped exactly like the menu — you can build what the authors anticipated and nothing else.

Wire up a graph. Visual scripting: nodes and connections instead of text. Much higher ceiling, because the pieces compose. The catch is that this is programming with a different notation, so you have taken on the conceptual work you were trying to avoid.

Have a model write it. You describe the behaviour and real script goes into the project. No menu means no ceiling from the menu, and the cost is that the code is written rather than assembled, so getting it right takes a round or two.

More on this: AI game maker comparison: the five axes that matter

Design. Whether the corridor is boring, whether the enemy is threatening or just annoying, whether the jump feels right at this height. Those questions decide whether the game is good and there is no tool that answers them.

Playing your own work honestly. This is genuinely difficult, and it is more important than anything technical. The person who has finished one small bad game and played it properly knows more than the person with three months of design notes.

The taste calls in the world, if your game has one. A landscape is spatial taste and there is no correctness test for it. A model with the right tools can build a valley; only you can say it is the valley you meant, and for the last nudge your hand is faster than a sentence.

More on this: An AI game maker for beginners, without the beginner ceiling

If programming interests you, yes, and Godot with GDScript is one of the friendlier places to start. Nothing on this page argues otherwise, and a tool that writes the code for you removes exactly the practice you would be trying to get.

If it does not interest you, learning it in order to make a game is now a detour rather than a prerequisite. That is a genuine change, and it is recent.

The middle position is common and reasonable: do not learn it first, and pick some up later because you got curious about what the code in your own project is doing.

It means you do not write the code. That is the whole of it.

It does not mean you cannot judge the result. You play the game and decide whether it is right, and that judgement is the input the whole process runs on. Any tool that treats not-writing-code as a reason to shield you from decisions has misunderstood who you are.

Being handed work back — play this, is it right, what should change — is the normal loop rather than a failure. It is the only mechanism by which a game gets good, and you are the only one who can do it.

More on this: Best no-code AI game maker: where the ceiling is

Flockbay is the third option above, and it goes past the code. It asks what you want, writes a brief, and once you approve it builds the game and writes GDScript into your project, then plays it to check its own work. There is no behaviour list anywhere in the product. The engine is Godot, open source, bundled inside a desktop app for Windows and Linux.

The world is built too. A project is 2D or 3D, read from your first message: in 3D that means terrain, water, weather, buildings and characters; in 2D it means tile ground and sprites at an exact position. Flockbay builds both with its world tools, and the same tools are buttons around the Godot editor's view for the one change you would rather make by hand. The game runs locally on the bundled Godot at your machine's framerate.

You can read the code — it is a normal Godot project on your disk — and nothing requires it. Building needs an internet connection; playing what you built does not. 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: Who writes the code in Flockbay?