Difference between revisions of "LlTriggerLandmark"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
| Line 1: | Line 1: | ||
{{LSL_Function | {{LSL_Function | ||
|func = llTriggerLandmark | |func = llTriggerLandmark | ||
|func_id = REQUEST | |func_id = REQUEST | ||
|func_sleep = 5.0 | |func_sleep = 5.0 | ||
| Line 9: | Line 9: | ||
|return_type | |return_type | ||
|return_text | |return_text | ||
|p1_type|p1_name|p1_desc | |p1_type = key|p1_name = landmark|p1_desc = The UUID of a pre-existing landmark | ||
|p2_type|p2_name|p2_desc | |p2_type|p2_name|p2_desc | ||
|p3_type|p3_name|p3_desc | |p3_type|p3_name|p3_desc | ||
Revision as of 11:05, 20 February 2007
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: llTriggerLandmark( key landmark );| REQUEST | Function ID |
| 5.0 | Forced Delay |
| 100.0 | Energy |
Allows a script to trigger the activation of a specific landmark, as identified by it's UUID, and teleport an avatar/user to the defined destination.
| • key | landmark | – | The UUID of a pre-existing landmark |
Caveats
- This function causes the script to sleep for 5.0 seconds.
- Function is automatic if teleporting to a landmark already contained within the user's inventory
- Provides standard Landmark Dialog if landmark does not exist within the user's inventory
This function might also require a specific permission to be set in order to function (to help prevent abuse).
Examples
Notes
I'm sure I'm not the only one who already has tons of landmarks, though there are a select number of which I use quite often. I have efforted to create a HUD which will povide easy access to commonly-used landmarks, but there is no function in LSL to access them.