A beginner engine that does not have to be outgrown

The first is being too hard. You open a professional engine, and before anything moves you have to understand scenes, nodes, signals, a scripting language, physics layers and an import pipeline. Most people stop here, and stopping is a reasonable response to a wall.

The second is being too closed. You open a friendly tool, make something in an afternoon, and a month later you want a mechanic the tool does not have. There is no way through, because the simplicity was made of removed options.

Both are real and both waste months. What you want is something that is easy on day one and does not become the reason you are stuck on day sixty.

You do not write code. Director 1 writes the GDScript, in your project, for whatever you describe. That removes the wall that stops most beginners, which is not the concepts but the syntax and the hours lost to a typo.

You build the world by dragging things around. Terrain, water, weather, buildings, characters. It is a level editor and it behaves like one, so what you are doing is visible and immediate.

And you find out quickly whether something works, because you press play and the game runs locally on the copy of Godot in the app. Fast feedback is most of what makes a beginner keep going.

The engine is Godot, open source, and your project is a real Godot project on your disk. Nothing about it is a beginner format. When you want something unusual, the answer is not that the tool does not support it.

There is also no template list to grow out of. The app builds what you describe rather than offering a fixed menu of game shapes, so the second game does not have to be a variation on the first.

If you eventually want to read the code, it is plain GDScript sitting in your project. Plenty of people learn this way, by reading something that already works on a game they care about. That is optional and nothing in the app requires it.

It is not instant. You will build a world, play it, dislike a lot of it, and go back in. That is the work, and it is the same work in every tool. What is removed is the coding, not the making.

It is a desktop app for Mac and Windows, so you need a computer you can install software on. Building needs an internet connection; playing what you built does not.

The download is free and there is a free plan, so starting costs nothing. Indie is $10 a month and Pro is $50 if you want more usage.

Something small with one idea in it. A short walk through a place you built, with one thing to find and one thing to avoid. That is a complete game and it will teach you more than an ambitious one you never finish.

The reason to start there is not modesty. It is that a finished small thing exercises every part of the process, including the ending, the menu and the save, which are the parts that big first projects never reach.

Then make another one. The second is much better than the first, and the third is better than both, and that progression is the actual path regardless of which tool you use.

Some people arrive not writing code and leave writing a little of it, because there is a working example in front of them that does something they care about.

That is a much better way in than a tutorial series, and it is available here because the code is plain GDScript sitting in your project rather than something hidden.

It is entirely optional. Plenty of people never open a script and finish games anyway. The point is that the door is not locked if you become curious.