How do I learn about Godot?

Finding resources in my own language is quite difficult, and even when I do find them, they’re very limited. Also, most Turkish resources focus on 2D games, whereas I prefer developing 3D games. I read the documentation but didn’t understand anything. It wouldn’t be a problem if it were in English; I could translate it using Google Translate. Could you recommend some resources and learning techniques (including GDScript)?

Obviously, GDQuest isn’t translated into my language (I’m talking about the GitHub version). Also, the Godot Docs feel like an encyclopedia meant only for people who already know the basics of Godot (or maybe I just don’t get it). I need a solid, beginner-friendly resource that teaches the engine from scratch, ideally structured like a website

Hey, there’s a really nice and super beginner friendly guide walking you through the basics of how to make a 2D and 3D game with godot, showing you many of the basic features of the engine, and holding your hand throughout the process!

As for translations, DeepL, which you got a link to above, is a really nice translation tool that does a very good job of translating text!

Nope. The Godot documentation is comprehensive and includes a special section for beginners. It’s very clear and easy to follow. That’s where I started out myself.

But it’s best to start at the beginning — the introduction — where the basic concepts are explained.

To be honest, I’m really confused about what I should do right now; I’m stuck in a bit of a ‘tutorial hell.’ I also have a question: Why should I look into other engines when Unity is already so well-established, with such massive resources and community support? Does an engine being open-source really matter that much to the end user? To me, its only real advantages seem to be that it’s lightweight and free. I want to make a game but I have absolutely no prior knowledge—please enlighten me.

Godot seem easier than unity

As you said most of resources translated to your language focus on 2d

However at least in Godot it seem the concepts you learn on 2d (input, sound, progamming, progamming patterns) can be also used in 3d without you needing to learn a lot more

You should first try making a game following a tutorial then try learning Gdscript (Gdquest is really good if you can translate it) then you could read about progamming patterns game dev progamming patterns (while not specific to Godot this one helped me a lot) theres a video on YouTube about all 2D Nodes and 3D ones i think it also has captions

For a learning technic if you want to escape tutorial hell dont watch or read anything about how to make a specific game but instead about how to make the mechanics. Trying to figure things yourself can also help

Also forgot to metion but the observer pattern in the link i sent is in Godot and is called signals. The flyweight are Godot resources. There are already built in resources but you can use custom ones if you want to use the strategy pattern.

Well, the question of choosing an engine is a slightly different matter than the one that was asked.

But there’s a view — one I share — that Godot is the best way to learn programming in general and game development in particular. GDScript can be a good first language to learn. Especially since there’s excellent official documentation with tutorial examples. To do something in Unity — do you know enough C#?

I only know the powershell language lol. Also, I’ve only made games in scratch in my life.

if you have problems with learning godot from scratch, maybe try learning programming from scratch first? Godot is game engine, and it don’t teaches you how to write code, rather how to use it with libraries, start with python, it’s beginer-friendly language and it’s quite powerfull + you use OOP version of it in godot

I disagree with you. I think just learning GDScript is enough. Why should I learn Python? After all, I will only make games, I will not use network analysis, artificial intelligence and other Python fields..

It generally isn’t if you plan to program the whole game yourself. You need to have some foundational computer science knowledge that doesn’t depend on which particular language you’re using.

How so? Memory addresses and other terms??

What’s a “memory address”?

loops, conditions, functions, clean code, variables, constants, enums, arrays, dictionaries, all of these are shared across every post asemmbler language that’s somewhat low level, you’ll use them 90% of time inside godot as you would outside of it

You can learn progamming with just Gdscript no need for python

Sure, you can, but games are arguably the most difficult pieces of software to make as a whole.
It might be a lot less indimidating and easier to start with just focusing on programming and understanding the basics, then applying those things to something more specific, such as game programming.

As @tibaverus said, it’s easier to start godot with knowledge of programming, rather than just dive into the deep waters instantly, python is just example, it can be scratch, C++ or even BASIC, just it needs to resemble mid-low level programming languages with it’s logic

In order to successfully program a game, your skills have be on the level where it makes no differences if you’re doing it in Python or in GDScript. In other words you’ll have to “learn GDScript” to such a degree that you could just swap it with Python at any time.

You should do as you please. That said, by your own admission you’re already stuck in ‘tutorial hell’. Having more tutorials to read will not help you escape. Building an actual game will. This holds true regardless of which engine you pick.

Do the two mini introductions linked earlier in the thread by tibaverus and tomcat. They’re gentle introductions that explain the fundamentals of working in Godot: nodes, scenes, signals, instantiation, et cetera. They’re not comprehensive, but they help you grow the sort of intuition you need to make things in the engine.

To the player? No. To you, the developer? If you want to have a good laugh, search for ‘unity runtime fee’ in your favorite search engine.