What a fantastic lecture. There isn’t a single second wasted in it. Instant sub, I hope your channel keeps growing!

Hi, your video is amazing. I'm still learning regarding state machine and will be watching your other videos, I just want to say thank you for your amazing discussion.

Man this is the type of high quality content that Godot is missing! Thanks for the great video and keep up the amazing work. Subscribed

this is what I'm looking for, you are so detailed in explaining the steps,thank you for it ,

State Machines changed my life.

I implemented this kind of state machine in my current game after watching your videos and I very happy with the result! It made the states easier to code, debug and control

Hey man thanks so much for the videos. New to game dev but not necessarily programming and I really like these short digestible vids that help me get my mind in the right place for how game loops work. Really easy to follow. Appreciate the effort you put into these vids!

You're good at explaining! Thank you

very very useful. just what i was looking for .

Incredible video. Very compact and informative! Just like you said I was seemingly already using a frankensteined version of this in my game that somewhat worked but still made a lot of problems. Well, time for some refactoring :D

oh, god This is one of the best tutorial Ive ever seen , your fantastic bro keep moving, I sub without hesitation 👌👌 , good job

aw man this is awesome, these tutorials of yours are super underrated

thank you so much...!

Instant subscription! Awesome tutorial, keep up! :)

Great video!

That segment about "Life without state machines" was me jsut now trying to make my first player controller with a double jump. i thought to myself that there HAS to be a way to do this more efficiently, and found your video. I'm trying to apply my web dev knowledge into game dev and it's hard as hell. Thank you for this video lmao.

Criminally underrated channel. Just wait bro, the subs are coming.

Why did I not found this gold mine channel before???? >>> This video is A GEM!!!

I've been looking for a decent video on general state machine theory for a while and was wondering why I hadn't come across this ages ago. It's because you're new! *Sub* Thanks! Great stuff!

Your teaching method is flawless. I'm a potato brain and I understood like 95% of this. Has me excited to get to trying this in Godot

Thanks for the great game dev class, should pay you for it so good thing i have UKposts premium

Cool video, I've created a custom StateMachine and State Nodes, and adding new states is about creating new state child nodes to the state machine nodes. If the states are not memory intensive you can instance all of then instead of creating / destroying on the fly and just switch true / false to their physics process and input functions.

Great!

Thank you, this will help Me out for optimization of enemy ai for.my.game.

Your content is very good!

"Most have never heard of" Learned it, implemented it(the proper OOP GoF State Machine design pattern) in my own projects(not game dev). Now looking into how to implement it well in UE. It's very badly implemented in UE where it only supports it for the animations(either mesh or sprite animations) but not the full player state machine where we can handle inputs properly, play animations, sounds, etc.

Can confirm, I did implement something resembling that enum. But it started feeling messy, so here I am. 😅

Thank you for this incredibly detailed video. Is there any chance in future you would consider making them without the music in the background? i find it super difficult to learn/concentrate on something new in a logical manner when music is playing. I'm sure there're more folk like me who struggle with the ADD side of things. If not, there's always mute and closed captions =D

Still a little over my head with the jargon - but I like your voice. It makes me feel like I'm getting it more than I am :P

good vid, looking forward to part 2

Great presentation and easy to understand. Subscribed. One thing I had a question about was the final section on cleaning up the Jump state exit() function by creating a Base state which holds the exit() function. Does the "requirement" to call exit() from Jump state warrant the work to create the Base state if you were working on a project? Are there other states you could imagine "needing" to exit() that you would not want to duplicate code on? Or is it for the purposes of following good practices?

i love state machines. but have some trouble when it comes to more complex or overlapping states. for example if u have a swimming or climbing state. you can jump when climbing or leaving water. but its an other jump then from ground. what about if u want to separate jump-state into jumping, inair and landing to do something like coyote timer or different animations. next issue i have is the reusability of states for other characters that maybe cant jump. there is a hard coupling between states. evenry state needs to know at least the possible target-states. sorry for that many questions xD anyways, great video.

We are standing on the shoulders of giants... one apple man once said.

A state machine is a MUST for a character controller. “Cleaner, easier to maintain, and easily expandable with little effort” is true. I wasted so much time thinking a state machine is too complicated, it’s actually way more simple than one big messy controller script.

The diagrams for state machines are not called flowcharts, but instead statecharts or state transition diagrams

I would stay in the enumerator pattern rather than in the state pattern, even for complex logic. Maybe if there were nested states I'd opt in for an abstraction, but probably also with an enumerator within another enumerator, but in a different class or something.

I'm super confused about where/how to add the initial State interface. I keep getting errors and the documentation isn't helping :(

ngl i had trouble following the video because all the images were static and i had to go looking for what changed after you swapped an image showcasing code

Hi! please use monospace fonts :D

lmao when I was starting out, I use phases, as like in Magic the Gathering. So when I found out about FSM, I was like hol up , this basically the same thing I was doing since I was 12 yrs old lols

3:41 "Can only be at one state at a time" - what about "Jump" + "Attack", or "Move" + "Jump"? I understand you'll explain it later, but it's a bit confusing for a beginners.

State state state state. And that's it.

1k th like lesgooo

still can't figure out why people would ever *not* use state machines... I mean, if you're using a basic engine like construct it's kinda excusable, but for ones like Unity, Godot (which I have a slight impression that it's the one you use too), and Unreal, you're definitely a masochist

Very educative video but background music is very annoying. May be I am not a game developer so that why I am annoying Awesome video !!!

this video is super helpfull thank you so much PS : youtube algorithme sucks

8:05 I'm a bit concerned that you are coupling the states, making state change logic less transparent and making every state dependent on knowing of other states existence

You go from the original horrible mess of _if_ statements (which motivates the need to find something better), directly to the best solution of a list of states (enumerators) + all the variables you need to switch between the states. Short, simple, maintainable, easy to debug, easy to read, easy to comprehend, easy to implement, easy to explain, does exactly what you want and no more. Perfect! Done! Right? Nope: Then you go backwards _two_ steps to an even _more_ horrible mess than the original! Full of unnecessary complications, indirectness, and orientationism. It becomes hard to debug, hard to read, hard to explain (nearly half the video vs 1 minute for enumerators!), hard to maintain. Ugh. 😣 By the way, I added a like to the video because: A) The first half was great! B) I can't blame people for falling for the OO propaganda as it has been indoctrinated into the entire programming population since probably before you were born. I know I sure fell for it...