Allow teleport to this location requests using LSL
Mars Tamale
An enhancement to LSL function library to allow a worn attachment to request or offer teleport to wearers or target's location (+/- small range offset perhaps) exactly as if the TP request came from the wearer of the scripted object themselves.
To avoid the potential risk of griefing this could be restricted to friends of the attachment wearer only (up to you) or generate short script delay / only have one outstanding at a time. But as I can search for any name in the Search for People from Content tab I do not see this as a particular problem.
Popular use would be for leashes which could automatically teleport wearers to their leasher's position when they have just teleported away (possibly with some help from RLV to automate the acceptance but not mandatory)
eg:
key llRequestTeleportAgent(key target, vector offset) - Same as Request Teleport
key llOfferTeleportAgent(key target, vector offset) - Same as Offer Teleport
Key delivered could be actioned from dataserver event where the data would indicate the response:
0 = denied - Avatar does not exist (or is not in friends list if restricting to friends only)
1 = delivered and accepted
2 = delivered and rejected (Cancelled)
3 = delivered and rejected (Timed out)
The offset may be restricted to +/- <10,10,10> basically to ensure people don't land on other people's heads like with normal TP requests.
Log In
Spidey Linden
Merged in a post:
Feature request: llTeleportRequest, llTeleportAgentRequest
Toothless Draegonne
This would be a new LSL function, that would provide inworld objects and attachments a way of sending teleport requests to one or more users.
This would
not
force a teleport like an RLV or Experience-based teleport. It would simply send an invite, in an identical way to how the viewer can send teleport requests. This function would also be able to be blocked by using normal object or owner block commands in the viewer.A proposed format would be
llTeleportRequest(list keys, string message)
. The person receiving the request would receive a normal teleport request, with a message akin to x.resident's "Warp Bubble" has sent you a teleport request: [slurl], [message]
.This function would not require any permission check, as it does not force anybody to do anything. Some kind of sensible throttle along the lines of the llInstantMessage throttle would likely be enough to prevent abuse. As with normal teleport requests, this method would also bypass the normal teleport routing of a region/parcel. It would essentially be the exact same mechanism, but instigated by script instead of by viewer.
Kinda Vile
Not too keen on this. The throttle would need to be very restrictive and if you can, experiences would outright be a more feasible option when doing this locally.
I'm assuming the use case is grid-wide since you reference llInstantMessage. Something like this would need a very strong throttle for me to be comfortable with it's existence (1 per agent per 180 seconds), and this would be scoped to all scripts the owner is using at the time that could possibly run it.
Careless Whisper
Kinda Vile A throttle for this is definitely warranted, but such a strong throttle as you suggest is totally unjustified. I see no reason this should not share the exact same throttle system as llInstantMessage down to them counting against each others usage.
If an item or creator becomes a nuisance, they're very easily blocked in the viewer. A throttle that hobbles the utility of the function is not the answer to that problem.
Kinda Vile
Careless Whisper I guess I did suggest something a little too strong. But I do worry about TP spam being a huge issue with things like this.
Toothless Draegonne
Kinda Vile
This feature request has nothing to do with actually forcing a teleport. It would be functionally identical to how countless SL DJs and other socialite-type people already work when they highlight their entire contact list and send a teleport request. Abuse potential is basically zero, and you should be able to block the object or agent in the same way as if they'd sent the request manually.
This would just be a way of sending requests/offers with a script. Your DJs and socialites could even have a handy little object they can wear instead of adding hundreds of contacts. A little floating orb or something, "click here to be added to my TP list", and accompanying summon button on a HUD.
It also has little or nothing to do with experiences. Experiences are a KV store and automatic permissions grant. A teleport request requires no permissions.
Kinda Vile
Toothless Draegonne Not what I meant. I wasn't trying to imply that you would be forcing a teleport. But spamming requests is a nuisance and when you can do that through a script it makes it a lot less tedious to achieve that.
You can abuse experiences, but them being opt in means some hoops have to be jumped through to get there. I'm making the comparison that this doesn't require any of this.
To reiterate, I just think that there definitely needs to be a decent throttle behind these simply because the last thing most people want is a lot of TP requests from an object to a suspicious location. Apart from that it's not too bad an idea.
Toothless Draegonne
Kinda Vile
I already suggested adding an llInstantMessage-alike throttle. That would curb basically any abuse potential down to a minimum, and would actually make the scripted version slower to hit a bunch of people, than it would for me to just highlight my entire contact list and hit "spam".
Any other forms of abuse that people have mentioned, are the kinds of crazy, dedicated abuse that would require an army of alts, and at that point you're already getting into the kinds of territory that an army of bots can already achieve. Requiring an experience would make absolutely no sense for this function. It's not pinned to any particular parcel or region, and it doesn't force anybody to do anything. Limiting it to only lands that have a compatible experience, would be nerfing the entire function to the point where you might as well not bother and just have the usual "spam my friends list a bunch of times" approach that we already have, rather than something a lot more friendly, for instance, "click this floating orb to be added to my TP list."
Bleuhazenfurfle Resident
I like the idea, I don't think you'll get much in the way of a response from it, though, and there's a whole slew of functions that are more deserving of such a response than this. (Also, "Ignore" should remain a thing!)