Difference between revisions of "CHANGED TELEPORT"
Jump to navigation
Jump to search
m (<lsl> tag to <source>) |
(Updated parcel scripts disabled to reflect latest testing.) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
|type=integer | |type=integer | ||
|value={{LSL Hex|0x200}} | |value={{LSL Hex|0x200}} | ||
|desc=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 | |desc=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 queued and occurs after the user moves to a script-enabled parcel. | ||
|examples= | |examples= | ||
<source lang="lsl2">default | <source lang="lsl2">default | ||
Latest revision as of 14:10, 20 June 2023
| 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 queued and occurs after the user moves to a script-enabled parcel.
Caveats
Related Articles
Examples
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.");
}
}
}