Видео

Man, u've create nice content, sad to see that channel is abandoned :(

Thank you, very clean and useful explanation with examples

this was the most comprehensive, simple and useful video I've seen in months..

Thank you so much it's so easy and help me a lot of in my project

Depth of field will ruin performance

Try to guess "Demeter" Stardew Valley lol

thanks you so much but i have a dumb question, can I add multiple functions into one interface or i must avoid that? Anyway tanks you very much !

what if i have other post effects, will it turn those off too

The main mistake of the author of this video, as well as others like it, is that they consider the state machine as a tool for setting the state. But one should use a state machine as a tool for determining (!) the state of an object. Yes, there is a tricky definition of a state machine, but who reads all this... That is, describe all the states of an object, determine them and, based on the state of the object, execute methods. More complex projects may have more than 1 state machine. The second mistake many authors make is to copy the animator’s unity ideology. They argue that an object must change from one state to another. For example, from waiting only to running. Apparently they forgot about the wonderful animator's hell, which everyone has already said 1000 times. Modern animation programs don't have any states. You can call any animation from code. Just like in Unity, but we love states - arrows, entanglements....? And finally. Multiple returns in code. We moved away from multiple ifs to returns. And to empty return. And, according to the idea, return should return something - that’s what it was invented for, but no, we use it as an analogue for stopping the execution of a method. Also multiple returns are not very good architecturally. Since we have 1 entry point into the method and 10 exit points from it. There are other problems with this approach, but I probably won’t describe them...

It's cool in a way, but there is a priority, can't you have an if and a print depending on wich one triggers ?

Thank you for this tutorial, it was really helpful! Though this makes me wonder: is the interface only accessible to the script that defined it or is it accessible from any script? And if it isn't, how can I for example make an object damageable by different objects (and not just the player)?

Amazing explanation

what if you have a special attack for example when ur sprinting and jumping? how would you fit that into this structure

The animation not working if there is math in them is very true! And I'm one of them who use time scale, i created.. was it if statement to check if the time scale is above 0 then the math is done and if less it will stop calculating so the animations wont brake. definitely i crate a small test to see this out !

wow i was almost going crazy trying to understand from other source. thank you so much

I can't begin to tell you how much this has helped me, Thank you.

So, with mine, It somewhat works. The keybind works, etc etc. shows green in editor, HOWEVER, When actually playing on that map, pressing N doesn't make the camera lens go green, it just brightens up the world a little. Any reason on why? nvm I broke it even more, upgraded to urp and it doesn't even show anything now.

that was really usefull and clear , im just not sure .. where do you write the Interface - > public Interface Idamageable { void damage(amount) }

Great Video!

Perfectly explained fast and clear

Thank you! This tutorial really helped me, and I appreciated how quick you went through with this one. I really didn't want to use Timescale as it felt like I wouldn't have any control.

This saved my life

why you need to write all of them when you can just write in 1?

this video explains interfaces better than my college classes lol

GetComponent can retrieve Interfaces? I thought it could only grab actual components, makes the name misleading.

this is good but how do i check if the collision is not in play, because I'm using a boolean in my code to check if the enemy is grounded or not using this interface method

I will just use events in tandem with time scale. Even more control and efficiency.

Thank you for not using the word C.O.N.T.R.A.C.T. once!!!!

To the nay sayers in comments, this is how you are supposed to pause. Dont be lazy and sloppy take your time to make your game right. Events are efficient and performant and this removes any bugs with pausing from the various other lazy methods.

This might seem like a stupid question, but what are you doing in this line? EnemyTarget target = hitInfo.collider.GetCompoment<EnemyTarget>(); is this a way to create an instance of a variable from another class? What is is required to do this? I understand the rat cast part I am actually only confused about the declaration of target

I could do this with sub classes. Interfaces just makes things a little bit longer. Then why are they exist? I never felt like I really need interfaces.

damn such a great explanaition. definetely deserves a sub. thank you so much man :D

Thank you, I am currently making something where the player can move in 2d, but needs to interact with stuff and need something that allows them to interact with a button without knowing what the interactable object does

i doubt u can come up with a dev name for Portal or Portal 2 lol

"find a script that will be affected by pausing" - like almost all of them? Do I need to put all this amount of code in every script that is affected by pause?

You are actually teaching here how to create a singleton and use delegates and events. This is not a tutorial of "better pausing technique" in Unity.

Doesn't work, tried to make it work with many and many changes but nothing

I never fully understood interfaces and this perfectly explains it. Thanks.

This is incredibly helpful. Thank you!

code link cant open :(

i cant reach code links

this was an amazing explanation, i already used and fully understood interfaces, but this helps increase the Modularity of code , which decreases time to add new features, and removes dependency within code , which can then further be boosted by the observer method

I can't express how much this 4 minute video has helped me. Thanks so much!

Thank you. Implemented... wow.. so much easier than the jumble i was working with. Great, consise, easy to follow tuturial.. and exaclty what i wanted and how i wanted it to work. Damage ammount on the thing that actually does the damage... then health on the thing that actually looses health... so simple.. no of these weird incorrectly placed and refenenced tangles

I thought I was watching a tutorial Little did I know it was actually a speedrun.

But watch out, often clean code is very slow code, sometimes even many times slower.

That is a good start. I would also add that all the if should be extracted to a guard method that returns a tuple (bool isAttackable, string message) = CanAttack(..); Methods must only do one thing. This one is doing two: 1. checking to see if you can attack, then if you can then attack. This makes the code much more testable.

Better yet, use chain of responsability. A list of classes implementing the same interface, each one checking for a specific condition. The method walks the list of classes before performing the action and returns early if any of them fail. That way you just need to add a new entry to the class list when adding a new restriction, leaving the original method untouched.

i understand it now, you are a beast

I'm still not sure if I need to be using interfaces or a base class on my current project