Difference between revisions of "LlTeleportAgentHome"
Jump to navigation
Jump to search
(If this were true it would be a breaking change (main land security systems would fail). The suggestion SVC-6360 seeks to allow EMs usage of this function and it's unresolved (as of last month).) |
m |
||
| Line 1: | Line 1: | ||
{{LSL Function | {{LSL Function | ||
|inject-2={{Issues/SVC-212}}{{LSL_Function/avatar|avatar|sim=*}} | |inject-2={{Issues/SVC-212}}{{Issues/SVC-6360}}{{LSL_Function/avatar|avatar|sim=*}} | ||
|func_id=158 | |func_id=158 | ||
|func_sleep=5.0 | |func_sleep=5.0 | ||
Revision as of 01:18, 28 July 2012
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: llTeleportAgentHome( key avatar );| 158 | Function ID |
| 5.0 | Forced Delay |
| 100.0 | Energy |
Teleports avatar on owner's land to their home location without any warning, similar to a God Summons or dying.
| • key | avatar | – | avatar UUID that is in the same region |
The object owner must also be the land owner. If the land is deeded to a group the object will need to be deeded to the same group for this function to work.
Caveats
Examples
<lsl>default { state_entry() { llSetText("Don't touch me!", <1,0,0>, 5.0); } touch_start(integer total_number) { llTeleportAgentHome(llDetectedKey(0)); // Teleports the Agent home }
}</lsl>Deep Notes
All Issues
~ Search JIRA for related Issues
|
|
SVC-212 | A | New Feature Request - llTeleportAgent | |
|
|
|
SVC-6360 | A | Estate managers should be able to use llTeleportAgentHome() |
Signature |
|---|
function void llTeleportAgentHome( key avatar ); |