This was VERY useful. I swear, I don't know why things like this are not part of standard Unity sponsored training. When developers have knowledge about tools such as scriptable object events, scriptable object variables, and Action based event systems such as this, the whole process becomes MUCH easier. There wouldn't be so many indie developers that get overwhelmed and quit.
This is best quality channel on youtube for learning unity. Clearly explained, elegant code, isolating the subject at hand with 0 distractions. I'd pay for your courses!
I watched many tutorials on this to understand this concept but I didn't learned it, actually implementing in my game helped me to understand it more and I use it everywhere. Observer pattern is the most simplistic and easy to use in Unity. If you want to make a game, this is a must-learn concept.
Finally, a practical example that actually explains how to use Actions. I can already see the advantage of them in terms of having ridiculous spaghetti code like I have now.
Thank you so much for this tutorial. After watching another tut that explained the theory really well this one made if finally click for me, because it had some actual examples!
awesome vid! I've been using Actions writing my game now and I'm pretty new to it. I have a basic understanding of how it works but your explanation helped me grasp the concept a lot better. Great explanation!
Really like your presentation and explanations - been learning unity for six months and this is perfect for where I'm at. Seen lots of RU-vidrs, and you're among the ones I'd call natural teachers.
Was looking for a subscription pattern in C#/Unity coming from a ruby webdev background and feel lucky to have come across this one. Great examples covering several implementation cases that would have had me bumbling around documentation for a while. The nullexception gotcha at the end of the video was the cherry on top. I hope you can find success on this platform in one way or another because your content feels like a shining newborn star in the nebula that is unity game dev tuts
What a great video. I was looking around a lot trying to figure out how delegates and events worked and this video just explained it perfectly! Thanks a lot man :D
What an awesome tool to have. First time even hearing about actions at all, they kind of remind me of interfaces - except they can be AoE, which is extremely dope! Came here from the Manage In-Game Time vid, this was 15 minutes well spent. Great job!
Honestly, thank you. Actions have been a headache for me on my project for a while, the way I was shown to do them previously was much clunkier and harder to understand. Watching this, I got them in under ten minutes, and I've just put it into practice and it worked first time. I feel like I can go through my code now and really clean it up, which is amazing. Excellent tutorial, really well explained, great example, just.. thanks!
Hey Mike! Just curious if you made one of these or a follow up to this one--which I cannot find--discussing public static event Action and its differences and how to use? Like preventing raising event from outside of the Actions class because it is an event and not just an Action. I think many people could benefit from your simplistic way of describe how things work without going overboard!! Thanks for all you do!!
Seems like you haven't made a video in a while but I'm just learning unity and have come across multiple of your tutorials and they were all extremely helpful! I especially like that you always explain WHY you should or shouldn't use certain things instead of just speedrunning the correct answer thank you
I'm still here and kicking. Just going through some stuff atm along side some project work + IRL job related work. I hope to get back to recording again this year ♥
Amazing tutorial the concepts were explained simply and quickly and the example usecase really helped me get my head around the topic (unlike some tutorials which just leave me with "well thats cool but like...why?").
COME ON RUFF! give the man his well deserved promotion hahaha . Thanks a lot mate, very clear overview and explanation. I've been looking up information about Actions in unity but couldn't find anything as detailed a this. One question that's bugging me now, what's the big different between events and actions?
😂 Let's just hope he listens. That's a whole video in its self. They're pretty similar on the face of them but Events, Actions, Delegates etc all have their own benefits at their own times. I'll probably do a comparison video at some point soon like I did with the Update vs Fixed Update vs Late Update video
Why does the Event *care* whether anything is listening? It seems to me that you haven't really "decoupled" anything, since we still need either end to be present. I get that adding a null check gets round this, I'm just not understanding the extra layer of complexity (which must add an overhead?) Great videos btw!
That's just how events and actions work. Because they're a delegate and not an actual function or method they don't strictly "exist". So if there aren't any subscriptions to that event then it's null. If you try to invoke null then you get a null reference exception
I see what you’re trying to say… But, while you have removed the dependencies on your manager classes, you have introduced a new dependency, namely the dependency on your Actions class. Another approach: Instead of using a separate Actions class, you could declare the Enemy's action in the Enemy class, then you have a one-way dependency from the Manager class on the Enemy class - but not the other way around. Whether that's better or worse depends on your overall project structure.
That's definitely true, but Actions is a static class so the dependency is all but guaranteed at any time unless you manually remove it, sort of a central hub for action references
@@comp3interactive Yes, I understand what you're saying. But you gotta ask yourself why you are removing dependencies in the first place? Often, for greater reusability, in particular the ability to reuse some of your classes in another project. With your approach, you'll end up with one gigantic Actions class that, when copied over as a whole into a new project, will contain a lot of actions that aren't relevant for that new project. There's no perfect solution to this problem and yours is perfectly fine. But since the rest of the video was very well presented, it just kinda feels like a sentence or two about the drawbacks would have been nice.
Totally agree with you. I'm gonna heart the comment so people can see it, next week I have another video coming out with a "real world" example which is more akin to the way you're referring to
Both arguments are valid. But rather than the ability of moving the Actions class to another project, the main advantage here is to store all the Actions in one place. Because it is hard to remember the Classes to bind/unbind things. The IDE will help us find the actions we are looking for. The best part of the Observer Pattern is; we can test ie. Player Prefab just by dragging and droping in a Test_Scene and test how the player movement feels without any other components in the scene. Nothing will crash or will need the score UI or any other stuff we don't need to test at that moment.
Exactly, like you both said, there's no real "one size fits all" solution, which is true for most projects. The only reason I chose this method was I was working on a project at the time which used this way 😂
how do i write return value from action, as i want to make sure it has been listened and loop if it wasnt listened. as this action need to be done before proceeding. Thanks
I've been considering an ActionsManager for exactly this kind of stuff (stats, ui, etc) and now I see this is Actions, not Events. Ahhhhhhh, so yeah this will work better for me I think. Question about changing scenes though. I think this is the same kind of C# static class as in your video on Pooling, is it not? When I implemented that I started getting errors when restarting the same scene. (When all players on one side die it shows the Game Over screen and then starts the scene again.) How do you handle that with these C# classes, the ones not inheriting from MonoBehaviour? I'm thinking they don't go in DontDestroyOnReload ... but then what?
how do i write return value from action, as i want to make sure my initialization done then stop doing this action. supposed the listening gameobject take some time to be instantiated
I had an issue I hope you can solve, In the private void OnEnable its giving me an error that says "operator '+=' cannot be applied to operands of type 'Action' and 'method group' It has the same error in the private void OnDisable
![How to Use Actions in Unity [Unity Tutorial]](/img/logo.svg){kind=logo}
