You may need to create another trigger that has condition: object in area, and effect: turn off the task-object trigger.
Then maybe do something similar in reverse to turn the looping task object trigger back on.
OR, better yet, just set the condition of the looping task object trigger to "object in are" and set the area to areas where your object's destination is NOT. So like,
|
||||||||||||||||||||||||
||||-->||||| X |||-->|||| --> X
|||||||||||||||||||||||||
So that you have a "path" created by "condition: object in area" that tasks object X to a location just past the end of the path...
Gosh that sounds confusing, I hope it makes sense! But this way, once objects leave the area, the trigger should "stop", even though it's set to loop.
Matt - "Crasher"