I’m not sure what you’re trying to say…
Binding is for when the function doesn’t have a convenient self alternative like OnTakeAnyDamage does in the form of AnyDamage, or when the target is not self.
Not every event has the convenient self binding, and you often care about targets other than self.
You can bind another object’s events to your own functions, and use the DamagedActor pin to tell which actor got damaged.
For example, say my actor wants to get notified whenever a different actor gets damaged. That’s not possible with Event AnyDamage, because the target is self. If AnyDamage is getting called, that means this actor has taken damage.
On the other hand, if you bound an event in this actor to that other actor’s OnTakeAnyDamage event, then you’d be able to do what you wanted when they got damaged.
Furthermore, if you bind multiple different actors, even multiple types of actors, then you can use the DamagedActor pin on OnTakeAnyDamage to be able to know which got damaged, and act accordingly.
So to directly answer the question, you would use AnyDamage (the self binding) if you only care about self, and bind when the target is not self.
In this case, there is no reason at all to bind. This is the exact case that AnyDamage exists for- to prevent you from needing to bind OnTakeAnyDamage when you only care about self.