Huge thanks again to NordPass Business for sponsoring this video. If you want a powerful password manager to conveniently and securely access your data from anywhere make sure to check them out. At nordpass.com/clearcode you can get a 3 month trial to check it out. Doing that will also support my channel and help me make more videos!

@manwhas

10 ай бұрын

wbt your pygame ce one thats on your github is it a course?if so pls send link so I can buy it or is it an unreleased vid?

@amanterobot

10 ай бұрын

Hi.... sorry for going off topic but as this video is the most recent there are more chances you may read it. Just wanted to ask about pygame tutorial vodeo. Can we still refer to it but using pygame community edition? And are there changes we should be aware about?

@firnyx

9 ай бұрын

@@amanterobot As far as I know pygame ce is mostly the same as pygame for now so his tutorials should still work with it I think

@PunCala

8 ай бұрын

Fantastic guide, probably the best guide there is, and what a perfect timing! Keep making these, you are doing *Godot's work*

@1neminutebonk3rs3

6 ай бұрын

you are a brilliant teacher. I have never watched any tutorial for more than 10 mins at a time and was planning to do the same with your video but I am at 53 min mark and I don't know If i want to stop or not. I really really like your work. Kudos man. Great work

As a long-time unity dev, this recent per-install unity fiasco finally made me start familiarizing myself with Godot, which has apparently gotten a lot beefier in the past year. after seeing how Blender, being free and open source, went from garbage to galaxy tier animation and modeling software, I believe in open source and think it's smart to bet on a FOSS game engine like Godot, which can only improve over time, as opposed to some corporate products, which can slowly degrade (like Unity.)

@Hilipinapixili

8 ай бұрын

I'm on the same boat as you. More than 5 years developing in Unity, currently looking around for alternatives after recent events. I mainly work on 2D so so far Godot looks promising, though I also plan on doing some crash courses in Unreal to leave the door open just in case my situation changes in the future.

@westingtyler2

8 ай бұрын

yeah, it seems Godot is pretty legit now for 3D, and is super refined for 2D. but yeah it's a good idea to have a wide skillset. one thing i've noticed is that getting up and running in Godot is super fast, covering a decade of Unity time. i think it's because now my brain thinks like a programmer and knows what features to crash course on faster. the true value of all that time with unity was that skill "programming" and not just in a single language, but the brain shape to think about it fast. and that transfers for sure. @@Hilipinapixili

@NervousNoodles

8 ай бұрын

The added attention from devs to Godot can only result in more people using the engine and more people wanting to contribute to it, and in turn resulting into a better product.

@ArmoredGameDev

8 ай бұрын

same@@Hilipinapixili

@rizwanzaman1793

8 ай бұрын

​@@Hilipinapixili I primarily do animation stuff in Unreal; Unreal being real time in 3D has helped me a lot - its very intensive though Where should I start if I want to learn 2D development?

A lot of videos I’ve watched so far have always said “be wary of tutorial hell” but this? This right here? Tutorial Heaven, bro. I’m learning so much, thank you for uploading this.

@cweasegaming2692

Ай бұрын

It's a valid thing to think about. I used this tutorial to learn godot and then stopped using "step by step" tutorials. This video in full is exactly the kind of thing you'd want to use to learn the engine. After that, figure things out as you go :)

@mkaks22gamerserise16

7 күн бұрын

bro this video is really different from tutorial hell

welcome unity refugees

@alexmcd378

Ай бұрын

Actually, I'm here because GMS doesn't have a Linux client. But yeah, unity removed itself as an option

@hafizhasan3668

Ай бұрын

You had to call me out ?

@FlamingMelon

Ай бұрын

Come on man

@GuyMakeGame

Ай бұрын

Hell yeah brother

@mkaks22gamerserise16

3 күн бұрын

i want to be unity dev in starting but after some time i not even start unity introduce new polices which make be to unreal but it was not able to run at 30 fps in my laptop so in jion godot

4:53:30 They've changed where some of the particle customization options are in the menu. Emission shape is under the spawn Gravity is under the accelerations menu Scale is under display

@taiseicee3656

5 ай бұрын

5:03:00 Direction, Spread, Initial Velocity Min, Initial Velocity Max have all been relocated to Spawn/Velocity/

@sebastiancontreras1559

5 ай бұрын

Thank you! I just got to this section yesterday and was very confused, or atleast more confused then I usually am. I just realized I have to go back and double down on learning the basics of python instead of trying to brute force my brain to know it.

@nota10Xdev

5 ай бұрын

Thank you so much. I don't get why they had to move everything around that much..

@dragoniscoming

5 ай бұрын

Thanks 🙂

@WingKeiEmmanuel

4 ай бұрын

Thank you very much, you have saved my life!

I'm a professional Unity dev of ten years who's hopping engines for Obvious Reasons. I couldn't have asked for a clearer, more comprehensive beginner's guide to Godot than this. Bravo, and thank you.

@MTLGSE

5 ай бұрын

How has the switch been ? It's cool to see the pros watch the same videos as us peasants lol.

It's rare for someone to be able to ride the line between detailed info and beginner-friendly info so well. You certainly have a talent for teaching. Thank you!

@ClearCode

8 ай бұрын

glad it's helping and thank you so much for the support :)

@nyscersul42

8 ай бұрын

Agreed, he did very well.

@vaibhavkrkm

7 ай бұрын

yes exactly!

@3aresnik

4 ай бұрын

Exactly!

Woaw. I've been coding for over 15 years professionally. During this period I've tried creating games multiple times, on and off. Unity being my engine if choice, just because the big community and abundance of guides and learning material. But because of recent events i downloaded Godot for my next dabble in making games. So, for a professional developer that is interested in making games on my free time, I am mighty impressed with your teaching method and skill. This content is good, not only for learning Godot, but for learning game development over all. You explain how to use "X" in the engine, the reason why "X" is important in the making of games in general AND also the logical and mechanical reasons behind "X"! I'am really impressed.

I'm 2 hours in and honestly Godot feels way more intuitive and beginner friendly compared to Unity. I'm a complete beginner and started learning Unity, got frustrated quite early on. Then the Unity fiasco started and I found this amazing thing, and I love it!

@azumashinobi1559

8 ай бұрын

Similar story for me. Everyone said unity was THE super easy to learn program and now I feel gaslit lmao. Like it's not impossible to learn obviously but it's not exactly intuitive all the time

@moldman5694

8 ай бұрын

@@azumashinobi1559 It's definitely harder than many make it out to be, especially since most tutorials don't actually explain the inner mechanics of unity but rather go "do this, then do this". And the fact there's often like 5 different systems in Unity that can be used to achieve the same thing, half of which are planned to be deprecated, certainly doesn't help a lot of the time

@azumashinobi1559

8 ай бұрын

@@moldman5694 right I hated the "do this, then do this" style tutorials so much. I like to have a fundamental understanding of what's actually happening and what my options are as opposed to memorizing instructions

@katakuri774

8 ай бұрын

​@@azumashinobi1559 did you find this tutorial to be better in that regard?

@1stflower834

8 ай бұрын

this happened to me with godot, sadly

bro really came back after 3 months with an 11 hour long video 👏🏼 just wanna say thanks because i’ve been following along all your pygame vids and they’ve taught me a lot.

@ClearCode

11 ай бұрын

It's actually 14 hours, KZread stopped me at 12 hours so there's a link to a part 2 at the end :P

@jayroi1814

11 ай бұрын

@@ClearCode lmao nice

@donaragorn

11 ай бұрын

​@@ClearCodemaybe should've split the video equally, cause the 11:3 length ratio of the two parts is a bit weird. Also why is the second part unlisted?

@Criticalthinking_

11 ай бұрын

@@donaragorn this is like complaining about the plate being the wrong color when u get a free meal.

@donaragorn

11 ай бұрын

@@Criticalthinking_ I'm not complaining, I'm simply asking. Sorry if my tone came off as complaining.

Fantastically clear and wonderfully paced. I can’t believe I watched a KZread video as long as the LOTR trilogy and never got bored.

@ClearCode

10 ай бұрын

Thank you so much! If it helps, I also never thought that I would become the guy who makes LOTR trilogy sized tutorials :)

@daygenandrews1321

9 ай бұрын

​@ClearCode I'm glad it was you, thanks for this resource

@pmurph1

9 ай бұрын

@@ClearCode Extended Edition length. Think I'm just finishing The Two Towers or thereabouts. Thanks for this, haven't touched anything since GameMaker Studio before GMS2 came out so this is really helping.

I could cry, and I might cry by the end of this series; I've only finished the first video and I feel like I've finally found the teacher and tutorial that will slingshot me out of this excruciating hell of years and years of trying to understand how any of this works. I'm so sick and tired of bouncing from game engine to game engine, tutorial to tutorial, bashing my head against a wall trying to learn a language that I can understand, and above all else, trying to follow "crash course" videos that go a thousand miles an hour without actually teaching me anything; just mindlessly copying what they are doing and hoping it sticks, even though they didn't tell me what any of it actually does, or how they even got the information in the first place. I don't know what kind of inhuman monster can learn from something like that, but it isn't me. You are an excellent and wonderful teacher. I went from having one of, if not the most shittiest defeating weeks of my entire life, to feeling like there's hope again to do something I've wanted to for 30 years now. My sincerest thank you for this incredible work! I will follow it till the end; I've already learned so much from this past hour or so than I have ever with any other tutorial.

@trashstar4704

7 ай бұрын

dude i felt exactly the same i haven't watched this yet but a glowing review like this from somebody in a similar situation makes me hopeful

@gfsg5440

6 ай бұрын

this gotta be the realest thing ive ever seen

@themushroomherders

5 ай бұрын

While this may be very true - the bit about learning how to problem solve. I feel like the biggest issue not talked about in development is the historical reasons for the functionalities of these engines. Why ‘this function’ is called here for ‘this reason’ or ‘that reason’. I jumped into Godot thinking I would have to learn how to hard code everything from scratch and learned that there are built in native functions and methods to all this stuff that were developed for the purpose of not needing to hard code everything. This is my first game engine/real programming environment to really ever work with, and I think for a beginner it can become very daunting to think how do I get ‘this’ to do ‘that’ when there is a seemingly infinite number of feasible ways to accomplish that problem. While, yes, there are an endless amount of ways to accomplish a task, there are a lot of native tools that allow for these problems to be accomplished a lot more efficiently and seamlessly that we’re created for the purpose of nullifying a lot of these inefficient ways, that we’re developed over many years within the game development industry. I feel like I’m not learning a coding language, but I’m learning the slang variant of the logic involved. I think this is the most difficult part about learning programming in Godot, again, my first gaming engine. But, somehow, honestly, I feel so safe working in Godot. I don’t know if it’s the programming environment, or GDscripts evolution from Python, but it feels still so intuitive. That being said I would love a better resource to understand the syntax behind all these “magic” methods and in-built functions, something that I could apply to all coding languages, and I am so thankful for this tutorial/teacher’s guidance. I feel like I’m really learning the fundamentals of the logic behind coordinating communication of different nodes within the engine’s environemnt. I am approximately 2/3rd of the way through this video and I feel like I can begin to solve my own problems and guide myself to solve them. Happy programming to everyone! 🫠☕️🕉️

@kjbaran

3 ай бұрын

@@themushroomherders someone who understands the difference between cause and effect, remarkable.

@gabbeeto

3 ай бұрын

@@themushroomherders sometimes I wonder why he's done few things in such ways. So I tried to do it in another way that it is shown in here and I learned why he's done in that way because of that. that happened with me in the signal part for example when he used signals to let the level know when the player should shoot.. I thought that was dumb because now we rely on code on the level and if I want to change to another scene I'm going to have to do the same again and that's not good so I haven't used the signal and try to do everything inside the player(the lazer is separated from the player in another scene but didn't signal the level). and if you are rebellious and you try to do it in more than one way, you learn so much more I think

@3:00:08 for anyone doing the Laser testing with the remote view, just a note of a change in Godot 4.1. After the initial shot the names will appear by the node type name so "@Area2D@x" instead of "@Laser@x", this was a change to how "add_child()" functions. To have it display the node's name instead of the node type's name use this instead "add_child(laser,true)" and instead of showing as "@Area2D@x" it will show as "Laserx"

@kelvinm560

7 ай бұрын

However, you get a performance hit. From the docs "This operation is very slow. As such, it is recommended leaving this to false, which assigns a dummy name featuring @ in both situations."

@byucknahthered3914

7 ай бұрын

@@kelvinm560 right, you wouldn't leave it enabled when releasing a game but for troubleshooting/bugfixing it's handy.

@ayushsidam289

6 ай бұрын

Thank you very much bro. 🙂🙏🏻

@guy3480

Ай бұрын

you just saved me from so many google searches THANK YOU

@byucknahthered3914

Ай бұрын

@@guy3480 ah, you are most welcome :)

I was in the middle of learning Unity when they made their announcement. I'm glad there's already a Godot community to help me make the switch.

@pouyanrezvani3314

8 ай бұрын

Yeah. Same here

@1wntv

8 ай бұрын

lol same here

@AndyRosaDesign

8 ай бұрын

I worked with Unity for 4 years before the announcement.. from now on only Open Source software.. and I bet after this all mess the Godot Community will grow exponentially and the engine will improve to Unity level and beyond

@rohitchaoji

8 ай бұрын

I first started learning Godot over a year ago. Or well, I tried. Now I'm actually low-key glad this happened because this means we'll have much better tutorials, documentation and help from more experienced game developers and designers, whereas I was relying on somewhat incomplete tutorials which would have some aspects of it broken due to different versions of the engine being used.

@user-qx7zu7xg6u

8 ай бұрын

Welcome

People like you really are really driving the pygame and even godot community forward

9:43:29 I wanna make a warning about this part, when it comes to changing the collision layers. Godot 4.1.1 here. Although changing the collision layers for the ItemContainer scene does change the collisions layers in the "crate.tscn" and "toilet.tscn" (as expected), these changes aren't being carried on for the crate nor the toilet in the Outside level. These two objects were placed in the Outside level BEFORE any change is made in the collision layers of ItemContainer.tscn. For reasons I don't yet understand, that toilet and that crate instances do not update automatically if they were placed BEFORE doing the changes in the "ItemContainer.tscn" collision layers. I don't know if this is how it should be, or if this is a Godot 4.1.1 thing, or if there is some custom option somewhere that determines this behavior. Saving the scenes after editing the layers doesn't "fix" it by itself. I had to do it manually for these objects placed before the layers were edited in the parent scene. EDIT: this is a known bug, there is a github entry about it I ran into that issue into another tutorial too. However, in this tutorial, no changes had to be made manually after changing ItemContainer. Anyway, I hope I could get the idea across. EDIT: changed some writing mistakes

@BigManBand22

7 ай бұрын

Thanks for posting this! Had this issue and couldn't figure it out

@emily11421

7 ай бұрын

Thank you! Ran into this issue.

@geo6232

7 ай бұрын

Big Help, thank you :)

@maksscratch

7 ай бұрын

god, i thought i was going insane... thx for posting!

@gasparmc

7 ай бұрын

@@maksscratch cool, ppl should go and like so this comment stays on top

A bit of a shortcut that removes some of the complexity for beginners for selecting a random marker for the lasers at ~ 3:06:00 instead of using randi() and the size of the array you can use the built in godot function for handling this: var selected_laser = laser_markers.pick_random() that being said I think if you are learning, understanding using modulo, randi(), and how you can use them with arrays is super important so it is still really good to show/practice it as shown in the video.

@Dipj01

2 ай бұрын

Thanks for this!

@rijden-nu

Ай бұрын

I wanted to post this as well. Note that generating a 32 bit random number and then dividing that over a number that we know is 2 bits (in this case) just to get the 2 bit modulo may also be slightly excessive and slow. Not that you would notice, but still.

Some more advices I think could be useful here (disclaimer: I'm only 2 hours into the video and downloaded the final version to check it out) 1. In your game, if you have a bigger screen you can see more, which can be unfair. It's easy to fix this by doing these steps (which will make your game scale if you increase the window size) 1. Project -> Project Settings 2. Turn on Advanced Settings (button on the top right) 3. Go to Display -> Window 4. Set the Stretch Mode to "canvas_items" 2. The things that mess with physics (moving, colliding etc) should be done inside the _physics_process, not _process. For this game it won't change that much, but it can generate some inconsistent physics for some more complex games. Things like timers, which depend on real time instead of physics frames, are usually better at _process. I will keep updating here with advice I can find, or if someone wants to reply with their own =).

@user-ou1qf7qo6b

10 ай бұрын

Legend! Thanks for that.

For anyone at 2:39:00 you can simply right click the gate node and select "save branch as scene". This will import it all into a new scene so you don't have to rebuild it

@rrropet

4 ай бұрын

Also you can copy and paste the nodes into the new scene, but I chose to rebuild it because it reinforces the steps in my memory 😊

What a phenomenal comprehensive tutorial. You've made learning Godot so easy! 🙌

What an amazing Introduction to Godot! It's also very nice that you show all the features directly in use in the game you're building. Given the quality of this Tutorial, this must have taken a long time. Thanks a lot!

@ClearCode

8 ай бұрын

Thank you so much! And yeah, it took forever :)

Amazing work! You actually made me get back to Godot, i tried to understand it many times! watched bad/outdated tutorials and kept feeling lost, the Godot Docs is massive and great but i felt overwhelmed, this video is just perfect for me!

@ClearCode

10 ай бұрын

Thank you so much!

@joeylantis22

6 ай бұрын

did you really just waste $50 dude

@Maxitanker

6 ай бұрын

​@@joeylantis22 Wasted? Dude, this is a best tutorial for Godot that I found, and it's FREE. If someone is able to donate some money for a good tutorial then why not?

@steve12622

5 ай бұрын

The Money is Well spent and deserved. This Video would be Well Wörth 50 bucks If He marketed it.

@synystervic5208

4 ай бұрын

​@@joeylantis22 just choose a good place and sleep buddy , nobody likes you.

OH MY GOD THANK YOU I wanted to learn Godot for sooo long but all the tutorials were shit or outdated. I have watched the complete 4 hours of your pygame tutorial (and even coded along) + the complete 2 hour python classes tutorial and you explain everything SO GOOD you are BY FAR the best coding channel (at least when it comes to explaining things) on youtube :)

@konjecture

11 ай бұрын

Have you made anything yourself after watching the Python tutorial?

@abdu11ahh

11 ай бұрын

@@konjecture lol Thats what i ask my self too im just following tutorials and tutorials and never made anything my self i guess Im not Creative

@Anceph

10 ай бұрын

@@abdu11ahh you can try to recreate simple games that you love like minecraft or google game ideas

For anyone using Godot 4.2, 7:33:26 you will get an error in the console while transitioning inside/outside or viceversa. Just create new method "change_scene" and call it with "call_deferred" like this: func _on_gate_player_entered_gate(_body: Variant) -> void: var tween = create_tween() tween.tween_property($Player, "speed", 0, 0.5) call_deferred("change_scene", "res://scenes/levels/inside.tscn") func change_scene(scene_path: String) -> void: get_tree().change_scene_to_file(scene_path) I don't know if it something Godot 4.2 specific, but now my errors are gone.

@kirillinski

5 ай бұрын

thank you this worked for me too

@victora8679

5 ай бұрын

That fixed it for me too. Thanks!

@sherifOneWay

5 ай бұрын

thanks so much dat fixed it but why this happen in 4.2 and what dose it mean 🥲🥲 ?!

@pablyco

5 ай бұрын

Also you can use: get_tree().change_scene_to_file.bind("YOUR SCENE PATH").call_deferred() or var outside_level: PackedScene = preload(""YOUR SCENE PATH") get_tree().change_scene_to_packed.bind(outside_level).call_deferred()

@ItsGrezzz

5 ай бұрын

@@sherifOneWay I could be mistaken as I'm a beginner here too (please correct me if so) - but my understanding is that call_deferred() ensures that when we try to change scenes it waits until the thread is empty (ie. it's finished processing everything that it was working on) before executing. If you read one of the error messages it gives a hint as to why this might be desirable: "Removing a CollisionObject node during a physics callback is not allowed and will cause undesired behavior." Essentially what's happening is that we decide that we want to change scenes while we're in the middle of processing the physics - this is because the trigger to change scenes is a collision between the player and the Area2D from the gate. When we change scenes we're basically just destroying the current scene, so all of the physics nodes that are currently being worked on disappear. I guess this could lead to certain physics interactions being missed or not completing whatever they're supposed to be doing. Adding call_deferred() just ensures that all the physics completes correctly before we destroy the scene and move on.

WAN Show Gang

@ClearCode

Ай бұрын

lol, I was watching the WAN show when they mentioned me :D

@geraldwheatly1824

27 күн бұрын

Good recommendation, luke

42:09 _ready() is run when a node's children have already had their _ready() functions called _enter_tree() is run when a node enters the node tree This was a really important clarification that took a while for me to understand as a Godot beginner. Thanks so much for this tutorial! 💕

@ClearCode

10 ай бұрын

there is also _init() :P

It's time to learn Godot because of Unity's new Fee policy. 🔥🔥🔥

I just finished the whole tutorial. As someone with debilitating ADHD (among other conditions) and someone with a dream of making my own games since 2004-2005, and who tried and failed miserably in 2012-2013, and again in 2017... I feel this is my time and thanks to you I'm closer than ever to finish my first game. This was a relief finishing this amazing tutorial where you explain everything necessary with kindness and patience. It's been a while since a completed a course or tutorial in this long format. I did take some breaks because I have some real life responsabilities, worries among other personal stuff going on. But yeah, what a relief! I couldn't thank you enough that you uploaded this for free. As someone living in Venezuela, where the economy and everything is in shambles, and finding access to international payment methods is restrictive, this is life-saving. For this, I wish you the best in life. Thanks again, this was a worthwhile journey! Now time to make some games!

7:27:00 just leaving this for anyone who accidentally does it: you can NOT do the @export var scene thing for both outside and inside. If you try godot (4.2.1 atm) will break and you'll even get a dependency error if you try to restart it (and wont be able to open your scene at all). You can fix this by either in the "Fix Dependency" choose another scene (like level) or in your gd script remove the @export and switch it back to explicit. Note: it's not a problem it cant find the file, it's more of a conflict. Even before that error you'll see your transition from scenes break. In the video you'll notice that the @export is only done for the inside scene, hence why the problem doesnt appear. I'm assuming this is because dragging the scene over somehow creates some loop between the two scenes and just breaks. This will break if you preload manually too. ---- This wont break the game but you might notice there's a bunch of "errors" in the debugger when running (errors, not warnings). These are caused by the transition happening during signal processing rather then "right after" which godot doesn't like (since it may or may not interrupt other things its trying to do). To fix this simply move the change_scene_to_packed code to it's own function (eg. change_level) and then call that function in the signal handler via call_deferred("change_level")

Who else is here after the fallout from Unity pricing changes? All that aside- what a FANTASTIC tutorial from Clear Code that is easy and fun to follow. I'm going full speed ahead into Godot now and this is exactly the starting point I needed. Can't believe this video is free. Thank you sir!

@hiyosinth

8 ай бұрын

exactly, i love unity, but not to the point of going potentially bankrupt good luck with godot

@shinozakinn576

8 ай бұрын

X2

@Vivek-qc8qo

4 ай бұрын

Have you completed this tutorial by now 😂 ? I bet you didn't, this is hella boring and it's better to build an actual game and learning through instead of Playing with assets

@urdadtai

3 ай бұрын

@@Vivek-qc8qo ur the typa guy to fall into tutorial hell huh?

I'm a complete and total noob here. I'm just starting to learn everything. My goal is completely solo game development from the ground up. This video, while a daunting task in itself, has made leaps of bounds of progress happen almost overnight. This is such a great basic foundation of knowledge in godot. You introduced new topics at the perfect times, and you explained everything beautiful. Thank you so much for the time and dedication I know this tutorial took!

For anyone struggling with the crate section, here's 2 possible solutions on why it may be breaking 1. For many people including myself, when they update the collision masks of the item container it doesn't actually apply the changes to the inherited scenes. It registers, but it doesn't apply. It applies visually in the editor, but it doesn't apply technically. To fix this, simply delete the old scenes and relink them to the outside scene, and you should be fine. 2. If you do that but then the objects stop being added to the tree, make sure to check the group for the item container. I don't know what went wrong, but Godot at some point removed the group for my item container, causing it to break with no errors. I hope somebody finds this helpful, and if you do, I wish you good luck on your journey

@azrielsatan8693

5 ай бұрын

Thank you, solution 1 worked for me.

@MegaByteKaos

5 ай бұрын

Solution 1 worked for me as well.

@thepresidentgaming404

5 ай бұрын

Thank you very much ,1st worked fine

@christopherkerr6187

5 ай бұрын

THANK YOU! Option 1 fixed my issue. I went through each item related section 3x before stumbling upon this advice. Cheers!

@Aditya_Kumar_12_pass

4 ай бұрын

Thanks!! 1 worked perfectly fine

I think I started this tutorial 3 weeks ago. Spent a little time each day working through it. First I'd like to thank @ClearCode for making this. It is well done and goes into just the right amount of depth for each topic. And to everyone who comes across this video. Take your time. There is no rush to try and finish this video (and the second part) in one or two sittings. There was plenty of sessions where I made almost no progress in the tutorial. Rather I found a bug and spent all my time trying to find what I did wrong. That's part of the process! Good luck everyone and keep on coding!

@saulmaldonado4607

8 ай бұрын

where can i find the second part?

@SunnyCress

8 ай бұрын

@@saulmaldonado4607in the description

@SunnyCress

8 ай бұрын

Did you encounter any issues with the signal player has entered gate? Mine seems to be an operand whereas his isnt

Unity's refugees coming through~

Actually we can ( .pick_random()) to pick randomly from an array instead of using ( randi % ...) in the selected_laser variable It is good to know both

@ClearCode

10 ай бұрын

ohhhhh thank you!

@AgentChick

10 ай бұрын

This is actually huge to know, lol.

@Shmaisanimostafa

10 ай бұрын

@@AgentChick yes, especially for non-programmers, where they turn off when they see the modulo

@Maltosier

4 ай бұрын

i think the funny part is that when he was typing randi, pick random briefly appeared in the suggestions dropdown. It made me go "wait what?" so i tried it and it def did the same thing.

Don't think Godot is as simple (or the documentation is) as eloquent and articulate this introduction is. Hands down the best (probably not as much discovered) introduction for even those who know next to nothing about game programming. I am two hours in and curious how animations work like spinning wheels of a car or a walking character or exploding brick and such. Thank you.

I'm barely 50 minutes in but I can tell you I love how in depth you explain everything. I'm so thankful for people like you in this world.

AYYYYY Wassup my fellow Unity devs

6:15:00 Little tip: You can drag and drop the name of a property instead of manually typing it. So in this case, if you click and drag 'zoom' onto the script, it will give you "zoom" this is useful for properties with long/complicated names.

@ayushsidam289

4 ай бұрын

Wow!!! Thanks. 😀🙌

What an incredible tutorial! Rarely do I feel the video can justify having the word 'ultimate' in the title, but this tutorial was just that! I still have so much to learn but it's been really nice to have so much guidance during my first few steps in Godot. Thank you for all the time and effort into making this tutorial, and I'm looking forward to your future Godot uploads!

I don't comment very often but the sheer willpower and time to organize this information and compile it into a video must have taken ages. Well done and thank you! Let the well deserved views and subscribers continue to flow in.

One of the most thorough and well structured tutorials that I've ever watched ❤

@ClearCode

8 ай бұрын

Thank you so much

11:22:27 some explanation of that performance penalty: GPU runs multiple threads in parallel (32 for CUDA) on a single processing unit, and these threads are following the same instructions, but with their own memory (own variables). If one thread diverges due to "if" statement, the other threads have to wait until it finishes "if" block. In many cases conditions are perfectly fine, all depends if condition result will be the same between multiple threads at that point in time. Also problem with "current_a == 1.0" is that floats are an approximation, and almost in all cases you need inequality operator e.g. "current_a >= 0.9999". Godot manual have some more info about floats in shading language section.

@ClearCode

10 ай бұрын

thank you, that's really interesting :)

I'm 9:19:27 into the video I've spent at least a week and a half watching this. This introduction is truly amazing. While there are some minor errors and debugger errors due to some very minor changes to Godot since this video, I actually used those errors as a exersie myself to see if I could debug and fix them. And it works. I've really learned a lot I think if you want to get the most out of the video, is not to follow every value and item placement, but rather to make it your own and realize how everything interacts. Most importantly, if you get an error try to fix it yourself using your resources (comment section, Godot debugger, google, etc) and if all else fails go back in the video to see if you had everything down correctly In all though if you are knew and you want to have a basic mastery of the coding and node uses in Godot I highly recommend watching the whole thing. (Piece by piece to prevent burnout or forgetting some minor detail)

I'm truly blown away by this tutorial! It was very helpful, especially in seeing a working example of using signals in a medium sized project, and you explained the reasoning for each step super well. I get that this is meant as an introduction, so you did certain things in a contrived way for demonstration, but I wanted to call out: - 2:00:56 If your node has a collider, you should always make movement calculations in _physics_process(). Otherwise you might miss collisions, since _process() can be called multiple times per physics tick. However, until they finish adding built-in physics interpolation to Godot 4 (should be soon), it might make the game look less smooth. - 3:06:20 and 8:53:50 Arrays have a pick_random() method for convenience. - 6:02:00 In practice I would combine the Blinking and Explosion animations into one. - 6:36:42 This can crash the game if there is a "hit" property (not a method) on the body, so using has_method() is safer. - 6:38:28 Autostart should be checked. Then you don't need to start the timer inside _ready(). - 7:17:04 For light decals, you get a more natural result by changing the blend mode to "Add", which can be done in the Material settings. - 10:44:14 Alternatively to using groups and checking distance in code, I would create an Area2D for the explosion and use physics layers here.

@fvhaudsilhvdfs

5 ай бұрын

that pick_random() method is clutch

Amazing. The only downside of this tutorial is there isn't more of it. Thank you so much!

@felix_xb

3 ай бұрын

There is more of it actually... check the description

Please make more Godot tutorials like this! Your way of explaining shaders just blew my mind at how easy you made it to comprehend You just earned a new subscriber

Really helpful video. Currently almost 4 hours in at the part where we have to make the laser travel in the player's direction, and while doing the exercise I actually implemented it in a way I find a bit simpler, using some basic trigonometry. For the calculations, instead of finding the vector between the player position and the mouse position like you did, I just used the player rotation, like this: var dir = Vector2(cos($Player.rotation), sin($Player.rotation)) laser.rotation = (PI/2)+$Player.rotation laser.direction = dir

@lightsilver127

2 ай бұрын

Great tip!

As many other Unity devs at the moment, I was also motivated to finally take a closer look into Godot, but after some very confusing tutorials with ugly code styles, I was ready to put Godot back into my drawer. But after finishing the whole tutorial within 2 days, I kinda like Godot now and will definitely give it a try for a future project or game jam game. Looking forward to the second part of the tutorial and then playing around with some 3D tutorials afterwars. 😍

8:28:20 You can just write Color() and then right-click on "Color" and choose the Colorpicker to get a color-value. Very good and extreme detailed tutorial. Well done like always!

At 7:33:22 a note of caution. If you also change outside level scene to use exported PackedScene for loading, then Godot wouldn't be able to open these .tscn files due to circular imports, the transitions in game would also be broken. I fixed it for myself by opening tscn file with text editor, and removing PackedScene from ext_resource and from Area2D node. The workaround that I used is to create a custom Resource that holds PacketScene exports and a level manager singleton to handle transitions

@BigManBand22

7 ай бұрын

I just had this same problem. Thanks for posting this!

@BigManBand22

7 ай бұрын

Another solution is just using get_tree().change_scene_to_file("res://scenes/levels/inside.tscn") instead of change_scene_to_packed(scene_name). That seems to be working for me to get through the tutorial.

@DrFlorent

7 ай бұрын

Thanks a lot for your comment, I was stuck on this issue and didn't understand what caused it! For now I'll probably continue the tutorial with change_scene_to_file, just to make sure I don't break anything by trying to implement a workaround ^^'.

@FelisArmis

7 ай бұрын

Can you please provide an example of your solution?

@noctemcat_

7 ай бұрын

@@FelisArmis Haha, don't worry I really jumped a gun with it. Just don't use exported Packed scenes and continue tutorial. Later in the tutorial we created something similar, so I needed to scrap and change my solution anyway

luke's WAN show shout out got me here.

Thank you so much for this amazing 14 hours tutorial! Just wanted to mention that in your resources/graphics folder, the projectile images are missing. I just moved the projectiles folder from the full game to the resources/graphics folder. Thanks a lot again!

10:17:33 2:38:01 - Custom Signals (very important) 2:51:15 - Custom Scenes 08:08:46 - Autoload scripts 8:41:59 - Await 9:37:22 - Groups 11:01:00 - Script Timers

I'm an hour and half into this, can say I've never been more excited to finish a tutorial let alone an 11 hour one!

Just a small update in case somebody got confused as I did, if you are looking for the Emission Shape in the 'Emitting Particles' section, you can now find it under Spawn > Position > Emission Shape now :)

@issleepy6353

3 ай бұрын

Thank you!!

This super mega tutorial has the potential to spawn thousands of new Godot game developers. Very good pacing and very clear and thorough explanations. Great job!!!

This tutorial has made me realize just how powerful the node system, quick iteration, and simple code syntax is. The separation of concerns granted by the nodes and signals is how I would imagine modern software to be designed. Comparing to Unity, Godot feels like a system that has strong foundation with a clear goal and focus on quick iterations. Whereas, Unity feels like a bandage of features built on a house of cards that doesn't always behave as you would expect especially when interacting with each other. I could be wrong on my analysis so far, but this is the impression with about 3 hours into the course.

@stanley8006

7 ай бұрын

If you have gone through the full course, what are your thoughts? I have slowly enjoyed the months of Godot use, love the new features coming in.

@praveshkhanal

7 ай бұрын

@@stanley8006 After finishing the whole course, I created a 2d game for a jam and I think this is a complete engine with strong foundations. The only feature I missed from Unity was the ability to automatically generate Collision shapes from sprites, but that didn't slow me down too much. Again iterations were much faster on Godot than I am used to so I was able to get a lot more done for the Jam.

@Gupatik

3 ай бұрын

so eould you advice me to go with godot instead of unity, I see some ppl saying it's incomplete!!!

The first tutorial that is actually beginner friendly, and not skipping important stuff just because of "you will find out later".

I am following this through (4 hours in now). This has to be one of the best Godot tutorials on KZread. It does need you to have a basic coding understanding. Provided you have that, this is a no-nonsense well-paced guide where I'm picking up so much information. Absolutely brilliant. Thank you so much.

@hybs9473

10 ай бұрын

What if you have a background in web development? Does that work as basic coding understanding to be able to understand this tutorial?

@beepboop6199

10 ай бұрын

@@hybs9473 yes

@depressito

2 ай бұрын

@@hybs9473 this is probably too late, but it definitely helps a lot if you have a background in web dev. I didn't get a web dev job but I learnt web dev for 5 or 6 months and it helped me a lot

@depressito

2 ай бұрын

@@hybs9473 I was mainly focusing on html, css and javascript(when I stopped learning front-end web dev I was learning about react, typescript and tailwind) and even there are new things like signals, the video helps you understand pretty well. I think that you don't to learn much before starting this video. you can either do the first 3 weeks in cs50(week 2 should be the last week) or the foundations of the odin project, you can already follow the entire video.. you just need to know about Object/dictionaries, arrays, while/for loops, functions, variables. Most people recomend you to learn python because the syntax is similar before following this video but you can still follow if you know javascript..

The way you express information is very 'clear' and the value you're adding by these videos is invaluable

I just wanted to thank you. For now I'm 4hrs deep, and already learned a lot. I think, I never saw such good tutorial / classes / however we call it. Creazy good with a lot of knowledge. If I could, I would double upvote this. Cheers!

There is now (for SOME REASON) a huge demand for Godot tutorials, please keep making more!

@gasparmc

8 ай бұрын

oh "what could i be" lol

Man I can barely make my own video last 2 minutes my god. I'm 6 minutes in and this already looks like an amazing tutorial. The fact that this is free is amazing! (I'll update this comment based on how far I've gotten) 23 Minutes in, everything feels really clear, and I never feel like I have to catch up. Gonna take a break here. I also have an issue where I can't drag files into the FileSystem. (Problem solved, I can just open the folder in file explorer) 1h in and everything is at such a nice pace. I don't ever feel pressured, yet I feel so much more in control over the software now. I feel like this tutorial has a lot of potential! Also finally a good explanation of Nodes. Crazy how such a weird concept is finally so easy to comprehend. 1h 22m in, not much more. Was already familiar with DeltaTime, but this just reassured all my thoughts. Nice to see basically every concept being went through, and I'm not even a 10th of the way through. It's now 23 : 00 (11PM) so I'm gonna return to this tomorrow. 2h 10m in. Coming from a Scratch user (yes ... you can actually make proper games in that, you can check out Griffpatch if you want) I'm much more used to writing my own functions for physics and stuff, but these explanations make me feel more confident in these inbuilt one. Especially about "move_and_slide" with the "velocity" variable. 2h 38m: Timer and signals, this is something I think I was looking for. Absolutely crucial concepts and very nice to know. I will say the "$Timer.start()" function wasn't really made clear before the exercise, but after I viewed the solution, everything makes sense :) 3h 20m: Clones huh. This is not at all like Scratch's clones work ... so I'm just slightly confu-. Whatever so long as I can copy paste rewatch and chatgpt whatever I'm fine I think (I am definetly a professional)

I thought this was an hour and not 11 hours.. amazing level of detail!!! I actually came here because another course I am doing (my frist one for Godot) started off really easy but it's zipping through increasingly advanced material and I am not keeping up with the leraning, just typing what I see and absorbing some of it, sometimes. I'm nearly 2 hours into this one and I feel like every, single step is explained in detail, which is what I need. THANK YOU!!!! I thought I was going to blitz a 1hr course since I've been (kind of) keeping up with another course already but I am learning something the whole way. Also THANK YOU SO MUCH for providing the files at every stage!!! If I miss something, I am not punished for it, nor do I have to dig back through practically frame-by-frame to find what I missed that is preventing my progress in the future. Absolutley so thankful for this.

This comment section has been helping out quite a lot. The more recent comments are identifying the issues that may arise from following the tutorial and also telling how they can be fixed. And if you're getting any problems from tutorial then it may not be the video's or your fault but it could be because the engine has gotten a few updates since this video was last uploaded and the methods presented in the video may be outdated. Really appreciate the comments as they're very helpful.

1 million views !! congratz !! i'm almost done with your tutorial (9 hours into it). So far you've explained things really well. I was able to understand everything you've said so far, i only had to change a few things because of Godot 4.2 but i'm still surprised by the quality of your tutorial and the length of it. Ty very much for it and helping godot grow :)

Due to the recent... Unity fiasco, I decided to switch to Godot and this video is a huge help with that. Thank you.

this is by far the best intro to godot 4 tutorial on youtube. You did a fantastic job. I've been a bit overwhelmed getting into godot but your learning style, speech, and excercises have greatly helped me. Thank you so much!

I havent even seen 5 minutes yet, but thank you so much for making this. 11 hours is nutty dude.

I'm watching this video for 5 days now, and it is probably the most comprehensive godot guide I saw on youtube. It covers every fundamental of the engine. Great video, thanks for sharing knowledge with us. I will definitely keep checking for more videos from you.

The sheer size of this video is impressive, massive props for the dedication to make this! I'll be watching this over the next week or so, and I'm sure I'll learn tens of new things I never knew about the Godot engine. This is the first video I'll be watching from your channel, but I'm sure it won't be the last!

This is such a great tutorial. Your pace and focus on details that matter is absolutely excellent! I cannot thank you enough.

I'm 3 hours in and already I feel the need to give you some support. Clear, consise and the order in which you go through things is fantastic.

Couldn't have come out with this at a better time. Gonna be going through this course over the weekend. Thanks!

Of all of the “ultimate” introductions to most things on KZread, this meets & exceeds expectations. What an incredible tutorial by an excellent instructor.

This is the best beginner tutorial video I've found so far, and I've gone through quite a few. The exercises are great to encourage me to practice and after the first couple of prompts I actually found myself pausing the video before you explain how to do something, just to see if I can do it myself. Thank you so much!

One of the best tutorials out there, not just in this topic but in general as far as teaching anything goes. Clear, to the point, simple sequences, enough but not too much repetition and most importantly some exercises embedded in the material. This kind of stuff will literally empower people to be employed, be artistic and just generally have fun. Thank you.

Thank you always for all the pieces of art you have uploaded! Got your Python course some weeks ago and all of your explanations are extremly easy to understand :D

Thanks for this! You are essential to my python programming and game dev progression. After finding your videos I've since found a passion that was since lost when I was young. I never thought I could get in to game dev and programming because I hated math and anything thing that looked like it but it wasn't as bad as I thought, then you came along and now I'm having tons of ideas for goals and projects that I want to do for myself

7:27:00 for the constant "unused paramater" warnings, those can be disabled in Project / Project Settings / (enable "advanced" in top right) / Debug category / GDScript (in this case "unused parameter"). In addition different types of other errors, that are normally warnings can be converted to errors, such as narrowing conversion or unsafe casts.

I'm only three hours into the video so far but I am BLOWN AWAY by how good of an explanation this is. I'm new to Godot but I do have some minor math and programming background and I love love LOVE how you handle each new topic! I tend to prefer getting a deep understanding of everything and you lay the guide out in such a way that just makes sense for someone who's just diving in - starting with simple basics that you'd think of first before slowly introducing ways of doing things that are "better" for reasons that you lay out in simple, well defined ways! And the progression of it all makes sense for someone making a game too - right before I'd gotten to the "code to instantiate lasers" part I was thinking that that would need to happen, and now I'm on that section! It's so good and I'm looking forward to finishing the whole video as well as actually getting in and making something myself.

Excellent video. Super clear, not rushed, but not drawn out. Thank you 🙏

This is an absolutely fantastic tutorial. Even beginners are taken along by your great and detailed explanations. You go over every important point that might raise questions. Thank you for your effort and your great video.

I have absolutely no experience in video game development or coding and the latter has always intimidated me to no end. This video is so well put together and not only information dense but so succinctly spoken that you've taken all of my apprehension and turned it to excitement. I have a funny feeling that you've just sent me down a long path. Or at least helped me to take the first steps. Thank you!

im using this tutorial but writing in c# (i came from unity, still a beginner overall) and its absolutely amazing tutorial. its well written, no stops(like "uhh uh") always continuing and explains well whats happening and what it does. its perfect thank you.

Hi Clear Code, I am really appreciate the tutorials you make. I started code in pygame a year ago because your videos not only teach code but also explain the ideas behind it. This makes me truly understand programming in a desginning level and I made few games using pygame. Now I started using Godot because I wanted to create a more complex game and I feel python's proformance is not good enough. But I struggled to learn godot because most tutorials didnt explain things clearly as you did. Thanks for the programming videos you made over the years. Gaming programming now has became the most important passion to me and it was your videos that overcame difficulties on the way. Love!

Man… I fell out of programming years ago. I really enjoyed both game development and your content back in the day. Just stumbled across this video on my page, and I’m wondering if this is a sign I should get back into it? Either way, thank you all that you’ve done for the community! Your impact has meant a lot.

@jvsvogler

11 ай бұрын

Do it!

@dundy96

11 ай бұрын

Do it!

@UNKNOWNS303

11 ай бұрын

Do it!

@naminex4443

11 ай бұрын

Do it!

@hashtagornah

11 ай бұрын

Do it!

One of the most useful and comprehensive Godot tutorials I've followed through. It definitely helped me understand the engine and a good workflow more than most other tutorials that leave out some important details about WHY something is being done.

Amazing tutorial! You are a great teacher! 2 hours in and I'm absorbed in Godot. Thank you for creating this - I'm excited to dive deeper into game dev with Godot.

This is an incredibly well made course. Thanks so much for all the effort that went into it!

Incredible tutorial man. Thanks for giving me the opportUNITY to switch!

From the very beginning, I could see what a great teacher you are. I'm only just over an hour into the video now(it has taken me days, lol) but I wanted you to know how much I appreciate you!

Very informative and patient with explaining and not quickly jumping from one thing to the next. You're a legend for releasing this.

This video is pure gold for Godot newbies or others (like me) who started with Godot 3 and now switch to Godot 4. A thousand thanks for this ! One happy new subscriber.

This is one of the most comprehensive introductions to Godot I’ve ever seen 🤩 Keep them coming! 💪

The fact that you pause for people to try and do stuff themselves is a gamechanger, i followed some other tutorials but they werent as proficient at actually teaching how to use the info you get. This one hits the spot!

I love this tutorial so much I can’t stop watching lol. The camera zoom with a tween was awesome. I will start this project today. Thanks for this.

godot looking really fine latelly.

2:38:58 I was sure there is a better way to go about rebuilding Gate object manually and i'm glad there is. You can select all the elements related to Gate object, open context menu and choose "Save branch as scene". Seemed to work for me, but not sure if there are edge cases if scripts are involved. Also doing it manually might be a good practice if you are starting out.

@naminex4443

7 ай бұрын

ty m8!