Godot 4 Crash Course for Beginners - GameDev 2D Top Down Tutorial

In Godot 4.1, they've changed the way the state machine transition arrows work in the AnimationTree flow chart (where you draw the lines to show which states transition to which). They now default to automatic, which causes it to cycle through all of the animations really fast and basically look like nothing is happening. To fix, select the arrows between idle and walk and in the Inspector, under Advance, change mode to Disabled

37:37 for people using the full release of godot 4, the ≠ used in the code can be typed out using !=. They do the same thing, but the engine can read !=

Great tutorial, thanks for sharing. There is a minor problem with walking diagonally (walking in two directions at the same time, e.g. up and left). The input direction vector will be a bit longer than the vector when only walking in one direction. The effect will be a slightly higher walking speed when walking diagonally. This is because the diagonal d in a square is d = a * sqrt(2) when a is the length of the squares sides. To fix this problem, when calculating the velocity of the character, instead of "input_direction * move_speed" use "input_direction.normalized() * move_speed".

A quick reminder with movement vectors is to use the normalized() function. So when we made the input_direction for the player, just add a .normalized() at the end of the closing parenthesis : var input_direction = Vector2( Input.get_action_strength("right") - Input.get_action_strength("left"), Input.get_action_strength("down") - Input.get_action_strength("up") ).normalized() if you don't do this you'll notice your player moving a lot faster if you walk diagonally. Normalizing makes it where your speed is always 1 rather than the 1.4 you get otherwise.

Hey! Godot 4 actually has a bunch of new Input methods that I think you should check out in the docs! I haven't watched the whole video yet (work) so forgive me if you mention this in the video. Anyways, two new ones that are very useful are Input.get_axis and Input.get_vector. These are basically shorthand for Input.get_action_strength("positive action") - Input.get_action_strength("negative action") but in one function. Input.get_axis is for platformer-type movement (left and right) while Input.get_vector is for top-down type movement (up, down, left, and right). You just pass the positive ("right") and negative ("left") actions and it returns the proper input. Great video so far! I can't wait to finish it!

I like the tut so far, it's nice to get into 4.X from 3.X but, just leaving this here if people might into problems: 33:34 They changed up the autoadvance a bit with 4.1.1 I think, it's active by default it seems (under Advance -> Auto). And you have to set it to "enable" on the links between walk and idle animation for the Dude to idle and not just spazz between the two states indefinitely. 36:27 also I've noticed that I had to set the blend values to the full ends ( 1.1 , -1.1) or it creates some funky results of animation blending. The Default behaviours are probabyl set differently in 4.1.1 Okay nevermind the blend mode has to be changed... xD 43:38 You can also do that with the rektangle tool, when you draw a rectangle you just get a few of the special tiles.

This tutorial is fantastic, you get into exactly the right amount of detail for everything, love it!

Thanks for the video, very informative! I'm new to Godot but not new to game dev, so this was a great way to get up to speed with how Godot works differently from other engines.

Might have been me, but a couple notes since some stuff have changed since this was recorded. So hopefully this helps some people. I am using - v4.0.beta13 - Some of the inspectors have changed slightly, so just open up some the other caret/caron menus ">, v" (not sure the term, haha) and you might find the option you are looking for. - Animation Tree for each connection "->-" between idle and walk, click on them, Inspector>Advance>Mode, Set to "Enable", keep the "Start"->-"Idle" as "Auto" || Looking at the tutorial I noticed the interface for AnimationTree was different, so poking around and that is how I fixed it. - As pointed out in the comments if you can't easily type ≠ you can type != instead (plus some dummies ruined ≠ ) I may have missed it being mentioned but for the cow animations you add "Animation>[animation]" and not "BlendSpace2D" like you did with the playercat animation

I followed a tutorial series for Godot 3.2 that included how to use a TileMap and TileSet. When I tried to use one in Godot 4.1, it was completely different and I had no idea what to do. Thanks for explaining it!

I've been testing godot 4 for a bit, so I new all this stuff, but I have to say I could have used this video when I started with Godot, or something similar back then. It comprises a lot of different things that are very useful for beginners, so this is a 5/5. Very much appreciated the effort, it's great seeing people making Godot tutorials!

Last time I tried game dev Godot was in some early 3.0 alpha I think. I saw Godot 4 release and some spark inside me lightend up and made me try gamedev again. Thank you for your tutorial man ❤❤

Just simply a great tutorial. Please make more godot game dev content in the future!

39:54 If you are having trouble getting your animations to travel between states in 4.1.3, adjust the call by added an additional parameter of false: state_machine.travel("Walk",false) state_machine.travel("Idle",false)

Excellent tutorial, just what I was looking for! Thank you.

Fantastic intro video, I'm a first timer and followed along no problem. Thanks! :D

Great tutorial! It helped a lot and was so much fun!

you worked 7 hours straight! Respect

Thank you for doing godot tutorials, I really hope you do more in the future.

Great video Chris!