To briefly introduce myself as someone leaving a review after taking this course: - Started as a complete beginner from Godot 3 - Completed 1 Godot Engine learning book (went through it twice) - Studied 3 free video courses on Godot Engine (2 on Inflearn, 1 on YouTube) - Studied 2 paid video courses on Godot Engine - Released 1 Play Store app using Godot Engine Despite the above experience, I was still unaware of the hidden features tucked away in every corner of Godot Engine and the functions of countless nodes, constantly using only what I was familiar with, when I took this course. I followed along with every single piece of code from start to finish without missing anything. The result was complete satisfaction. Let me detail what I was satisfied with. 1. Even for a single feature, it teaches multiple methods step by step. For example, the book I studied was based on Godot 4, yet it only taught one method from Godot 3 for moving with arrow keys and ended there. However, this course starts with the method shown in that book, then tries more efficient ways to write code, and even shows how to write it in one line through several step-by-step approaches. You might think that for simple player movement code, you could just save one method and use it whenever needed, but it's not that simple. Godot Engine is designed to calculate direction and rotation based on the Vector2 class, and by following the instructor's guidance, I naturally understood methods for easily calculating direction and rotation. If I had only learned one method for arrow key movement, I would have had to learn direction/rotation calculation methods separately, which would have taken longer to understand each method and delayed the connection between direction/rotation calculations and how movement keys work. Also, the various methods shown for 'setters' that update data when states change were useful, and what particularly stands out in my memory is the state machine. In the book I studied, the only method taught for implementing a state machine was using enums. I didn't know Godot Engine had state machines until I took this course. Oh, the inadequacy of a book I paid 30,000 won for. This course teaches both how to implement state machines using enums and how to use the built-in state machine functionality directly. 2. It teaches detailed features and tips that are easy to miss. First, this was the first course I've seen that properly explains the relationship between Path2D nodes and PathFollow2D. I've seen other courses cover these nodes, but I've never seen a detailed explanation that when you set a path with a Path node and place PathFollow as a child, it moves along that path. Hearing this one sentence immediately made me understand the relationship between the two nodes. I also learned various shortcut functions that are convenient to use once you know them. 'Ctrl + Alt + O', 'Ctrl + Shift + O', 'Shift + Alt + O', 'Ctrl + Shift + F', etc. - they're indispensable. It also shows how to set up extra blank space at the bottom when writing code. It's a small thing, but it's an extremely useful feature. Let me briefly look at feedback from other reviews. - From the latter half, the delivery speed became fast and difficult to understand. => It's true that it gets harder from the latter half. Sometimes explanations are skipped, but I think it's at a level where learners can search and figure out those parts themselves. I think it's good to consider doing your own research as a kind of practice. - The code isn't logical and explains things according to personal preference. It's scattered. => I agree with this too. But code inevitably reflects the writer's preferences, and this would happen even if Bill Gates himself came to teach. Also, scattered code is an unavoidable characteristic of Godot Engine. Signals go back and forth everywhere, and you have to bring node names from within scenes to write code, which can sometimes make it confusing what's what, but I think there's no problem for learning the overall flow of Godot Engine, and it's something you can sufficiently overcome when working on your own projects. If you still think this course is difficult despite the above explanation, you can just go through it 2 or 3 times. I think this one course can do it all. Don't think too hard about it, and let's approach it step by step with the mindset that even a journey of a thousand miles begins with a single step.

I wanted to make a game on my own without knowing anything about coding, so I diligently searched for overseas YouTube tutorials, and yours taught me the most meticulously about the things I was curious about, which helped me understand a lot! As the lecture covers a lot of content, there were some overwhelming parts for a beginner, but the more I listened to it again and again, the more I discovered the parts I was missing, and with that, I realized how meticulously the instructor taught. Everything was really in the lecture. Thank you so much for explaining in such detail that I can create my own game that I'm planning, in addition to the shooter game we made together. There were no redundant explanations despite the detail, so I watched it while admiring that it was a really neat lecture. I think I'll keep watching it like a bible until I get used to it! The tuition fee is really worth it. The updated parts were also very helpful. If you open shader or other advanced lectures in the future, please let me know, I definitely want to take them 👍👍

Personally, this is a very satisfying lecture. The content increases as you go on, but I diligently completed it. After listening to it all, I feel like I am full of development enthusiasm.