Difference between revisions of "LlTriggerLandmark"
Jump to navigation
Jump to search
m (LSL llTriggerLandmark moved to LlTriggerLandmark) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= | {{LSL_Function | ||
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. | |func = llTriggerLandmark | ||
|func_id | |||
== | |func_sleep = 5.0 | ||
* Function is automatic if teleporting to a landmark already contained within the user's inventory | |func_energy = 100.0 | ||
|sort | |||
|func_desc = 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. | |||
|func_footnote | |||
|return_type | |||
|return_text | |||
|p1_type = key|p1_name = landmark|p1_desc = The UUID of a pre-existing landmark | |||
|p2_type|p2_name|p2_desc | |||
|p3_type|p3_name|p3_desc | |||
|p4_type|p4_name|p4_desc | |||
|p5_type|p5_name|p5_desc | |||
|p6_type|p6_name|p6_desc | |||
|p7_type|p7_name|p7_desc | |||
|p8_type|p8_name|p8_desc | |||
|p9_type|p9_name|p9_desc | |||
|p10_type|p10_name|p10_desc | |||
|p11_type|p11_name|p11_desc | |||
|p12_type|p12_name|p12_desc | |||
|constants | |||
|spec | |||
|caveats = * 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 | * 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 | |||
|helpers | |||
= | |also_header | ||
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. | |also_functions | ||
|also_tests | |||
|also_events | |||
|also_articles | |||
|also_footer | |||
|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. | |||
|mode = request | |||
|deprecated | |||
|location | |||
|inventory | |||
|permission | |||
|negative_index | |||
|cat1 | |||
|cat2 | |||
|cat3 | |||
|cat4 | |||
|cat5 | |||
|cat6 | |||
}} | |||
Latest revision as of 19:12, 20 February 2007
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
|
LSL Feature Request |
| The described function does not exist. This article is a feature request. |
Summary
Function: llTriggerLandmark( key landmark );| 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.
Deep Notes
Signature |
|---|
//function void llTriggerLandmark( key landmark ); |