Difference between revisions of "CHANGED TELEPORT"
Jump to navigation
Jump to search
m |
m |
||
| Line 15: | Line 15: | ||
} | } | ||
}</lsl> | }</lsl> | ||
|functions | |functions= | ||
{{LSL DefineRow||[[llTeleportAgentHome]]|}} | |||
|events= | |events= | ||
{{LSL DefineRow||[[changed]]|}} | {{LSL DefineRow||[[changed]]|}} | ||
|cat1 | |cat1=Teleport | ||
|cat2 | |cat2 | ||
|cat3 | |cat3 | ||
|cat4 | |cat4 | ||
}} | }} | ||
Revision as of 10:26, 1 March 2009
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Constant: integer CHANGED_TELEPORT = 0x200;The integer constant CHANGED_TELEPORT has the value 0x200
The avatar this object is attached to has teleported. This event only occurs in the root prim of an attachment when the user has teleported. This event does not occur in child prims of attachments, nor does it occur due to a "sit teleport". If the user teleports into a parcel where their scripts are disabled then the CHANGED_TELEPORT event is dropped and does not occur even if the user moved to a script-enabled parcel.
Caveats
Related Articles
Examples
<lsl>default {
changed(integer change)
{
if (change & CHANGED_TELEPORT) //note that it's & and not &&... it's bitwise!
{
llOwnerSay("The object has been teleported while attached.");
}
}
}</lsl>