Last night I tried out Godot 3.0 for the first time.
I had been using Godot 2.1.4 for quite some time. And I was really excited to learn all about the new tech. When I saw the post that Godot 3.0 was launched I couldn’t believe it! Godot had finally come! I thought it would never come!
The one thing that I am very grateful for is that the developers said a long time ago that this update would break code.
When I was learning how to use Unity, they had made some very big changes when changing versions and It just broke all of my code. As a learner this was very frustrating. The code in tutorials broke and I had to look elsewhere to learn what to do.
With Godot, this is different. Everything is very intuitive to use. I can easily do what I need to do and figure out things with the built-in documentation. For a complete beginner to programming, Godot still has a good learning curve, but it is not as steep as Unity.
And that’s why I ditched Unity. My code kept on breaking, and I couldn’t keep up with all of the fancy changes. Also, making 2D games was just clunky at the time. I would go back to Unity if I needed to. But right now Godot has everything I need.
So let’s talk about my first Impressions of Godot 3.0 as an avid user of Godot 2.1.4.
The first change that makes a difference in they way I work is the use of properties and Methods. In Godot 2.1.4 I could easily sling variables around and call functions from anywhere. This gave me great freedom as a programmer. But this freedom makes it easy to write messy code.
Objects should have a purpose. And some methods should be handled privately within the object. In Godot 3.0 I can’t just set an object’s position from another object anymore. The object itself must handle setting it’s own position. I can however give it coordinates from an outside object.
Another big change is the debugger. I can’t seem to find the remote inspector. Maybe they dropped it in this version.
Oh! I found it! You have to go to Debug at the top and click on Deploy with Remote Debug. This will give you access to the remote inspector very easily. Nice!
How to enable the remote inspector in Godot 3.0
Well, I guess they moved things around. That was expected. The new UI is fresh and slick, but it comes with the cost of re-learning where everything goes.
I do wish that the properties in the Inspector were all expanded by default. I don’t like making extra clicks to access my properties in the inspector. Perhaps there is a way to set this by default.
But there is an easy one click solution for each new scene or node that you make. I wish I could set this to the default, though.
How to expand the properties in Godot 3.0
The types of Nodes has changed a bit and the methods for them have also changed. This is the biggest thing I have to get used to. Many things cross over from Godot 2.1.4, but the updates will take some time to re-learn. All of these changes are for the better.
The only thing that I got myself scratching my head on is what the import tab does exactly. Perhaps if I import some sounds or something it will be more useful.
Oh! I see If I click on assets in my file system, I can reimport them into the system with different settings. For instance, this Image.
What the Import Tab does in Godot 3.0
There is still a lot of fiddling around and learning how things work in the new Godot 3.0. I’m happy to be using it to make some games. It’s the best system that I know to make games quickly and thoroughly.
Perhaps after I learn quite a bit more, I can write up some documentation. But for now, here’s my humble little blog post.
Thanks for reading! If you have any questions about the Godot game engine, leave me a comment below! I’ll try to answer as much as I can. This is still very new to me and many other people out there who wanted to wait till the stable version was released.