Or just store the unit in a variable then add the event to another trigger that unit comes within x of variable the just refer to the variable in the other trigger as unit b
@warden13: yes, you must know unit B when creating the trigger, but sometimes don't know it when the event triggers. As an example: a trigger with multiple of these events, one event for each unit B in a set, would present this challenge. The trigger would fire when a unit approaches any of the units in that set.
You are assuming that there is an entirely different trigger written for each unit B. You can see why that is tedious for all but the most basic uses of the event, and completely unworkable if you need it to be dynamic.
The solution I'm using now is to have a function that takes unit B as an argument and creates a trigger for this particular unit B. Then, I attach the unit B to the trigger, and retrieve by first retrieving GetTriggeringTrigger and using that to retrieve the unit. Annoying, but works fine.
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!