Teleporting to <0,0,0> by intermittently.

[PcTek Cyberstar]

Most of the time my teleporter works great, I sit on the object and away I go to my huds requested destination.  However, sometimes I wind up at <0,0,0> usually in sea water.  Would it be prudent to have the telporter check the region coordinates and if for some strange reason you are at <0,0,0> to replay the requested teleport vector again, before ejecting you from the prim?  Moreover, is this idea feasible in the production environment as opposed to only a theoretical possibility?

[Ela Talaj]

Precheck destination coordinates before doing TP (I presume by llSetRegionCoordinates() but doesn't really matter how) and if your destination is not a vector or is less than or equals 0 or greater than 255 along X or Y axes just send user a message "invalid destination".

[Nova Convair]

If you use llSetRegionPos it is simple since this function returns TRUE if it worked and FALSE if not.

Since <0,0,0> is a valid position you need to check if the target coordinates are ZERO_VECTOR. But that can't happen or there is a bug in your script - most probably it starts teleport and there is no target coordinate set - that will result in you getting dumped at <0,0,0>