Because I bet whoever discover Godot with this learning game and jump joyfully straight to the Godot editor will bang his head against a brick wall, like I did. After I played this I was confident as it's just your well-known programming, but I was completely lost when I went to the editor for the first time. I am not talking about the range of buttons that can look impressive. I was stuck having just 'nodes' on a plan, and nothing else. When I started a script it began with a curious 'extand node'. I searched how to have something like the robot or turtle you code in your game but nothing. Just nodes with wich I couldn't do anything while it looked like something essential. I replayed and searched your entire game lesson here in case I foolishly missed anything but no.
Fortunately, I am not a complete beginner and I found the documentation (link at the top). Now I understand node and the scary inability to grasp the editor disappeared. I almost gave up on using Godot because of that experience but now I am finally interested and curious.
As a conclusion, I think you should guide the beginner to at least have a sprite to code with, like the ones you use in practice, for example with a link to the documentation's example tutorial, and also warn to learn Godot's key concepts. I know this game is about learning GDScript, not Godot, but your nice appealing little game floating around on this site may be the entrance door to Godot for a lot of curious people, and currently, because of the raised issue, may accidentally lead to negative publicity
That's why the screen at the end of the course invites people to keep learning, and gives them two options: either free tutorials on our channel, or, for those who want to and can support us financially, our school curriculum.
For people following from the official docs, the end screen invites them to continue with the official docs' getting started series.
In all three cases, they'll get to learn about the node etc., which this app hides to reduce cognitive load.
Thanks for the suggestion to add a lesson or at least explanations about nodes and a sort of steppingstone to using Godot.
At the moment we have a lot of work on our school curriculum (this app is a free and open source module from our curriculum that we made to help address the lack of GDScript course at the time), but as the app is open source, if teachers want to contribute more material or work on improvements and bug fixes, this is always much welcome.
← Return to game
Comments
Log in with itch.io to leave a comment.
tysm I started making games recently and I didn`t understand GDScript, super easy, clear, good cource, thanks
this was really helpful I started Godot about a month ago and I don't understand the code
I think you should really warn any beginner to also see the full Godot documentation if he wants to really create with Godot engine, or at least put a link to it:
https://docs.godotengine.org/en/4.4/index.html
And in particular, the key concepts overview in it:
https://docs.godotengine.org/en/4.4/getting_started/introduction/key_concepts_ov...
And/or the 2D example tutorial:
https://docs.godotengine.org/en/4.4/getting_started/first_2d_game/index.html
Because I bet whoever discover Godot with this learning game and jump joyfully straight to the Godot editor will bang his head against a brick wall, like I did. After I played this I was confident as it's just your well-known programming, but I was completely lost when I went to the editor for the first time.
I am not talking about the range of buttons that can look impressive. I was stuck having just 'nodes' on a plan, and nothing else. When I started a script it began with a curious 'extand node'. I searched how to have something like the robot or turtle you code in your game but nothing. Just nodes with wich I couldn't do anything while it looked like something essential. I replayed and searched your entire game lesson here in case I foolishly missed anything but no.
Fortunately, I am not a complete beginner and I found the documentation (link at the top). Now I understand node and the scary inability to grasp the editor disappeared. I almost gave up on using Godot because of that experience but now I am finally interested and curious.
As a conclusion, I think you should guide the beginner to at least have a sprite to code with, like the ones you use in practice, for example with a link to the documentation's example tutorial, and also warn to learn Godot's key concepts.
I know this game is about learning GDScript, not Godot, but your nice appealing little game floating around on this site may be the entrance door to Godot for a lot of curious people, and currently, because of the raised issue, may accidentally lead to negative publicity
My two cents
That's why the screen at the end of the course invites people to keep learning, and gives them two options: either free tutorials on our channel, or, for those who want to and can support us financially, our school curriculum.
For people following from the official docs, the end screen invites them to continue with the official docs' getting started series.
In all three cases, they'll get to learn about the node etc., which this app hides to reduce cognitive load.
Thanks for the suggestion to add a lesson or at least explanations about nodes and a sort of steppingstone to using Godot.
At the moment we have a lot of work on our school curriculum (this app is a free and open source module from our curriculum that we made to help address the lack of GDScript course at the time), but as the app is open source, if teachers want to contribute more material or work on improvements and bug fixes, this is always much welcome.
The source code can be found here: https://github.com/GDQuest/learn-gdscript
We also made an interactive tutorial that runs directly in Godot that runs through the essential concepts of the engine, to give people an overview of the tools they'll need to learn and practice using: https://www.gdquest.com/tutorial/godot/learning-paths/godot-tours-101/