@Islam Abukoush wait WHAT

@Islam Abukoush You really played with my emotions like that. Damn.

@Islam Abukoush Bastard :,)

True

Is he dead?

Well didn't work for me. But I should mention I'm just a beginner and I barely understood all of Brackey's pipline in this video

@@3d_toys Rly ? because that's exactly what I thought to do when I watched this video, However I didn't test it so maybe there is something that i'm missing

I wonder if this has actually worked

Sykoo but i thought you were the “screw the performance!” guy xD

@@ryanrichardson4056 I used to then I figured out you could have 3x the objects for the same performance.

I am a dev

Can you be specific about how to turn it into static class? and with the singleton Instance thingy does it not mean that I can also access its variables?

@@bicuswang5149 Just remove its MonoBehaviour inheritance and make the class itself static. Make all the variables and methods static, remove the SharedInstance field as its no longer needed and you have it. After that you just need another way of automatically calling the Awake method for the class to initialize properly. - You can do that by either using a RuntimeIntializeOnLoadMethod attribute on the Awake method, which will automatically invoke the method after the first scene is loaded. - Or you can use a static class constructor, which is a class constructor with no parameters that gets automatically called once as early as possible. After that you can use the class like before, just instead of ObjectPooler.SharedInstance.GetPooledObject you just call ObjectPooler.GetPooledObject. Static classes are a better way of doing Singleton MonoBehaviours that don't need any of the MonoBehaviour features (like the update methods, or access to the parent gameobject, etc.) as without the extra MonoBehaviour stuff they are more lightweight and easier to use/understand how to use them.

​@@nocturne6320 If we're not using the Mono behaviour class, than how are we going to add the list of Item we need to pool from the Inspector ?

So what you mean in the point 3 is that we start Instatiate the Game Object and put it on the pool when they really are needed(requested) ?

@@kuroakevizago You could have another class (monobehaviour) with just a list of items to pool that you could pull the items from. As they are needed only for initialization you could destroy that script afterwards. Or add some method for it into the class, which should be there anyway as it could be useful to request a new object to be pooled, or request an item that is already pooled to have a bigger pool size.

Using singleton is bad practice actually. I can understand that brackeys did that for beginners, but anyway. You can always create a [SerializedField] in CubeSpawner and put your ObjectPooler into that field from the inspector.

@@IluXa4000 Singleton is a base pattern, why is a bad practice? Can you link a resource can prove your affermation?

@@IluXa4000 Like what? From when singletons are bad practice? Please explain and give us a resource of this revelation. Singletons are totally normal and fine and used often. As often as you have some unique class that should be instantiated once and all other scripts have access to it.

but i think the interface was not necessary, I did this with a normal public method without creating any interface.

@@giovanni.piedimonte lmao hegot ratiodin a youtube comment section

He tends to do that.

Seriously. I'm amazed how he breaks complex things down and how well he describes each feature.

that's not gonna work, try: public string Brackeys = "Best Unity Tutorials";

Simon Madception love it XD

But for better performance maybe you could go for this: public readonly string Brackeys = "Best Unity Tutorials";

It should be [ReadOnly] not readonly

Hello, how it is possible to get that cool blue background?

you predicted dani's muck game

SPAR Group I was thinking about using it for projectiles. They are one of the most expensive and common things to spawn and you can predict the pool per weapon (either max magazine size or by Max range / velocity * Rounds per second). But I like the idea for particle based objects since they are expensive.

@SPAR Group that's not what object pooling is for 😂, muzzle flashes don't need to be pooled as they only have 1 per gun, not an unknown amount

Ya, that region bit it the most useful thing in the video. Don't get me wrong, object pooling is great. But that applies to less than the regions stuff would, I would think.

Would it be better if he was miserable and frowning?

I've been watching a few Brackeys' tutorial series and his good mood really made my day, so I'm going to put it in a "good thing" bin.

Kaze Well you can minimize cheating just by having anything important to the game (damage handling, move speed, player positions etc.) running on the server and only having clients send input to the server. Then your only problem will be bots.

Thanks to the both of you. This really helps!

jeka7676 sweet dude. Yea, my game is a single player but with a global leaderboards. Well, I'm trying to set the leaderboard now haha. Thx again!

Kaze I mean you'll want to look more into. The topic is much deeper, but yeah that's the general jist of it.

I doubt it hard that he will do such an extensive series.. I asked him in an email months ago how are backends in some round based mobile games implemented and if he can recommend any providers - no answer. It is almost all about back end server programming and session syncing - easier for round based games and harder for real time action. There are some BaaS providers, like GameSpark, that decrease the steep learning curve and have extensive documentation and tutorial. But if you use that providers and have a f2p game and you have what I call "sudden success" - means a lot more that 100 000 monthly active users and the in-app-purchases are not generating capital, you are f*cked with a huge bill on the table.

This isn't recommended. This video is garbage. I tried implementing this to my mobile game and it causes a lot of crash at the startup. That because the start method contains a lot of instantiation. If I have 300 pool game objects the object pooler will need to call instantiate method 300 times at start method in just a single frame. One frame = 300 game object instantiation = slow and freezing mobile game

Well yeah, the title isn't "Object pooling in unity, plus extraneous capabilities" Just pooling...

Hello, how it is possible to get that cool blue background?

Are you still having issues with this? If so I'm happy to try and help. Without the code it's a bit hard to pinpoint, but what I'd try is putting debug. Log wherever the rotation is suppose to occur and see exactly where it is stopping. That should hopefully give you an idea as to why it's not working.