วีดีโอ

You should make those type of videos more.

For someone whho works with Java, I had my fair share of complaining about the abuse of inheritance and lack of real composition. You managed to explain it in a way that I can just replicate eithout sounding too technical. Thanks!

Saw this in my Timeline and although I knew about both concepts, I still watched the full video as it was really spot on.

I think you can do a hybrid approach here, and create an Entity Class with required components.

Awesome video! A neat trick for switching states: using the return value from the state's process function instead of signals. That way, you can have @export variables for each state to define its next potential states, and return them to the state manager that does the switching This also removes the need for a dictionary!

So, my 600 line switch is now 1100 lines in 14 files.. How is this better?

Great tutorial. In your Entity example at the start. Entity should extend Node and then it can be attached to anything. Create your player as a CharacterBody and attach the entity script. Your Mobs are RigidBodies and your Trees are StaticBodies. You can have Entity extend PhysicsBody3D to be even more type safe. That way you can only make an entity out of something that must have a hitbox

A great explanation of inheritance vs composition. However you jumped from using Classes to Components without explaining the pros and cons of each. Composition pattern can be used for both Classes and Components. You don't have to use a Component for everything?

bruh I can't make my enemy move, i've seem the video contless times and my slime stays put

easily, just dont use godot

Idk if the initial example was the best… I mean “entity” is just to broad for a class. It should be “Character” class for player/enemy and a “environment” class for a tree/building etc

Its the same paradigm that React teaches you to use. Kind of an interesting crossover in paradigm. I've always really liked Composition, I'm glad its gaining traction elsewhere.

Pretty nice, but isnt this what a resource is supposed to be used for?

If state != current_state == true; I do not quite understand this part. To me it looks like it would allow infinite state change requests instead of parsing one state through at a time. Like running and attacking at the same time. Any suggestions?

did everthing perfect twice and still get "Invalid get index global_position(on base nil)"

I wanted to get to know FSM better and see some code example, bur at halfway point of the video my mind just started to melt...

The link to the Level Template by someone2639 in the description is broken. Anyone know where I can find the level template elsewhere? :)

state is one of the 50 places in the northern America and they all have terrible pizza except for mooses tooth which only has one location

You're a lifesaver! I had to give up on my shmup project in Godot 3 before I saw this.

I found a great hack! If you change the font color to the background color, then your project looks pristine!

the link to the template is broken. the working link can be found by going to the mega document, ctrl +f search for 'template'

The template is unavailable now, its there anyway to do something similiar without the template?

So for a state machine would I still have to define the variables for say a dash move state or does Godot fill in the blanks if I extend the node? Looks like you still made reference to some things with certain parts of the state machine but I'm not sure how crucial those are.

If I hadn't known Finite State Machines for years beforehand, I would definitely know by now! Your concise concept & excellent explanation makes FSMs - an often over-complicated yet rather basic topic - easily understandable by beginners as well as intermediate developers IMHO. Awesome content quality I have rarely encountered with video tutorials, and especially on TH-cam. Nicely done, keep it up!

this is pretty neat and very helpful! there's still one thing that confuses me tho. why is there a hitbox child and the hitbox component child with a collision shape in it? that seems redundant, but both need a hitbox as far as i know

as that its nearly midnight ill leave this video for later but i will return and thank the youtube god for recomending this video

this video help me alot thank for makeing it :D

Found this video alongside your others as very helpful thank you! Would love to get a use case for Resources as well! 🙏🏾

After watching this a number of times now, I've noticed that the exit() function is never actually used, it hasn't got any defined instructions in either of the states.

actually i think this is a great way of introducing the concept of Object Oriented Programming in general, beyond their use in godot!

I fell into the exact trap you gave as an example. Looking forward to refactor my game to use more composition and less inheritance!

Unashamed to admit I set the speed of the video to 0.75 and rewound the video dozens of times.

What I think is great about this tutorial is that you don't need to know about the way each state behaves. I like that this isn't the main focus as each state for each game is different for each game dev. At the same time, each state explained here is also extremely versatile due to it's simplicity so if you wanted to you could still use it and just iterate upon it later. But just to know how states work is quite wonderful.

Thank you!! I was meaning to use a more component-oriented approach in my game, but I've struggled with finding out how to implement that properly. This video really helped me understand it better - the code examples were especially helpful!

Best video ever, and this is not just for Godot 4, this works well for Godot 3 and mainly other types of programming if you get the logic behind it. Perfectly explained and simple. Absolutely brilliant

the discord template link does not work anymore

if using C# interfaces would be a good idea as well. Not only can you extend properties, but you can also have classes take which functions they are going to have (interfaces sort of act like components)

thank ^^

thanks for this man! I am using inheritance for my inventory system and now composition will greatly help while implementing enemy nodes

helped me a lot, thanks

I think you should use Node instead of Node2d for components (for performance purposes)

Can you give an example of interacting with components from the outside? I don't see how this is useful outside this specific case -- reason being is that it works so elegantly only because Area happens to be a collision thing, which interacts with other native things in the engine and allowing you to easily get a reference to it from the collision system. If I wanted to bestow an object with special properties using components, there's still not a real good way to interact with those without hard-coupling them that I can see?

so this is the real programmer work.. omg I'm so ashamed to myself

Great stuff, thanks a bunch! Added a signal to hitbox component with the attack position and knockback, now everything can be knocked back if needed :D

Watching this i felt like the Kel meme from Good Burger. "Yes I know some of these words". Im far too green at coding for this but saving it for later when hopefully I can understand more than the first 1.5 minutes.

Keep it up! I really loved this video!

That example blew my mind

okay i found out how. btw thank you for making these. there arent that many tutorials that guide in coding in general instead of just specific coding structures