Originally Posted by cohadar
Actually it is not because you cannot have 2 onDamage triggers on the same unit (try it and see.)
I just tested this and there were no issues - multiple damage detection triggers per unit would all trigger whenever the unit took damage, resulting in multiple debug messages. Multiple damage detection triggers per unit do not seem to be an issue.
Even if they really were, it's really a no-brainer to turn off aBuff damage detection and have your own damage detection call the appropriate abuff functions instead.
Unless you have other points to make, I'm going to consider this system to be properly named.