llTeleport();

This would be a neat function and would be quite simple to make... the format would be as follows...

key magicalteleporterperson = j00;
key object = OMFG-ITS-A-KEY;
string destination_station = teh_sim;
vector pos_in_teh_sim = <my,house,w00t>

default
{
blah
Script junk
llTeleport(key magicalteleporterperson, key object, string destination_station, vector pos_in_teh_sim);
}
}
}

Well, that wounldt be the actuall code... but you get it.

EXPLANATION ON STUFF

key magicalteleporterperson - Put a person's name there and their the ones thats going on the magical teleporter journey! (OMFG!!!111@)

Key object - You could send a magical object through the magical teleporter and it would go to its magical destination (OMFG!!!111@@!!!1)

string destination_station - This is the sim that you want the magical thingie to go to (man I love magic!)

vector pos_in_teh_sim - Tells ja where your magical thing is going...

I know the obvios remarks like: OMFG!!! People are gonna teleport right inside of my face, and it'll burn with the fires of 1,000 evils!!! or - Me and my gurl were like doin it in the back, and this guy teled there and we were loike totally busted!!! Well, I came up with THIS to counter it: You can set your land to be able to tele to!!! (OMFG!!!11!!!2) oh, and the sandbox should be allowed to...


Thats my semi-logical explaination on llTeleport();
(I hope I get an A+!!!)

llTeleport(key person, vector offset)

person - "person" is the users' key. This must be a key, as a name would allow griefing.

offset - "offset" is the distance coordinates away from the prim that it doing the teleporting.

llTeleport should cause a dialog box to pop on the user, who belongs to the key, up upon activation to prevent people from grabbing users and locking them in teleport loops -- imagine two stargates placed face-to-face so when you walk out of one, you go into the other, which then leads you out of the first.

Yeah, thats what I was goin for.. But if you've ever been in a stargate... It actually takes 15 seconds or so to get to the other side... (Its a wormhole... OMFG!!!!!11@2!)

Intrasim teleports are important, but so are intersim ports. And I also don't want random people porting into my house, so I think security is important too. So I'd like to see an llTeleport() call that used a prim at both ends of the port (like a Stargate, woo). The LSL would look something like:

llTeleport(key destination, key avatar)

The avatar teleports and arrives standing on (hovering over) the destination object. An llSetTeleportTarget() call allows the destination object to adjust the arrival coordinates. A teleport() event would inform the destination object that someone just arrived, which lets it hand them a notecard or whatever.

I would want the llTeleport() call to require a teleport PIN to teleport to a destination object. (Or possibly just that the transmit and destination objects have the same owner.)

functions
llTeleport(key destination, integer pin, key passenger)
llSetTeleportTarget(vector target)
llSetTeleportPIN(integer pin)

events
teleport(key passenger)

me like me like.
<stamp>
an attachment should be able to teleport people too. There should be a permission associated with this. PERMISSION_TELEPORT a land owner doesn't need the permission to TP someone but any other script does. Attachments would be granted this permission over there owner automaticaly. Teleporting to a location that is in the sim on in the next sim would not cause a full teleport (similar to what would happen if you sit tp'ed into the next sim). Would be nice if attachment keys didn't change. This setup satisfies the need for respawning in an MMORPG.

So to tp a random other person you would call and you are not the owner of the land...

default
{
    touch_start(integer a)
    {
        llRequestPermissions(llDetectedKey(0), PERMISSION_TELEPORT);
    }
    run_time_permissions(integer a)
    {
        if(a&PERMISSION_TELEPORT)
            llTeleport(GUID, 384, llGetPermissionsKey());
        llResetScript();
    }
}

//GUID = llGetKey();
default
{
    state_entry()
    {
        llSetTeleportTarget(<0,0,1>);
        llSetTeleportPin(-384);
    }
    teleport(key passenger)
    {
        llInstantMessange(passenger, "Welcome to Burger King, may I take your order please");
    }
}

imagine having lojack in you vehical and being able to teleport to it when you loose it.

pat answer one: this feature would damage the community

pat answer two: this feature would be used for griefing

pat answer three: the land barons & estate owners would kick our collective ass

my answer: this feature is absolutely paramount to the success of second life as a useful internet medium. i'm in a perpetual state of amazement that we don't have the ability to teleport anywhere on the map and the ability to script an offer.

and with all due respect olmy, frell security. unless you own a hidden or access restricted estate sim, there is no privacy on the grid. there never has been and there never will be. scream your head off at me if you please; it won't change the fact.

one solution though would be a land option to not allowing teleporting to or from the parcel.

/STAMP
/stamp again
/triplicate application of personal endorsement
/one more or good measure
/another one for the myriad of people who don't have professional second life accounts because it's "just a toy"
/finally one from my employer who won't use the software professionally because it's "just another video game"

Highly supported. Inter-sim teleports should be possible as well as intra-sim teleports however. Long range teleports should be a pull rather than a push (object X in location Y has requested your presence, do you wish to go?), however there is potential for widespread abuse there, so a small (say L$1) fee should be placed on the function.

-Adam

I said nothing about privacy. Perhaps "security" was the wrong word to use. But I'd like to be able to control who gets to create teleports onto my land. The system I suggested does that quite nicely, and with good granularity. Turning off teleports for all my land is not a good option, as I'd actually like to be able to allow friends to teleport in.

The other reason for the landing pad object approach is that it is similar to how "offer teleport" works now - the av gets teleported to where your av is. Teleporting to an object can't be much harder, so it should be fairly easy for LL to implement.

And I like Adam's idea about the offer teleport notice. I was thinking the same thing too acutally, just forgot to write it down.

sorry for being pissy. you did say "security" and for good reason. an event could be easily griefed if a teleporter were dropped in the middle of kiddyland while you were trying to host a meeting or contest.

i get pissy when i think people are demanding privacy on the grid because there is none and there never will be and i, for one, don't want the software to be nerfed because people want to believe that they can live a secret life. we're all supposed to be adults here and adults know better than that.

there's already the rez timer that could derez your event teleportation offering prim a few minutes after starting time. that'd keep people from interrupting. it might also prompt us to be on time for a change.