Відео

Nice introduction to events but as the others said i dont think you have the expertise to be making this types of videos (yet) In a real game, id assume you would have those balls inside a list/array or other datastructure, so you could just inject that into the ball manager, much easier to understand and cleaner. Events are fun but i think they are more useful when used by SYSTEMS to communicate with other systems. For example, having "physicsManager" inform "ballManager" of a collision or something, since you dont want those 2 systems (or 3, 4 or 1000, plenty of systems would want to be modified about collision) to know about /depend on each other :)

Can anyone tell me how to make that lightning animation, please?

wouldn't 'a' plane/car be the concept and 'the' plane/car be the OCCURANCE of that concept instead? since 'the' implies a specific plane/car and 'a' implies its generalized?

I like to use interfaces for this pattern. Then you have control over which type of collection the callbacks are stored in (event is always basically a list), and you can add modular logic as needed. For example you may decide you want to store the balls in some specific order - you could then just add an Order property to the interface and use it as needed.

Kinda backwards. The balls shouldn't know about the manager at all, as they are at a lower level. So the events should be on the ball side. Because the balls get a dependency now. Imagine you want to replace the manager, now you have to modify the ball code as well.

can I use particles system from specific game?

You explained the Unity static class and event concepts very clearly. I had trouble understanding the specifics from the Unity chapter alone, but this filled in several gaps. Thank you!

This is called the pub/sub pattern. It's only one of many, many ways to do message passing in OOP, and definitely not the end-all be all. The pro is it's simple, but the cons are it's relatively slow and very difficult to scale without major maintainability costs. Great for small projects!

To anyone reading this comment: avoid doing this as it will really make your code hard to manage later when you need to add bigger features to your game (think about YandereDev code for example). In this case what you should be doing is have your ball manager NOT BE STATIC, and have it somewhere in a game object. Then in the script where you want to reference the BallManager, have a field in the following syntax: [SerializeField] private BallManager myBallManager; The SerializeField attribute will let your reference the ball manager in your scene directly in the editor when you click on the script to which you want to add the reference. This will make things a lot more manageable as you can clearly determine which objects interact with your ball manager without having to look everywhere in your code! Plus If you want to have multiple ball managers running at once, this solves that issue. To the video creator, please be careful when trying to explain programming concepts as a non-programmer. A lot of these tips can hinder beginners and set them up for failure. Leave it to the pros out there :P (no offense, in my case I wouldn’t teach plumbing just because I fixed a pipe once)

If you have such a mess of a code that you need to step through with a debugger - you might be doing something wrong. A simple temporary Debug.Log here and there for a quick check should be enough. Otherwise you can also check the call stack to see what was called, and where it went wrong.

DO NOT FOLLOW THIS Thank god this "only" got 46k views. Overcomplicated code, faulty examples and misinformation. Spend more time learning unity than editing funny images on the video if you want to help people.

This is why people who dont understand a thing should not make videos about it. You are showing people really bad practices...

do you have video on how to make these animations

Correct my if I'm wrong but at 6:56, shouldn't you subscribe to the event in the start method? Cross reference another class in the awake method can be tricky because you'll end up in a race condition. With subscribing in the Start method we make sure that BallManager is 100% initialized before Ball.

Excellent stuff, thanks for breaking it down so well.

this was very, very informative

The best!

U explode my brain. I didn't even suspect such a powerful potential of the particle system

Dani

Youre a hero

awesome vids.

Great explanation. Super helpful

I've seen good tutorials in the past. This was a game changer for me. Thank you.

Thank you, with your great tutorial I save a lot of work and heachache

Good video, thank you!

Great video!!! thank u! <3

Thanks for sharing

It's amazing, I only needed to watch the first 4 minutes to click subscribe

For every beginners watching this video, please don't take it as a good practice (I mean it). This is actually the opposite, and you should absolutely avoid to program like this. Let me explain a bit more : Singleton design pattern (ensuring that a class has a single instance, and providing a global access point to this instance ) is what the creator wants to show you. First, the singleton pattern is not correctly designed, and doing like it's done in the video can lead to errors. Exposing global variables like that, accessible everywhere in the code, is of course the easiest (read : laziest) way to make components communicate. The biggest issue with that, is the control flow of your application. In the example that is shown in the video, it is all fun and games, everything works properly, because it is a super simple example, with a manager and a ball. Let's say you want to create a big project, with NPCs, World Building, Quest system, inventory etc etc ... If you design your application like this, it means that every system you create, has the possibility to communicate with every other systems of the application. As the project will grow, this will (100%) lead to systems that should have no connection whatsoever communicating together, and therefore, create an absolute undebuggable / unscalable project. The way to go, is first to read actual real books or articles about software design before going to youtube for some obscure tutorials. Advice number one, and probably the most important : learn the SOLID principles , apply it whenever you can. Learn about inversion of control, read articles about design patterns that are ACTUALLY real scalable, good practices. Of course it seems harder, but if you really want to progress, and make real projects, this is the only way to go. And basically, every "problems" that the creator thinks he is solving by using a singleton are actually only problems when you don't know how to handle them (this is no criticism, just a fact). First example : when he says "If you have a lot of balls that you want to communicate, it is tedious to assign them in the editor manually". Solution : Create a serialized array of balls. You can then select them all in the editor, and drag and drop directly to the ball manager script. Second : When he says "If the manager instantiates a ball, he won't be able to communicate with it" : Wrong ! Create a prefab of the ball, with the script Ball attached on it , and do like this in the manager : [SerializeField] private Ball ballPrefab; void OnEnable() { Ball ball = Instantiate(ballPrefab); ball.DoSomething(); } It is as simple as that. If you want to create multiple balls, iterate through an array of the size you want, and instantiate the number of balls you want (and it is actually not even the best way to do that, a pooling system is better to avoid garbage collection overhead, but this is another topic). If you want to keep a reference to the balls in the scene, create a list at the top of the class, and add the balls that you instantiated to this list. I hope this will help a poor soul seeking for answer about unity, which is of course a big, complex topic ! But please, don't take advices like this, this is bad practice. Read before youtube ;)

Thanks mate!

thank you so much for your tutorial

Can you just use "FindObjectOf..." to do all this?

So its like a Hearer and Speaker.... (Just Guessing) Where the Hearer is the static BallManager NameInstance; and the Speaker are the event static Action OnEnableBALLS; Hmmm.... so to talk to Statics Objects i "need" a Action On.... ok... theres probably other methods but im guessing this works in most Situations

i like the ball counter

Thanks for this informative video

bro what are y doing? Just use a List<Ball> balls in the manager class? You are mixing a lot of weird stuff ( I didn't watch the events stuff though).

Nice video. At the end, might be beneficial to comment out the "timer -= Time.deltaTime" so that the timer is not changing on update, but will change for however many seconds you've paused. :)

a perfect tutorial, thank you for your hard work and time

lol. I liked the video, then read the caption about taking a shot every time you said ball.... and I was sold on subscribing. That is the solid comedy.

Thanks.

hi! I'm trying to upload a 3d model to unity store, they say "Check Model Import Logs Model assets should work without issues. Please make sure that there are no errors or warnings when these models are imported." what do I do wrong? What does it mean?

I rolled my own power plant.. best decision I ever made. The money I make from being an energy mogel far exceeded what I could have made with my 2d metroidvania platformer.

A complicated problem demands a complex solution. Using the simple solution can come with the cost of neglecting or overkilling certain aspects. In an example of a baby shape sorter, round hole is needlessly large for a small square piece, but a large square piece would fit in only with its corners cropped.

I think I watched this video a year ago, and I didn’t understand it at all. Recently I’ve been working on a lite RTS game with 100s of different objects, systems, managers. I have actually been using this exact pattern and it works so well! It gets really powerful if you make a scriptable object for the balls. Then each can have specific properties and data you can either pass through the event or reference for very precise control.

It is important for a manager to communicate correctly with their balls

You're really underrated man, like your last video was awesome and now you suddenly appear with this piece of art! The warning sign XD 0:20

Thank you bro!

your explaining is amazing thanks [ : )]

3:16 I didnt expected to be insulted like that lol Amazing video btw thanks

thanks dude