Lol, you have far way to go.
I thought you're making it a loop (2 triggers required), but you seem to misunderstood the "loop" I mentioned ;p
Well, if you use the loop I mentioned (2 triggers required), you could have a mark of C, but now, it's F >.>"
Okay for looping, we should at all times avoid the use of "Wait" inside a looping action (like what you did).
It can cause weird bugs (don't ask me what kind), but you should avoid it at all time.
Wait, do you know how to play with variables ?
If you don't know this, it would be huge problems teaching you since that is the basic knowledge one should have before coding intense trigger.
Here's a test map which will help you to get C (this is still not MUI, but this is the trigger I hope you create in the first place)
Map:
http://www.hiveworkshop.com/forums/pastebin_data/wfeyjf/_files/Exam%20Test%201.w3x
Information about the map;
- When you activate the spell for 1 unit at a time, it won't bug.
- But when you activate the spell for more than 1 unit at a time (quickly cast all those spells to different units before the 5 seconds duration timeout), it will bug.
What kind of bug ?
Okay, you target Unit A, right after that you target Unit B.
Only unit B is healed while Unit A does not gain anything, why does this happen ?
It is because the data gets overwritten by Unit B, that's why the new unit now is Unit B, leaving Unit A unhealed.
You will need a method to counter this situation, either Hashtable or Indexing.