Comments

Log in with itch.io to leave a comment.

Viewing most recent comments 1 to 12 of 139 · Next page · Last page

Solo está en inglés o también está disponible en español?

(+3)

WOWZA! A free learning resource intended to COMPLETELY teach you how to code in a VERY VERSATILE game engine?

(+2)

PSA:

do not put an endless loop in your code. THe game will crash.

(1 edit) (+1)

i just finished the course, and i was wondering if some things could be added (like saving to files and such) otherwise, this is great for learning godot

edit: then again, this is free, so i’m happy with what i learn for free

(1 edit) (-2)

Does not work well in mobile, does not fit to width of device. Even when changing text size still difficult to read. 

(+1)

Thanks!

I have a programing question that isn't clarified by the app if its OK to ask here: 

In lesson 14 the practice where we make the robot take half damage, the if statement where we make the robot  take damage half damage if their level is above level 2 only works if that if statement is the first thing written in the take_damage function. Why does it only work in that order.


Example:

var level = 3

var health = 100

var max_health = 100

func take_damage(amount):

    health -= amount

    if health < 0:

        health = 0

    if level > 2:

        amount *= 0.5

^ This doesn't work.

========================

var level = 3

var health = 100

var max_health = 100

func take_damage(amount):

    if level > 2:

        amount *= 0.5

    health -= amount

    if health < 0:

        health = 0

^ This does work.

(1 edit) (+1)

I would assume (based on my experience with Python, which GDScript is similar to) that the first example does not work because the order of execution is different. In that example, when "take_damage(amount)" is called, "amount" is first subtracted from "health", then it checks if health is lower than 0, then it checks the level and changes the "amount" after the original "amount" has already been subtracted. I hope that makes sense.

(+1)

To clarify: Assuming it works like in Python, functions are generally processed from top to bottom.

this makes sense to me. it sounds like an order of operations problem. thanks for the response!

Always happy to help!

I checked the app to see when/if it mentions this, it looks like in lesson 4 it's kinda mentioned in passing but it's easy not to remember ten lessons later, haha.

(+1)

This is so cool! Perfect for an absolute beginner to learn the basic fundamentals of programming. The lessons are well written and the pacing feels good. It's short and sweet with fun interactive portions

If you already know how to code I'd suggest skimming through the list of lessons first. If they all seem too easy, skip ahead to reading the docs and trying out a tutorial

If you get stuck check the hints, re-read the lesson, or look at previous questions in that lesson. If you're really confused there's even a solution button that shows you the answer

I knew a bit about python and it's language and gd is rlly simlar so I was suprised at how easy it was.. BUTT (hehe butt) can you guys please make it so people can make there own variables? Bc at the start I wanted to make my own lines of code that does the same thing but more simplified but couldn't bc of the restrictions of the syntax.

(+2)

tysm I started making games recently and I didn`t understand GDScript, super easy, clear, good cource, thanks

(+1)

this was really helpful I started Godot about a month ago and I don't understand the code

(+8)(-1)

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

(1 edit) (+4)

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/

Viewing most recent comments 1 to 12 of 139 · Next page · Last page