Відео

there is no negative prompt, did they remove that now?

Nice video! I know it has been a while since the video was posted and hopefully you see my comment. I see that you wrote a function in a ScriptableObject, but I have seen it lately in another tutorial and into unity forums that should be avoided as the main purpose of SOs is to hold data/properties. Do you have any knowledge on this? I am actually asking as I am currently struggling a little to create my own ability system due to the complexity I want to apply and I believe it could help if there is no overhead/less performance on SO functions.

4 years spent with unity learnt 1 or 2 things from this video thank you

[SelectionBase] is actually awesome. I recommend just making a script where that's the only thing in it and add it to every object you need it for, instead of adding [SelectionBase] into the top of all your scripts! Genuinely some great tips in this video!

How did u do this water terrain?

Cool tip. Is there a way to do it through code on runtime?

Is this compatible with online systems like unity or photon networking? Can I make it run?

Sneaky way of advertising your own asset, I like it ;) Jokes aside, I just bought soap yesterday, I can't really use it yet since I am a beginner. But I got a job as solo dev for a video game and soap helps me attack the steep learning curve, great asset

Excellent!

Isnt just reading value from another script easier than having to create soapvariable, hook up events and drag and drop them?

few points I'd like to add: - a public method in a script is a good indication of an interface - while utils class is a nice and a common pattern, I usually prefer to extract them utils to separate classes, like the Closest Enemy method, it could go into an enemy manager, grid system or graph or whatever - for the love of god, if you have an if statement and no (else) and nothing beneath it, just use a guard clause it's easier to read - good video and nice tips, well done

I don't know where did you get that information that GetComponent is slower than getting a reference in a private field through a dependency injection, you may be misunderstand them with FindWithTag, FindGameObjectsWithTag or Find which have to search in the hierarchy. GetComponent<T> is as fast as accessing a generic class. having too many variables exposed in the editor is also an overhead for every time you compile.

Very useful tips!

While I am far from an expert dev, I tend to disagree on the last point when it comes to object pooling specifically. If I know the type of game I am making, I want to know if I am pooling or not from the beginning. It changes code where things die, it changes how I handle any projectile spawning mobs I may have. It has some pretty big branching effects that can be a bit messy to go back and change later. Otherwise I agree that you shouldn't optimize prematurely

2 things missed in this. 1. Don't use update unless its vital it needs to be done every single frame. If u want to check something continuously just make a Coroutine because once u have checked it u can just stop a coroutine and there are a lot less errors and a lot less resources being utilized for that checking system. Imagine checking continuously then once you find it it will keep on checking degrading the performance. Have it check continuously via the Coroutine once found execute the function have the Coroutine stop then once you need to check again have it start the Coroutine once again. 2. Always make your functions private void unless you need it to be accessed by something. Having just void then the function name is just lazy and doesn't give much help to others trying to use or look at your code.

really great video thanks😍

Deserialization at runtime is not "zero performant cost", there is of course overhead to it. But yea, deserialization is faster than a GetComponent call.

4:18 nice subs added :)

thanks for the tips, I sometimes make some of the mistakes mentioned in this video while writing scripts. keep going :)

What if you instantiate a prefab from assets then you can't assign scripts from hierarchy to the prefab.

DRY is a complicated one; The code you used in the example is perfectly fine. I just can't help myself but to say: I DON'T WORRY about repeating code. I think repeating code can be great given the circumstance (example incoming). What you shouldn't do is repeat CONCEPTS. For instance: lets say you are making a web page, and it shows your username at the top corner of the page,.. you can make like a "DisplayUsername()" so that it draws your username and avatar and when clicked allows you to log out and go to your profile and stuff - that's great, and anytime you want to show the users avatar and stuff, just call DisplayUsername() and you're all set. What eventually happens is there is going to be another place in the website, where you need to display the username again... lets say, you are making a comment section and you want to show their username there, so you think "I know DRY, so I'll just use that method I got for this!", so you call DisplayUsername(), but the icon is a little too small for that, and also the name needs to be a little bigger, and also you want to disable the logout and other options when clicked ---- so, as a great programmer that DRYs, you add configuration arguments to DisplayUsername, so now it's DisplayUsername(isTinyIcon, isNameLarger, isLogoutEnabled);... and this method grows and grows and grows.... each time creating a more and more complicated swiss army knife. This works great - one method to do all this stuff - you really pat yourself on the back thinking about how many methods you avoided making and how this one tool is very amazing and much wow.... until.... some changes start messing up other changes... and maybe some options conflict with other options --- and you're getting complaints... or maybe the business logic changes and we need to add stuff... --- all these things now are competing against each other and it makes maintainability almost impossible without going completely bonkers playing whack-a-mole against uncountable bugs and drowning in technical debt. But what did you do wrong --- the username code is all in one place and you didn't repeat yourself a single time.... IN CONTRAST, you could not DRY and just write out what you need specifically in the instances you need them... the username in the comments section is just done DIFFERENTLY with much of the same code, than it does in the top corner, or anywhere else. YES the code might look almost exactly the same, as if you copy and pasted it but just changed a few little things... but that's the strength of it. The reason for DRY is: if you have a requested change for a CONCEPT, you would only need to go to one place in the code to update it... so you don't have multiple places and forget one and then just once in a blue moon, that one specific use case that was missed is run with the old bug in it. DRY is not trying to save lines of code or save amounts of methods in existence it's just for maintainability... the second it's less maintainable to make it more DRY, then that's the second you lost the plot. Dry is one of those 'to the hammer, every problem is a nail' type things... the real quality code understands why and where DRY is important.

I appreciate the attempt at 5:03 to be more performant, but Vector3.Distance reads better. IF there is a real performance consideration (which I doubt), I would definitely abstract that out to a utility class, rather than just assume anyone reading that will know the intent of (x.pos-y.pos).sqrMagnitude ---- because at a glance that doesn't mean anything. Ideally C# would allow for static extension methods eventually, and when they do that's a good candidate for Vector3.QuickDistance(x, y). Until then, either having a helper method in class, or if ubiquitous like in this case, having it in a Vector3Util.QuickDistance() is a good idea, to communicate what the intent is.

_ability.Update() and the like are not right. 3:54 You need to choose for ability to be monobehavior or not, if not (and they inherit from object) then maintaining the updates manually like that is correct (create an update method and even passing in the deltaTime is great) - if they are (which was the case in the example where you extend from monobehavior), then you should NOT manually maintain the update for them, and they SHOULD be added as a component on the host game object.

IsDead is begging to be a guard clause on line 66, if(IsDead) return;//or similar

I was going to rag on you for the second one, but you came around to exposing that variable in editor and setting it there - My experience is getcomponent is needlessly slow and shouldn't be used in cases where you can easily set it at compile-time in editor.

The selection base and component container selection when using debug are awesome. Thank you!

Definetely need to try SOAP!!!

How can i preview the image in the inspector like that?

Thanks. Useful, I already know quite a bit about most of these. But what was so good about your video is that you showed each one in use which is soooo much better than just recommending them. Well done. Good luck with your subscription growth.

good tips thanks!

Would have been good to call out that Soap is an asset you made and perhaps compare it to the alternatives instead of omitting that fact completely. Nothing wrong with promoting your own stuff but it comes off as a bit dodgy here since you don't even mention it.

Awesome video! I've used DOTween in almost every project. If you like Odin and SOAP, then I would also recommend a new one called Scriptable Sheets. It makes managing Scriptable Objects a breeze, and without any coding!

Great video! The synergy section was great. I really appreciate you covering Unity assets. I noticed most if-not all of these assets have been on the store for quite some time. I also noticed you mentioned SOAP for Scriptable Objects. I wanted to recommend a brand new asset (released last week) called Scriptable Sheets. It's available now on the Unity Asset Store, and tailored for Scriptable Objects lovers!

One of the best "tool recommendation" videos! Actually showing their use in a game (both standalone and in the synergies section) makes their benefits much more obvious. Thank you!

Thanks for this

thank you!! Have you tried soap's alternatives? is it really worth it if you know how to design the architecture by yourself? soda seems good as well I'm a huge fan of SA architecture but I always build it from scratch by myself based on Ryan Hipple's 2017 talk.

SR Debugger looks great, but unfortunately it seems to be abandoned by the dev. Not updated in over 2 years.

The synergies section at the end was a nice touch

В натуре четко. Спасиббо

Odin is nice but the company behind it requires you to sign up and use their website to update instead of just doing it in unity like all other products BEWARE

App?

finally a real unity tips i dont know

amazing video, thank you!

Helpful ❤

Cool, I was makign something similar myself. I'm interested in buying it. If I advertise it on my channel can I get a discount?

Fantastic

Actually 12 Tips not 11 😆

Bro how much it costs to remove unity splash screen for 1 game I am new to unity community ,please answer bro.

🤯