I just think this is too simple to actually be a resource. I'd struggle to justify approving it because all it does is select your timer system for you, write a simple struct type, and implement a simple callback. There's no mapping knowledge or research behind it beyond simple timer attachment.
Aside from that the application is terribly limited, and if it wasn't it would probably skip straight to over engineered. I don't think this is the sort of thing that should be submitted as a resource because it is faster to write yourself than learn, more flexible, and more suited to the individual case and map author's preferences.
For example, what if I wanted a unit to be damaged over time through a lightning bolt? Or wanted to detect the damage type? Or even just wanted a projectile to hit the unit from the caster, or wanted to deal damage based on the health of the unit, or unit type, or didn't want the damage to stack (like in a buff) or ...
And we don't need a system to accomplish those things. It's just called mapping.
So I'll probably leave this here, you will most likely have to find another moderator's support to get this approved.
I'm on a page about incorrect corrections, and spent the better part of like two hours trying to get someone to understand that -5^2 = -25, not 25, and then that post had comments get reposted because that group is self sustaining, and that person was in turn trying to explain what I just explained to them. And I'm taking that as a victory
I will be AFK for a couple of days you guys hold down the fort while I am gone. I will be checking in on my phone but that will severly limit me. Be back saturday!