@@user-nn5st8qm5v In Unreal Engine, the `OnAnyDamage` event is typically not called if the damage value is less than or equal to zero. This is because damage values that are non-positive usually indicate that there is no actual damage to process, and thus the event doesn't need to be triggered. However, including the check for `Damage
For anybody in the future. I'm running UE5.1 My UFUNCTION() is void TakeDamage(AActor* DamagedActor, float Damage, const class UDamageType* DamageType, class AController* InstigatedBy, AActor* DamageCauser); and then binding that to the owner function within the cpp file is AActor* MyOwner = GetOwner(); if (MyOwner) { return; MyOwner->OnTakeAnyDamage.AddDynamic(this, &UHealthComponentSecond::TakeDamage); } It's frustrating having to use outdated tutorials (even the official documentation is outdated right now) but always remember that if you aren't struggling, you aren't learning. Good luck. Great content btw, not much you can do as updates happen haha.
just wanted to say im really glad you take a "modular" approach that so many tutorials do not take. coming from several years of unity, it has been a little painful watching some tutorial videos as they leave little room for further implementation or expansion. good video!
Thanks. I'm getting a lot of Unity comparisons recently, I wonder why... But yeah, component based workflows are heavily overlooked in unreal which is unfortunate. My upcoming content will have a stronger focus on that too.
This is awesome -- never thought about making things such as the health modular! This is such a great tutorial generally for how actor components can help you separate out things from your character scripts. Thank you!!!
This was - if not the best - a great showcase and explanation while providing a practical toolset I can use further into my project. Health component may be simple, but the knowledge gained is massive. You are really good at this, and I can't wait to watch more!
If you can't compile due to declaration of 'Owner' hides class memeber. Change AActor* Owner to MyOwner (or any other variable name that is not 'Owner'). That solves it.
Doing a Udemy course called ‘Pro Unreal Engine Coding’ by a guy called ‘Rob B.’ I thought you sounded a little like him. Then I found out you’re a Rob B. too! You’re not the same person of course but I instantly trust you lmao
Noticed that at least here in 4.25 the first parameter in the signature you copy from is now an AActor OnTakeAnyDamage, and NOT the AActor* object in the video. Including this will give you some fancy C2664 error, but simply removing the first AActor object fixes everything. Other than that, thanks for teaching me about ActorComponents. I could've used them far long ago to avoid the mess my character is.
Thanks, Mikkel, that is quite likely a 4.25 update then. There've been a lot of changes in the latest version that seems to have changed and approaches I've become familiar with no longer work. Some of the other videos in this playlist have commented saying that certain parts don't work. I am currently going through a new playlist on C++ covering more basic concepts so I might redo these videos too to account for the recent changes. Good to hear you found the solution though and thanks for sharing.
Ran into this too [4.25.1] - wish I'd seen your comment a half hour earlier, ran my tail in circles for a while (it gives the error on the call to the delegate line "Owner->OnTakeAnyDamage.AddDynamic(this, &UWhateverComponent::TakeDamage);") - fix, as stated, is to remove unneeded 'AActor OnTakeAnyDamage' param entirely. Cheers Mikkel.
I was just testing some values and I noticed that when I changed the DefaultHealth in the editor that the health is still 100 instead of the new value I had put in the editor. Is there something I'm missing or would I need to set the health = DefaultHealth in the constructor in blueprint?
Hey as far as handling damage. Should I just use the built-in functionality provided by unreal or create my own functions? I am going to have a couple types of damage that apply damage with some accompanied effects. Ie) Run through fire: damage over time, Run over Ice: slow character movements speed.
Depends on the project really. Having your own health system can be useful but also overkill for smaller projects. For what you mentioned I'd probably roll a custom health system but even then you could assign the existing damage type to different elements. There's no right or wrong answer really so sorry for the washy answer there.
That just means I didn't have an error there, the compiler won't ignore an error and just compile. Either something has changed since I released the tutorial, so you might want to check the documentation for the version you're working in. Or you've missed something somewhere else in the code that relates to the MyOwner variable.
VS doesn't find anything, I guess it's because of 'hide external dependencies folders' setting that I've set to true previously. But I can't set it back to false, this settings is greyed out now, any advice on how to fix this?
In this video, we implement a simple health component which will for simple implementation of health to any other Pawn or Actor class in your games.
This is a great tutorial, but you don't need to check Damage
@@user-nn5st8qm5v In Unreal Engine, the `OnAnyDamage` event is typically not called if the damage value is less than or equal to zero. This is because damage values that are non-positive usually indicate that there is no actual damage to process, and thus the event doesn't need to be triggered.
However, including the check for `Damage
For anybody in the future. I'm running UE5.1
My UFUNCTION() is
void TakeDamage(AActor* DamagedActor, float Damage, const class UDamageType* DamageType, class AController* InstigatedBy, AActor* DamageCauser);
and then binding that to the owner function within the cpp file is
AActor* MyOwner = GetOwner();
if (MyOwner) {
return;
MyOwner->OnTakeAnyDamage.AddDynamic(this, &UHealthComponentSecond::TakeDamage);
}
It's frustrating having to use outdated tutorials (even the official documentation is outdated right now) but always remember that if you aren't struggling, you aren't learning. Good luck.
Great content btw, not much you can do as updates happen haha.
just wanted to say im really glad you take a "modular" approach that so many tutorials do not take. coming from several years of unity, it has been a little painful watching some tutorial videos as they leave little room for further implementation or expansion. good video!
Thanks. I'm getting a lot of Unity comparisons recently, I wonder why... But yeah, component based workflows are heavily overlooked in unreal which is unfortunate. My upcoming content will have a stronger focus on that too.
You have good videos. Please don't abandon your series on Unreal Engine in the middle like most people
Thanks, I guess you mean the C++ series specifically rather than just Unreal in general?
@@DevEnabled Yeah, there are very few good free series on C++. You have a great way of explaining everything.
This is awesome -- never thought about making things such as the health modular! This is such a great tutorial generally for how actor components can help you separate out things from your character scripts. Thank you!!!
Great to hear a new solution has been presented. Components are a very flexible way to work.
This was - if not the best - a great showcase and explanation while providing a practical toolset I can use further into my project. Health component may be simple, but the knowledge gained is massive. You are really good at this, and I can't wait to watch more!
If you can't compile due to declaration of 'Owner' hides class memeber.
Change AActor* Owner to MyOwner (or any other variable name that is not 'Owner'). That solves it.
Best Unreal tutorials on youtube!
Appreciated, always great to know they're helping.
Doing a Udemy course called ‘Pro Unreal Engine Coding’ by a guy called ‘Rob B.’ I thought you sounded a little like him. Then I found out you’re a Rob B. too!
You’re not the same person of course but I instantly trust you lmao
wow I was searching for this! Thanks!
Thanks, for showing the C++ implementation
Noticed that at least here in 4.25 the first parameter in the signature you copy from is now an AActor OnTakeAnyDamage, and NOT the AActor* object in the video. Including this will give you some fancy C2664 error, but simply removing the first AActor object fixes everything.
Other than that, thanks for teaching me about ActorComponents. I could've used them far long ago to avoid the mess my character is.
Thanks, Mikkel, that is quite likely a 4.25 update then. There've been a lot of changes in the latest version that seems to have changed and approaches I've become familiar with no longer work. Some of the other videos in this playlist have commented saying that certain parts don't work. I am currently going through a new playlist on C++ covering more basic concepts so I might redo these videos too to account for the recent changes. Good to hear you found the solution though and thanks for sharing.
Ran into this too [4.25.1] - wish I'd seen your comment a half hour earlier, ran my tail in circles for a while (it gives the error on the call to the delegate line "Owner->OnTakeAnyDamage.AddDynamic(this, &UWhateverComponent::TakeDamage);") - fix, as stated, is to remove unneeded 'AActor OnTakeAnyDamage' param entirely. Cheers Mikkel.
Thanks bro, helps a lot
@@rushikeshbhandare8946 Great to hear.
I've learned a lot, thanks sire.
Please implement c++ event dispatchers in upcoming tuts :D
Cheers !
Great tutorial, just used it in 5.1 thanks!
So good! keep em coming! best youtuber for Unreal and c++!
Perfect
Thanks for the video, helped!
Thank you very much!
You're welcome!
Thanks for the playlist!
Small buglet in the name of the video: "Damage", not "Damange"
thank you and thanks for mentioning it, I missed that somehow.
I was just testing some values and I noticed that when I changed the DefaultHealth in the editor that the health is still 100 instead of the new value I had put in the editor. Is there something I'm missing or would I need to set the health = DefaultHealth in the constructor in blueprint?
Hello, at 13:00 it does not show any health component. Any help would be appreciated
If you've been following the tutorial closely and it hasn't shown up, try recompiling it in-engine. Make sure the name you're using is correct too.
Hey as far as handling damage. Should I just use the built-in functionality provided by unreal or create my own functions? I am going to have a couple types of damage that apply damage with some accompanied effects. Ie) Run through fire: damage over time, Run over Ice: slow character movements speed.
Depends on the project really. Having your own health system can be useful but also overkill for smaller projects. For what you mentioned I'd probably roll a custom health system but even then you could assign the existing damage type to different elements. There's no right or wrong answer really so sorry for the washy answer there.
How is ur Compiler ignore the MyOwner Error, in my code it giving me error and wont build the code.
That just means I didn't have an error there, the compiler won't ignore an error and just compile. Either something has changed since I released the tutorial, so you might want to check the documentation for the version you're working in. Or you've missed something somewhere else in the code that relates to the MyOwner variable.
@@DevEnabled your compiler is marking it red. it is also not an attribute added anywhere it can access.
think it is ignoring it completely.
For me I had to #include "GameFramework/Actor.h" in the .CPP file
@@SlumpogMillionaire Thank you! You got it!
I want to play hit animations that have different enemies depending on the player's attack motion
Can you help me?
7:48
VS doesn't find anything, I guess it's because of 'hide external dependencies folders' setting that I've set to true previously.
But I can't set it back to false, this settings is greyed out now, any advice on how to fix this?