Thank you for the spirited encouragement! ☺We do in fact have more on the way

I was pretty surprised too, tho your videos are exceptional!

Would love another video made by you about this! :)

Aw, thank you Nicky! That means a lot since your videos helped me create these videos. We wanted to help devs get a feel for the patterns quickly, so I bet they'll seek out other videos that go more step by step like yours 💖 Love your new procedural animation series 🔥

@@HomeMech ☺Now that is an awesome surprise! So happy to hear! And thank you for the shoutout of the proc ani series!

@@AriaZed Thanks so much for the kind words!

That means the world to me coming from you, thanks Ciro!!! ☺

Haha, great idea! In fact, in our upcoming factory video, we start exactly like that ☺ In the case of command, I'm reminded of the bunny story we learn to tie our shoes, either the floppy ears or down the hole 🕳🐇 There are other complicated or just plain bad ways to tie your shoes, but sometimes it's useful to have the "right thing to do" be easy to remember. 📩Hassle interface support, roger roger🤖

Thank you for the feedback! We have more videos on the way soon, including a final video where the patterns are used together in a system. Since the videos each have their own personality that fits the pattern, we hope that the difference between them is clearer when taken as a whole. But do let us know what you think!

Thank you!! Slow down a bit noted 😅

You can put an extra boolean IsComplete in each command, and make the commands manager not move on to the next command until the current one is completed.

Great question! There are several ways to go about this. In a "WalkCommand" you could have an "isComplete" flag that starts out false and is set true once the character has reached the destination or the coroutine is complete. You can also invoke an event like "commandComplete." This is probably a good idea for the robot chef--"Order up!" 😄 It's worth noting that chatbots like GPT are *very* good at assisting in modifying or fine-tuning the patterns in various ways like you are asking. Just knowing the patterns a little is enough to unlock all the great advice that you wouldn't get if you didn't prompt for it. The concise nature of the ebook examples make them perfect for copy-pasting with a prompt. That said, I could see it suggesting something more complicated, like integrating the commands with a state machine, so it may be worth seeing a simple boolean flag or event-based approach first.

Finite State Machine, a simple enum and switch statement. Or an interface or even delegate would work

If the Execute command is a coroutine (or async) then you can just wait for it to finish.

Great point! The examples are simple as needed to capture the pattern. How to handle a sequence of commands really depends, and our main objective is that people understand the pattern first. We have a final video on the way that is an action/fighting combo system (like Mortal Kombat or Street Fighter) using the command pattern--in that system, managing, evaluating, and clearing the sequence of button actions that might produce a combo is essential and pretty involved 😅

Mentira

🤖I am flattered you'd think someone would choose my voice from a drop down menu and think "yes, that's the one I want" haha 🙈

@@HomeMech Sorry :S

@@forestrf Don't be! It's a compliment in a funny kind of way 😄

Sorry to hear! Please let me know if I do better in the videos coming out next. I wish there were a way to do the robot chef story without code and then with the code... all that's needed to understand the basic gist of the pattern is the concept of putting robot chef orders in an envelope so you can create a list of them and thus have complete control over when they are opened/executed.

what are you having troubles with

@@HomeMech i think maybe just the classic undo redo functionality would be the best explanation of it. lets be honest you're not going to *actually* use this verbose code for something like this example

​​@@HomeMechI think OP is having a hard time understanding ICookingCommand and interfaces in general, since this is more of an intermediate level video. He most likely doesn't understand how interfaces can be used in dependency inversion. Maybe make a separate beginner video showing the purpose and how dependency inversion can be achieved with interfaces

@@jayocaine2946 I think there is just too much abstraction going on in the example, IRecipe, ICommand, a simple ICommand example, with a Queue and Execute method I think would be enough than going ICommand.Execute -> IRecipe.Cook ...

what point are you getting hung up at?

Skill issue

@@Caffeen save that for video games bud, these are people trying to learn. Why on earth would you bad mouth someone who's trying to understand something and better themselves?

@@jayocaine2946 "Such a bad video" I'm all for people trying to learn and better themselves, and I would never insult someone for having difficulty learning, but badmouthing someone who put the time and effort into trying to teach you something is incredibly disrespectful.

@@Caffeen It's not a great video or explanation. The usual example given for command pattern is usually an undo/redo functionalty because it's the best example you can give. Whatever weird abstract robot thing he's doing here is not an actual every day coding problem. It's a metaphor and not a very good one at that, he tried to be much too creative when it's explanation has already been perfected other places on the internet and in school