The ultimate introduction to Godot 4

This video is sponsored by NordPass Business: An amazing password manager that allows you to securely store and access unlimited passwords, including wifi credentials and credit card information. You can use it for yourself or for entire teams or share your own passwords easily.
You can get a 3 month trial at:
nordpass.com/clearcode/
A complete guide to Godot 4! This video will cover every aspect of the gaming engine and will teach you all the basics.
Second part: • The ultimate introduct...
Find/support me on other channels
Patreon - / clearcode
Twitter - / clear_coder
Discord - / discord
Code: github.com/clear-code-project...
Project stages: drive.google.com/drive/folder...
Timestamps:
00:00:00 - Intro
00:01:11 - Sponsor NordPass Business
00:02:41 - What is Godot
00:10:02 - Scenes and Nodes
00:36:33 - Working with code
00:57:56 - More on code
01:11:09 - Delta
01:21:34 - Getting input
01:38:38 - More on nodes
01:48:55 - Physics!
02:15:23 - Signals (+Area)
02:38:01 - Creating custom signals
02:51:11 - Creating custom scenes
03:21:07 - RigidBody2D
03:45:54 - Using a camera
03:51:37 - Tilemaps
04:28:11 - Tilemaps and physics
04:49:41 - Emitting particles
05:09:08 - Lights
05:35:54 - Animations
06:07:42 - Tweens
06:29:21 - Connecting the laser to the level
06:39:52 - Inheritance
07:04:25 - Creating the inside level
07:27:09 - Adding a level transition
07:33:26 - Getting started with user interfaces
08:02:31 - Adding the health bar to the UI
08:08:46 - Making the UI interactive
08:25:52 - Adding color to the UI
08:36:45 - Prettier transitions
08:46:16 - Creating items
09:06:15 - SetGet
09:23:52 - Creating crates
09:55:54 - Expanding the inside level
10:17:31 - Creating the scout
10:37:55 - Creating the grenade
10:49:22 - Scout & Health
10:57:43 - Player & Health
11:06:25 - Shaders
#godot #godot4

[@ClearCode]

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]

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]

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]

@@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]

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

[@1neminutebonk3rs3]

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

[@westingtyler2]

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]

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]

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]

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]

same@@Hilipinapixili

[@rizwanzaman1793]

​@@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?

[@OmarLeKing]

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]

bro this video is really different from tutorial hell

[@CopperAirplane]

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:03:00 Direction, Spread, Initial Velocity Min, Initial Velocity Max have all been relocated to Spawn/Velocity/

[@sebastiancontreras1559]

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]

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

[@dragoniscoming]

Thanks 🙂

[@WingKeiEmmanuel]

Thank you very much, you have saved my life!

[@snakery18]

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]

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

[@nyscersul42]

Agreed, he did very well.

[@vaibhavkrkm]

yes exactly!

[@3aresnik]

Exactly!

[@garethwilcock7130]

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]

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

[@MSMPokeGamer]

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

[@PowerHausMusic]

omg hey MPG!

[@mianokamuru6333]

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]

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

[@ouijinn]

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]

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]

this gotta be the realest thing ive ever seen

[@themushroomherders]

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]

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

[@gabbeeto]

@@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

[@JoshuaBarratt]

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

[@ClearCode]

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

[@daygenandrews1321]

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

[@pmurph1]

@@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.

[@emperor8716]

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]

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

[@jayroi1814]

@@ClearCode lmao nice

[@donaragorn]

​@@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_]

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

[@donaragorn]

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

[@dCoreGaming]

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.

[@vincernio]

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]

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.

[@vantatree2062]

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

[@SporkSlayer]

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]

Yeah. Same here

[@1wntv]

lol same here

[@AndyRosaDesign]

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]

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]

Welcome

[@byucknahthered3914]

@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]

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]

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

[@ayushsidam289]

Thank you very much bro. 🙂🙏🏻

[@guy3480]

you just saved me from so many google searches THANK YOU

[@byucknahthered3914]

@@guy3480 ah, you are most welcome :)

[@gasparmc]

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]

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

[@emily11421]

Thank you! Ran into this issue.

[@geo6232]

Big Help, thank you :)

[@maksscratch]

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

[@gasparmc]

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

[@davidwhitten179]

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!

[@thej3683]

Now that you’re way more experienced than I am, how solo developing going?

[@khaledalshammari857]

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]

Thank you so much!

[@joeylantis22]

did you really just waste $50 dude

[@Maxitanker]

​@@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]

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

[@synystervic5208]

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

[@gallow_]

For anyone around 4:46:10 on the physics layers tilemap section, there's a little eye dropper tool beside paint that allows you to click on tiles without overwriting any collision data you've already drawn

[@zongopbongo]

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]

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 😊

[@oliverblaser]

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]

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

[@Apf3l]

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]

Have you made anything yourself after watching the Python tutorial?

[@abdu11ahh]

@@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]

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

[@weirdg]

WAN Show Gang

[@ClearCode]

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

[@geraldwheatly1824]

Good recommendation, luke

[@ul1xes]

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]

thank you this worked for me too

[@victora8679]

That fixed it for me too. Thanks!

[@sherifOneWay]

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

[@pablyco]

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]

@@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.

[@zemeio1184]

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]

Legend! Thanks for that.

[@ignskeletons]

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!

[@ClassicSama]

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

[@shinozakinn576]

X2

[@Vivek-qc8qo]

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]

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

[@Skovos]

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.

[@tomarik]

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]

where can i find the second part?

[@SunnyCress]

@@saulmaldonado4607in the description

[@SunnyCress]

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

[@anarqee]

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]

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]

@@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]

@@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]

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

[@1stflower834]

this happened to me with godot, sadly

[@manybuckets969]

AYYYYY Wassup my fellow Unity devs

[@Gatitasecsii]

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.

[@flyntwick]

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

[@Shmaisanimostafa]

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]

ohhhhh thank you!

[@AgentChick]

This is actually huge to know, lol.

[@Shmaisanimostafa]

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

[@Maltosier]

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.

[@mellowminx]

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]

there is also _init() :P

[@itsasecrettoeverybody]

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.

[@BernhardHofmann]

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

[@Koden]

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]

Wow!!! Thanks. 😀🙌

[@quantum_hg3299]

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

[@tziganeofwales]

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.

[@RAGHAV4882]

luke's WAN show shout out got me here.

[@qooldeluxx]

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!

[@IsometricPolygon]

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

[@felix_xb]

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")

[@Adam-dd9lo]

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]

that pick_random() method is clutch

[@AstroTechGuy]

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!

[@denisc555]

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!

[@AuthorJoeyBissonOfficial]

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

[@Unskilledcrab]

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

[@ClearCode]

Thank you so much

[@JustSuds]

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

[@kozmizm]

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!

[@madmulk9]

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.

[@archerwayne4643]

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!

[@YuutoGaming]

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

[@PunCala]

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

[@gasparmc]

oh "what could i be" lol

[@matc83]

Really glad to see all the great tutorials for Godot coming out! Keep up the good work!

[@geeves21312]

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.

[@Marco-L]

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.

[@benfree_man]

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

[@buckamoona]

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!

[@widearchshark3981]

I am following this through (4 hours in now). This has to be one of the best Godot tutorials on KZbin. 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]

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

[@beepboop6199]

@@hybs9473 yes

[@depressito]

@@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]

@@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..

[@CharlExMachina]

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

[@samychlaus]

Thanks a lot for this video and for all the time taken to made this ! I've reached the end of the first video, time to watch the second part.

[@jlogicgaming2825]

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.

[@cat_meow2]

Unity's refugees coming through~

[@squarerootof2]

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!!!

[@Afreshio]

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!

[@cornelbejan1293]

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!

[@subarunatsuki1902]

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

[@savagekid94]

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

[@MH-lr6ue]

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.

[@Jhonbxl]

Thanks all this lengthy work. It's clear, full of good details and advices related to good practice, has a nice rythm, is easy to grasp. Top notch teaching material.

[@EpicGamerXander]

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!

[@noname85808]

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

[@juanpabloloyola5119]

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!

[@HxTrEmEcHaOs]

One of the things I really appreciate in this tutorial is that you demonstrate mistakes and how to fix them, and even explain why they don't work. This is top notch.

[@shaeffer007]

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

[@felix_xb]

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

[@user-de7hr3hf5v]

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!

[@mohsinhijazee2008]

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.

[@degariuslozak2169]

watching this alongside doing the Godot tutorials helps so much

[@Aaron_Esh]

Your lessons are so good. One of the best I've ever seen on KZbin

[@jakes-dev1337]

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

[@user-cf6rq4xw4z]

I've never seen someone who can explain everything so detailed and reasonable at the same time in any Tutorial. +Rep

[@rohitchaoji]

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.

[@captainmink1320]

Amazing tutorial ... beginner friendly and perfectly paced. I am only 2 hours in and enjoying it tremendously.

[@ClearCode]

Thank you so much!

[@siegfriedabrams4918]

Pacing in this guide is just immaculate, super comfortable to follow. Great job!

[@177silas]

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!

[@juliangutierrez3734]

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

[@legowyn24]

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]

Thank you, solution 1 worked for me.

[@MegaByteKaos]

Solution 1 worked for me as well.

[@thepresidentgaming404]

Thank you very much ,1st worked fine

[@christopherkerr6187]

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]

Thanks!! 1 worked perfectly fine

[@KostasNostos]

Love everything about the guide. Very good structure with ascending difficulty. Many thanks and Bravo! Subscribed & waiting for more!

[@sirmccannonarms9521]

Thank you so much for putting in the time and effort to make this introduction to Godot. I'm almost 3 hours in and every bit has been great!

[@GreenLightDev]

The amount of help that this video has been can't be overstated.

[@zeerocool]

Great intro, thank you for making such detailed content. Wish you the best.

[@ClearCode]

Thank you so much!!!

[@user-bh1xv9zv3g]

This is the best tutorial on Godot 4 I've seen so far. Thank you so much!

[@Twelveoglock1]

Just happy to say I actually finished this video and am onto part 2. Learned a ton!

[@asthalis]

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.

[@bill_makes_games]

This is truly the ultimate introduction to godot. Would love to see more godot videos ❤

[@Zhinarkos]

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.

[@irowan2414]

this tutorial blends teaching the specific example, but also the core concepts really well. great work

[@arvin390]

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]

Great tip!