that would be a script
you would exec in some unit init (for ex. binladen)
[] exec "triggerpos.sqs" or whatever you decide to name it, and put that in the script
yes it will keep the trigger on him
then you can group it to the group of people wo have to catch him, set it to any member, and then put in the other stuff you need for him to be set captive
you can add something like what i did earlier to make it so there can't be anyone on binladens side in the trigger as well.
basically the distance thing was simulating a trigger over him, but just making it harder to do