I loved that 'like' example. I was fiddling with some lego, which I had to snap together and put down before moving to the mouse to like the video. Perfectly executed!
This is actually the most useful style of editing a video about programming. WAYYYYY easier to understand than listening to a professor talk for an hour with a piece of chalk.
Hey! I just wanted to say that your tutorials are the most clear and detailed one that we can find on TH-cam. It may not seem like it but I know that editing this kind of video takes a lot of time. Also, these topics (Design Pattern) are so important in game development. It allows us to complete a game without any frustration. Big congrats and thank you!
Despite the difficulty of me trying to grasp this concept, your explanation is rock solid! I feel that if I watch this once or twice more, I'll actually be able to implement this in my games!
I watched a lot of tutorials to be able to understand everything about the command pattern and adapt it to my needs; your tutorial has the clearest explanation. (I still suggest watching other tutorials too if anyone is having problems)
One thing i have to say is, i have seen lots of tutorials of unity and programming about many topics, and there are lots, but all of them are not that much relevant some are and one of them is yours one thing that i love about you and your channel is, your only talks about relevant things means point to point no other useless stuff and this makes your video more interesting. that's why i love your channel. keep uploading this cool stuffs. love you from india...
A better design is to create a CommandProcessor class with a Queue collection that stores commands and processes them. Stack stores the history. But for anything other than trivial commands that finish instantly, you have a lot of challenges to overcome to have accurate undo-ing of commands. The CommandProcessor can be added to any class you want to execute commands, and will be nice and generic so it doesn't care what type of concrete commands it's running. It only cares if it's a simple ICommand or an IUpdatedCommand that needs updates and takes a while to finish. Without this, you can't implement more interesting things like moving a character along 5 waypoints because all of the commands execute instantly and the character will just go straight to the last waypoint instead of following them in sequence and moving on when the active one is complete. It was kind of a challenge for me to implement this sort of system properly, but once I ironed out all of the problems in it I ended up with a reusable system I can apply to literally anything and just create new commands for it to run literally any logic. Some things may to inherit CommandProcessor and override the way it processes commands, so mark its methods virtual. An example is if you're making an RTS game and you want a unit to attack an enemy but if it's given a an order to move or retreat it will cancel the attack command and do as the player commands. Otherwise, it will be stuck attacking until it dies or kills the enemy before it can respond to the next commands enqueued, and it can't do that if it's dead, can it? So the command processor for the units will override the ProcessCommands() method of the CommandProcessor base class and deal with this accordingly, by canceling commands that are followed by a higher priority one like an immediate move, stop, retreat, etc ...
Excellent. I can't say I've ever seen a more complex group of programming topics condensed so clearly in 22 minutes. Excellent concept breakdown, excellent presentation, excellent explanations. For those of you who are somewhat new to programming and struggle to understand concepts like interfaces, abstract classes, or their purposes, watch this video. It will make it clearer. If you already understand these things pretty well, you'll wonder why nobody ever explained it this way to begin with.
This is the next level of tutorials. Not only explained in the "command pattern for dummies" kinda way, but it's also animated, well-structured, and super concise.
I love how you take things from ground up and then build upon that. One of the best videos of command pattern I have ever watched!! ❤❤ Please make more videos of this type.
Hey thank you for the kind words! I try to make things understandable to myself so I guess it just happens that a lot of people think similar to me 😅 happy to hear you do too!
Hey, solid intro on command pattern; thank you for that. One tiny nitpick (mostly for those watching to think about) at 17:05, SetRandomLightColor() should really just pick a random color, then call SetLightColor() feeding in the random color instead of repeating the same logic.
Genuinely one of the best game dev channels going. In a world of racing to the shortest video, it's great to see in depth tutorials like this. Thanks and keep it up! 🙂
I clicked this video out of interest since I've learnt design patterns and have been programming for a while but have only recently heard of this pattern. I ended up realising that despite not knowing this pattern, I've already used it in a personal project for the purposes of compilation of a scripting language I created for a text based action game engine I made back in University. At least now I have a name for this pattern. This just shows how useful this pattern is that despite not knowing of its existence, I ended up using it because it achieved the goal in a clean and efficient way.
i watched tons of tutorial videos and you are one of the best. Really appreciate your effort of making animations and stuff to make it really easy to understand.
compared to infallible code the way you explain the concept is really effective, not so fast not too slow. keep doing videos and please cover some more paaters and SOLID patter as well
So I've decided that my first game dev related income I'll put $50 towards patreon, if anything your videos keep me going. Today I am going to be working with a asset I got off Unity Store to do some level design. I have an idea for the way the game will look, it's general loop, and the scenes needed to facilitate this for the purpose of making a demo. Up until now I had been doing prototypes where I test out ideas and mess with things to get familiar with coding and developing in Unity. Each one of these prototypes I figured I'd be using in some way on my final project. I realized it's a lot easier to be inspired to develop my final project if I can see a level instead of working with primitives. So I'll be working on 2 combat maps and one Town map. I still haven't really landed on what the world map will look like. After that I will have a separate project for developing the UI visuals. Right now I think I'm at a point where I've taken in all of this stuff and I can use it but without your videos I'd forget I know this stuff. This means to me I'm in need to some way to note down patterns and possibly I should refer to my old projects more. Anyway thank you for being you.
I recently used the command pattern at work, it would have been great to see your video first :P Implementations can be done so differently which is always great to see
Its been a great help, I just wish the example wasnt so contrived. Additionally the one of the things you mentioned was that commands allow for delayed actions, but that was completely ignored in the example because the input immediately caused action.
Hello IHeartGameDev, as a programmer I want to say that you have explained the basics of OOP very well and thank you for that but I wouldn't call it delaying the execution. And since you have started with the OOP concept you could take a look at abstraction, encapsulation, inheritance and polymorphism. I am not sure if you guys are using these concepts on Game Programming but I would love to help you out if you ever need.
Hey, Can you create tutorials on how to setup character animation with multidirectional animation for twin stick shooter...thanks for your help, your great...and sorry for my bad English
Thank you for all your tutorials about Unity. They are so helpful. Could you make some Tutorials about the Unity particle system? How to use this tool and how to use it with animation. :)
Why did you execute newCommand in lightApp invoker in addCommand method? arent they supposed to be different? newCommand.execute() in execute() part of invoker and pushing command to stack in addCommand() ?
Would this be useful to damage an enemy in a multiplayer game by different players or is it fine to just subtract it directly? Can someone give a example for a not turn based game?
Wait a minute.... If you add multiple change Colors into the queue, won't they all believe they have the same 'previous color'? For a proper undo, shouldn't state be saved at execution?
Ah I think I see what you are saying. In this example, we execute immediately after instantiation which is why it works without a problem. In the case that we didn't want to execute immediately, that would be necessary. Good point!
I am not sure I like it or not this command pattern :D. This would make me difficult to understand where commands are used and how. I need to reverse engineering often I think.
![[กูเพิ่งซื้อมึงปิดหนี] 20 นาที ผมรีวิวเกมที่แย่ที่สุดในโลก CONCORD](http://i.ytimg.com/vi/XhC-3q3Ii7I/mqdefault.jpg)
I loved that 'like' example. I was fiddling with some lego, which I had to snap together and put down before moving to the mouse to like the video. Perfectly executed!
Rad! Love to hear that the Meta example was able to click 😊 cheers Taro! 🍻
oo, one master of another master's video.
This looks like the kingdom of masters :D
Wonder if Taro noticed that he was one of the house instance owners in 3:34
Over a month of research, recording and editing later... I can’t wait to finally share this tutorial! See you all Sunday! Cheers! 🍻
I really hope the patreon supporters vote for the combat system, I've been waiting so long for that haha
Really appreciate the amount of effort u have put in the video. I know how much of work it takes to pull of these things. Really appreciate that!!!
This is actually the most useful style of editing a video about programming. WAYYYYY easier to understand than listening to a professor talk for an hour with a piece of chalk.
Thanks very much Dustin!! Glad you liked it!
Hey! I just wanted to say that your tutorials are the most clear and detailed one that we can find on TH-cam. It may not seem like it but I know that editing this kind of video takes a lot of time. Also, these topics (Design Pattern) are so important in game development. It allows us to complete a game without any frustration. Big congrats and thank you!
Thank you so much for the kindness, Anthony!
Despite the difficulty of me trying to grasp this concept, your explanation is rock solid! I feel that if I watch this once or twice more, I'll actually be able to implement this in my games!
I watched a lot of tutorials to be able to understand everything about the command pattern and adapt it to my needs; your tutorial has the clearest explanation. (I still suggest watching other tutorials too if anyone is having problems)
One thing i have to say is, i have seen lots of tutorials of unity and programming about many topics, and there are lots, but all of them are not that much relevant some are and one of them is yours one thing that i love about you and your channel is, your only talks about relevant things means point to point no other useless stuff and this makes your video more interesting. that's why i love your channel. keep uploading this cool stuffs. love you from india...
Thank you so much for such a kind comment! 😊 I am happy that these videos offer more and new ways to explain these concepts.
@@iHeartGameDev thanku to you bro!! Keep working 🤗
Please also cover SOLID principles exactly like the way you did state pattern. And obviously this video was helpful like always :)
A better design is to create a CommandProcessor class with a Queue collection that stores commands and processes them. Stack stores the history. But for anything other than trivial commands that finish instantly, you have a lot of challenges to overcome to have accurate undo-ing of commands. The CommandProcessor can be added to any class you want to execute commands, and will be nice and generic so it doesn't care what type of concrete commands it's running. It only cares if it's a simple ICommand or an IUpdatedCommand that needs updates and takes a while to finish. Without this, you can't implement more interesting things like moving a character along 5 waypoints because all of the commands execute instantly and the character will just go straight to the last waypoint instead of following them in sequence and moving on when the active one is complete. It was kind of a challenge for me to implement this sort of system properly, but once I ironed out all of the problems in it I ended up with a reusable system I can apply to literally anything and just create new commands for it to run literally any logic.
Some things may to inherit CommandProcessor and override the way it processes commands, so mark its methods virtual. An example is if you're making an RTS game and you want a unit to attack an enemy but if it's given a an order to move or retreat it will cancel the attack command and do as the player commands. Otherwise, it will be stuck attacking until it dies or kills the enemy before it can respond to the next commands enqueued, and it can't do that if it's dead, can it? So the command processor for the units will override the ProcessCommands() method of the CommandProcessor base class and deal with this accordingly, by canceling commands that are followed by a higher priority one like an immediate move, stop, retreat, etc ...
Excellent. I can't say I've ever seen a more complex group of programming topics condensed so clearly in 22 minutes. Excellent concept breakdown, excellent presentation, excellent explanations. For those of you who are somewhat new to programming and struggle to understand concepts like interfaces, abstract classes, or their purposes, watch this video. It will make it clearer. If you already understand these things pretty well, you'll wonder why nobody ever explained it this way to begin with.
This is the next level of tutorials. Not only explained in the "command pattern for dummies" kinda way, but it's also animated, well-structured, and super concise.
Great video!! just a small correction. At 13:44 STACK is LIFO (Last in - First Out).
Love your videos!!!
I love how you take things from ground up and then build upon that. One of the best videos of command pattern I have ever watched!! ❤❤
Please make more videos of this type.
Hey thank you for the kind words! I try to make things understandable to myself so I guess it just happens that a lot of people think similar to me 😅 happy to hear you do too!
Hey, solid intro on command pattern; thank you for that. One tiny nitpick (mostly for those watching to think about) at 17:05, SetRandomLightColor() should really just pick a random color, then call SetLightColor() feeding in the random color instead of repeating the same logic.
I love your tutorials and explanations :) Especially for this advanced stuff. You're helping me a lot. Thank you for those videos!
Your kindness means the world. Thank you 🙏
very good and detailed explanation of everything, from basic to advanced for programmers of all level to understand
Genuinely one of the best game dev channels going. In a world of racing to the shortest video, it's great to see in depth tutorials like this. Thanks and keep it up! 🙂
Bro you should make a series of coding it is really difficult and your way of explaining is owesome
My next video will be on another pattern!
I clicked this video out of interest since I've learnt design patterns and have been programming for a while but have only recently heard of this pattern. I ended up realising that despite not knowing this pattern, I've already used it in a personal project for the purposes of compilation of a scripting language I created for a text based action game engine I made back in University. At least now I have a name for this pattern.
This just shows how useful this pattern is that despite not knowing of its existence, I ended up using it because it achieved the goal in a clean and efficient way.
i watched tons of tutorial videos and you are one of the best. Really appreciate your effort of making animations and stuff to make it really easy to understand.
Thank you so much Kizz06! I’m glad you like the videos and appreciate the effort!
I really liked the analogy with the like this video command, smart!
Thank you :)
This is honestly one of the best tutorials made on this topic
Thanks Nicky!
compared to infallible code the way you explain the concept is really effective, not so fast not too slow. keep doing videos and please cover some more paaters and SOLID patter as well
great video, i'd love to see a follow-up showcasing a variety of different applications for this
So I've decided that my first game dev related income I'll put $50 towards patreon, if anything your videos keep me going. Today I am going to be working with a asset I got off Unity Store to do some level design. I have an idea for the way the game will look, it's general loop, and the scenes needed to facilitate this for the purpose of making a demo.
Up until now I had been doing prototypes where I test out ideas and mess with things to get familiar with coding and developing in Unity. Each one of these prototypes I figured I'd be using in some way on my final project. I realized it's a lot easier to be inspired to develop my final project if I can see a level instead of working with primitives. So I'll be working on 2 combat maps and one Town map. I still haven't really landed on what the world map will look like.
After that I will have a separate project for developing the UI visuals. Right now I think I'm at a point where I've taken in all of this stuff and I can use it but without your videos I'd forget I know this stuff. This means to me I'm in need to some way to note down patterns and possibly I should refer to my old projects more.
Anyway thank you for being you.
This is one of the clearest and most concise videos on a subject like this I have ever seen! Kudos!
Thats what i've been searching for
Excellent video. It is very difficult to find paid content with such quality as this video!
I was wondering _how_ to work the "Banana Command Class" into my code, thank you so much! ✌️
Awesome video, cant wait for the Observer Pattern video later today
the one tutorial I've been looking for! it just clicked!
THANK YOU!
Give this man a rider license.
Awesome video. Glad someone is covering topics that are necessary to be used in production. Have you thought about making a video on inventory system?
I recently used the command pattern at work, it would have been great to see your video first :P
Implementations can be done so differently which is always great to see
This video-editing is very high level.
I wish people would know your channel more and more
Love this. Nice one man. Always wanted to try this out. Good to have the basic knowledge
Thank you so much for this brother. This means alot!!
Its been a great help, I just wish the example wasnt so contrived. Additionally the one of the things you mentioned was that commands allow for delayed actions, but that was completely ignored in the example because the input immediately caused action.
Good to see you back at it Nicky, I love the videos.
This video is pure gold. Thanks!!
This is the most unique way someone got me to press the like button. I literally had to press it just to understand the concept of an invoker hahahaha
Lol happy you understand it now though!
Hello IHeartGameDev, as a programmer I want to say that you have explained the basics of OOP very well and thank you for that but I wouldn't call it delaying the execution. And since you have started with the OOP concept you could take a look at abstraction, encapsulation, inheritance and polymorphism. I am not sure if you guys are using these concepts on Game Programming but I would love to help you out if you ever need.
Not sure how I found this video, but thanks!
I’m not a C# dev but I can see where this would be useful in Swift 😁
It's very very well explained. Thank you and good job !
This was very informative, well structured, good examples, easy to follow with the refactoring etc. Very high quality, thanks :)
Really love your charisma man, nice to see more advanced topics! Keep up the good work ❤️
Very high quality tutorial, thanks!
❤️❤️❤️
More design patterns ❤️❤️
Another amazing video. I cant wait to see more use cases of this pattern in the future!
Hey, Can you create tutorials on how to setup character animation with multidirectional animation for twin stick shooter...thanks for your help, your great...and sorry for my bad English
Hey! That sounds fun to do one day!!
You got your like, bc that was a great meta example.
Besides, my hand was also busy with coffee.
Even if I know this pattern, I wouldn't have explained it better :D
Thank you!
Thanks for such a great explanation 😍😍Loved it
Thank you for all your tutorials about Unity. They are so helpful. Could you make some Tutorials about the Unity particle system? How to use this tool and how to use it with animation.
:)
You are AMAZING! This is a premium quality tutorial. Thank you so much!!!
Awesome tutorials dude. Really. Would love to see some command queue handling :3, also callbacks from command
dude, fantastic, thank you
Thanks for watching Brian!
The quality of your videos is amazing! Keep up the good work :)
Wow! might be the best tutorial I have seen about this. Thanks
Would like to see some systems like : inventory system, grid system, merge system, stat system
Broooo! This is sooo detailed AF! Thank you! 🎮
Cheers mate! Thank you for the love!
Took me a whole year. My brain finally invoke the subscribe button.
nice ! runs great on my laptop on medium settings :)
Some of the best content on youtube!
Nice tutorial!!
Thank you for this awesome tutorial 💙
Thank you for watching!
5:50 my invoker (Brain.cs) had already liked the video on the Awake() function 😎. Great video, man!
좋은 영상 감사해요
객체지향으로 코드를 구성하는데 도움이 될거같아요
개발자는 언제나 공부를 해야하네요!
perfect also when u will be making practical use of it my req is that also show use of conservation with it
Really good tutorial, very interesting, easy and visual. Good work man, i want more videos, i learn a lot with your channel!
Amazing video ,thanks for sharing
The video Is good
worth waiting
This was great! Please More :)
Damn, the way you suggested subscription is damn sick 😂
Thank you! I thought it made sense at the time!
Great video! Just 1 question, what's the difference between Command and Observer pattern?
13:44 Stack should be last in first out
Really well done.
Very well explained! Thank you !
Great video
So good tutorial! applause!
Perfect tutorial can u make exactly same for factory and abscract factory pattern :D
I love you man you're the best
Thanks so much for the kindness!
Thank you
Excellent!
Really great videos! 😁 👍
Good tutorial!
Super helpful! Love your videos
I keep thinking about the lazy lambda functions when delay is mentioned
Hey can you demonstrate multiplayer game development ?
Awesome!
Why did you execute newCommand in lightApp invoker in addCommand method? arent they supposed to be different? newCommand.execute() in execute() part of invoker and pushing command to stack in addCommand() ?
good tutorial
Крутое видео. Теперь хочется бросить всё и идти делать пошаговую РПГ с возвратом во времени.
thx and subscribed
Would this be useful to damage an enemy in a multiplayer game by different players or is it fine to just subtract it directly? Can someone give a example for a not turn based game?
Wait a minute.... If you add multiple change Colors into the queue, won't they all believe they have the same 'previous color'? For a proper undo, shouldn't state be saved at execution?
Ah I think I see what you are saying. In this example, we execute immediately after instantiation which is why it works without a problem. In the case that we didn't want to execute immediately, that would be necessary. Good point!
@@iHeartGameDev Delayed execution being one of the main advantages of the pattern :)
@@weckar total oversight on my part. Thank you for pointing it out, Weckar. Much appreciated!
Awesome!
System.Action or System.Func seems easier, if you just want to delay invoke a method.
I am not sure I like it or not this command pattern :D.
This would make me difficult to understand where commands are used and how. I need to reverse engineering often I think.