Who makes a GOOD full-sim teleporter?

Oooo, I've always wondered about that Sleep, but never noticed an improvement with it (so always eliminated the half second delay that annoyed me)! LOL Maybe with the new Havok it will all be a moot point anyway? (And less havoc? )

/me waves back!

Reaally dumb question here: when someone above said that the "sit" teleporter is a hack, were they talking about the"teleporter" freebie script that's floating around? I've used that in my shop, as signposts (like Calla has) where you right click on the sign and select "teleport" and it zips you over to another section of the shop. Does this freebie thing that I have not work over 300 m or something? (I've never tried it.)

The hack is in using the llUnSit script function to unsit an avatar at a distance from where they are. Not what the function was intended for but it does make a nifty teleporter. The basic llUnSit call can only move an avatar 300 m, but there is a further hack, WarpPos, that can teleport huge distances (apearently even across sims, though i've never tried that)

Yeah, the only in-world teleporting method that's really not a "hack"--it actually uses the function's intended behavior--is llMapDestination. It works really well, but folks just don't expect the world Map to pop up when they try to TP, and if they wait (unnecessarily) for the Map to populate, that can take a long time; the map TP itself, though, is almost instantaneous within a sim.

But I dunno... this "hack" label is kinda arbitrary when it comes to LSL, which is mostly documented by scripters after trying to divine how a new function actually behaves. Ironically, llTeleportAgent has been documented since release 1.8.0--unfortunately, it doesn't exist. As Accasbel said, it sure would be nice if there actually were such a function.

Of course in response to the OP's post...the simplest tp method really is a notecard vendor with landmarks to each location embedded

No frills
Reliable, instantaneous
No sitting
No rezzing of beams

But no fun!

That doesn't work with a set landing point does it? Won't it just say "could not teleport" then?

Also wouldn't that mean users would have to open the notecard, click the LM to copy to their inventory, if they have automatic preview on in prefs it would open, if not they'd have to find it and open it it in inventory, then click TP? (With the Nicholaz viewer you can just double-click LMs in inventory to TP without the extra step, has the Linden viewer caught up to that yet?)

But it would also be easily updated, and usable by many simultaneously, and fewer scripts!

It would be nice if the Linden view leapfrogged rather than caught up.

llTpMyAssButLeaveTheAttachmentsWhereTheyWereThankYou() would be kewl.

Hmmm... good question. I've often been puzzled when I get the "cannot teleport closer to destination" message; maybe this is what that's about. I'm guessing that the "notecard vendor with landmarks" would give out individual landmarks, not embedded in notecards, so if auto-preview is on, it should just pop open. At least in the Linden viewer, double-click opens the LM; instead, a right-click gives a context menu from which Teleport is an option. That's kinda consistent with how animations and sounds behave in Inventory.Well, seems to me that handing out a landmark would be an asset server transaction, which seems a bit "heavy," but maybe I'm being paranoid.

[Edit: Forgot to mention, to the "easily updated" point, there are scripts that parse the *default* name of a landmark in order to update teleporter destination lists, where the teleport itself is effected by llMapDestination or other means. This is pretty slick--except that scripts can't "see inside" a landmark, so they just have to rely on the name, which can be changed by the user into something the script won't know how to parse. But for normally-named landmarks, this does make updates more intuitive.]

Sorry for necropost, but I just finished fixing this for me and thot I'd pass it on. Script with shorter sleep time works fine, no flying, little delay. This one also adjusts automatically when you move the prim its in, and lets you set the destination x,y,z in the object description field.

// Short-range teleport script, with no flying after TP
//----------------------------------
// Script substitutes the "sit" pie postion with name of object containing script
// and reads target position from object description field, e.g.:
// Description 169,158,600.25 (spaces within position string ok)
// If you change the description/position, must reset script (or move the object)

// There is little error checking. If you type just text into the description field
// instead of x,y,z coords, you will get an error. But if you type in 150,7000;32 you
// will end up lost when you TP.
// Max distance that sit target can be from TP object is 300m along any one axis.

// If TP object is moved, it will recalculate the TP target.

// For best results, make sure teleport destination is far enough away from
// other objects so avatar does not collide after tp (end up flying).
// Setting Z point to .25 meter above actual landing seems to help.

vector targetPos;

reset() //resets target position, pie name, etc.
{
vector target;
list destination;

destination = llParseString2List(llGetObjectDesc(),[","],[]);
targetPos.x = llList2Float(destination,0);
targetPos.y = llList2Float(destination,1);
targetPos.z = llList2Float(destination,2);
if (targetPos == ZERO_VECTOR) { // user probably typed in a text desc
targetPos = llGetPos();
llSay(0, "Bad destination in object description: use format x,y,z";
}
llSay(0,"TP target set to " + (string)targetPos);
target = (targetPos- llGetPos()) * (ZERO_ROTATION / llGetRot());
llSitTarget(target, ZERO_ROTATION);
llSetSitText(llGetObjectName());

} // endreset

default
{
state_entry()
{
reset();
}

on_rez(integer startup_param)
{
llResetScript();
}

changed(integer change)
{
if (change & CHANGED_LINK)
{
if (llAvatarOnSitTarget() != NULL_KEY)
{
llSleep(0.15); // delay to avoid flying on unsit
llUnSit(llAvatarOnSitTarget());
} // end of avatar was sitting
}
else //some other prim change event
{
reset();
}
} // end changed event

moving_end()
{
reset(); // try to compensate for object movement
}

} // end default

Seconded. I used those for my mall which covered an entire sim and the sky mall up above,and I was very happy.