Видео

Saw that you haven't uploaded a video in some time. Hope you're doing well.

Amazing. Really approachable and knowledgeable. You have a gift for teaching (and programming, too)!

Hey I just found your channel just starting to get in the Godot myself. Still getting used to the scripting a bit and you're going more of the visual scripting. I was wondering if you ever plan on doing the add-on for godot's visual scripting?

thanks this was very helpful dude

Excellent tutorial, thank you so much mate!

Best Godot tutorial to get people up to speed that exists.

This is so informative while being so funny 😂

Hey! Strongly believe you are overcomplecating the problem. You are puting too many responsibilities into each class while also having string referencies. Also puting lots of code into single file. Kinda opposite of Engine ideology i believe. Why not use composition instead? Put code that you like into separate child node of object. Heres simple example of how to get child component of given class: static func get_component(owner:Node,class_type:Object)->Node: var comps:Array[Node] = owner.get_children() for comp in comps: if is_instance_of(comp,class_type): return comp return Scene composition: Target | -HP (class_name Health) -Other nodes..... For example we have class with name Health extending Node. Than we can just try: var health = get_component(target,Health)

Came from your Godot for absolute beginners video. And this more advance video were still fun for me to dip my toes in more advanced concepts. And you explained it well.

When you are using the if "implements" in other_area does the area in question need to be an Area2d node ? In my setup, the script for the enemy is attached to a characterbody2d with an area2d node child, and this if "implements" code isn't working.

bro I watched this like 3-4 times and I always die laughing at 1:08

Am i gonna be able to do that same game in my mobile phone using godot 4?

For personal future reference: 4:18:25

I am fairly inexperienced in programming and so on, let this be prefaced. I was searching for "interfaces" in regards to separating input checking from a player script and came across this video. Isn't the entire setup fighting the entire design "philosophy" of Godot's Node system? And please correct me if I'm wrong, so I may learn, but: Wouldn't it be easier, quicker, and more modular to just create separate nodes for expected behavior from entities? Instead of creating this autoload interface, we create a node with a script, giving it the class name "Damageable" and specifically handle how damage is processed in there. For Example: It would probably be beneficial to handle the entire health system of an entity inside one of these components, offloading the responsibility from calculating damage, when to queue_free() itself and so on, from each enemy type, player, or whatever can take damage in your game, be it an asteroid or other obstacle that isn't a player nor enemy, onto it's own component. Have an indestructible obstacle? Don't attach the health component, simple. This, at least it seems to me, is, on a fundamental level, how Godot seems to want to handle it's relations. A Player doesn't need to have a sprite, it could instead have a 3d Model as a child, representing it's visual component. You define little amalgamations of complex objects by adding functionality through attaching more nodes. An Area2D could therefore just be defined as a "Hitbox Component" and can have a Class attached to it like that. With this setup, you don't even need to check if something "has_method", if the area you are checking (using the built in keyword "is") IS (of the class) HitboxComponent, you can directly call the function from there, giving you intellisense and even let you control + click it and see the functions declaration. All in all this system requires at most as much setup as this interface has but has a range of benefits for structuring and visually adding functionality to any given entity on the fly, right? Sort of like using little "mini interfaces" in the form of nodes instead of an autoload and essentially having to rewrite behavior for entities that cannot inherit every behavior, such as an obstacle.

This dude's ability to use verbal and visual aids to convey his point so effectively is super impressive.

At 3:19:50, he creates a signal "on area entered 2D". I'm following along and doing the project with the tutorial but I don't see that signal anywhere. I've made sure I'm selected on everything he has selected, poked around but my list of signals to choose from is much shorter than his. Any thoughts on why I can't find and add this elusive signal?

I just wanted to say that your tutorial is amazing

Thank you so so so so much shaban

couldnt you defined Implements as a const in Interface autoload, so you dont have to do the string compare?

Can someone point me to the hardest Godot tutorial, please?

43:46 I've made something move!! I'm going to make the next Finial Fantasy game :)

Who else pressed F5 at 08:35 to be fast forwarded in the video to 22 minute :)🤣🤣

Your way of teaching is wonderful!! I overtake a lot of block by following your tutorial. Thanks a lot Stefano

Will you make more godot content? Your videos are very helpful

this is great im loving it. im an absolute beginner and i just decided to give a shot at godot since i was also learning python. the first ever tutorial started is this tutorial and im glad i did. i have to say tho, its not a breeze, theres still a lot to understand. i am 3 hours in as of now, on my day 3. anyway what was i saying, silly me. sir, you should be more visible. where are you teaching, is there any more lessons? or do you have any game projects? you need to provide us some info cause you got some serious teaching skills and your sense of humor cracks me up.

44:20 - Small tip for anyone whose player object seems to 'lag behind' the mouse cursor, instead of being instantly positioned like in the video: it's because you have vsync turned on in the project settings. Turn it off and the position will update instantly instead of trailing behind.

Thanks a lot for making this tutorial. Really has helped me understand 3d concepts more. You're a great teacher! 👍

Thanku so much pls make tuturial on 3d physics how can i make anything move as i want ,im talking about vegicle controller and more , how make complex physics in 3d world and mechanics

Guys, is there a guide that would fill the gap between the "absolute beginners" video and this one? I already feel lost on the model reimporting stage.

"In a single video" The video: 10 hours

Thanks!

Do you have a video somewhere where you show, not only how to put a score-system into the game, but a high-score as well? So far I have only had time to watch the 4 hour long tutorial and it was superb!!

Great vid!! Hoping for more!!! 🎉

OH MY GOD

Thanks for the tutorial! I am starting with Godot and this helped me a lot to go through it.

2:00:20 they fixed that bug with the icon not changing when you change a node type. In 4.2.2 my icon changed. :)

I'm coming back to programming with the hopes to write games, after decades of not writing a single program line. I watched a dozen videos and followed multiple tutorials and each one bounced off my brain... until this one. I'm only 1/4 of the way through but I'll be watching the whole way, coding along with you, and by now it's clear that the knowledge and confidence I gain from this will get me on the path I need to be on. Thank you!

You didn't only say "how", but explained why, and which ways of doing things that are future-proof because you're justifying the "why"s with positive composition habits. Thank you so much, the tutorials so far have been specific to one context, or example, but not many explanations as to why or why not to do something a certain way. I had trouble with the layers and masks, it not being reflected in a value or in the UI elsewhere if it changes, where to place scripts depending on what I wanted them to effect/what went in them, when it is appropriate to use export/global variables and constants, what is best to put in the autoload, the fact that you can even make a sibling node to the main node, etc. ALL these things caused me so much frustration when going from following a tutorial of somebody else's to a T, and then going "Well now I want to make changes besides these ones" and breaking things unintentionally. Thanks a lot for making a tutorial in what must be the best teaching style for me, based on how much clicked!

you are awesome! thanks a lot for all the help <3

Wouldn't a dictionary of callables or something like that have a similar effect? I'm a beginner at coding. I just am trying to figure out why that couldn't replace this.

Took me a couple of weeks, but I'm finally done! I no longer feel like I'm just hacking things together and seeing what sticks... This kind of a structured approach to gamedev is absolutely amazing. A huge thanks to its creators!

Maybe checking all the scripts files at the start of the execution when the singleton is ready, get all the files .gd, check if they have the interface variable, then assert if the methods exist and so on. This is totally independent of the node tree and would crash faster

Abledoooooooo

Renamed play_system.gd to strike_system.gd Chabane wants the play system to be concerned with only the mechanics of striking the cue_ball. Realized his intent 7ish hours deep into the tutorial. Thanks for pulling an all-nighter for the community @tutemic

It's an honour to learn from such an honourable man! I'm with you on all fronts, brother. No matter the risk. This is why I make video games.

Hello, amazing video! I have this _on_sleeping_state_changed and I noticed the sleeping keeps switching from true to false constantly even with the ball stopped. Do you have any idea why this might happens? Thanks

Excellent tutorial thank you

And Why are there skulls on our uniform? Are "we" the baddies? 😁

I'm encountering a lot of errors while watching this video, this video might be outdated or I'm just dumb. (most likely the second one)

26:01 Emperor penguin