Detect teleport?

Okies... me again. Sorry.

This time it's a question more out of curiosity, i.e. no practical reason. Is there ANY way to actually detect a teleport (either start or destination) other than periodically checking the position/sim of an avi? Which I'd imagine gets interesting on sim crossings...

Thankee!
-Jenni

The changed event will fire and you can look for CHANGED_TELEPORT if it is a real SL teleport. For "fake" teleports involving sitting on objects, it will be guesswork (or call it heuristics if you don't want to say you're guessing).

(should mention, the script has to be involved in the telport to catch anything, there isn't a good way to check when others come and go unless they help out with some kind of attachment.)

large volume detect object that ceases to detect an av inside it's volume... for fun make it a follower

I remember a while back Jana Kamachi had discovered a way to not only detect a teleport, but what sim the avatar teleported to. Linden Lab caught on fairly quick and fixed the bug though. It was fun while it lasted though!

~chuckle~ I didn't even think about detecting OTHERS teleports... and somehow missed the CHANGED event. ~sigh~

Detecting a sit teleport should be reasonably easy if the distance is big enough... check position every sec and if it's larger than X meters, presume teleport? Not sure if the avi gets a changed notification when sitting, but I'd presume it does, so this kind of check could be selective.

Again, this is all just out of curiosity, and I very much appreciate everyone indulging my curiosity.

Ah good that makes it MUCH easier, then the problem is solved for real teleports.


Unfortunately that one isn't so easy. The object you sit in will get a CHANGED_LINK, but your attachments won't get any reliable event. You can try to catch sits by polling llGetAgentInfo on a timer, but you may miss some of the really quick sits a teleport prim might use. (Many have a little delay before the unsit, but others don't bother).

That leaves you with the guesswork, compare distance against time. Regular flight and vehicles can be faster than an llSetPos() teleporter, and even a warppos/posjump teleporter that moves you less than a few dozen meters will give iffy numbers. If you are only really interested in big moves, it might still work out well enough to do the job.

bloody nightmare is what it was... the grief trackers were on overdrive. fortunately a 3 second intermediate teleport to a no-scripts zone helped (as did speed hopping, but teleports have always been touchy at times)