Second Life Wiki - User contributions [en]

LlDerezObject

2025-02-01T17:27:37Z

Sei Lisa: Be more specific about the return value

{{LSL_Function
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llDerezObject
|return_type=integer|return_subtype=boolean
|p1_type=key|p1_name=id|p1_desc=The ID of an object in the region.
|p2_type=integer|p2_name=flag|p2_desc=Deletion options.
|func_desc=Derezzes an object previously rezzed from within the object containing the script.
|return_text=which is TRUE for success or FALSE for failure.
|spec=
Deletes, or marks temp, an object that was previously rezzed by this script. The object's root prim must have been previously rezzed from a script within this object.
If the object is successfully deleted this function returns TRUE, if it fails for any reason it returns false.
|caveats=
* The targeted object's rezzer must be the same as the object hosting this script
* The target must not be an attachment
* The target must be copyable
* The target's owner must be the same as the script's owner.
* When marking an object as temporary, the object must not contribute to the navmesh.
|examples
|helpers
|constants=
{{{!}} class="sortable" {{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! Constant
! Value
! class="unsortable" {{!}}Description
{{!}}-
{{!}} [[DEREZ_DIE]]
{{!}} 0
{{!}} Immediately delete the object.
{{!}}-
{{!}} [[DEREZ_MAKE_TEMP]]
{{!}} 1
{{!}} Mark the object as temporary so that the simulator will remove the object at a later time.
{{!}}}

|also_functions
|also
|notes
|cat1=Script
|cat2
|cat3
|cat4
}}

LlTransferOwnership

2025-02-01T13:49:34Z

Sei Lisa: Returns an integer with the result of the transfer

{{LSL_Function
|inject-2={{Issues/SVC-7631}}{{Issues/BUG-5656}}
|func_sleep=0.0|func_energy=10.0
|func=llTransferOwnership
|return_type=integer
|p1_type=key|p1_name=agent_id|p1_desc=Agent ID for the avatar to receive ownership of the object
|p2_type=integer|p2_name=flags|p2_desc=Flags controlling transfer behavior.
|p3_type=list|p3_name=options|p3_desc=Options applied to the ownership transfer. No options are defined at this time.
|func_footnote
|func_desc=Transfer ownership of the object containing this script to {{LSLP|agent_id}}.
|return_text=indicating the result of the transfer.
|spec=
Transfers ownership of an object rezzed in world to {{LSLP|agent_id}}. The object must be transferable by its current owner and must not be an attachment.

Optionally this function may force the object to derez itself into the destination agent's inventory, or make a copy of itself directly into inventory.

|caveats=
* {{LSLP|agent_id}} must be an agent in the region.
* There is no way to detect if the receiver ignored, rejected or blocked the transaction (aside from a [[changed]] event never occurring.)
* The function fails with a return code of [[TRANSFER_NO_PERMS]] if:
** The object is no-transfer.
** The object is no-copy and {{LSLP|flags}} includes the [[TRANSFER_FLAG_COPY]] flag.
* Calling this function from an attachment will fail and return [[TRANSFER_NO_ATTACHMENT]]
* WARNING: Any no-trans items in the transferred object will be removed from the object received by the target agent. If the transfer is of the object itself, these items are lost.
* WARNING: If the transfer is a copy, any no-copy inventory items will be present in the object received by the target agent and removed from the original.

|constants=
{{LSL Constants/Transfer Flags}}

{{LSL Constants/Transfer Errors}}
|examples
|helpers
|also_functions=
{{LSL DefineRow||[[llGiveInventoryList]]}}
{{LSL DefineRow||[[llRemoteLoadScriptPin]]}}
{{LSL DefineRow||[[llSetRemoteScriptAccessPin]]}}
{{LSL DefineRow||[[llMapDestination]]}}
|also_events=
{{LSL DefineRow||[[changed]]}}
|also_tests
|also_articles
|notes
|permission
|negative_index
|sort=GiveInventory
|cat1=Inventory
|cat2=Avatar
|cat3
|cat4
}}

On damage

2025-02-01T12:24:40Z

Sei Lisa: Mention llDamage in See Also

{{LSL_Event
|event_id=|event_delay|event=on_damage
|p1_type=integer|p1_name=num_detected|p1_desc=The number of damage events pending against the avatar or task.
|event_desc=This event is triggered when damage has been inflicted on an avatar or task in the world but before damage has been applied or distributed.

All llDetected* functions that are normally available within a collision event are available while processing this event. Additionally the [[llDetectedDamage]] and [[llAdjustDamage]] methods may be called while processing this event.
|event_footnote
|constants
|spec
|caveats=
* Requires the region to [[llGetEnv|allow damage adjustment]] for the event to run
|examples=<syntaxhighlight lang="lsl2">string damageType2String(integer type)
{
if (type == DAMAGE_TYPE_GENERIC)
return "generic";
else if (type == DAMAGE_TYPE_ACID)
return "acid";
else if (type == DAMAGE_TYPE_BLUDGEONING)
return "bludgeoning";
else if (type == DAMAGE_TYPE_COLD)
return "cold";
else if (type == DAMAGE_TYPE_ELECTRIC)
return "electric";
else if (type == DAMAGE_TYPE_FIRE)
return "fire";
else if (type == DAMAGE_TYPE_FORCE)
return "force";
else if (type == DAMAGE_TYPE_NECROTIC)
return "necrotic";
else if (type == DAMAGE_TYPE_PIERCING)
return "piercing";
else if (type == DAMAGE_TYPE_POISON)
return "poison";
else if (type == DAMAGE_TYPE_PSYCHIC)
return "psychic";
else if (type == DAMAGE_TYPE_RADIANT)
return "radiant";
else if (type == DAMAGE_TYPE_SLASHING)
return "slashing";
else if (type == DAMAGE_TYPE_SONIC)
return "sonic";
else if (type == DAMAGE_TYPE_EMOTIONAL)
return "emotional";

return "type " + (string)type;
}

default
{
on_death()
{
llSay(0, "I'll be back!");
}

on_damage(integer count)
{
integer index;
for (index = 0; index < count; ++index)
{
key object = llDetectedKey(index);
string object_name = llDetectedName(index);
key owner = llDetectedOwner(index);
key rezzer = llDetectedRezzer(index);
list damage = llDetectedDamage(index);

string owner_name = llKey2Name(owner);
string rezzer_name = llKey2Name(rezzer);

llSay(0, "I was struck by " + object_name + "{" + (string)object + "} owned by " +
owner_name + "{" + (string)owner + "} rezzed by " +
rezzer_name + "{" + (string)rezzer + "} for " +
(string)llList2Float(damage, 0) + " points of " + damageType2String(llList2Integer(damage, 1)) +
" damage (originally " + (string)llList2Float(damage, 2));

float new_damage = llList2Float(damage, 0) / 2.0;

llSay(0, "Reducing damage by 50% to " + (string)new_damage);
llAdjustDamage(index, new_damage);
llSay(0, "llDetectDamage = [" + llDumpList2String(llDetectedDamage(index), ", ") + "]");
}

}
}</syntaxhighlight>
|helpers
|also_header
|also_events={{LSL DefineRow||[[on_death]]|}}
{{LSL DefineRow||[[final_damage]]|}}
|also_functions={{LSL DefineRow||[[llDetectedDamage]]|}}
{{LSL DefineRow||[[llAdjustDamage]]|}}
{{LSL DefineRow||[[llDamage]]|}}
|also_articles
|also_footer
|notes=
|mode
|deprecated
|cat1=Script
|cat2=Combat2
|cat3
|cat4
}}

LlXorBase64Strings

2025-02-01T10:50:24Z

Sei Lisa: Recommend a non-broken function

{{LSL_Function
|deprecated=llXorBase64
|func_id=262|func_sleep=0.3|func_energy=10.0
|sort=XorBase64StringsCorrect
|func=llXorBase64Strings
|return_type=string
|p1_type=string|p1_name=str1|p1_desc=Base64 string
|p2_type=string|p2_name=str2|p2_desc=Base64 string
|func_footnote={{LSLP|s2}} repeats if it is shorter than {{LSLP|s1}}. Retained for backwards compatibility.
|return_text=that is a {{LSLGC|Base64}} string of {{LSLP|s1}} xor'ed with {{LSLP|s2}}.
|spec
|caveats=*'''Incorrectly performs an exclusive or on two Base64 strings and returns a Base64 string'''
**Use [[llXorBase64]] instead.
|examples
|helpers
|also_functions={{LSL DefineRow||[[llXorBase64]]}}
|notes
}}

LlListSortStrided

2024-04-19T13:14:05Z

Sei Lisa: Add caveat, add info on negative stride, fix typo in example

{{LSL_Function
|inject-2={{Issues/SVC-2988}}{{Issues/SVC-5146}}{{LSL_Function/stride|stride}}
|func_id=184|func_sleep=0.0|func_energy=10.0
|func=llListSortStrided|return_type=list
|func_complexity=O(N2)
|p1_type=list|p1_name=src|p1_desc=List to be sorted.
|p2_type=integer|p2_name=stride
|p3_type=integer|p3_name=stride_index|p3_desc=The index within the stride to sort by. stride_index is 0-indexed. The first element is 0, second 1, etc. An index of 0 is functionally identical to using [[llListSort]]. Negative indexes count from the end of the stride, e.g. -1 means the last element in the stride.
|p4_type=integer|p4_name=ascending|p4_desc=if [[TRUE]] then the sort order is ascending, otherwise the order is descending.
|func_footnote
|func_desc=llListSortStrided is llListSort with the added parameter of stride_index, adding the flexibility to sort by any item in the stride. These routines use the same underlying code and have the same computational complexity.
|return_text=that is {{LSLP|src}} sorted by the {{LSLP|stride_index}} item in every {{LSLP|stride}}.
|spec=The sort order is affected by type. For strings and keys, it is case sensitive and sorts by Unicode character code. 
<source lang="lsl2">llListSortStrided(["a", "á", "B", "C", "d", "e"], 1, 0, TRUE) // returns ["B", "C", "a", "d", "e", "á"]</source>

For ascending sort, each type is sorted individually and then feathered to have the same order of types.
<source lang="lsl2">llListSortStrided([1, "C", 3, "A", 2, "B"], 1, 0, TRUE) // returns [1, "A", 2, "B", 3, "C"]

llListSortStrided([1, 3, 2, "C", "A", "B"], 1, 0, TRUE) // returns [1, 2, 3, "A", "B", "C"]

llListSortStrided([1, "C", 3, "A", 2, "B"], 2, 0, TRUE) // returns [1, "C", 2, "B", 3, "A"]

llListSortStrided([1, "C", 3, "A", 2, "B"], 2, 1, TRUE) // returns [3, "A", 2, "B", 1, "C"]</source>

|caveats=*It uses the same unoptimized selection sort algorithm as llListSort, which is an algorithm with a Big O of N². A [[JIRA]] issue exists to improve this function, {{Jira|SVC-2988}}.
* Originally the wiki stated that non-zero values for the "ascending" parameter would produce an ascending sort. That was incorrect. For this function, the value must be exactly 1 (or TRUE) for an ascending sort.
* [[Vector]]s are sorted by magnitude. {{Jira|SVC-5643}}
* [[Rotation]]s are not sorted in any meaningful order. If a list containing only rotations is sorted in ascending order, it will be returned unchanged.
* For descending sort, if there are mixed types, the final order is deterministic (the same input will always produce the same output) but it can be completely useless. <source lang="lsl2">llListSortStrided([2, "B", "C", 3, 1, "A"], 1, 0, FALSE) // returns ["A", 3, 1, "C", "B", 2]</source> If there are no mixed types, however, the descending sort works just fine.
* When the stride is greater than 1, if the list length is not a multiple of the stride, the list will be returned unchanged.
* stride_index must be less than stride and greater than or equal to -stride, otherwise an empty list is returned.
* When strings contain numbers, the numbers are still sorted left-to-right like any other character, which may not necessarily match numeric order: <source lang="lsl2">llListSortStrided(["127", "3", "25"], 1, 0, TRUE) // returns ["127", "25", "3"] because the 1 in 127 is before the 2 in 25 which is before the 3</source> To sort them in numeric order, numbers in strings can be padded with zeros: <source lang="lsl2">llListSortStrided(["127", "003", "025"], 1, 0, TRUE) // returns ["003", "025", "127"]</source>
** This order differs from the order of items in a prim's inventory, which is "natural order" (e.g "New Script 2" is sorted before "New Script 11").
|constants
|examples=
<source lang="lsl2">
list score_board = ["Awesome", "Resident", 200, "Star", "Marxman", 999, "Happy2", "Survive", 1];
default
{
state_entry()
{
llOwnerSay("Unsorted: " + llDumpList2String(score_board, ","));
score_board = llListSortStrided(scoreboard, 3, 0, TRUE);
llOwnerSay("Sort by first names: " + llDumpList2String(numbers, ","));
// Object: Sort by first names: Awesome,Resident,200,Happy2,Survive,1,Star,Marxman,999

score_board = llListSortStrided(scoreboard, 3, 1, TRUE);
llOwnerSay("Sort by last names: " + llDumpList2String(numbers, ","));
// Object: Sort by first names: Star,Marxman,999,Awesome,Resident,200,Happy2,Survive,1

score_board = llListSortStrided(scoreboard, 3, 2, TRUE);
llOwnerSay("Sort by last names: " + llDumpList2String(numbers, ","));
// Object: Sort by first names: ,Happy2,Survive,1,Awesome,Resident,200,Star,Marxman,999

}
}
</source>

llListSort and llListSortStrided really only works on items of the same type. It will work on lists that hold diverse data types -- to be clear, it won't blow up your script -- but the results returned are usually meaningless.

<source lang="lsl2">list mylist = ["brown", <0.000000, 0.000000, 0.000000>, "house", 17.005, 100, "cat", <3.000000, 3.000000, 3.000000>, 39];
list tmplist = llListSortStrided(mylist, 1, 0, TRUE);
llSay(0, llList2CSV(tmplist));</source>

This returns in chat:

brown, <0.000000, 0.000000, 0.000000>, cat, 17.004999, 39, house, <3.000000, 3.000000, 3.000000>, 100

The same ordered in descending order returns even more meaningless results:
<source lang="lsl2">list mylist = ["brown", <0.000000, 0.000000, 0.000000>, "house", 17.005, 100, "cat", <3.000000, 3.000000, 3.000000>, 39];
list tmplist = llListSortStrided(mylist, 1, 0, FALSE);
llSay(0, llList2CSV(tmplist));</source>

returns in chat:

39, <3.000000, 3.000000, 3.000000>, cat, 100, 17.004999, house, <0.000000, 0.000000, 0.000000>, brown

===Utilizing the Results===

It's important to note that the source list that you are sorting will remain unchanged. Instead, a new, sorted list will be produced. So, it's important that you capture this with a variable (unless you are acting directly on the results.)

<source lang="lsl2">llListSortStrided(myList, 1, 0, TRUE); // You've wasted cpu time; you didn't capture the results

list newlist = llListSortStrided(myList, 1, 0, TRUE);// Okay. You've captured the results.

llSay(0,llList2CSV(llListSortStrided(myList, 1, 0, TRUE))); // No need to capture, using the results right away.</source>

==={{LSLPT|Stride}} parameter===

Most times, you will want to set "integer stride" to 1 (0 also works) to tell it to sort each item in the list on its own basis. (If you are working with a strided list, though, see the special section below on sorting strides.)

===Sort Order===

Setting the parameter "integer ascending" to [[TRUE]] returns a sorted list that is in ascending order. 
For example: ["Apples", "Bananas", "Oranges"]

Setting the parameter "integer ascending" to [[FALSE]] returns a sorted list that is in descending order. 
For example: ["Oranges", "Bananas", "Apples"]

===Sorting Strided Lists===

If you have a [[List#Strided_lists|strided list]], in which you are keeping related pieces of data together in chunks, letting each list element sort on its own basis would be disastrous.

<source lang="lsl2">list demographics = ["John Adams", "male", "2007-06-22", "Shirley Bassey", "female", "2005-11-02", "Matt Damon", "male", "2008-05-19"];</source>

====Bad Example====

<source lang="lsl2">list tmplist_1 = llListSortStrided(demographics, 1, 0, TRUE);
//tmplist_1 == ["2005-11-02", "2007-06-22", "2008-05-19", "John Adams", "Matt Damon", "Shirley Bassey", "female", "male", "male"]
//The strides have been destroyed, the sorted data is now useless</source>

====Good Example====

Instead, because you have the data grouped (aka "strided") in sets of 3, you need to do this:

<source lang="lsl2">list tmplist_2 = llListSortStrided(demographics, 3, 0, TRUE);
//templist_2 = ["John Adams", "male", "2007-06-22", "Matt Damon", "male", "2008-05-19", "Shirley Bassey", "female", "2005-11-02"]
</source>

|permission
|negative_index
|sort=ListSort
|cat1=List
|cat2
|cat3
|cat4
|location
|issues=
}}

LlList2ListSlice

2024-04-18T15:02:45Z

Sei Lisa: Fix examples. Fix inconsistency with exclusion ranges where the description said they were supported and the caveats said they weren't.

{{LSL_Function
|inject-2={{LSL_Function/negative index|true|start|end|noExclude=}}{{LSL_Function/stride|stride|slice}}
|func_id=198|func_sleep=0.0|func_energy=10.0
|func=llList2ListSlice
|return_type=list
|p1_type=list|p1_name=src
|p2_type=integer|p2_name=start
|p3_type=integer|p3_name=end
|p4_type=integer|p4_name=stride
|p5_type=integer|p5_name=slice_index
|func_footnote=The index of the first entry in the list is {{HoverText|0|zero}} 
The index of the first entry in a slice is {{HoverText|0|zero}} 
If {{LSLP|start}}, {{LSLP|end}}, or {{LSLP|slice_index}} are negative they are indexed from end of list. -1 is last element in the list. -list_length is the 1st element of the list. 
If {{LSLP|slice_index}} is negative it is counted from the end of its stride regardless of whether or not the stride exceeds the end of the list. e.g: -1 is the last element in a stride. 
If {{LSLP|start}} > {{LSLP|end}} the range from start to end is treated as an exclusion range. 
|func_desc
|return_text=of the slice_index'th element of every stride in [[List#Strided_lists|strided list]] whose index is a multiple of {{LSLP|stride}} in the range {{LSLP|start}} to {{LSLP|end}}.
|spec
|caveats
|constants
|examples=
<source lang="lsl2">list mylist = [0,1,2,3,4,5,6];
list result_a = llList2ListSlice(mylist,0,-1,3,0); //start at first item in list, go to the end, return 1st slice of every stride of 3
//result_a == [0,3,6]

list result_b = llList2ListSlice(mylist,0,-1,3,1); //start at first item in list, go to the end, return 2nd slice of every stride of 3
//result_b == [1,4]

list result_c = llList2ListSlice(mylist,1,-1,3,1); //start at second item in list, go to the end, return 2nd slice of every stride of 3
//result_c == [2,5]

list result_d = llList2ListSlice(mylist,2,-1,3,-1); //start at third item in list, go to the end, return last slice of every stride of 3
//result_d == [4]

list result_e = llList2ListSlice(mylist,4,2,1,0); //4>2 so this is an exclusion. slice indices count from 0 and first element after exclusion. Return every element not in range with a stride of 1
//result_e == [0,1,2,4,5,6]</source>

<source lang="lsl2">list menu = ["1", "one", "2", "two", "3", "three"];
default
{
state_entry()
{
llListen(10, "", llGetOwner(), "");
}
touch_start(integer detected)
{
list buttons = llList2ListSlice(menu, 0, -1, 2, 0);
llDialog(llDetectedKey(0), "choose a number", buttons, 10); //display the digits
}
listen(integer channel, string obj, key id, string message)
{
integer index = llListFindList(menu, [message]);
if (index != -1)
{
list names = llList2ListSlice(menu, 0, -1, 2, 1);
llOwnerSay("you chose " + llList2String(names, index/2) + " (" + message + ")");
}
}
}</source>

|helpers=*[[User:Fred_Gandt/Scripts/Functions#StrideOfList|StrideOfList]] - Starting from '''start''' and stopping before '''end''' exceeded it skips every '''stride'''-1 items. returns the slice_index element of the stride if its position is less than list length.
|also_functions=
|also_events
|also_tests
|also_articles
|notes= If the list is not modulo the stride, elements up to the length of the list will be returned in the final slice matching conditions. e.g. a list of 5 elements with a stride of 2 will return 3 elements for a 0,5 range on slice index 0 but only 2 if the slice_index is 1.
|permission
|negative_index
|haiku={{Haiku|Fetch me the last names|In a database of lists|Oh look columns. Neat!}}
|sort=List2ListSlice
|cat1=List
|cat2
|cat3
|cat4
}}

LlListFindStrided

2024-04-14T10:17:50Z

Sei Lisa: Minor typo that prevented compilation

{{LSL_Function
|func=llListFindStrided
|func_id=201|func_sleep=0.0|func_energy=10.0
|return_type=integer
|Return_text=index of the first instance of {{LSLP|test}} in {{LSLP|src}} matching conditions.
|p1_type=list|p1_name=src|p1_desc=what to search in (haystack)
|p2_type=list|p2_name=test|p2_desc=what to search for (needle)
|p3_type=integer|p3_name=start|p3_desc=Start of range to search
|p4_type=integer|p4_name=end|p4_desc=End of range to search
|p5_type=integer|p5_name=stride|p5_desc=Number of entries per stride within src

|func_footnote=If {{LSLP|test}} matching range and stride conditions is not found in {{LSLP|src}}, -1 is returned. 
The length of {{LSLP|test}} may be equal to or less than {{LSLP|stride}} in order to generate a match. 
The index of the first entry in the list is {{HoverText|0|zero}} 
If {{LSLP|test}} is found at the last index in {{LSLP|src}} the positive index is returned (5th entry of 5 returns 4). 
If {{LSLP|start}} or {{LSLP|end}} is negative, it is counted from the end list. The last element in the list is -1, the first is -list_length
|func_desc
|spec
|caveats=
* Strict type matching and case sensitivity is enforced.
** "1" != 1
** "1.0" != 1.0
** 1 != 1.0
** "a822ff2b-ff02-461d-b45d-dcd10a2de0c2" != (key)"a822ff2b-ff02-461d-b45d-dcd10a2de0c2"
** "Justice" != "justice"
* If {{LSLP|test}} is an {{HoverText|empty list|[]}} the value returned is {{HoverText|0|zero}} rather than -1.
|constants
|examples=<source lang="lsl2">list mylist = ["a",0,"b",1,"c",2,"b",1];

integer result_a = llListFindStrided(mylist, ["b"], 0, -1, 1); //Stride 1 full range functionally equivalent to llListFindList(mylist,"b");
//result_a = 2

integer result_b = llListFindStrided(mylist, ["b",1], 2, -1, 1); //Inclusive range for start and end will find 2nd list in list
//result_b = 2

integer result_c = llListFindStrided(mylist, ["b"], 3, -1, 1); //The first "b" is at index 2 and will be skipped by starting at 3
//result_c = 6

integer result_d = llListFindStrided(mylist, ["b",1], 2, -1, 1); //Inclusive range for start and end will find 2nd item in list
//result_d = 2

integer result_e = llListFindStrided(mylist, ["b",1], 3, -1, 1); //The first "b",1 series is at index 2 and will be skipped by starting at 3
//result_e = 6

integer result_f = llListFindStrided(mylist, ["b",1], 3, -2, 1); //The first "b",1 series is at index 2 and will be skipped by starting at 3. The second ["b",1] set exceeds the range criteria of the search.
//result_f = -1

integer result_g = llListFindStrided(mylist, ["b",2], 0, -1, 1); //No consecutive elements match ["b",2]
//result_g = -1

integer result_h = llListFindStrided(mylist, ["c"], 0, -1, 2); //With a stride of 2, "c" will be found.
//result_h = 4

integer result_i = llListFindStrided(mylist, ["c"], 0, -1, 3); //With a stride of 3, "c" won't be found.
//result_i = -1

integer result_j = llListFindStrided(mylist, ["c"], 0, -1, 4); //With a stride of 4, "c" will be found.
//result_j = 4

integer result_k = llListFindStrided(mylist, ["c"], 1, -1, 2); //While the stride is even, starting at the 2nd element will miss this stride.
//result_k = -1

</source>
<source lang="lsl2">list numbers = [1, 2, 3, 4, 5];
default
{
state_entry()
{
integer index = llListFindStrided(numbers, [3], 0, -1, 1); //Functionally identical to llListFindList(numbers, [3]);
if (index != -1)
{
list three_four = llList2List(numbers, index, index + 1);
llOwnerSay(llDumpList2String(three_four, ","));
// Object: 3,4
}
}
}</source>
<source lang="lsl2">//You can also search for two items at once to find a pattern in a list
list avatarsWhoFoundMagicLeaves = ["Water Duck", "Green Ham", "Fire Centaur","Red Leaf"];
default
{
state_entry()
{
integer index = llListFindStrided(avatarsWhoFoundMagicLeaves, ["Fire Centaur","Red Leaf"],0,-1,2);
if (index != -1)
{
list output = llList2List(avatarsWhoFoundMagicLeaves, index, index + 1);
llOwnerSay(llDumpList2String(output, ","));
// Object: Fire Centaur, Red Leaf
}
}
}</source>
<source lang="lsl2">//It's nearly a database
list food_db = ["FIRSTNAME", "LASTNAME", "FAVORITE FOOD", "ALLERGIES",
"Awesome", "Resident","Apples",0,
"Charlie", "Kites", "Peanuts", "dogs",
"Cool", "McLastname", "Burgers","peanuts"];
default
{
state_entry()
{
list potential_allergen = ["peanuts"];
integer any_allergies = llListFindStrided(food_db, potential_allergen,4,-1,4);
if (any_allergies != -1)
{
llOwnerSay("Every can eat it");
}
else
{
list output = llList2List(food_db, any_allergens - 3, any_allergens - 2);
llOwnerSay(llDumpList2String(output, " ")+" is allergic to it!");
// Object: Cool McLastName is allergic to peanuts
}
}
}</source>

|helpers=
|also_functions=
{{LSL DefineRow||[[llSubStringIndex]]|Find a string in another string}}
|also_events
|also_tests
|also_articles
|notes
|sort=ListFindList
|cat1=List
|haiku={{Haiku|I made a database|Using Only Some Lists|Find by last name.}}
|cat2
|cat3
|cat4
}}

LlGetNotecardLineSync

2024-03-17T14:39:28Z

Sei Lisa: Add link that explains the Dataserver concept. Presumably the Dataserver is what's doing the caching.

{{LSL_Function
|inject-2={{LSL_Function/negative_index|false|line}}{{LSL_Function/notecard|name|uuid=true}}
|func_id=|func_sleep=0.0|func_energy=10.0
|sort=GetNotecardLineSync
|func=llGetNotecardLineSync
|return_type=string
|p1_type=string|p1_name=name
|p2_type=integer|p2_name=line|p2_desc=Line number in a notecard (the index starts at zero).
|func_desc=Gets the line {{LSLP|line}} of the notecard {{LSLP|name}} from the [[Server architecture#Dataserver|dataserver]] immediately, provided it is cached, and without raising a dataserver event.
|Return_text=containing the text of the requested line from the notecard.
|func_footnote=Returns [[EOF]] if {{LSLP|line}} is past the end of the notecard.
|spec=
This function returns a string containing the requested line from a notecard in prim inventory, without the need for an asynchronous dataserver event, if the notecard is cached/known in its entirety by the simulator. This speeds up acessing notecard lines tremendously, and allows for near instantaneous random access.

If the notecard does not exist it returns the constant [[NAK]] and will shout a message to the debug channel. If the notecard has not been previously cached on the simulator it will return the [[NAK]] constant.

It is not safe to assume a notecard has been previously cached. Data for a previously cached notecard may be dropped from the cache at any time, especially on a busy server.

|caveats=* If notecard contains embedded inventory items (such as textures and landmarks), [[EOF]] will be returned, regardless of the line requested.
*If the requested line is longer than 1024 bytes the returned string will be truncated to the first 1024 bytes of the line.
*A dataserver event does '''not''' get raised. Therefore, other scripts in the linkset are unaware of the processed notecard lines.
|constants
|examples=
<syntaxhighlight lang="lsl2">
string NOTECARD_NAME = "notecard";
key READ_KEY = NULL_KEY;

default
{

touch_start(integer total_number)
{
READ_KEY = llGetNumberOfNotecardLines(NOTECARD_NAME);
}

dataserver(key request, string data)
{
if (request == READ_KEY)
{
integer count = (integer)data;
integer index;

for (index = 0; index < count; ++index)
{
string line = llGetNotecardLineSync(NOTECARD_NAME, index);
if (line == NAK)
{
llOwnerSay("---NAK---");
}
else if (line == EOF)
{
llOwnerSay("---EOF---");
}
else
{
llOwnerSay(line);
}
}
}
}
}
</syntaxhighlight>
|also_functions={{LSL DefineRow||[[llGetNumberOfNotecardLines]]|}}
{{LSL DefineRow||[[llGetNotecardLine]]|}}
|also_events
|also_articles
|also_tests
|permission
|cat1=Notecard
|cat2=
|cat3=
|cat4=
|history=
}}

LSL Operators

2023-11-18T14:21:15Z

Sei Lisa: Add note about confusing precedence of || and &&

{{LSL Header|ml=*}}
Operators are used to cause an operation (or mathematical action) to be performed on one (such as !) or two operands. The easy and common example is 1 + 2 where 1 and 2 are operands, and the '''+''' is the operator. This concept can be extended much further with LSL since operands can be variables with the special case of the assignment operators requiring that the left hand side be a variable.

The following table lists the operators in descending order of evaluation, i.e. higher in the table means higher evaluation precedence. Multiple operators on the same line share evaluation precedence. Parenthesize an expression if you need to force an evaluation order.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Description
! Usage Example
|-
| <code>()</code>
|| parentheses: grouping and evaluation precedence
|| <code>integer val = a * (b + c);</code>
|-
| <code>[]</code>
|| brackets: list constructor
|| <code>list lst = [a, 2, "this", 0.01];</code>
|-
| <code>(''type'')</code>
|| typecasting
|| <code>string message = "The result is:" + (string)result;</code>
|-
| <code>!</code> <code>~</code> <code>++</code> <code>--</code>
|| logical NOT, bitwise NOT, increment, decrement
|| <code>counter++;</code>
|-
| <code>*</code> <code>/</code> <code>%</code>
|| multiply/dot product, divide, modulus/cross product
|| <code>integer rollover = (count + 1) % 5;</code>
|-
| <code>-</code>
|| subtraction, negation
|| <code>integer one = 3 - 2;</code>
<code>integer neg_one = -1;</code>
|-
| <code>+</code>
|| addition, string concatenation
|| <code>integer two = 1 + 1;</code>
<code>string text = "Hello" + " world";</code>
|-
| <code>+</code>
|| list concatenation
|| <code>list myList = [1, 2, 3] + [4, 5];</code>
<code>list newList = oldList + addList;</code>
|-
| <code><<</code> <code>>></code>
|| [https://en.wikipedia.org/wiki/Arithmetic_shift arithmetic] left shift, [https://en.wikipedia.org/wiki/Arithmetic_shift arithmetic] right shift
|| <code>integer eight = 4 << 1;</code>
<code>integer neg_one = -2 >> 1;</code>
|-
| <code><</code> <code><=</code> <code>></code> <code>>=</code>
|| less than, less than or equal to, greater than, greater than or equal to
|| <code>integer isFalse = (6 <= 4);</code>
|-
| <code>==</code> <code>!=</code>
|| comparison: equal, not equal
|| <code>integer isFalse = ("this" == "that");</code>
|-
| <code>&</code>
|| bitwise AND
|| <code>integer zero = 4 & 2;</code>
<code>integer four = 4 & 4;</code>
|-
| <code>^</code>
|| bitwise XOR
|| <code>integer zero = 4 ^ 4;</code>
<code>integer six = 4 ^ 2;</code>
|-
| <code><nowiki>|</nowiki></code>
|| bitwise OR
|| <code>integer four = 4 <nowiki>|</nowiki> 4;</code>
<code>integer six = 4 <nowiki>|</nowiki> 2;</code>
|-
| <code>&&</code> <code><nowiki>||</nowiki></code>
|| logical AND, logical OR
|| <code>integer isFalse = (FALSE && TRUE);</code>
<code>integer isTrue = (FALSE <nowiki>||</nowiki> TRUE);</code>
|-
| <code>=</code> <code>+=</code> <code>-=</code> <code>*=</code> <code>/=</code> <code>%=</code>
|| assignment
|| <code>integer four = 4;</code>
<code>integer eight = four; eight *= 2;</code>
|}

'''Note:''' Modulus (<code>%</code>), like division, cause a ''Script run-time error. Math Error'' when its second operand equals zero.

'''Note:''' The <code>%</code> operator only accepts integer (<code>%</code> as modulus) and vector (<code>%</code> as cross product) operands.

'''Note:''' Unlike most other languages that use the C-style <code>&&</code> and <code>||</code> operators, '''both''' operands are '''always''' evaluated. For example,

<syntaxhighlight lang="lsl2">if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</syntaxhighlight>

: will cause a Math Error rather than say "Aha!"

'''Note:''' The <code>++</code> (increment) and <code>--</code> (decrement) operators have two versions, pre- and post-. The ''pre''-increment (or ''pre''-decrement) operator increments (or decrements) its operand by 1; the value of the expression is the incremented (or decremented) value. The ''post''-increment (or ''post''-decrement) operator increases (or decreases) the value of its operand by 1, but the value of the expression is the operand's original value ''prior'' to the operation.

<syntaxhighlight lang="lsl2">integer count = 0;
if( ++count == 1 ) // 'count' is incremented then evaluated.
llSay(PUBLIC_CHANNEL, "Aha"); // message will be said.</syntaxhighlight>

<syntaxhighlight lang="lsl2">integer count = 0;
if( count++ == 1 ) // 'count' is evaluated then incremented.
llSay(PUBLIC_CHANNEL, "Aha"); // message will not be said.</syntaxhighlight>

'''Note:''' In most programming languages, and in the LSL bitwise operators, the AND operator has greater precedence than the OR operator. However, the LSL logical operators <nowiki>||</nowiki> and <nowiki>&&</nowiki> have ''the same'' precedence. For example:

<syntaxhighlight lang="lsl2">1 || 1 && 0 // result: 0 because it's the same as (1 || 1) && 0</syntaxhighlight>
<syntaxhighlight lang="lsl2">1 | 1 & 0 // result: 1 because it's the same as 1 | (1 & 0)</syntaxhighlight>

'''Note:''' The order of evaluation is from right to left. If the value of x starts as 1 then the first two conditions below evaluate false and the second two evaluate true:

<syntaxhighlight lang="lsl2">(x && (x = 0) == 0 && x)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x && (x = 0) == 0 && x == 0)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x == 0 && (x = 0) == 0)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x == 0 && (x = 0) == 0 && x)</syntaxhighlight>

Both sides are evaluated regardless of the the truth of either side.

==+ Operator==
'''Note:''' Equality test on lists does not compare contents, only the length.
{| {{Prettytable}}
|+
<code>result = left + right</code>
|-{{Hl2}}
!Left Type
!Right Type
!Result Type
!Description
|-
|integer
|integer
|integer
|Adds '''left''' and '''right'''
|-
|integer
|float
|float
|Adds '''left''' and '''right'''
|-
|float
|integer
|float
|Adds '''left''' and '''right'''
|-
|string
|string
|string
|Concatenates '''right''' onto the end of '''left'''.
|-
|list
|*
|list
|Concatenates '''right''' onto the end of '''left'''.
|-
|*
|list
|list
|Affixes '''left''' onto the start of '''right'''.
|-
|vector
|vector
|vector
|Adds '''left''' and '''right'''
|-
|rotation
|rotation
|rotation
|Adds '''left''' and '''right''' Not useful for combining rotations, use [[#* Operator|*]] or [[#/ Operator|/]] instead.
|}

==Shorthand Operators==
{| {{Prettytable}}
|+
Alternatives to the simple '=' operator...
|-{{Hl2}}
!Simple assignment operator
!Shorthand operator
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

=={{Wikipedia|De Morgan's laws|w=n}}==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitwise Equivalencies
!AND
!OR
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boolean Equivalencies
!AND
!OR
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Due to {{Wikipedia|De Morgan's laws|w=n}}, by row, code in the '''AND''' column is logically equivalent to code in the '''OR'''. '''a''' and '''b''' need not be variables, they can be expressions. In certain circumstances these equivalencies can be used to simplify complex code. It is important not to confuse the two sets when using them. The first two rows depict De Morgan's laws as it is formulated, the second two build upon it.

{{clear}}

== Useful Snippets ==

Typecasting can also be used if you have to concatenate many parts into a string:

<syntaxhighlight lang="lsl2">
// the following twp statements are equivalent:
string message1 = (string)["I have ", 5, " children at the average age of ", 8.2, " years"];
string message2 = "I have 5 children at the average age of 8.200000 years";
</syntaxhighlight>

{{LSLC|}}{{LSLC|Syntax}}{{LSLC|Keywords}}
{{LSLC|FixMe}}

User:Gwyneth Llewelyn/sandbox

2023-07-01T12:03:48Z

Sei Lisa:

= Congrats! You've found my sandbox! =

Few people are that wiki-savvy. You've earned my respect, I say.

:If you say so. But you're making it really hard to track actual changes and contributions to the wiki contents, due to your spamming of the changelog page (which is where I found this one). I don't think there's a filter for removing edits from a certain person, and even if there were, I would still be interested in any potential actual content edits you make, to review them. Is that spamming on purpose? Why should anyone care about the availability of wikipedia templates that are not even in use anywhere?
:I maintain a database of LSL keywords and the wiki changelog is my main source of information, together with the sim keywords list which is usually slower to catch up than the wiki, so following the wiki changes is part of my job to maintain the database. I also want to review and fix incorrect information posted by users when I find it. --[[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 05:03, 1 July 2023 (PDT)

{{#vardefine:ip-num|{{#switch:{{{npl|}}}
|32=1|31=2|30=4|29=8
|28=16|27=32|26=64|25=128
|24=256|23=512|22=1024|21=2048
|20=4096|19=8192|18=16384|17=32768
|16=65536|15=131072|14=262144|13=524288
|12=1048576|11=2097152|10=4194304|9=8388608
|8=16777216|7=33554432|6=67108864|5=134217728
|4=268435456|3=536870912|2=1073741824|1=2147483648
|0=4294967296|{{#expr:4294967296 - {{IP_Range/IP2Int|{{{subnet|255.255.255.255}}}}}}}
}}}}

{{IP_Range/IP2Int|{{{subnet|255.255.255.255}}}}}

{{#expr:4294967296 - {{IP_Range/IP2Int|{{{subnet|255.255.255.255}}}}}}}

{{#var:ip-num}}

<phptag>
$foo = 'hello world';
echo ucfirst( $foo . "!!!\n" );
</phptag>

{{#log:32|2}}

LlHMAC

2023-05-07T10:31:54Z

Sei Lisa: If the input changes, so does the output

{{LSL_Function
|func_id=|func_sleep=0.0|func_energy=10.0
|sort=HMAC
|func=llHMAC
|return_type=string
|p1_type=string|p1_name=private_key
|p2_type=string|p2_name=msg
|p3_type=string|p3_name=algorithm
|func_footnote=This function supports md5, sha1, sha224, sha256, sha384, sha512 for '''algorithm'''.
|func_desc
|return_text=that is the {{Wikipedia|Base64|Base64-encoded}} {{Wikipedia|HMAC|HMAC}} hash of '''msg''' when using hash algorithm '''algorithm''' and secret key '''private_key'''.
|spec
|caveats
|constants
|examples=<syntaxhighlight lang="lsl2">default
{
state_entry()
{
string private_key = "secret key";

// Supported algorithims for llHMAC() include:
// md5, sha1, sha224, sha256, sha384, sha512

string algorithm = "sha1";
string msg = "Hello, Avatar!";

string digest = llHMAC(private_key, msg, algorithm);

// For the given private_key/msg/algorithm, expect the HMAC
// digest to be 'ffCDntkagRO5mIEtd2tYzM2Bg8I='
llSay(0, "HMAC digest of message '" + msg + "' using algorithm "
+ algorithm + " is " + digest);
}
}</syntaxhighlight>
|helpers
|also_functions=
{{LSL DefineRow||[[llSignRSA]]}}
{{LSL DefineRow||[[llVerifyRSA]]}}
{{LSL DefineRow||[[llSHA1String]]}}
{{LSL DefineRow||[[llSHA256String]]}}
{{LSL DefineRow||[[llMD5String]]}}
|also_events
|also_articles=
|notes=
|cat1=Hash
|cat2=Encoding
|cat3=Encryption
|cat4
}}

LSL SIM STAT ASSET UPLOADS

2023-04-09T08:41:59Z

Sei Lisa: Wrong text for the constant, wrong page name. Change to #REDIRECT and suggest for deletion.

#REDIRECT [[SIM_STAT_ASSET_UPLOADS]]

[[Category:Suggested_For_Deletion]]

Category:LSL Vector

2023-04-08T22:12:40Z

Sei Lisa: Oops, fix also the variable

{{LSL Header|ml=*}}{{LSLC|}}{{LSLC|Types}}
==Vector==

A vector is a data {{LSLGC|Types|type}} that contains a set of three {{LSLGC|Float|float}} values.

===Components===
Each element can be accessed individually by appending .x, .y, or .z to the variable name.

<syntaxhighlight lang="lsl2">
vector vec = <1, 2, 3>;
float x = vec.x; // 1.0
float y = vec.y; // 2.0
float z = vec.z; // 3.0
</syntaxhighlight>

===Uses===
Vectors are often used for...
* {{LSLGC|Movement|Position}}: x, y, and z are in metres.
* {{LSLGC|Movement|Velocity}}: x, y, and z are in meters per second.
* {{LSLGC|Color|Colour}}: x is Red, y is Green, and z is Blue.

===Operators===
Vectors support the following operations:
==== Addition, Operator "+" ====
<syntaxhighlight lang="lsl2">
vector v = <1, 2, 3> + <0.5, 0.0, 3>; // <1.5, 2.0, 6.0>
</syntaxhighlight>

==== Subtraction, Operator "-" ====
<syntaxhighlight lang="lsl2">
vector v = <1, 1, 1> - <0.5, 0.0, 3>; // <0.5, 1.0, -2.0>
</syntaxhighlight>

==== Dot Product, Operator "*" ====
<syntaxhighlight lang="lsl2">
float f = <9, 2, 7> * <4, 8, 10>; // 122.0
</syntaxhighlight>

==== Cross Product, Operator "%" ====
<syntaxhighlight lang="lsl2">
vector v = <2, 3, 4> % <5, 6, 7>; // <-3, 6, -3>
</syntaxhighlight>

==== Scalar ====
A vector can be multiplied or divided by a [[Float]] or [[Integer]] to scale it.

Each component of the vector will be multiplied or divided by the same value.
<syntaxhighlight lang="lsl2">
vector v = <1, 2, 3> * 1.5; // <1.5, 3.0, 4.5>
vector v = <1, 2, 3> / 1.5; // <0.666667, 1.333333, 2.000000>
</syntaxhighlight>

==== Rotation ====
A vector can be multiplied or divided by a [[Quaternion]] to rotate it.
<syntaxhighlight lang="lsl2">
// 45-degree rotation around the Z (up) axis
rotation r = llEuler2Rot(<0, 0, 45> * DEG_TO_RAD);

// Vector whose direction is 1 meter to the east
vector v = <1, 0, 0>;

// Vector whose direction is north-east
vector rotated = v * r; // <0.707107, 0.707107, 0.000000>

// Vector whose direction is south-east
// (division performs a rotation in the opposite direction)
vector rotated = v / r; // <0.707107, -0.707107, 0.000000>
</syntaxhighlight>

===Useful Snippets===
Check whether a string value is a valid vector:
<syntaxhighlight lang="lsl2">integer IsVector(string s)
{
list split = llParseString2List(s, [" "], ["<", ">", ","]);
if(llGetListLength(split) != 7)//we must check the list length, or the next test won't work properly.
return FALSE;
return !((string)((vector)s) == (string)((vector)((string)llListInsertList(split, ["-"], 5))));
//it works by trying to flip the sign on the Z element of the vector,
//if it works or breaks the vector then the values won't match.
//if the vector was already broken then the sign flip will have no affect and the values will match
//we cast back to string so we can catch negative zero which allows for support of ZERO_VECTOR
}//Strife Onizuka</syntaxhighlight>

Category:LSL Vector

2023-04-08T22:12:00Z

Sei Lisa: Cross product returns a vector, not a scalar

{{LSL Header|ml=*}}{{LSLC|}}{{LSLC|Types}}
==Vector==

A vector is a data {{LSLGC|Types|type}} that contains a set of three {{LSLGC|Float|float}} values.

===Components===
Each element can be accessed individually by appending .x, .y, or .z to the variable name.

<syntaxhighlight lang="lsl2">
vector vec = <1, 2, 3>;
float x = vec.x; // 1.0
float y = vec.y; // 2.0
float z = vec.z; // 3.0
</syntaxhighlight>

===Uses===
Vectors are often used for...
* {{LSLGC|Movement|Position}}: x, y, and z are in metres.
* {{LSLGC|Movement|Velocity}}: x, y, and z are in meters per second.
* {{LSLGC|Color|Colour}}: x is Red, y is Green, and z is Blue.

===Operators===
Vectors support the following operations:
==== Addition, Operator "+" ====
<syntaxhighlight lang="lsl2">
vector v = <1, 2, 3> + <0.5, 0.0, 3>; // <1.5, 2.0, 6.0>
</syntaxhighlight>

==== Subtraction, Operator "-" ====
<syntaxhighlight lang="lsl2">
vector v = <1, 1, 1> - <0.5, 0.0, 3>; // <0.5, 1.0, -2.0>
</syntaxhighlight>

==== Dot Product, Operator "*" ====
<syntaxhighlight lang="lsl2">
float f = <9, 2, 7> * <4, 8, 10>; // 122.0
</syntaxhighlight>

==== Cross Product, Operator "%" ====
<syntaxhighlight lang="lsl2">
float f = <2, 3, 4> % <5, 6, 7>; // <-3, 6, -3>
</syntaxhighlight>

==== Scalar ====
A vector can be multiplied or divided by a [[Float]] or [[Integer]] to scale it.

Each component of the vector will be multiplied or divided by the same value.
<syntaxhighlight lang="lsl2">
vector v = <1, 2, 3> * 1.5; // <1.5, 3.0, 4.5>
vector v = <1, 2, 3> / 1.5; // <0.666667, 1.333333, 2.000000>
</syntaxhighlight>

==== Rotation ====
A vector can be multiplied or divided by a [[Quaternion]] to rotate it.
<syntaxhighlight lang="lsl2">
// 45-degree rotation around the Z (up) axis
rotation r = llEuler2Rot(<0, 0, 45> * DEG_TO_RAD);

// Vector whose direction is 1 meter to the east
vector v = <1, 0, 0>;

// Vector whose direction is north-east
vector rotated = v * r; // <0.707107, 0.707107, 0.000000>

// Vector whose direction is south-east
// (division performs a rotation in the opposite direction)
vector rotated = v / r; // <0.707107, -0.707107, 0.000000>
</syntaxhighlight>

===Useful Snippets===
Check whether a string value is a valid vector:
<syntaxhighlight lang="lsl2">integer IsVector(string s)
{
list split = llParseString2List(s, [" "], ["<", ">", ","]);
if(llGetListLength(split) != 7)//we must check the list length, or the next test won't work properly.
return FALSE;
return !((string)((vector)s) == (string)((vector)((string)llListInsertList(split, ["-"], 5))));
//it works by trying to flip the sign on the Z element of the vector,
//if it works or breaks the vector then the values won't match.
//if the vector was already broken then the sign flip will have no affect and the values will match
//we cast back to string so we can catch negative zero which allows for support of ZERO_VECTOR
}//Strife Onizuka</syntaxhighlight>

Template:Unicode

2023-03-31T06:37:20Z

Sei Lisa: Replace obsolete, broken function with current, working one

{{HoverText|U+{{padleft:{{{1|0}}}|4}}|Unicode character {{LSL Hex/Parse|{{{1|0}}}}}}}

LlSetSoundQueueing

2023-02-03T12:29:20Z

Sei Lisa: New functions don't have IDs

{{LSL_Function/Headless
|inject-2={{Issues/SVC-4260}}{{LSL_Function/boolean|queue|pd=sound queuing:|bool=*|default=false}}{{LSL Function/link-face|link}}

|head={{LSL Function/Head
|func=llSetSoundQueueing
|p1_type=integer|p1_subtype=boolean|p1_name=queue
|func_id=208|func_sleep=0.0|func_energy=10.0
|func_footnote
|func_desc
|return_text
}}
{{LSL Function/Head
|func=llLinkSetSoundQueueing
|p1_type=integer|p1_subtype=link|p1_name=link
|p2_type=integer|p2_subtype=boolean|p2_name=queue
|func_id=|func_sleep=0.0|func_energy=10.0
|func_footnote
|func_desc
|return_text
}}
|summary=Set whether attached sounds wait for the current sound to finish. If {{LSLP|queue}} is [[TRUE]], queuing is enabled, if [[FALSE]] queuing is disabled. Sound queuing is disabled by default.
|caveats=
*The sound queue is only 1 level deep - this means that beside the sound that is currently playing, there can only be 1 sound in reserve. The sound queue is first-come, first-serve.* [[#SVC-4260|SVC-4260]]
*Further to the above, the queue order is reversed when using [[llPlaySoundSlave]] - using the below example, the default behaviour would be to play SoundName1 and SoundName2, however when using the aforementioned function the order would be to play SoundName2 and SoundName3.
*Sound queuing is a property of the prim, not the script. It can be activated and deactivated by any script in the prim and survives script reset, re-rez and script removal.
*If used to make smooth transitions using slave/master sounds the sounds tend to go out of sync.
*Although sounds are queued, the volume of all sounds in the queue is set by the last item in the queue. If your application requires the use of differing volume values, you may wish to implement [[llAdjustSoundVolume]] alongside the sound queue
*There is a very small (but audible) gap of silence between sounds due to network latency and processing time.
*The queued sound must be fully loaded in the viewer, or else it will not play. [[llPreloadSound]] is not always reliable in doing its job.
*Queueing a sound that is identical to the one currently playing will fail. Use [[llLoopSound]] instead.
*While this function does not have a delay, enabling or disabling the sound queue is not instant. It seems to take approx ~0.1 seconds to set the queueing flag.
|constants
|examples=
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llPreloadSound("SoundName1");//This loads the sounds into all in range viewers and cuts delay between sounds.
llPreloadSound("SoundName2");//All sound parameters can be the name of a sound in the prim's inventory or a UUID of a sound");
llPreloadSound("SoundName3"); //This sound will be skipped, as the queue is only 1 level deep.
}
touch_start(integer detected)
{
llSetSoundQueueing(TRUE);//Set to TRUE for queueing and SoundName2 plays after the SoundName1 has ended.
//Set to FALSE only the second will be played since the prim has only one sound emitter and the second was called last.
//Can be set anywhere within the script (if within an event it will activate when the event is triggered.
llPlaySound("SoundName1", 1.0);
llPlaySound("SoundName2", 1.0);
llPlaySound("SoundName3", 1.0); //This sound isn't played as the queue is already full, so this is discarded.
}
}
</syntaxhighlight>
|helpers
|also_functions={{LSL DefineRow||[[llLoopSound]]}}
{{LSL DefineRow||[[llLoopSoundSlave]]|3=Plays a looped sound {{HoverText|attached|The sound moves with the prim}}, synced with the master.}}
{{LSL DefineRow||[[llPlaySoundSlave]]|3=Plays a sound once {{HoverText|attached|The sound moves with the prim}}, synced with the master.}}
{{LSL DefineRow||[[llAdjustSoundVolume]]|3=Adjusts the volume of playing sound(s).}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Sound
|cat2=Prim
|cat3
|cat4
|history={{LSL Added|0.2.0|remote=http://secondlife.wikia.com/wiki/Version_0.2.0}}, the queue is only one level deep.
}}

LlStopSound

2023-02-03T12:27:53Z

Sei Lisa: New functions don't have IDs

{{LSL_Function/Headless
|inject-2={{LSL Function/link-face|link}}

|head={{LSL Function/Head
|func=llStopSound
|func_id=92|func_sleep=0.0|func_energy=10.0
|func_footnote
|func_desc
|return_text
}}{{LSL Function/Head
|func=llLinkStopSound
|p1_type=integer|p1_subtype=link|p1_name=link
|func_id=|func_sleep=0.0|func_energy=10.0
|func_footnote
|func_desc
|return_text
}}
|summary=Stops the attached sound(s) currently playing, if they were started by [[llLoopSound]]
|caveats=
*There is no way to stop a specific sound.
*In a linked set use [[llLinkStopSound]] to stop sound in a specific prim.

|constants
|examples=
<source lang="lsl2">
default
{
state_entry()
{
llLoopSound("string soundname if in object inventory or UUID", 1.0);
}
touch_start(integer total_number)
{
llStopSound();//As if by magic the sound stops!!
}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llSound]]|3=This function has been deprecated, please use [[llPlaySound]] instead.}}
{{LSL DefineRow||[[llPlaySound]]}}
{{LSL DefineRow||[[llPlaySoundSlave]]}}
{{LSL DefineRow||[[llLoopSound]]}}
{{LSL DefineRow||[[llLoopSoundMaster]]}}
{{LSL DefineRow||[[llLoopSoundSlave]]}}
|also_tests
|also_events
|also_articles
|notes
|deprecated
|cat1=Sound
|cat2=Stop
|cat3
|cat4
}}

LlLinkPlaySound

2023-02-03T12:27:07Z

Sei Lisa: New functions don't have ids

{{LSL_Function
|inject-2={{LSL Function/link-face|link}}
{{LSL_Function/inventory|sound|uuid=true|type=sound|volume=volume}}{{LSL Function/link-face|link}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llLinkPlaySound|sort=LinkPlaySound
|p1_type=integer|p1_subtype=link|p1_name=link
|p2_type=string|p2_name=sound
|p3_type=float|p3_name=volume
|p4_type=integer|p4_name=flags|p4_desc=Bit flags used to control how the sound is played.
|func_footnote
|func_desc=Plays {{HoverText|attached|The sound moves with the prim}} {{LSLPT|sound}} once at {{LSLPT|volume}}
|return_text
|spec
|caveats=*A call to llPlaySound replaces any other sound (so that only one sound can be played at the same time from the same prim), except sounds started with the deprecated [[llSound]] which always plays sound files till the end.
*Sound files must be 30 seconds or shorter.
*Sounds are always sampled at 44.1KHz, 16-bit, mono (stereo files will have one channel dropped--merged (as in combined)--when uploading).
*If the object playing the sound is a {{HoverLink|HUD|Heads Up Display}}, the sound is only heard by the user the HUD is attached to.
**To play a sound inworld from a HUD use [[llTriggerSound]].
*It is impossible to play two (or more) sounds at the same time and have them start playing at exactly the same time ~ {{JIRA|VWR-15663}}
**If multiple sound emitters play the same exact sound within range of the viewer at the same time, they are usually not in sync due to latency between the server/client and script execution & communication delays. This can produce echos, odd resonance, and other strange effects that you (probably) do not want.
*When used in conjunction with [[llSetSoundQueueing]], sounds may incorrectly [https://community.secondlife.com/forums/topic/443645-llplaysound-plays-the-sound-twice-or-more/ play more than once.] This can be fixed by disabling the sound queue if only a single sound sample is to be played.
|constants={{LSL Constants/PlaySoundFlags}}
|examples=<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llPlaySound("some_sound",1.0);
}
}
</syntaxhighlight>
|helpers
|also_functions={{LSL DefineRow||[[llTriggerSound]]|3=Plays a sound {{HoverText|unattached|The sound does not moves with the prim}}.}}
{{LSL DefineRow||[[llTriggerSoundLimited]]}}
{{LSL DefineRow||[[llLoopSound]]|3=Plays a sound {{HoverText|attached|The sound moves with the prim}}.}}
{{LSL DefineRow||[[llLoopSoundMaster]]}}
{{LSL DefineRow||[[llLoopSoundSlave]]}}
{{LSL DefineRow||[[llPlaySoundSlave]]}}
{{LSL DefineRow||[[llSetSoundQueueing]]|3=Sets a prim property which allows sounds to be queued, instead of overwriting eachother.}}
{{LSL DefineRow||[[llStopSound]]}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Sound
|cat2
|cat3
|cat4
}}

Jump

2023-01-05T18:40:57Z

Sei Lisa: clarify what "fail silently" means exactly

{{LSL Header|ml=*}}{{#if:

{{#vardefine:name|jump}}

{{#vardefine:p_jump_target_desc|Name of a label inside the same function or event scope.}}
{{#vardefine:p_label_target_desc|A label that can be jumped to, if the jump is in the same scope or child scope. It isn't possible to jump between scopes (such as between functions, events or states).}}

{{#vardefine:header_title|jump {{LSL Param|jump_target|target}};}}
{{#vardefine:header_text|{{{!}}
{{LSL DefineRow|label|target|{{#var:p_jump_target_desc}}}}
{{!}}}
}}

{{#vardefine:constants_nb|
<div id="box">
<h2>@{{LSL Param|label_target|target}};</h2>
<div style="padding: 0.5em">
{{{!}}
{{LSL DefineRow|label|target|{{#var:p_label_target_desc}}}}
{{!}}}
</div>
</div>
}}

{{#vardefine:examples|
<syntaxhighlight lang="lsl2">integer a = 5;
jump over;
@in;
a = 6;
@over;
llOwnerSay((string)a);
if(a < 6)
jump in;
//script will say 5 and then 6</syntaxhighlight>
<syntaxhighlight lang="lsl2">
integer getLinkWithName(string name)
{
integer i = llGetLinkNumber() != 0; // Start at zero (single prim) or 1 (two or more prims)
integer x = llGetNumberOfPrims() + i; // [0, 1) or [1, llGetNumberOfPrims()]
for (; i < x; ++i)
{
if (llGetLinkName(i) == name)
jump break; // Found it! Exit loop early with result
}
i = -1; // No prim with that name, return -1.
@break;
return i;
}
</syntaxhighlight>
More often than not, the rather ugly 'jump' can be avoided, especially in user defined functions, as this version of the above script demonstrates
<syntaxhighlight lang="lsl2">
integer getLinkWithName(string name)
{
integer i = llGetLinkNumber() != 0; // Start at zero (single prim) or 1 (two or more prims)
integer x = llGetNumberOfPrims() + i; // [0, 1) or [1, llGetNumberOfPrims()]
for (; i < x; ++i)
{
if (llGetLinkName(i) == name)
return i; // Found it, return its index
}
return -1; // No prim with that name, return -1.
}
</syntaxhighlight>

}}

{{#vardefine:notes|
It is generally considered inadvisable to use jumps (commonly know as gotos) where other flow control structures could be used.
* {{Wikipedia|Goto}}
* [http://xkcd.com/292/ XKCD:Goto]
}}

{{#vardefine:lso|
<h5>Multiple Jumps Bug</h5>
The following function, <code>jumpy</code>, demonstrates the multiple-jump-sites-to-a-single-target bug. It appears this function should result in an infinite loop, and it does when the script is compiled for the Mono VM. However when compiled for LSO VM because of this bug the second jump never happens and the function returns. LL reported they were unwilling to fix this bug as to do so would be a breaking change. This bug was fixed in the newer Mono VM.

<syntaxhighlight lang="lsl2">jumpy(){
jump next;//first jump
@next;
jump next;//second jump - BUG never gets executed
return;
}</syntaxhighlight>

}}

{{#vardefine:caveats|
*'''In [[LSO]] Only:''' If multiple jump sites are declared for the same target label within scope, then only the first (top to bottom, left to right) will function as expected, all others will silently fail.
*Labels are scoped at the event and function level, meaning that it is not possible to declare duplicate labels within the same event or function, even if the labels are enclosed in different if-statements, loops etc. -- {{JIRA|SVC-6712}}
**If you attempt this, the script will silently fail to compile.
*If code exists after a return that is not encapsulated in a flow control structure, the compiler will return an error about the code being dead even if the code is accessible with a jump. -- {{Jira|SVC-1929}}
}}

{{Issues/SVC-6712}}
{{Issues/SCR-256}}
{{Issues/SVC-1929}}

{{#vardefine:helpers|}}

{{#vardefine:also_header|<h3>Keywords</h3>
{{{!}}
{{LSL DefineRow||[[return]]|}}
{{LSL DefineRow||[[state]]|}}
{{!}}}
}}

{{#vardefine:also_footer|}}
{{#vardefine:also_functions|}}
{{#vardefine:also_events|}}
{{#vardefine:also_articles|}}
{{#vardefine:also_tests|}}
{{#vardefine:location|}}

}}{{LSL Generic}}{{LSLC|Flow Control}}

PRIM OMEGA

2022-11-10T20:07:01Z

Sei Lisa: Fix the extra caveat to make it appear

<onlyinclude>{{#if:

{{#vardefine:omega_const|{{LSL Const|PRIM_OMEGA|integer|18|c=Used to {{GetSet|{{{1|}}}|get the object's llTargetOmega settings|rotate the object at on the given axis at the given rate|/}} }}}}

{{#vardefine:caveats|{{#var:caveats}}
*[[PRIM_OMEGA]] on nonphysical objects, and child prims of physical objects, is only a client side effect; the object or prim will collide as non-moving geometry.
*[[PRIM_OMEGA]] cannot be used on avatars sitting on the object. It will emit the error message "PRIM_OMEGA disallowed on agent".
*If [[PRIM_OMEGA]] does not appear to be working, make sure that that Develop > Network > Velocity Interpolate Objects is enabled on the viewer.
*In the parameters returned by <code>llGetPrimitiveParams([PRIM_OMEGA])</code>, the vector is normalized, and the spinrate is multiplied by the magnitude of the original vector.}}

{{#vardefine:p_axis_desc|arbitrary axis to rotate the object around}}
{{#vardefine:p_spinrate_desc|rate of rotation in radians per second}}
{{#vardefine:p_gain_desc|also modulates the final spinrate and disables the rotation behavior if zero}}

}}</onlyinclude>{{#if:

}}{{LSL Constant
|inject-2={{LSL PrimitiveParam Categorize|Prim}}
|name=PRIM_OMEGA
|type=integer
|value=32
|desc=Used to make the object spin at the specified axis and rate, or retrieve spin settings. See [[llTargetOmega]] for specification.
|examples=<source lang="lsl2">
// Set this prim rotating
llTargetOmega(<1.0,3.0,0.5>, TWO_PI, 1.0);

// Read back this prim's current target omega
list current_omega = llGetPrimitiveParams([PRIM_OMEGA]); // returns [axis, spinrate, gain]
vector axis = llList2Vector(current_omega, 0); // Should be llVecNorm(<1.0,3.0,0.5>)
float spinrate = llList2Float(current_omega, 1); // Should be TWO_PI*llVecMag(<1.0,3.0,0.5>)
float gain = llList2Float(current_omega, 2); // Should be 1.0

// Set all child prims rotating
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_OMEGA, <1.0,3.0,0.5>, TWO_PI, 1.0]);
</source>
Also, can use llSetPrimitiveParams for the root prim.
<source lang="lsl2">// will need two prims linked together for this script.
default
{
state_entry()
{
// make some sort of rotation angle for the omega...
vector rotationAngle = <2.3, 5.5, 9.7> * llTan(85);

// rotate the main prim slowly using the same rotataion angle, rate, and gain...
llSetPrimitiveParams([ PRIM_OMEGA, rotationAngle * 0.3, 1.0, 1.0 ]);

// rotate the link satellite prim separately around its own axis
// it will rotate also around the main prim because the main prim is rotating.
llSetLinkPrimitiveParams(2, [ PRIM_OMEGA, rotationAngle, 1.0, 1.0 ]);
}
}
</source>
|constants
|pa={{LSL Constant/List|i_front=[ {{#var:omega_const}}, |i_end= ]
|text=When used with [[llSetPrimitiveParams]] & [[llSetLinkPrimitiveParams]]
|i1_type=vector|i1_name=axis
|i2_type=float|i2_name=spinrate
|i3_type=float|i3_name=gain
|toc=llSetPrimitiveParams
}}
|pb={{LSL Constant/List|i_front=[[llGetPrimitiveParams]]([ {{#var:omega_const}} ]);|
|r_front=Returns the [[list]] [ |r_end= ]
|text
|toc=llGetPrimitiveParams
|r1_type=vector|r1_name=axis
|r2_type=float|r2_name=spinrate
|r3_type=float|r3_name=gain
}}
|functions=
{{LSL DefineRow||[[llSetPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|}}
{{LSL DefineRow||[[llTargetOmega]]|}}
|events
|location
|history=*Introduced in [[Release Notes/Second Life RC BlueSteel/11#11.06.20.233291|Second Life RC BlueSteel 11.06.20.233291]], June 22, 2011
*Rolled to main server channel the week of 7/11/2011
|cat1
|cat2=Effects
|cat3=Physics
|cat4=Rotation
}}

PRIM OMEGA

2022-11-10T20:05:07Z

Sei Lisa: Fix a number of problems with the example and add caveat

<onlyinclude>{{#if:

{{#vardefine:omega_const|{{LSL Const|PRIM_OMEGA|integer|18|c=Used to {{GetSet|{{{1|}}}|get the object's llTargetOmega settings|rotate the object at on the given axis at the given rate|/}} }}}}

{{#vardefine:caveats|{{#var:caveats}}
*[[PRIM_OMEGA]] on nonphysical objects, and child prims of physical objects, is only a client side effect; the object or prim will collide as non-moving geometry.
*[[PRIM_OMEGA]] cannot be used on avatars sitting on the object. It will emit the error message "PRIM_OMEGA disallowed on agent".
*If [[PRIM_OMEGA]] does not appear to be working, make sure that that Develop > Network > Velocity Interpolate Objects is enabled on the viewer.}}
*In the parameters returned by <code>llGetPrimitiveParams([PRIM_OMEGA])</code>, the vector is normalized, and the spinrate is multiplied by the magnitude of the original vector.

{{#vardefine:p_axis_desc|arbitrary axis to rotate the object around}}
{{#vardefine:p_spinrate_desc|rate of rotation in radians per second}}
{{#vardefine:p_gain_desc|also modulates the final spinrate and disables the rotation behavior if zero}}

}}</onlyinclude>{{#if:

}}{{LSL Constant
|inject-2={{LSL PrimitiveParam Categorize|Prim}}
|name=PRIM_OMEGA
|type=integer
|value=32
|desc=Used to make the object spin at the specified axis and rate, or retrieve spin settings. See [[llTargetOmega]] for specification.
|examples=<source lang="lsl2">
// Set this prim rotating
llTargetOmega(<1.0,3.0,0.5>, TWO_PI, 1.0);

// Read back this prim's current target omega
list current_omega = llGetPrimitiveParams([PRIM_OMEGA]); // returns [axis, spinrate, gain]
vector axis = llList2Vector(current_omega, 0); // Should be llVecNorm(<1.0,3.0,0.5>)
float spinrate = llList2Float(current_omega, 1); // Should be TWO_PI*llVecMag(<1.0,3.0,0.5>)
float gain = llList2Float(current_omega, 2); // Should be 1.0

// Set all child prims rotating
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_OMEGA, <1.0,3.0,0.5>, TWO_PI, 1.0]);
</source>
Also, can use llSetPrimitiveParams for the root prim.
<source lang="lsl2">// will need two prims linked together for this script.
default
{
state_entry()
{
// make some sort of rotation angle for the omega...
vector rotationAngle = <2.3, 5.5, 9.7> * llTan(85);

// rotate the main prim slowly using the same rotataion angle, rate, and gain...
llSetPrimitiveParams([ PRIM_OMEGA, rotationAngle * 0.3, 1.0, 1.0 ]);

// rotate the link satellite prim separately around its own axis
// it will rotate also around the main prim because the main prim is rotating.
llSetLinkPrimitiveParams(2, [ PRIM_OMEGA, rotationAngle, 1.0, 1.0 ]);
}
}
</source>
|constants
|pa={{LSL Constant/List|i_front=[ {{#var:omega_const}}, |i_end= ]
|text=When used with [[llSetPrimitiveParams]] & [[llSetLinkPrimitiveParams]]
|i1_type=vector|i1_name=axis
|i2_type=float|i2_name=spinrate
|i3_type=float|i3_name=gain
|toc=llSetPrimitiveParams
}}
|pb={{LSL Constant/List|i_front=[[llGetPrimitiveParams]]([ {{#var:omega_const}} ]);|
|r_front=Returns the [[list]] [ |r_end= ]
|text
|toc=llGetPrimitiveParams
|r1_type=vector|r1_name=axis
|r2_type=float|r2_name=spinrate
|r3_type=float|r3_name=gain
}}
|functions=
{{LSL DefineRow||[[llSetPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|}}
{{LSL DefineRow||[[llTargetOmega]]|}}
|events
|location
|history=*Introduced in [[Release Notes/Second Life RC BlueSteel/11#11.06.20.233291|Second Life RC BlueSteel 11.06.20.233291]], June 22, 2011
*Rolled to main server channel the week of 7/11/2011
|cat1
|cat2=Effects
|cat3=Physics
|cat4=Rotation
}}

PosJump

2022-10-03T07:16:16Z

Sei Lisa: Revert for historic purposes and add a clear note about the replacement

{{LSL Tip|This page contains obsolete information and is kept only for historic purposes. The exploit that allowed this method to work was fixed in 2012. Use [[llSetRegionPos]] instead.}}

Here's an interesting method for bypassing the 10m limitation in Non-Physical movement. '''Be aware that IT WILL NOT WORK FOREVER, there are plans to fix this bug - for long-term use, rely on [[warpPos]].''' Alternatives that offer the same functionality are being considered. Until there's an alternative, this bug ''may'' be allowed to persist. More information [http://jira.secondlife.com/browse/SVC-4089 here.]

'''A replacement function ''[[llSetRegionPos]]()'' has been released and is now live grid-wide.'''

'''As of August 13th, 2012 there are already reported breakages of this function on some Channels.'''

<syntaxhighlight lang="lsl2">
posJump(vector target_pos)
{
// An alternative to the warpPos trick without all the overhead.
// Trickery discovered by Uchi Desmoulins and Gonta Maltz. More exact value provided by Fake Fitzgerald.
llSetLinkPrimitiveParamsFast(!!llGetLinkNumber(), [PRIM_POSITION, <1.304382E+19, 1.304382E+19, 0.0>, PRIM_POSITION, target_pos]);
}
//the !!llGetLinkNumber() thing is a little trick to always point to the root regardless of where the script is or whether the linkset got only one or more prims.
// If you are using a single prim object, you can substitute 0 or LINK_THIS. If it is a multiple prim object, you can substitute LINK_ROOT.
</syntaxhighlight>

If the target position turns out to be no-entry, your object will go offworld. So Alias Turbo included a step that sends the object back to its starting position (just in case!) before trying the target position again. So in the case that the target position is no-entry, it will either move 10m at most, or not at all.
<syntaxhighlight lang="lsl2">
safe_posJump(vector target_pos)
{
// An alternative to the warpPos trick without all the overhead.
// Trickery discovered by Uchi Desmoulins and Gonta Maltz. More exact value provided by Fake Fitzgerald. Safe movement modification provided by Alias Turbo.
vector start_pos = llGetPos();
llSetLinkPrimitiveParamsFast(!!llGetLinkNumber(), [PRIM_POSITION, <1.304382E+19, 1.304382E+19, 0.0>, PRIM_POSITION, target_pos, PRIM_POSITION, start_pos, PRIM_POSITION, target_pos]);
}
//the !!llGetLinkNumber() thing is a little trick to always point to the root regardless of where the script is or whether the linkset got only one or more prims.
// If you are using a single prim object, you can substitute 0 or LINK_THIS. If it is a multiple prim object, you can substitute LINK_ROOT.
</syntaxhighlight>

Talk:LlTeleportAgent

2022-10-03T06:50:44Z

Sei Lisa: uses

== Alternate version for freaky future-proofness ==

{{LSL_Function|func_id|mode=request|func_sleep=0.1|func_energy=10.0|func=llTeleportAgent|sort=TeleportAgent|p1_type=list|p1_name=parameters||func_desc=[[User:SignpostMarv Martin|SignpostMarv Martin]]'s freaky future-proofed multi-purpose take on [[llTeleportAgent]].
* TELEPORT_AGENT,(key) id - the key of the Resident you wish to teleport (required, also signals the start of a subset in batch queries- see the second example)
* TELEPORT_REGION,(string) region - the name of the region you wish to send TELEPORT_AGENT to (if missing, defaults to current region)
* TELEPORT_POSITION,(vector) position - the destination you wish to send TELEPORT_AGENT to, specified in local co-ordinates (if missing, defaults to <128.0, 128.0,0.0>)
* TELEPORT_FOCUS,(vector) focus - is intended to focus the avatar's attention on a location, specified in local co-ordinates (if missing, defaults to TELEPORT_POSITION)
* TELEPORT_PERMISSION_REQUIRED, (integer) boolean - supply either TRUE or FALSE (defaults to FALSE)
* TELEPORT_LOGINURI, (string) uri - if specified, restarts the client as if called with '''-url secondlife://region/x/y/z/ -loginuri TELEPORT_LOGINURI''' (not required, if missing doesn't do anything)
* TELEPORT_VALIDATE_ONLY (integer) boolean - if set to TRUE, the function only returns whether or not the supplied parameters are valid
|return_text=(integer) success|spec|caveats=* TELEPORT_AGENT must be the script owner or must be on script owner's land.
* If TELEPORT_AGENT is not on the script owner's land, PERMISSION_TELEPORT must be granted and TELEPORT_PERMISSION_REQUIRED is ignored/defaults to TRUE
* Aside from TELEPORT_AGENT, the order of parameters within a subset does not matter. Only the last TELEPORT_VALIDATE_ONLY in the list is processed|examples=Single-user teleportation:
<pre>
teleport_to_ahern(key id)
{
llTeleportAgent([TELEPORT_AGENT,id,TELEPORT_REGION,"Ahern"]);
}
default
{
touch_start(integer touched)
{
if(llDetectedKey(0) == llGetOwner()) // Not sure of the correct way to handle things on deeded land
{
teleport_to_ahern(llDetectedKey(0));
}
else
{
llRequestPermissions(llDetectedKey(0),PERMISSION_TELEPORT);
}
}
run_time_permissions(integer perms)
{
if(perms & PERMISSION_TELEPORT)
{
teleport_to_ahern(llGetPermissionKey());
}
else
{
llWhisper(0,"Teleportation permissions must be granted.");
}
}
}</pre>
Star-Trek style teleportation (works on script owner's land only):
<pre>
vector transporter_size = ZERO_VECTOR;
vector transporter_pos = ZERO_VECTOR;
key caller = NULL_KEY;
integer n = 0;
list away_team = [];
list calibration = [TELEPORT_REGION,"Ahern"];
vector destination = <128.0,128.0,0.0>;
default
{
state_entry()
{
transporter_size = llGetScale();
llListen(1,"",NULL_KEY,"Beam me up Scotty");
}
listen(integer channel,string name,key id,string message)
{
caller = id;
llSensor("",NULL_KEY,AGENT,transporter.x/2.0,PI_BY_TWO);
}
sensor(integer sensed)
{
llWhisper(0,"Energising");
n = 0;
while(n < sensed)
{
away_team = (away_team=[]) + away_team + [TELEPORT_AGENT,llDetectedKey(n)] + calibration + [TELEPORT_POSITION,llDetectedPos(n) - transporter_pos];
++n;
}
llTeleportAgent(away_team);
away_team = [];
}
no_sensor()
{
llInstantMessage(caller,"I canee do it Captin");
}
}
</pre>
|}}

Just a note, my take on the function returns a bitfield containing any errors in execution.
* TELEPORT_ERROR_REGION_UNREACHABLE- would be used if the sim is offline, non-existant, teleporting to that region is disabled etc.
* TELEPORT_ERROR_INVALID_URI- would be used when the login URI is either malformed, blacklisted or not whitelisted at the estate or parcel level
** If TELEPORT_LOGINURI has been disabled ''entirely'' at the estate or parcel, this is also returned.
** White/Blacklisting would be useful for Residents with places on multiple grids to prevent griefers from putting a prim over their kiosk to redirect them to a phishing site.
* TELEPORT_INVALID_AGENT- would be used if the agent is not online, or not in the current sim. Or obviously, if the value passed along with TELEPORT_AGENT wasn't a valid UUID :-P
(it'd be nice if someone tweaked the template to have the correct parameters for the return stuffages based on these notes)

I'm thinking that for batch queries, the ordering restrictions should be relaxed a bit to allow for optimisation- e.g. any params specified before the first TELEPORT_AGENT set the defaults for the entire list.
[[User:SignpostMarv Martin|SignpostMarv Martin]] 19:54, 27 April 2007 (PDT)

:LL will never change the parameters of a function as it would break existing script and lead to confusion. Request a new function. -- [[User:Strife Onizuka|Strife Onizuka]] 08:11, 28 April 2007 (PDT)
::This function doesn't exist, so that rule doesn't apply.
::[[User:SignpostMarv Martin|SignpostMarv Martin]] 08:48, 28 April 2007 (PDT)
::: Internally, the llTeleportAgent project's # is SL-13078. --[[User:Torley Linden|Torley Linden]] 14:28, 30 April 2007 (PDT)
::: OMG I'm sorry for jumping on you I seriously thought there was a function in existence with this name (think it was confusing it with [[llTeleportAgentHome]]). -- [[User:Strife Onizuka|Strife Onizuka]] 14:45, 30 April 2007 (PDT)
: While a nice idea I think the function as already described is fine, just needs to be actually implemented, you know, before the world ends ^^ -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 11:25, 14 October 2010 (UTC)

== Was recently implemented ==

The function here (not the freaky one above, the original desired implementation) was recently implemented and seems to be recognised. Albeit disabled? --[[User:Nexii Malthus|Nexii Malthus]] 17:23, 4 November 2011 (PDT)
:Ah, okay, they are working on it, it is indeed currently limited. --[[User:Nexii Malthus|Nexii Malthus]] 20:54, 4 November 2011 (PDT)
::Limited in what way? The limitations described on the function's page are all reasonable, but I dread there being unreasonable limitations that render the function pointless. -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 04:08, 5 November 2011 (PDT)

== Automatic permission grants? ==

Without some kind of automatic permission grants (to landowner and attachments, at least) the only advantage this has over llMapDestination is that it doesn't require one click, and (as noted below) it's more limited in other ways. Even for intra-region teleports the existing WarpMove and PosJump hacks are more useful. There were comments by Lindens that such grants were going to be included, but there's no mention of them on this page. -- [[User:Argent Stonecutter|Argent Stonecutter]] 03:30, 30 May 2012 (PDT)

:Without landowner or estate owner waivers it is not very useful. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:10, 30 May 2012 (PDT)

== Using this to Rotate Avatars ==

Another often requested feature is the ability to rotate avatars. I'm very curious if teleporting an avatar to it's current position in the current sim but with a different lookat would effectively rotate it. Teleports often hang or fail when attempting to teleport short distances, so I hope this would work - unless there's going to be a more formal way to rotate avatars. We don't have one![[User:Adeon Writer|Adeon Writer]] 18:36, 29 December 2011 (PST)
: Apparently it can do that, or something very close. It helps to have the minimap on rotate to see this example in action -- When you walk through a Linden Realms portal, you are sent to a spot in the air just above a transparent llVolumeDetect prim. On collision with the prim, you can see that your avatar is spun around to face the workshop on landing. There is still a bit of a fall after this so it's maybe not strictly a teleport to the same spot, but the rotation part seems to be working OK inside the same region.

: Forgot to add -- It is not clear from the LR implementation if the rotation thing is possible across regions or not. The portals rely on landmarks, so they don't have enough data to set it on that end. --[[User:Cerise Sorbet|Cerise Sorbet]] 19:56, 29 December 2011 (PST)

::Cool. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:36, 31 December 2011 (PST)

== Why Even Bother Implementing this? ==

The currently proposed implementation ([https://wiki.secondlife.com/w/index.php?title=LlTeleportAgent&oldid=1167818 at time of writing]) is a function apparently has ignored every word of the (lengthy) discussion upon the subject. I'm posting to complain that far better proposals have been completely ignored, and wish to strongly request that [[User:Haravikk_Mistral/LlTeleportAgent|this proposed function]] be implemented instead, so that we might actually have a useable function.

Let's take a quick comparison of the current proposal versus the one that was requested years ago:

{| {{Prettytable|style=margin: 0px 0px 10px 1pt;}}
|-
! Feature !! [[LlTeleportAgent|Linden Proposal]] !! [[User:Haravikk_Mistral/LlTeleportAgent|Original Proposal]]
|-
| Co-ordinates || Uses static landmark requiring landmark creation, cannot be changed dynamically and requires asset retrieval. || Uses region name and co-ordinates as per [[LlMapDestination]], which can be changed dynamically by script.
|-
| Permissions || Uses inflexible script permissions system, requiring a dialogue in most common cases. || Allows the viewer to accept/decline teleport requests, allowing any mixture of automatic, dialogue-based or disabled teleport requests. Potentially allowing for different behaviour for objects on owner's land, friend's objects etc.
|-
| Implementation || Entirely new function with new permissions request and asset retrieval before teleport. || Uses existing [[llMapDestination]] implementation extended with a single bit to specify a teleport request.
|}

And this is me being generous, and the result is pretty damning. There is literally no advantage to the Linden proposal.
Hell, consider some simple cases:

{| {{Prettytable|style=margin: 0px 0px 10px 1pt;}}
|-
! Use-Case !! Description !! [[LlTeleportAgent|Linden Proposal]] !! [[User:Haravikk_Mistral/LlTeleportAgent|Original Proposal]]
|-
| Object Relay || By far the simplest system in use today, an object-relay allows an avatar to teleport between tele porters. For example from one on the ground to one in a skybox. || Requires each object in a simple teleport relay to contain a landmark (or have a list of keys) for all the other objects in the relay so that they can be selected as a teleport destination. Customer use-case; place tele porters, create landmark for each one, place set of landmarks into each teleport (excluding the one for the tele porter you're editing), use tele porters. || Can use messaging or object keys (if local) to dynamically maintain a list of active teleport relay points, and use this information to determine where to teleport the avatar. This allows a relay to be setup by anyone simply by placing the objects, and can update dynamically if the relay is changed. Customer use-case; place tele porter objects, use tele porters.
|-
| Teleport Broker || Commonly used by merchant stalls to direct avatars to their main store, but also useful for sending people to popular clubs or other useful locations. || Requires each broker to contain a landmark (or have a list of keys) for each location that a user might wish to teleport to. If a location is to be added then a new landmark must be created, so too if a destination is relocated, requiring landmarks to be replaced. || Can simply grab data from a messaging service (such as a website), which can be trivially updated without requiring the creation of a landmark. ||
|-
| Infinite corridor || More interesting case, but a simple corridor that appears to go on forever using some visual trickery. When the avatar reaches a certain "end" point they are teleported invisibly back to the "start" to continue onwards. || Requires creation of landmarks for the start and end points, such that if the corridor is moved it will stop working. If more than one avatar is using the corridor then they will both be given permissions dialogues every time the corridor loops. || End points of the corridor can dynamically link to one another, allowing the corridor to be relocated at will. Teleportation is seamless (if in same region) and requires no dialogue unless viewer uses more restrictive than normal settings.
|}

There is literally no advantage to the Linden proposed system, other than the fact it doesn't require them to read or acknowledge the feature that was '''actually''' requested by their users.
 -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 03:25, 30 May 2012 (PDT)

:The asset retrieval aspect is covered by [[llTeleportAgentGlobalCoords]]. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:10, 30 May 2012 (PDT)

:Honestly I don't like that they have mixed both the intra-region and the landmark teleporter into the same function. It makes the documentation harder to write.

::Ack, okay so I've over-reacted a bit having missed the other function. Even so, I don't see any need to have a landmark based function, and the coords function is still pretty unwieldy; if you need to use an llRequest* function to fetch necessary data, then there's something very wrong with the implementation! The permissions issue is still backwards; receiving of teleports is already in the viewer from other users, there's simply no need for server-side permissions to handle teleports, as the viewer can easily decide whether to automatically allow or deny a request, and it gives users the control they desire. The new experience permissions will help but there's just no need for them in this case, plus in the viewer it'd be possible to easily ignore requests that come too soon after the last. I just don't like anything about this implementation when we had a clear, and already exhaustively discussed solution proposed. -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 08:36, 30 May 2012 (PDT)

:::I think the permission is so you can grant them to an attachment so it can TP you (send you back to town when diablo smites you sort of thing). It's a good solution for Linden Realms, not so good for the rest of us. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 15:43, 30 May 2012 (PDT)

==Only works for the owner?==
Where does the information that this only works for the object's owner come from? That appears to be new restriction, and one that makes the function pretty pointless. [[User:Innula Zenovka|Innula Zenovka]] 17:08, 17 July 2012 (PDT)

:It is a [https://wiki.secondlife.com/w/index.php?title=LlTeleportAgent&diff=1170536&oldid=1170491 new restriction], it came after the botched roll-out. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:14, 18 July 2012 (PDT)

::Does this not effectively render the function largely useless, or is it simply to prevent abuse while problems are fixed? i.e - is it restricted to the object owner only for testing purposes? -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 12:47, 18 July 2012 (PDT)

:::I'm not in the loop, I just aggregate. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:14, 18 July 2012 (PDT)

The current description of functionality in the caveats is wrong, but I can't for the life of me find the text to edit it. Says that If landmark is not an empty string and...
landmark is missing from the prim's inventory or it is not a landmark then it fails silently. That was true, but with the implementation of https://jira.secondlife.com/browse/SCR-342 It now gives a script error: "Teleport failed: landmark name provided but assets is missing or invalid." If someone can figure out how to edit that comment, please do so.
[[User:Darien Caldwell|Darien Caldwell]] 16:39, 18 July 2012 (PDT)

:It's a template flag. I've disabled it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:14, 18 July 2012 (PDT)

== Throttle ==

There appears to be a throttle on this function similar to playing sounds. Calling it 2 times in a few seconds yields:
"Too many llTeleportAgent requests. Throttled until average falls."
Does anyone know the specifics?

--[[User:Gregory Maurer|--Gregory Maurer]] 19:20, 31 July 2012 (PDT)

:I don't see any Jira's mentioning a [https://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=%28summary+%7E+%22llTeleportAgent%22+OR+description+%7E+%22llTeleportAgent%22%29+and+%28summary+%7E+%22throttle%22+OR+description+%7E+%22throttle%22+or+comment+%7E+%22throttle%22%29++ORDER+BY+votes+DESC%2C+updated+DESC throttle for llTeleportAgent] (other than unacknowledged feature suggestions). Maybe open a new Jira for it? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:55, 1 August 2012 (PDT)

== Caveats: BUG 4062(or equivalent) Fixed? ==

This bug has been closed and reopened under different numbers several times, I think, but -- at least as I understand it -- it was finally fixed in [http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/14#14.04.16.289178 RC Magnum 14.04.16.289178]. Presumably that was rolled out for the whole grid shortly thereafter, but I'm afraid I haven't checked. [[User:Innula Zenovka|Innula Zenovka]] 08:51, 23 June 2014 (PDT)
:It was fixed as SCR-382 which became {{Jira|BUG-5533}}. There are no new JIRA reports of dead scripts after teleport since then. --[[User:ObviousAltIsObvious Resident|ObviousAltIsObvious Resident]] 09:32, 23 June 2014 (PDT)

== These days, isn't it easier to use secondlife:///app/teleport/region/x/y/z ? ==

Even some [[Teleporter Anywhere|scripts here on the LSL Library]] just spew out {{code|secondlife:///app/teleport/region/x/y/z}} and let the user click on it; as of 2022, you even get a chance to directly teleport to the link ''or'' see it on the World Map first.

Aye, I know, it's incredibly clunky, but almost as clunky as asking permissions to the object owner before doing a teleport (which, taking into account that the owner will be the ''only'' person to be able to use the teleporter, really makes absolutely no sense at all)...

{{Tick}} I'd vote to mark this function as well as [[llMapDestination]] as deprecated and obsolete, and get rid of them!

— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 13:50, 1 October 2022 (PDT)

:Just because you can't figure out uses, doesn't mean there aren't. Remember that a script holds the permissions indefinitely once granted. This function allows you, for example, to make a destination HUD with pictures and whatnot; the HUD would ask for permissions only once. We're also using it (also with a HUD that only asks for permissions once) to simulate entering or exiting a cave where there's no physical room for one; the user is teleported to the entrance without clicking anywhere, giving a kind of seamless experience. Chat links are no substitutive for that usage at all. --[[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 23:50, 2 October 2022 (PDT)

Template:LSL Function/give

2022-09-24T18:14:16Z

Sei Lisa: Attempt to fix llGiveInventory to not say that it can give to groups

<includeonly>{{LSL Injection Test}}{{#if:

{{#vardefine:target-type|~{{#expr:{{#if:{{{avatar|}}}|1|0}}+{{#if:{{{prim|}}}{{{object|}}}|2|0}}+{{#if:{{{link|}}}|4|0}}}}}}

{{#vardefine:pcaveats|{{#var:caveats}}}}
{{#vardefine:caveats}}

{{LSL Function/{{#switch:{{#var:target-type}}|~1=avatar|~2=prim|~4=link|uuid}}|group=|object={{{object|}}}|sim={{{sim|}}}|{{{1|}}}|}}

{{LSL Function/inventory|{{{2|}}}|type={{{type|}}}|uuid={{{uuid|}}}|full={{{full|}}}|insert={{{insert|}}}|}}

{{#vardefine:caveats|{{#var:pcaveats}}{{#ifeq:{{#var:target-type}}|~4||
* If '''{{LSL Param|{{{1}}}}}''' is {{#switch:{{#var:target-type}}|~1=not the owner|~2=not owned by the same person|not the owner nor shares the same owner}}, {{#ifeq:{{{uuid|}}}|true|'''{{LSL Param|{{{2}}}}}''' is not a [[UUID]]}} and '''{{LSL Param|{{{2}}}}}''' does not have transfer permissions, an error is shouted on {{#var:DEBUG_CHANNEL}}.
{{#if:{{{copyok|}}}||
* If '''{{LSL Param|{{{2}}}}}''' {{#if:{{{full|}}}|is not {{HoverLink|:Category:LSL_Permissions/Asset|copy, mod and transfer|full permissions}}|permissions do not allow copy}}, the transfer fails and an error is shouted on {{#var:DEBUG_CHANNEL}}.{{#switch:{{#var:target-type}}
|~1=|* If '''{{LSL Param|{{{1}}}}}''' {{#ifeq:{{#var:target-type}}|~2||is a prim that}} is not in the same region an error is shouted on {{#var:DEBUG_CHANNEL}}.}}}}}}
{{#switch:{{{type|}}}|script|=* When scripts are copied or moved between inventories, their state does not survive the transfer. Memory, event queue and execution position are all discarded.|#default=}}
{{#var:caveats}}}}

{{#vardefine:pcaveats}}

}}</includeonly><noinclude>
{{Multi-lang}}
{{UpdateLink}}
{{#vardefine:caveats}}{{#vardefine:p_target_desc}}{{#vardefine:p_target_hover}}{{#vardefine:p_item_desc}}{{#vardefine:p_item_hover}}
{| {{Prettytable}} {{#vardefine:caveats}}
|+<code><nowiki>{{</nowiki>{{FULLPAGENAMEE}}<nowiki>|target|item|type=sound|uuid=true}}</nowiki></code>{{{{FULLPAGENAMEE}}|target|item|type=sound|uuid=true}}
|-{{Hl2}}
! #var
! value
|-
{{VarPair|caveats}}
|-
{{VarPair|p_target_desc}}
|-
{{VarPair|p_target_hover}}
|-
{{VarPair|p_item_desc}}
|-
{{VarPair|p_item_hover}}
|}
{{#vardefine:caveats}}{{#vardefine:p_target_desc}}{{#vardefine:p_target_hover}}{{#vardefine:p_item_desc}}{{#vardefine:p_item_hover}}
{| {{Prettytable}} {{#vardefine:caveats}}
|+<code><nowiki>{{</nowiki>{{FULLPAGENAMEE}}<nowiki>|target|item|type=sound|uuid=false}}</nowiki></code>{{{{FULLPAGENAMEE}}|target|item|type=sound|uuid=false}}
|-{{Hl2}}
! #var
! value
|-
{{VarPair|caveats}}
|-
{{VarPair|p_target_desc}}
|-
{{VarPair|p_target_hover}}
|-
{{VarPair|p_item_desc}}
|-
{{VarPair|p_item_hover}}
|}
{{#vardefine:caveats}}{{#vardefine:p_target_desc}}{{#vardefine:p_target_hover}}{{#vardefine:p_item_desc}}{{#vardefine:p_item_hover}}
{| {{Prettytable}} {{#vardefine:caveats}}
|+<code><nowiki>{{</nowiki>{{FULLPAGENAMEE}}<nowiki>|target|item|type=script|uuid=true|link=*}}</nowiki></code>{{{{FULLPAGENAMEE}}|target|item|type=script|uuid=true|link=*}}
|-{{Hl2}}
! #var
! value
|-
{{VarPair|caveats}}
|-
{{VarPair|p_target_desc}}
|-
{{VarPair|p_target_hover}}
|-
{{VarPair|p_item_desc}}
|-
{{VarPair|p_item_hover}}
|}
</noinclude>

Listen

2022-09-24T18:02:06Z

Sei Lisa: Groups can't be listened to either

{{LSL_Event|event_id=12|event_delay
|inject-2={{LSL Function/uuid|id|group=}}{{Issues/SVC-92}}
|event=listen
|p1_type=integer|p1_name=channel|p1_desc=channel that the message appeared on.
|p2_type=string|p2_name=name|p2_desc=prim name or avatar {{LSLGC|Legacy Name}}
|p3_type=key|p3_name=id|p3_desc
|p4_type=string|p4_name=message|p4_desc=text spoken
|event_desc=Triggered by chat, use [[llListen]] to enable and filter
|constants={{LSL Constants/Chat}}
|spec
|caveats=*On [[state]] change or [[llResetScript|script reset]] all listens are [[llListenRemove|closed]] automatically.
*When an object changes owner any listen registered with [[llGetOwner]] will not automatically update itself until the script is reset. The scripter can catch this scenario per the example below.
*If a message satisfies the filters of multiple [[llListen]]s registered by the script, only one event will be raised.
*A prim cannot hear/listen to chat it generates.
*The location of the listen is not at the listening prim's location but at the root prim's location. This is to deter people using child prims for spying over parcel boundaries. {{LSLGC|Chat|Chat generating functions}} on the other hand generate chat at the calling prim's location (and not at the root prim's location).
*The above is not true for chat generated by avatars sitting on the same object as the listening prim.
|examples=
{{LSL Tip|Please make sure that you close open listeners where possible. You'll make the Second Life experience so much better when paying attention to details here.}}
Trivial example to listen to any chat from the object owner and respond once. To reduce lag and avoid spamming surrounding users, it is vastly preferable to listen on channels other than 0 and to trigger the listen event by chatting on an alternative channel such as '/5 hello'.
<source lang="lsl2">
// says beep to owner the first time owner says something in main chat;
integer listen_handle;

default
{
state_entry()
{ //Registers the listen to the owner of the object at the moment of the call. This does not automatically update when the owner changes.
// Change 0 to another positive number to listen for '/5 hello' style of chat.
listen_handle = llListen(0, "", llGetOwner(), "");
}

listen( integer channel, string name, key id, string message )
{
llOwnerSay("beep");
// Stop listening until script is reset
llListenRemove(listen_handle);
}

changed(integer mask)
{ //Triggered when the object containing this script changes owner.
if(mask & CHANGED_OWNER)
{
llResetScript(); // This will ensure the script listens to the new owner, and doesn't continue listening to the creator.
}
}
}</source>

|helpers
|also_header
|also_events
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llListenControl]]|}}
{{LSL DefineRow||[[llListenRemove]]|}}
{{LSL DefineRow||[[llDialog]]|}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the [[PUBLIC_CHANNEL]]}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat limited to region}}
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Communications
|cat2=Chat
|cat3
|cat4
}}

LlGetBoundingBox

2022-09-24T17:53:53Z

Sei Lisa: What is the bounding box of a group? :)

{{LSL_Function
|inject-2={{LSL_Function/uuid|object|sim=*|group=}}
|func_id=277|func_sleep=0.0|func_energy=10.0
|func=llGetBoundingBox|return_type=list
|p1_type=key|p1_name=object
|func_footnote=The bounding box is for the entire link set, not just the requested prim. Returns an empty list (<code>[]</code>) if {{LSLP|object}} is not found.
|func_desc
|return_text=that is the bounding box of {{LSLP|object}} relative to its root prim, in [[Viewer_coordinate_frames#local|local coordinates]]. Format: <code>[ (vector) {{HoverText|min_corner|vector min_corner;}}, (vector) {{HoverText|max_corner|vector max_corner;}} ]</code>
|spec=
The physical representation of an object is made up of the shape of the prims and avatars seated upon it. The bounding box is the smallest possible cuboid which can contain the physical representation of the object and have its faces aligned to the object's local axes.
|caveats=
* Regardless if {{LSLP|object}} is a non-root prim, the bounding box of the object is returned. This also applies if {{LSLP|object}} is an agent sitting on an object - the bounding box of the sat-upon object (including the agent's shape) is returned.
* Attachments have no bounding boxes of their own (as they have no physical interaction{{Footnote|[[Phantom]] and [[VolumeDetect]] do have physics interactions, which is why they still have bounding boxes.|Phantom and VolumeDetect do have physics interactions, which is why they still have bounding boxes.}}), instead the bounding box of the avatar is returned.

|constants
|examples=<source lang="lsl2">default//An avatar bounding box ruler thingy
{
state_entry()
{
llSetStatus(STATUS_PHANTOM, TRUE);
}

touch_start(integer total_number)
{
key target = llDetectedKey(0);
list box = llGetBoundingBox(target);
vector center = llDetectedPos(0) + (llList2Vector(box, 0) + llList2Vector(box, 1)) * 0.5;
vector size = llList2Vector(box, 1) - llList2Vector(box, 0);
llSetPrimitiveParams([PRIM_POSITION, center, PRIM_SIZE, size]);
llSetText("Name: " + llDetectedName(0) + ", UUID: " + (string)target +
"\nBounding Box Size: " + (string)size, <1.0, 1.0, 1.0>, 1.0);
}
}</source>

<source lang="lsl2">
// Enclose a named object in the tightest possible box
// that is aligned with the object's root prim axes.
// Drop this script in a box near the object to enclose
// (must be in a 10m range)

string ObjectNameToEnclose = "SearchMe";
key UUID;

default
{
state_entry()
{
llSensor(ObjectNameToEnclose, "", ACTIVE | PASSIVE, 10, PI);
}

sensor(integer n)
{
UUID = llDetectedKey(0);
llSetTimerEvent(1);
}

timer()
{
list info = llGetObjectDetails(UUID, [OBJECT_POS, OBJECT_ROT]) + llGetBoundingBox(UUID);
vector pos = llList2Vector(info, 0);
rotation rot = llList2Rot(info, 1);
vector corner1 = llList2Vector(info, 2) * rot + pos;
vector corner2 = llList2Vector(info, 3) * rot + pos;
vector size = llList2Vector(info, 3) - llList2Vector(info, 2);

llSetPos((corner1 + corner2) * 0.5); // Set position to the midpoint (average) of the corners
llSetRot(rot);
llSetScale(size);
}
}
</source>

|helpers=
<source lang="lsl2">
//(bool) isInPrim - determines whether a given vector position in the region is within the borders of a cuboid,
// respecting the cuboid's rotation.
integer isInPrim(vector vPos)
{
list bb = llGetBoundingBox(llGetKey());
vector min = llList2Vector(bb, 0);
vector max = llList2Vector(bb, 1);
vPos = (vPos - llGetPos()) / llGetRot();
float fTemp;
if (min.x > max.x)
{
fTemp = max.x;
max.x = min.x;
min.x = fTemp;
}
if (min.y > max.y)
{
fTemp = max.y;
max.y = min.y;
min.y = fTemp;
}
if (min.z > max.z)
{
fTemp = max.z;
max.z = min.z;
min.z = fTemp;
}
if (vPos.x < min.x)
{
return FALSE;
}
if (vPos.y < min.y)
{
return FALSE;
}
if (vPos.z < min.z)
{
return FALSE;
}
if (vPos.x > max.x)
{
return FALSE;
}
if (vPos.y > max.y)
{
return FALSE;
}
if (vPos.z > max.z)
{
return FALSE;
}
return TRUE;
}
</source>
|also_functions={{LSL DefineRow||[[llGetAgentSize]]|}}
|also_events
|also_tests
|also_articles
|notes
|history=
===== Sitting in 1.36 =====
Avatars historically when they sit upon an object have been treated as part of the object, like a prim, even being assigned a link number (which can be used to detect and manipulate them to some extent). Unrelated to this, requesting the bounding box for a child prim of an object would return the bounding box for the entire object (unless it was an attachment, which point it would return the bounding box for the avatar). The first is something of a misfeature, the latter is an honest to goodness feature; the combination of these two lead to something interesting: Prior to 1.36 requesting the bounding box of an attachment while seated returned the bounding box for the object sat upon. It got reported as a bug {{JIRA|SVC-1174}}, and the behavior was changed in 1.36. The bounding box for the object sat upon is unchanged by 1.36, the avatar still counts. However when the bounding box for the seated avatar is requested it does not fall through to the object being sat upon.
|cat1=Physics
|cat2
|cat3
|cat4
}}

LlKey2Name

2022-09-24T17:52:28Z

Sei Lisa: Does not accept group UUIDs; remove caveat

{{LSL_Function
|inject-2={{Issues/SVC-215}}{{Issues/SVC-4170}}{{Issues/SVC-3935}}{{LSL_Function/uuid|id|sim=*|group=}}
|func_id=210|func_sleep=0.0|func_energy=10.0
|sort=Key2Name|func=llKey2Name
|return_type=string|p1_type=key|p1_name=id
|func_footnote={{LSLP|id}} must specify a valid rezzed prim or avatar key, present in or otherwise known to the sim in which the script is running, otherwise an empty string is returned. In the case of an avatar, this function will still return a valid name if the avatar is a child agent of the sim (i.e., in an adjacent sim, but presently able to see into the one the script is in), or for a short period after the avatar leaves the sim (specifically, when the client completely disconnects from the sim, either as a main or child agent). 
Keys of inventory items will not work; in the case of these, use [[llGetInventoryName]] instead.
|func_desc
|return_text=that is the {{LSLGC|Avatar/Name|legacy name}} of the prim or avatar specified by {{LSLP|id}}.
|spec
|caveats=* It is difficult to tell the difference between a prim that has a name that is an empty string and a prim that is not in the sim, or because an invalid key was specified. Use [[llGetObjectDetails]] to avoid this problem.
* To get around the "avatar must be present" limitation, you can use the [[llRequestAgentData]] function and the [[dataserver]] event to obtain the avatar's name from a key.
* The opposite function ([[llName2Key]]) can be used to find the user key associated with an avatar in the same region. To find the user key of an avatar anywhere on the grid, use [[llRequestUserKey]], which triggers a [[dataserver]] event.
* If an avatar is "ghosted" (which occasionally happens due to a longstanding server bug), an empty string is returned even though the avatar is seemingly present and shows up in [[llSensor]] and the [[Mini-Map]]. This fact can be used as the basis of a [[Ghost Detector]] script.
|constants
|examples=
<source lang="lsl2">
// Best viewed in Chat History (ctrl-h)

default
{
collision_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llKey2Name(id);

string detectedName = llDetectedName(0);

llSay(0, "llKey2Name: " + name
+ "\nllDetectedName: " + detectedName);
}

touch_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llKey2Name(id);

string detectedName = llDetectedName(0);

llSay(0, "llKey2Name: " + name
+ "\nllDetectedName: " + detectedName);
}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGetUsername]]}}
{{LSL DefineRow||[[llGetDisplayName]]}}
{{LSL DefineRow||[[llGetObjectDetails]]}}
{{LSL DefineRow||[[llRequestAgentData]]|Uses the [[dataserver]] to request avatar information}}
|also_events
|also_articles=
{{LSL DefineRow||[[Prim Attribute Overloading]]}}
|also_tests
|notes='''World Wide Web Consortium'''
*[[N2K]] - Independent of databases or bots, this uses the [http://cgi.w3.org/cgi-bin/html2txt W3C html2text] to convert the viewer search to text and extract the key from Second Life's own services.
'''Active Name2Key Databases:'''
*[http://w-hat.com/name2key W-Hat name2key] (last names replaced with the ''Resident'' word for the {{LSLGC|Username|Usernames}})
*[http://kdc.ethernia.net/sys/name2key.php KDC name2key]

'''Dead Name2Key Databases:'''
*[http://kubwa.net/index.php?cmd=name2key Kubwa name2key] (Bot based name2key Database; Supports: {{LSLGC|Legacy Name|Legacy}} and {{LSLGC|Username}} formats; Shows related names; SSL support.) (Appears to be gone as of Apr 2013 [Reports Error 404])
*<s>http://wiki.apez.biz/Development (web-service API functions getAvatarKey and getAvatarName)</s> (Apez seems to be gone ? - May 2011)
*<s>http://www.libsecondlife.org/protocol/index.php/Name2key</s>(Appears to be gone as of Apr 2008, but search for name2key on that site for more information)
*<s>http://www.ulrikasheim.org/tools/name2key.html</s>(Appears to be gone as of Apr 2008)
*<s>[http://www.db4mv.info DB4MV name2key] (Name2Key Database for Avatars ({{LSLGC|Legacy Name|Legacy Names}},{{LSLGC|Username|Usernames}}, and {{LSLGC|Display Name|Display Names}}, GroupNames and Keys, LSL API)</s>(Currently listed as non-existant by host)

'''Name2Key Libraries:'''
*[[Name2Key_in_LSL]]
*[[User:Ugleh_Ulrik/Name2Key|Ugleh Ulrik's Name2Key PHP script]]
*[[Failsafename2key|Failsafe name2key script]]
|cat1=Avatar
|cat2=Prim
|cat3=Key
|cat4=Avatar/Name
|cat5=Legacy Name
|haiku={{Haiku|Numbers in machines,|Faceless, inhuman, sterile.|Bleak identities.}}
|history={{LSL Added|0.4.0|remote=http://secondlife.wikia.com/wiki/Version_0.4.0#Scripting}}
}}

LlListen

2022-09-24T17:47:13Z

Sei Lisa: llListen does not apply to groups either

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|pd=filter for specific|group=}}{{LSL Function/chat|channel|msg|input=*|pd=filter for specific}}{{Issues/SVC-3170}}{{Issues/SVC-92}}{{Issues/BUG-3291}}
|func=llListen
|sort=Listen
|func_id=25|func_sleep=0.0|func_energy=10.0
|return_type=integer
|return_subtype=handle
|return_text=that can be used to [[llListenControl|deactivate]] or [[llListenRemove|remove]] the listen.
|p1_type=integer|p1_name=channel|p1_desc= (-2147483648 through 2147483647)|p1_hover= (-2147483648 through 2147483647)
|p2_type=string|p2_name=name|p2_desc=filter for specific prim name or avatar {{LSLGC|Avatar/Name|legacy name}}
|p2_hover=filter for specific prim name or avatar legacy name
|p3_type=key|p3_name=id
|p4_type=string|p4_name=msg
|func_desc=Sets a [http://foldoc.org/index.cgi?query=handle handle] for {{LSLP|msg}} on {{LSLP|channel}} from {{LSLP|name}} and {{LSLP|id}}.
|func_footnote=If {{LSLP|msg}}, {{LSLP|name}} or {{LSLP|id}} are blank (i.e. <code>""</code>) they are not used to filter incoming messages.
If {{LSLP|id}} is an invalid key or assigned the value [[NULL_KEY]], it is considered blank as well. 
|spec=For the [[listen]] [[event]] to be triggered it must first match the criteria set forth by the filters; only when all the criteria have been met is a listen event generated. First the message must have been transmitted on {{LSLP|channel}}. If {{LSLP|id}} is both a [[key#valid|valid]] key and not a [[key#null key|null]] key, then the speaker's key must be equivalent{{Footnote|In general terms this means the matching for {{LSLP|id}} is not case sensitive. See [[key#equivalency]] for details on key equivalency.|In general terms this means the matching for id is not case sensitive.}} to {{LSLP|id}}. If {{LSLP|name}} is set, then the speaker's {{LSLGC|Avatar/Name|legacy name}} must match {{LSLP|name}} exactly (case sensitive). If {{LSLP|msg}} is set, then the spoken message must match {{LSLP|msg}} exactly (case sensitive).
|also_functions={{LSL DefineRow||[[llListenRemove]]|Removes a listen}}
{{LSL DefineRow||[[llListenControl]]|Enables/Disables a listen}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat limited current sim}}
{{LSL DefineRow||[[llRegionSayTo]]|Sends chat region wide to a specific avatar, or their attachments, or to a rezzed object of known UUID}}
|also_events={{LSL DefineRow||[[listen]]|}}
|also_tests
|also_articles
|haiku=
{{Haiku|Choose not much to say|Someone might overhear it|Blab no big secrets}}
|notes=*Avoid channel zero ([[PUBLIC_CHANNEL]]) and set {{LSLP|name}} or {{LSLP|id}} where possible to avoid lag. <code>llListen(0, "", NULL_KEY,"")</code> can be laggy as it listens to all chat from everyone in chat range and so should be avoided.

*In November 2007, [[User:Kelly_Linden|Kelly Linden]] offered [https://lists.secondlife.com/pipermail/secondlifescripters/2007-November/001993.html this explanation] to help scripters plan listeners more efficiently:
:#Chat that is said gets added to a history.
:#A script that is running and has a [[listen]] [[event]] will ask the history for a chat message during its slice of run time.
:# When the script asks the history for a chat message the checks are done in this order:
:#* {{LSLP|channel}}
:#* self chat (prims can't hear themselves)
:#* distance/[[llRegionSay|RegionSay]]
:#* {{LSLP|id}}
:#* {{LSLP|name}}
:#* {{LSLP|msg}}
:# If a {{LSLP|msg}} is found then a [[listen]] [[event]] is added to the [[event]] queue.
:
:The {{LSLP|id}}/{{LSLP|name}}/{{LSLP|msg}} checks only happen at all if those are specified of course.
:
:So, the most efficient communication method is [[llRegionSay]] on a rarely used {{LSLP|channel}}.
:Nowadays, [[llRegionSayTo]] is to be preferred, where appropriate.
*The integer returned can be assigned to a variable (then called a handle) and used to control the listen via [[llListenRemove]] or [[llListenControl]]. These handles are assigned sequentially starting at <tt>+1</tt> through to <tt>+2,147,483,647</tt>, going beyond which, according to [[User:Simon Linden|Simon Linden]], will roll the returned integer over to <tt>−2,147,483,648</tt>, when positive incrementation resumes. If an [[llListen]] is repeated with the exact same filters as a currently active listener, then the same handle number is returned. If an [[llListen|llListen's]] filters do not match any currently active listener, then the next handle in sequence is allocated (it will not re-allocate a recently removed handle).
*If you are using multiple listens in one script, each listen can be assigned its own handle with which to control it.
|caveats=*On [[state]] change or [[llResetScript|script reset]] all listens are removed automatically.
**A [[state]] change can be used as a shortcut to releasing listens.
*Only 65 listens can simultaneously be open in any single script.
**If this number is exceeded ''Script run-time error'' and ''Too Many Listens'' errors occur.
*For some time, the official SL viewer and several third-party viewers can use negative channels from the chat bar directly just as any other non-zero channel. Formerly, the standard SL viewer could only send chat on negative channels through [[llDialog]] or [[llTextBox]] responses, meaning negative channels were best suited for applications that did not require direct avatar chat.
*Be aware that if you mistakenly use an integer literal bigger than the maximum or smaller than the minimum, LSL will treat it as -1, ''without'' giving any compilation error. This means that all scripts listening to an out-of-range integer will be listening to channel -1 instead, or if the number has a minus sign in front, to channel 1. A safe rule is to never use more than 9 digits. If the channel number comes from a conversion from float (for example from [[llFrand]]), if the float is out of range for an integer, it will be converted to the number -2147483648 regardless of its sign or value.
*Messages sent by script on positive and negative channels are truncated to 1024 bytes. Messages sent by chat on positive channels are truncated to 1023 bytes. Messages sent by chat from negative channels are truncated to 254 bytes.
*Once a [[listen]] is registered its filters cannot be updated, if the listen is registered to [[llGetOwner]], the listen will remain registered to the previous owner upon owner change.
**[[CHANGED_OWNER|Owner change]] can be detected with the [[changed]] event.
**To work around this the old listen will need to be closed and a new one opened for the new owner.
*A prim cannot hear/listen to chat it generates. It can, however, hear a linked prim.
**Chat indirectly generated (as a result of [[llDialog]], [[llTextBox]] or from a [[Link|linked prim]]) can be heard if in range.
*You most certainly can listen to [[DEBUG_CHANNEL]], which will allow you to see all script errors no matter where in the [[region]] you are; also, you can raise your own script errors by using [[llSay]] on [[DEBUG_CHANNEL]]; however, remember that others will just see the script errors<nowiki>[</nowiki>dubious-[[Talk:llListen|discuss]]<nowiki>]</nowiki> as the hovering 'script error' icon — no matter if they're errors thrown by the scripting engine or your own debugging messages.
|examples=
Trivial example to listen to any chat from the object owner and respond once.
{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Single listen handle'''
{{!}}-
{{!!}}<syntaxhighlight lang="lsl2">
// Says beep to owner the first-time owner says something in main chat
// and then stops listening

integer listenHandle;

remove_listen_handle()
{
llListenRemove(listenHandle);
}

default
{
state_entry()
{
// Change the channel number to a positive integer
// to listen for '/5 hello' style of chat.

// target only the owner's chat on channel 0 (PUBLIC_CHANNEL)
listenHandle = llListen(0, "", llGetOwner(), "");
}

listen(integer channel, string name, key id, string message)
{
// we filtered to only listen on channel 0
// to the owner's chat in the llListen call above

llOwnerSay("beep");

// stop listening until script is reset
remove_listen_handle();
}

on_rez(integer start_param)
{
llResetScript();
}

changed(integer change)
{
if (change & CHANGED_OWNER)
{
llResetScript();
}
}
}
</syntaxhighlight>
{{!}}}

{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Two listen handles'''
{{!}}-
{{!!}}<syntaxhighlight lang="lsl2">
// Opens two listen handles upon touch_start and
// stops listening whenever something heard passes either filter

integer listenHandle_a;
integer listenHandle_b;

remove_listen_handles()
{
llListenRemove(listenHandle_a);
llListenRemove(listenHandle_b);
}

default
{
touch_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llDetectedName(0);

listenHandle_a = llListen(5, "", id, "");
listenHandle_b = llListen(6, "", NULL_KEY, "");

llSay(0, "Listening now to '" + name + "' on channel 5.");
llSay(0, "Listening now to anybody/anything on channel 6.");
}

listen(integer channel, string name, key id, string message)
{
if (channel == 5)
llSay(0, name + " said: '/5 " + message + "'");

if (channel == 6)
llSay(0, name + " said: '/6 " + message + "'");

remove_listen_handles();
}
}
</syntaxhighlight>
{{!}}}
|cat1=Communications
|cat2=Chat
|cat3=Legacy Name/As A Parameter
|cat4=Error
}}

LlRegionSayTo

2022-09-24T17:44:30Z

Sei Lisa: Revert the previous change and fix it the right way

{{LSL_Function
|inject-2={{Issues/SCR-66}}
{{LSL_Function/uuid|target|sim=*|group=}}
|func_id=363
|func_sleep=0.0
|func_energy=10.0
|func=llRegionSayTo
|sort=RegionSayTo
|p1_type=key|p1_name=target
|p2_type=integer|p2_name=channel
|p3_type=string|p3_name=msg
|func_desc=Says the text supplied in string {{LSLP|msg}} on channel supplied in integer {{LSLP|channel}} to the object or avatar specified by {{LSLP|target}}
|return_text
|spec
|caveats=
*Text is spoken directly to the object or avatar within the same region as the script.
*Scripts in tasks other than {{LSLP|target}} can not listen for and receive these text messages, with an exception for attachments as described below.
*Text can be a maximum of 1024 bytes. This can convey 1024 ASCII-7 characters, or 512 UTF-8 characters such as á
*A prim cannot hear itself, to prevent problems with recursion.
*Sending text on {{LSLP|DEBUG_CHANNEL}} is not supported
*Text sent to an avatar's ID on channel zero will be sent to the receiver's viewer.
*Text sent to an avatar's ID on non-zero channels can be heard by any attachment on the avatar
*A quick series of messages sent by llRegionSayTo cannot be relied on to arrive at their destination in the same order as sent.
*There is a per-destination throttle of 200 messages sent over 10 seconds on channel zero. Thereafter, there is also a per-sending-object throttle of 100 messages on channel zero over 300 seconds (5 minutes). This throttle is relevant only after the first throttle is activated. Messages sent on channels other than zero do not trigger the throttle but, once it is triggered, the block applies to all channels. The block is region-wide and applies to all objects with the same owner. The block apparently lasts until the region is restarted.
|examples=
<source lang="lsl2">
default
{
touch_start(integer num_detected)
{
key id = llDetectedKey(0);

// send a message to the chat window of the avatar touching
llRegionSayTo(id, 0, "You touched this!");

// send a message to the attachments of the avatar touching
// example channel: -12345
llRegionSayTo(id, -12345, "Hello there attachments!");
}
}
</source>
|helpers
|also_events=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[listen]]|Receives chat}}
|also_functions=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[llListen]]|Ask for listen events}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to a specific avatar, inside our outside the current region.}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the PUBLIC_CHANNEL}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
|also_tests
|also_articles={{LSL DefineRow||[[Hello Avatar]]}}
|notes=
* If one object 'says' something to another object (''e.g''., a button that, when touched, turns on a lamp), it is a good idea to use a very negative channel, ''e.g.'',
<source lang="lsl2">
llRegionSayTo("55499a64-45c3-4b81-8880-8ffb5a7c251b", -5243212, "turn on");
</source>
Negative channels are popular for script communications because, before September 2016, the standard Second Life client was unable to chat directly on those channels ("/-xxxx message" wouldn't chat "message" on channel "-xxxx").
* Messages sent on channel zero via LLRegionSayTo() are blocked after 200 messages on to the same destination in a 10 second period. After this throttle is activated, there is a further throttle, on objects belonging to the owner of the object that triggered the first throttle, of 100 messages per object over 5 minutes (see https://jira.secondlife.com/browse/BUG-5457). The block is region-wide and applies to all objects belonging to the owner, so if a script triggers the throttle, all objects in the same region belonging to the same owner will also be blocked. Messages sent on channels other than zero do not trigger the throttles. The throttles apparently reset only when the region is restarted.

Therefore, llRegionSayTo() is unsuitable for (say) verbose script debugging, and even moderate use can break users' content completely unrelated to the script for an indeterminate (and potentially very long) period of time. Consider using llOwnerSay() for debugging instead or, if this not appropriate, try llRegionSayTo(avatar, non-zero-channel, message) and have an attachment relay the message using llOwnerSay().
|cat1
|cat2
|cat3
|cat4
|history = Date of Release [[ Release_Notes/Second_Life_Server/11#11.04.26.227686 | 26/04/2011 ]]
}}

LlRegionSayTo

2022-09-24T17:27:20Z

Sei Lisa: Using 'target' as name automatically adds a text that says that a group is valid, and that doesn't work for this funciton

{{LSL_Function
|inject-2={{Issues/SCR-66}}
{{LSL_Function/uuid|target|sim=*}}
|func_id=363
|func_sleep=0.0
|func_energy=10.0
|func=llRegionSayTo
|sort=RegionSayTo
|p1_type=key|p1_name=dest|p1_desc=avatar or prim [[UUID]]
|p2_type=integer|p2_name=channel
|p3_type=string|p3_name=msg
|func_desc=Says the text supplied in string {{LSLP|msg}} on channel supplied in integer {{LSLP|channel}} to the object or avatar specified by {{LSLP|dest}}
|return_text
|spec
|caveats=
*Text is spoken directly to the object or avatar within the same region as the script.
*Scripts in tasks other than {{LSLP|target}} can not listen for and receive these text messages, with an exception for attachments as described below.
*Text can be a maximum of 1024 bytes. This can convey 1024 ASCII-7 characters, or 512 UTF-8 characters such as á
*A prim cannot hear itself, to prevent problems with recursion.
*Sending text on {{LSLP|DEBUG_CHANNEL}} is not supported
*Text sent to an avatar's ID on channel zero will be sent to the receiver's viewer.
*Text sent to an avatar's ID on non-zero channels can be heard by any attachment on the avatar
*A quick series of messages sent by llRegionSayTo cannot be relied on to arrive at their destination in the same order as sent.
*There is a per-destination throttle of 200 messages sent over 10 seconds on channel zero. Thereafter, there is also a per-sending-object throttle of 100 messages on channel zero over 300 seconds (5 minutes). This throttle is relevant only after the first throttle is activated. Messages sent on channels other than zero do not trigger the throttle but, once it is triggered, the block applies to all channels. The block is region-wide and applies to all objects with the same owner. The block apparently lasts until the region is restarted.
|examples=
<source lang="lsl2">
default
{
touch_start(integer num_detected)
{
key id = llDetectedKey(0);

// send a message to the chat window of the avatar touching
llRegionSayTo(id, 0, "You touched this!");

// send a message to the attachments of the avatar touching
// example channel: -12345
llRegionSayTo(id, -12345, "Hello there attachments!");
}
}
</source>
|helpers
|also_events=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[listen]]|Receives chat}}
|also_functions=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[llListen]]|Ask for listen events}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to a specific avatar, inside our outside the current region.}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the PUBLIC_CHANNEL}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
|also_tests
|also_articles={{LSL DefineRow||[[Hello Avatar]]}}
|notes=
* If one object 'says' something to another object (''e.g''., a button that, when touched, turns on a lamp), it is a good idea to use a very negative channel, ''e.g.'',
<source lang="lsl2">
llRegionSayTo("55499a64-45c3-4b81-8880-8ffb5a7c251b", -5243212, "turn on");
</source>
Negative channels are popular for script communications because, before September 2016, the standard Second Life client was unable to chat directly on those channels ("/-xxxx message" wouldn't chat "message" on channel "-xxxx").
* Messages sent on channel zero via LLRegionSayTo() are blocked after 200 messages on to the same destination in a 10 second period. After this throttle is activated, there is a further throttle, on objects belonging to the owner of the object that triggered the first throttle, of 100 messages per object over 5 minutes (see https://jira.secondlife.com/browse/BUG-5457). The block is region-wide and applies to all objects belonging to the owner, so if a script triggers the throttle, all objects in the same region belonging to the same owner will also be blocked. Messages sent on channels other than zero do not trigger the throttles. The throttles apparently reset only when the region is restarted.

Therefore, llRegionSayTo() is unsuitable for (say) verbose script debugging, and even moderate use can break users' content completely unrelated to the script for an indeterminate (and potentially very long) period of time. Consider using llOwnerSay() for debugging instead or, if this not appropriate, try llRegionSayTo(avatar, non-zero-channel, message) and have an attachment relay the message using llOwnerSay().
|cat1
|cat2
|cat3
|cat4
|history = Date of Release [[ Release_Notes/Second_Life_Server/11#11.04.26.227686 | 26/04/2011 ]]
}}

LlGetStatus

2022-09-24T17:00:57Z

Sei Lisa: Add STATUS_DIE_AT_NO_ENTRY and STATUS_DIE_AT_EDGE to priority order, now that they work

{{LSL_Function
|inject-2={{Issues/SVC-5531}}{{Issues/SVC-1773}}{{Issues/SVC-4197}}
|func_id=46|func_sleep=0.0|func_energy=10.0
|func=llGetStatus
|return_type=integer|return_subtype=boolean
|p1_type=integer|p1_subtype=bit mask|p1_name=status|p1_desc=A single STATUS_* flag
|func_footnote
|func_desc
|return_text=equal to the {{LSLP|status}} of the object.
|spec
|caveats=*Status is an object attribute; all prims in an object share the same status.
**[[STATUS_BLOCK_GRAB]] only really deals with the root prim. Try [[STATUS_BLOCK_GRAB_OBJECT]] instead.
*Querying for [[STATUS_CAST_SHADOWS]] always returns [[FALSE]] regardless of the setting.
*Only one flag should be specified at a time. As of Second Life Server 2022-09-09.574921, if more than one flag is specified, STATUS_DIE_AT_NO_ENTRY takes priority, followed by STATUS_BLOCK_GRAB_OBJECT, STATUS_DIE_AT_EDGE, STATUS_RETURN_AT_EDGE, STATUS_BLOCK_GRAB, STATUS_SANDBOX, STATUS_ROTATE_Z, STATUS_ROTATE_Y, STATUS_ROTATE_X, STATUS_PHANTOM, and STATUS_PHYSICS.
|constants={{LSL Constants/Status}}
|examples=<syntaxhighlight lang="lsl2">default
{
touch_start(integer total_number)
{
if (llGetStatus(STATUS_PHYSICS))
{
llSay(0, "This object is physical");
}
else
{
llSay(0, "This object is not physical");
}
}
}</syntaxhighlight>
|helpers
|also_functions=
{{LSL DefineRow||[[llSetStatus]]|Sets the object status.}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Status
|cat2=Physics
|cat3
|cat4
}}

LlGetStatus

2022-09-14T22:55:06Z

Sei Lisa: STATUS_DIE_AT_* was fixed; it seems I had to write this for it to be noticed.

{{LSL_Function
|inject-2={{Issues/SVC-5531}}{{Issues/SVC-1773}}{{Issues/SVC-4197}}
|func_id=46|func_sleep=0.0|func_energy=10.0
|func=llGetStatus
|return_type=integer|return_subtype=boolean
|p1_type=integer|p1_subtype=bit mask|p1_name=status|p1_desc=A single STATUS_* flag
|func_footnote
|func_desc
|return_text=equal to the {{LSLP|status}} of the object.
|spec
|caveats=*Status is an object attribute; all prims in an object share the same status.
**[[STATUS_BLOCK_GRAB]] only really deals with the root prim. Try [[STATUS_BLOCK_GRAB_OBJECT]] instead.
*Querying for [[STATUS_CAST_SHADOWS]] always returns [[FALSE]] regardless of the setting.
*Only one flag should be specified at a time. As of Second Life Server 2022-08-12.574216, if more than one flag is specified, STATUS_BLOCK_GRAB_OBJECT takes priority, followed by STATUS_RETURN_AT_EDGE, STATUS_BLOCK_GRAB, STATUS_SANDBOX, STATUS_ROTATE_Z, STATUS_ROTATE_Y, STATUS_ROTATE_X, STATUS_PHANTOM, and STATUS_PHYSICS.
|constants={{LSL Constants/Status}}
|examples=<syntaxhighlight lang="lsl2">default
{
touch_start(integer total_number)
{
if (llGetStatus(STATUS_PHYSICS))
{
llSay(0, "This object is physical");
}
else
{
llSay(0, "This object is not physical");
}
}
}</syntaxhighlight>
|helpers
|also_functions=
{{LSL DefineRow||[[llSetStatus]]|Sets the object status.}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Status
|cat2=Physics
|cat3
|cat4
}}

LlGetStatus

2022-08-26T10:33:28Z

Sei Lisa: Add caveats

{{LSL_Function
|inject-2={{Issues/SVC-5531}}{{Issues/SVC-1773}}{{Issues/SVC-4197}}
|func_id=46|func_sleep=0.0|func_energy=10.0
|func=llGetStatus
|return_type=integer|return_subtype=boolean
|p1_type=integer|p1_subtype=bit mask|p1_name=status|p1_desc=A single STATUS_* flag
|func_footnote
|func_desc
|return_text=equal to the {{LSLP|status}} of the object.
|spec
|caveats=*Status is an object attribute; all prims in an object share the same status.
**[[STATUS_BLOCK_GRAB]] only really deals with the root prim. Try [[STATUS_BLOCK_GRAB_OBJECT]] instead.
*Querying for [[STATUS_DIE_AT_EDGE]], [[STATUS_DIE_AT_NO_ENTRY]] or [[STATUS_CAST_SHADOWS]] always returns FALSE regardless of the setting.
*Only one flag should be specified at a time. As of Second Life Server 2022-08-12.574216, if more than one flag is specified, STATUS_BLOCK_GRAB_OBJECT takes priority, followed by STATUS_RETURN_AT_EDGE, STATUS_BLOCK_GRAB, STATUS_SANDBOX, STATUS_ROTATE_Z, STATUS_ROTATE_Y, STATUS_ROTATE_X, STATUS_PHANTOM, and STATUS_PHYSICS.
|constants={{LSL Constants/Status}}
|examples=<source lang="lsl2">default
{
touch_start(integer total_number)
{
if (llGetStatus(STATUS_PHYSICS))
{
llSay(0, "This object is physical");
}
else
{
llSay(0, "This object is not physical");
}
}
}</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llSetStatus]]|Sets the object status.}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Status
|cat2=Physics
|cat3
|cat4
}}

LlGetHTTPHeader

2022-07-22T00:31:53Z

Sei Lisa: Works fine outside http_request as long as the key is valid

{{LSL_Function
|func_id=349|func_sleep=0.0|func_energy=10.0|mode
|func=llGetHTTPHeader|return_type=string
|p1_type=key|p1_subtype=handle|p1_name=request_id|p1_desc=A valid HTTP request key.
|p2_type=string|p2_name=header|p2_desc=Lower case header value name.
|func_footnote=Returns an empty string if the header is not found, if the '''request_id''' is not a valid key received through the [[http_request]] event, or if the headers can no longer be accessed. Headers can only be accessed before [[llHTTPResponse]] is called and with-in the first 30 seconds after the [[http_request]] event is queued.
|func_desc
|return_text=that is the value for '''header''' for '''request_id'''.
|spec=
===Generated Headers===
These headers are automatically generated by the simulator, they were not actually sent by the requesting client. They supply information about the request to make parsing easier.

Sample URL: [https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/foo/bar?arg=gra {{HoverTextStyle|style=color:green;|<nowiki>https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322</nowiki>|2={{String|x-script-url}} = {{String|https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322}}}}{{HoverTextStyle|style=color:blue;|/foo/bar|2={{String|x-path-info}} = {{String|/foo/bar}}}}?{{HoverTextStyle|style=color:red;|1=arg=gra|2={{String|x-query-string}} = {{String|1=arg=gra}}}}]

{{{!}} class="lltable" border="1"
! header
! description
! example
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-script-url"
{{!}} The base url, as originally received from [[llRequestURL]]/[[llRequestSecureURL]]
{{!}} <nowiki>https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322</nowiki>
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-path-info"
{{!}} Any trailing path information from the requested url
{{!}} /foo/bar
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-query-string"
{{!}} Any query arguments, the text past the first "?" in the url
{{!}} arg=gra
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-remote-ip"
{{!}} IP address of the host that made the request
{{!}}
{{!}}}

===Common Headers===

{{{!}} class="lltable" border="1"
! header
! description
! example
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "user-agent"
{{!}} The user-agent header as reported by the requester
{{!}}
{{!}}}

===[[llHTTPRequest]] Headers===
{{LSL_Constants/HTTP_Headers|lower-case=*}}
|caveats=
* Header information becomes inaccessible after 30 seconds or if [[llHTTPResponse]] is called.
* Function returns an empty string in any context outside the [[http_request]] event. For instance, it cannot be used in the [[http_response]] event.
* Custom headers are not supported, only the headers listed in the specification are supported.
* LSL is not a CGI environment
** "Content-Type" is an example of a normal header name, in a CGI environment the name would be "HTTP_CONTENT_TYPE".
* '''header''' must be lower case (or it will match nothing). All header names are converted to lower case when they are received.
* When making a request...
** The path part of the URL must be prefixed with a forward slash
*** Good: https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/foo
*** Bad: https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322foo
** In order to use the query string, you must include a path (even if it is just a slash)
*** Good: https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/?arg=gra
*** Bad: https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322?arg=gra
|constants
|examples=
<source lang="lsl2">
key url_request;

default
{
state_entry()
{
url_request = llRequestURL();
}

http_request(key id, string method, string body)
{
if (url_request == id)
{
// if you're usually not resetting the query ID
// now is a good time to start!
url_request = "";

if (method == URL_REQUEST_GRANTED)
{
llOwnerSay("URL: " + body);

key owner = llGetOwner();
vector ownerSize = llGetAgentSize(owner);

if (ownerSize)// != ZERO_VECTOR
llLoadURL(owner, "I got a new URL!", body);
}

else if (method == URL_REQUEST_DENIED)
llOwnerSay("Something went wrong, no url:\n" + body);
}

else
{
list headerList = ["x-script-url",
"x-path-info", "x-query-string",
"x-remote-ip", "user-agent"];

integer index = -llGetListLength(headerList);
do
{
string header = llList2String(headerList, index);
llOwnerSay(header + ": " + llGetHTTPHeader(id, header));
}
while (++index);

llOwnerSay("body:\n" + body);
llHTTPResponse(id, 200, body);
}
}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGetFreeURLs]]}}
{{LSL DefineRow||[[llRequestURL]]}}
{{LSL DefineRow||[[llRequestSecureURL]]}}
{{LSL DefineRow||[[llReleaseURL]]}}
{{LSL DefineRow||[[llHTTPResponse]]}}
|also_tests
|also_events=
{{LSL DefineRow||[[http_request]]}}
|also_articles=
{{LSL DefineRow||[[LSL http server]]}}
{{LSL DefineRow||{{Wikipedia|List_of_HTTP_headers|Wikipedia:List of HTTP headers}}}}
|notes
|deepnotes=
|history=
*{{SVN|1836|rev=112899 |trunk=*|anchor=file22|ver=|ser=}}
|cat1=HTTP
|cat2=HTTP/Server
|cat3
|cat4
}}

LlListen

2022-07-07T13:35:28Z

Sei Lisa: Fix inaccuracies

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|pd=filter for specific}}{{LSL Function/chat|channel|msg|input=*|pd=filter for specific}}{{Issues/SVC-3170}}{{Issues/SVC-92}}{{Issues/BUG-3291}}
|func=llListen
|sort=Listen
|func_id=25|func_sleep=0.0|func_energy=10.0
|return_type=integer
|return_subtype=handle
|return_text=that can be used to [[llListenControl|deactivate]] or [[llListenRemove|remove]] the listen.
|p1_type=integer|p1_name=channel|p1_desc= (-2147483648 through 2147483647)|p1_hover= (-2147483648 through 2147483647)
|p2_type=string|p2_name=name|p2_desc=filter for specific prim name or avatar {{LSLGC|Avatar/Name|legacy name}}
|p2_hover=filter for specific prim name or avatar legacy name
|p3_type=key|p3_name=id
|p4_type=string|p4_name=msg
|func_desc=Sets a [http://foldoc.org/index.cgi?query=handle handle] for {{LSLP|msg}} on {{LSLP|channel}} from {{LSLP|name}} and {{LSLP|id}}.
|func_footnote=If {{LSLP|msg}}, {{LSLP|name}} or {{LSLP|id}} are blank (i.e. <code>""</code>) they are not used to filter incoming messages.
If {{LSLP|id}} is an invalid key or assigned the value [[NULL_KEY]], it is considered blank as well. 
|spec=For the [[listen]] [[event]] to be triggered it must first match the criteria set forth by the filters; only when all the criteria have been met is a listen event generated. First the message must have been transmitted on {{LSLP|channel}}. If {{LSLP|id}} is both a [[key#valid|valid]] key and not a [[key#null key|null]] key, then the speaker's key must be equivalent{{Footnote|In general terms this means the matching for {{LSLP|id}} is not case sensitive. See [[key#equivalency]] for details on key equivalency.|In general terms this means the matching for id is not case sensitive.}} to {{LSLP|id}}. If {{LSLP|name}} is set, then the speaker's {{LSLGC|Avatar/Name|legacy name}} must match {{LSLP|name}} exactly (case sensitive). If {{LSLP|msg}} is set, then the spoken message must match {{LSLP|msg}} exactly (case sensitive).
|also_functions={{LSL DefineRow||[[llListenRemove]]|Removes a listen}}
{{LSL DefineRow||[[llListenControl]]|Enables/Disables a listen}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat limited current sim}}
{{LSL DefineRow||[[llRegionSayTo]]|Sends chat region wide to a specific avatar, or their attachments, or to a rezzed object of known UUID}}
|also_events={{LSL DefineRow||[[listen]]|}}
|also_tests
|also_articles
|haiku=
{{Haiku|Choose not much to say|Someone might overhear it|Blab no big secrets}}
|notes=*Avoid channel zero ([[PUBLIC_CHANNEL]]) and set {{LSLP|name}} or {{LSLP|id}} where possible to avoid lag. <code>llListen(0, "", NULL_KEY,"")</code> can be laggy as it listens to all chat from everyone in chat range and so should be avoided.

*In November 2007, [[User:Kelly_Linden|Kelly Linden]] offered [https://lists.secondlife.com/pipermail/secondlifescripters/2007-November/001993.html this explanation] to help scripters plan listeners more efficiently:
:#Chat that is said gets added to a history.
:#A script that is running and has a [[listen]] [[event]] will ask the history for a chat message during its slice of run time.
:# When the script asks the history for a chat message the checks are done in this order:
:#* {{LSLP|channel}}
:#* self chat (prims can't hear themselves)
:#* distance/[[llRegionSay|RegionSay]]
:#* {{LSLP|id}}
:#* {{LSLP|name}}
:#* {{LSLP|msg}}
:# If a {{LSLP|msg}} is found then a [[listen]] [[event]] is added to the [[event]] queue.
:
:The {{LSLP|id}}/{{LSLP|name}}/{{LSLP|msg}} checks only happen at all if those are specified of course.
:
:So, the most efficient communication method is [[llRegionSay]] on a rarely used {{LSLP|channel}}.
:Nowadays, [[llRegionSayTo]] is to be preferred, where appropriate.
*The integer returned can be assigned to a variable (then called a handle) and used to control the listen via [[llListenRemove]] or [[llListenControl]]. These handles are assigned sequentially starting at <tt>+1</tt> through to <tt>+2,147,483,647</tt>, going beyond which, according to [[User:Simon Linden|Simon Linden]], will roll the returned integer over to <tt>−2,147,483,648</tt>, when positive incrementation resumes. If an [[llListen]] is repeated with the exact same filters as a currently active listener, then the same handle number is returned. If an [[llListen|llListen's]] filters do not match any currently active listener, then the next handle in sequence is allocated (it will not re-allocate a recently removed handle).
*If you are using multiple listens in one script, each listen can be assigned its own handle with which to control it.
|caveats=*On [[state]] change or [[llResetScript|script reset]] all listens are removed automatically.
**A [[state]] change can be used as a shortcut to releasing listens.
*Only 65 listens can simultaneously be open in any single script.
**If this number is exceeded ''Script run-time error'' and ''Too Many Listens'' errors occur.
*For some time, the official SL viewer and several third-party viewers can use negative channels from the chat bar directly just as any other non-zero channel. Formerly, the standard SL viewer could only send chat on negative channels through [[llDialog]] or [[llTextBox]] responses, meaning negative channels were best suited for applications that did not require direct avatar chat.
*Be aware that if you mistakenly use an integer literal bigger than the maximum or smaller than the minimum, LSL will treat it as -1, ''without'' giving any compilation error. This means that all scripts listening to an out-of-range integer will be listening to channel -1 instead, or if the number has a minus sign in front, to channel 1. A safe rule is to never use more than 9 digits. If the channel number comes from a conversion from float (for example from [[llFrand]]), if the float is out of range for an integer, it will be converted to the number -2147483648 regardless of its sign or value.
*Messages sent by script on positive and negative channels are truncated to 1024 bytes. Messages sent by chat on positive channels are truncated to 1023 bytes. Messages sent by chat from negative channels are truncated to 254 bytes.
*Once a [[listen]] is registered its filters cannot be updated, if the listen is registered to [[llGetOwner]], the listen will remain registered to the previous owner upon owner change.
**[[CHANGED_OWNER|Owner change]] can be detected with the [[changed]] event.
**To work around this the old listen will need to be closed and a new one opened for the new owner.
*A prim cannot hear/listen to chat it generates. It can, however, hear a linked prim.
**Chat indirectly generated (as a result of [[llDialog]], [[llTextBox]] or from a [[Link|linked prim]]) can be heard if in range.
*You most certainly can listen to [[DEBUG_CHANNEL]], which will allow you to see all script errors no matter where in the [[region]] you are; also, you can raise your own script errors by using [[llSay]] on [[DEBUG_CHANNEL]]; however, remember that others will just see the script errors<nowiki>[</nowiki>dubious-[[Talk:llListen|discuss]]<nowiki>]</nowiki> as the hovering 'script error' icon — no matter if they're errors thrown by the scripting engine or your own debugging messages.
|examples=
Trivial example to listen to any chat from the object owner and respond once.
{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Single listen handle'''
{{!}}-
{{!!}}<syntaxhighlight lang="lsl2">
// Says beep to owner the first-time owner says something in main chat
// and then stops listening

integer listenHandle;

remove_listen_handle()
{
llListenRemove(listenHandle);
}

default
{
state_entry()
{
// Change the channel number to a positive integer
// to listen for '/5 hello' style of chat.

// target only the owner's chat on channel 0 (PUBLIC_CHANNEL)
listenHandle = llListen(0, "", llGetOwner(), "");
}

listen(integer channel, string name, key id, string message)
{
// we filtered to only listen on channel 0
// to the owner's chat in the llListen call above

llOwnerSay("beep");

// stop listening until script is reset
remove_listen_handle();
}

on_rez(integer start_param)
{
llResetScript();
}

changed(integer change)
{
if (change & CHANGED_OWNER)
{
llResetScript();
}
}
}
</syntaxhighlight>
{{!}}}

{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Two listen handles'''
{{!}}-
{{!!}}<syntaxhighlight lang="lsl2">
// Opens two listen handles upon touch_start and
// stops listening whenever something heard passes either filter

integer listenHandle_a;
integer listenHandle_b;

remove_listen_handles()
{
llListenRemove(listenHandle_a);
llListenRemove(listenHandle_b);
}

default
{
touch_start(integer num_detected)
{
key id = llDetectedKey(0);
string name = llDetectedName(0);

listenHandle_a = llListen(5, "", id, "");
listenHandle_b = llListen(6, "", NULL_KEY, "");

llSay(0, "Listening now to '" + name + "' on channel 5.");
llSay(0, "Listening now to anybody/anything on channel 6.");
}

listen(integer channel, string name, key id, string message)
{
if (channel == 5)
llSay(0, name + " said: '/5 " + message + "'");

if (channel == 6)
llSay(0, name + " said: '/6 " + message + "'");

remove_listen_handles();
}
}
</syntaxhighlight>
{{!}}}
|cat1=Communications
|cat2=Chat
|cat3=Legacy Name/As A Parameter
|cat4=Error
}}

Talk:LlListen

2022-07-07T13:15:16Z

Sei Lisa: /* Debug messages viewable by others? */ new section

== general usage ==

{{QA
|Q=Does this function have to be called in every state?
|A=Yes, it's a feature.
}}
{{QA
|Q=How can i send commands in chat that cannot be seen by others?
|A=
{{QA
|Q=By other avatars?
|A=Use any channel other then 0 ([[PUBLIC_CHANNEL]]).
}}
{{QA
|Q=By other scripts?
|A=Can't keep other scripts from hearing what scripts or avatars say. But you can write complicated channel hopping communications that span the entire range of 4 billion channels, reducing the probability of anyone capturing a complete message.
}}
{{QA
|Q=What [happens] when i do configuration via public channel? There are some scripts that use commands like '/99stop' which cannot be seen in public channel by others
|A=They can be seen by other scripts, the number at the beginning indicates the channel. '/99stop' sends 'stop' on channel 99. That can also be written as '/99 stop' and have the same effect. Any script just has to listen on channel 99 to receive the command.
}}
}}

Please explain or show examples that explain what the arguments to llListen do. specific questions:

{{QA
|Q=What does it mean to filter on name? is that the name of the speaker? does it have to be a full exact match, or can it match a substring of the character's name? (for example, can i filter by "Baroque" or "Ken" rather than "Kendown Baroque"?)
|A=If you filter by name, the name must match exactly to the speaker. If it does not match in any way then no listen event is raised. There is no support for partial filtering on any of the filters.
}}

{{QA
|Q=similarly, I believe filtering by key means that the ID provided must be that of the speaker; is that correct?
|A=Correct.
}}

{{QA
|Q=is the message filter case-sensitive? for that matter, is the name filter?
|A=The message and name filters are case sensitive; the id filter is not.
}}

{{QA
|Q=What happens if you create a llListen with the exact same filters as a previously set up (and still active) listener? Does it ignore the second one? Create two with the same filter? Or error out? For instance, I have a case where I set up a listener to listen to a reply to several different dialog commands. Each command needs to make sure that the listener is open, but ideally, I could just set up the filter without checking to see if it already exists.
|A=Nothing bad will happen if you open two listens with the same filters or if the filters overlap; only one listen event will be raised. That said, there is a limit to the number of listens you can have open at any one time by a single script (65 per script) which means that opening multiple listens and not doing any form of tracking is very bad.}}

== Performance and Sim impact of llListen ==

I have heard some comments from sim owners that adding too many listens to a sim would either degrade performance, or there is a hard cap limit to the number that can be active. Is there any validity to this? There is also some discussion regarding filtered vs. unfiltered listens. Unfiltered is obviously an easy way to get aroung the 65 listener limit per script (and subsequently the number active on a sim), but may come with an overhead penalty. This seems somewhat counterintuitive as the filtering process should comsume more clock cycles than simply passing everything on a channel (or all channels?) to the script. -- {{User|Melany Lunasea}}

:Listens do impact sim performance. It's better to have a single listen processing commands coming in on a single channel then it is to have multiple listens open all on the same channel. -- [[User:Strife Onizuka|Strife Onizuka]] 23:13, 8 March 2008 (PST)

Kelly Linden on 11/13/07 to Scripters mailing list:

You are pretty close. The actual order of events is:
1. Chat that is said gets added to a history.
2. A script that is running and has a listen event will ask the history
for a chat message during its slice of run time.
3. When the script asks the history for a chat message the checks are
done in this order:
- channel
- self chat (objects can't hear themselves)
- distance/RegionSay
- key
- name
- message
4. If a message is found then a listen event is added to the event queue.

The key/name/message checks only happen at all if those are specified of
course.

So, the most efficient way is llRegionSay on a rarely used channel.
( above comment by [[User:Winter Seale]] 19:32, 8 February 2009 )
: Hee, i think i was adding this to the article while you were adding it to the talk page. Now we all know! --[[User:Cerise Sorbet|Cerise Sorbet]] 20:04, 8 February 2009 (UTC)

== Trivia ==
The listen id can loop similar to a standard integer, such that it may become negative and then theoretically
overlap. Although it would take months of straight opening/closing. Yes, I did just test this. -.-
[[User:Gregory Maurer|--Gregory Maurer]] 01:42, 16 January 2011 (UTC)

== Queen's English ==

Sorry Omei but I highly disagree with your judgement on the matter of the readability and grammar of this page. I would like a couple third-parties to judge the differences first before we keep this reverted. [[User:DonFabuuk Resident|DonFabuuk Resident]] 20:19, 8 December 2013 (PST)

:I mostly ignore grammar changes unless some nuance is lost or it becomes factually inaccurate. Furthermore short of [http://en.wikipedia.org/wiki/Engrish Engrish], I will ignore minor grammar uglinesses unless I can add technical value to the content. I recommend this approach to all editors as it reduces conflict. Preaching done, onto the disputed territory.
:#"channel '''channel'''" - Repetition is repetitive, there isn't much gained by having it and it's a bit tacky. I'm more on the side of chucking it then keeping it.
:#"If {{LSLP|id}} is a valid and not a [[NULL_KEY|null key]] then..." is not grammatical ("is a valid and"?) I think what you meant was "If {{LSLP|id}} is a valid key and not a [[NULL_KEY|null key]] then...". Part of the reason for making it "[[NULL_KEY|null]] key" vs. "[[NULL_KEY|null key]]" vs. "[[NULL_KEY]]" is that a key can be effectively null without being NULL_KEY.
:#"the speaker's key must match exactly." vs "the speaker's key must be equivalent." The thing is, keys aren't case sensitive in this context. "equivalent" is the better word, however this does bring up the point that we don't expose this idiosyncrasy of keys anywhere in the documentation. This will have to go on the ToDo list.
::I'll accept 'equivalent' then [[User:Omei Qunhua|Omei Qunhua]] 01:30, 9 December 2013 (PST)
:#"If {{LSLP|name}} is set then the speaker's name; then {{LSLP|name}} must match exactly." I don't see what grammar rule makes that work, it's an odd place to put a pause and using two "then"s in a sentence is kinda passe.
:I can understand why Omei would not like the changes, they are awkward. In an ideal situation, reverting would only be used when an edit was entirely wrong but this is reality. Normally when a situation like this would happen we (the community, yourself included) would review the final product make any corrections, and fix any awkward parts. If it were a little more obvious what you were trying to achieve with your edit, what nuance you were trying to elucidate, we would fix your edit, but your edit is sufficiently deficient the only way we can make the content make sense again is to revert your changes. I am not in love with the current content, I have no attachment to it, if you could explain what is wrong with it, I will help you change it.
:-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:05, 8 December 2013 (PST)

:Being the busy body that I am, I couldn't leave well enough alone and had to edit the article (I have a cold, I was tired, not a good combination). I hope the changes are acceptable. I am aware the links to key don't lead anywhere (I'll work on them later). Any thoughts? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:00, 9 December 2013 (PST)

== Debug messages viewable by others? ==

In this edit [https://wiki.secondlife.com/w/index.php?title=LlListen&curid=3298&diff=1210856&oldid=1209721] it is stated that "you can raise your own script errors by using [[llSay]] on [[DEBUG_CHANNEL]]; however, remember that others will just see the script errors as the hovering 'script error' icon". That's not true for my viewer, which filters out debug messages coming from scripts in objects that I don't own. Is there any modern viewer for which that sentence is correct? If not, it should be removed. --[[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 06:15, 7 July 2022 (PDT)

LSL Style Guide

2022-06-12T11:52:56Z

Sei Lisa: /* Script Structure */ Variables do not need to come before UDFs; mention event handlers as a mandatory part of states

{{LSL Header|ml=*}}{{RightToc}}

Every major open-source project has its own style guide: a '''set of conventions''' (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a '''consistent style'''. These guidelines, referred to collectively as a Style Guide, are not as rigid as the rules required by the language compiler but nonetheless are critical to creating maintainable code. The most critical aspect of a style is that you apply it consistently to the code you write.

Effective programming in [[LSL Portal|LSL]] requires that developers use a disciplined approach towards formatting and other conventions in their scripts.

{{LSL Tip| Applying a style guide to your code does not only help others read your code. '''It helps you as well''', because in future when you return to the code you wrote before, you'll appreciate reading formatted and annotated code.}}

== Use third party editors: ==

There are many [[LSL Alternate Editors|third party editors]] with [[LSL Portal|LSL]] syntax files available. See an example below of what your workflow would look like using an editor that has syntax highlighting and autocomplete and also applies an indent style to your code.

Using [[LSL Alternate Editors|third party editors]] has a few advantages over using the editor in the viewers:
* Autocompletion helps you avoid typos.
* Autocompletion sometimes not only does a linear autocompletion as in autocompleting <code>llS</code> to <code>llSay</code> but sometimes works even with fuzzy search by autocompleting <code>llslppf</code> to <code>llSetLinkPrimitiveParamsFast</code>.
* The syntax highlighting file colors the code exactly like the code you see in the official Linden Lab viewer making you not having to learn or adapt to a different coloring scheme.
* Autocompletion might also preformat code with indent styles when autocompleting states, events, conditional clauses etc.

== [http://en.wikipedia.org/wiki/Indent_style Indent styles]: ==

Most people, when they start programming on their own, will have programs that are UGLY to look at - to put it nicely, sometimes mistakenly thinking that such scripts occupy less space when compiled. Such scripts typically look like the following:

{| width="100%" {{Prettytable}}
|- {{Hl2}}
! '''unstyled source code'''
|-
||
<syntaxhighlight lang="lsl2">default {state_entry(){llSay(0,"Hello World.");}}</syntaxhighlight>
|}

However, that code is difficult to read (or at least to '''follow''') - even more so when one is writing a couple hundred lines program. There are several [http://en.wikipedia.org/wiki/Indent_style indent styles] with the two most common styles being:

{| width="100%" {{Prettytable}}
|- {{Hl2}}
! '''[http://en.wikipedia.org/wiki/Indent_style#K.26R_style K&R style] (used in Javascript based languages)'''
! '''[http://en.wikipedia.org/wiki/Indent_style#Allman_style Allman style] (used in C based languages)'''
|-
||<syntaxhighlight lang="lsl2">
default {
state_entry() {
llSay(0, "Hello World.");
}
}
</syntaxhighlight>
||
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSay(0, "Hello World.");
}
}
</syntaxhighlight>
|}

The '''K&R style''' conserves space - IN THE SOURCE CODE ONLY, however the '''Allman style''' is easier to read and easier to visually bracket-match. Once a scripter is in the practice of using a particular style, reading code in that style will become easier.

Consistent indenting makes reading both styles easier that's why it '''really comes down to whatever works for you'''. In both methods, indenting is the key indicating factor of levels of scope.

== Naming conventions: ==

There are many naming conventions in Second Life. Only the most used ones will be listed below.

Global Variables (variables used throughout the entire program) should be lowercase. For example:

<syntaxhighlight lang="lsl2">
integer index = 0;
string name = "Please set one";
</syntaxhighlight>

Others prefer to distinguish between global and local variables by prefixing variable names with a character, defining globals in the following manner:

<syntaxhighlight lang="lsl2">
integer gIndex;
string gName = "Please set one";
</syntaxhighlight>

Constant variables should be in ALL CAPS following the style guide used by Linden Labs. For example:

<syntaxhighlight lang="lsl2">
integer DIALOG_CHANNEL = -517265;
vector RED = <1.0, 0.0, 0.0>;
</syntaxhighlight>

Arguments used within a [[Category:LSL User-Defined Functions|user defined function]] or one of the standard [[Event|events]] should be named with '''easily readable and meaningful''' names. When using [[Event|events]], please use the standard names as listed here on the official wiki. An [[Event|overview of all events can be found here]]. Below is an example as can be found for the [[Listen|listen event]]:

<syntaxhighlight lang="lsl2">
// ...

listen(integer channel, string name, key id, string message)
{
key OwnerKey = llGetOwner();

if (channel == 1 && id == OwnerKey)
llOwnerSay("Hello Avatar");
}

// ...
</syntaxhighlight>

== Separating code: ==
Some people put too many function calls on one line. As shown in this example, too many function calls on a single line makes the code hard to read and almost impossible to debug.

<syntaxhighlight lang="lsl2">
list lst;
integer NUM_DIGITS = 10;

default {
touch_start(integer n) {
string name = llToLower(llGetSubString(llList2String(llParseString2List(llDetectedName(0), [" "], []), 0), 0, NUM_DIGITS - 1));
if (!~llListFindList(lst, (list)name))
lst += name;
// send a message to the owner, only reaches owner if online and within the same sim
llOwnerSay(llList2CSV(lst));
}
}
</syntaxhighlight>

Now here is the code, with the exact same features, in a simpler way. While hardly anyone could tell you what the above code did, almost everyone can figure out what the below code does.

<syntaxhighlight lang="lsl2">
list listOfStrings;
integer NUM_DIGITS = 10;

default
{
touch_start(integer n)
{
string name = llDetectedName(0);
list nameAsList = llParseString2List(name, [" "], []);
string firstName = llList2String(nameAsList, 0);
string startPart = llToLower(llGetSubString(firstName, 0, NUM_DIGITS - 1));
integer index = llListFindList(listOfStrings, [startPart]);

if (index == -1)
listOfStrings += startPart;

// send a message to the owner, only reaches owner if online and within the same sim
llOwnerSay(llList2CSV(listOfStrings));
}
}
</syntaxhighlight>

LSL lacks an optimizing compiler. For this reason, it may be necessary to balance the two styles to get faster, more compact executable code. Line combination optimization should only be done after the code is working & bug free. Improper optimization can lead to wrong results. Always test optimized code thoroughly.

==Script Structure==
LSL scripts are comprised of expressions, functions, statements, event handlers and states. The LSL compiler mandates a certain structure to scripts:

#User Defined Variables and Functions (see [[LSL Variables]] and [[User-defined functions]])
#[[default]] State (see [[State]]) with at least one [[LSL Events|Event Handler]].
#User Defined States, each with at least one Event Handler.

==LSL Portal Style==

Here in the [[LSL Portal]] we expect consistent white-spacing, and it should look similar to either '''K&R''' or '''Allman'''. We do not require strict adherence to either. We do not use tabs (as they take up an exorbitant amount of screen space) but some number of spaces, usually between 2 and 6, 4 being the most popular value and the value you will see almost everywhere. Generally speaking, it's taboo to edit an article just to fix the white-spacing, unless it's inconsistent (the edit should make it consistent, it should not change the style). Generally speaking, it's taboo to edit an article to change the style. Exceptions do exist, if you are making substantial changes to most of the code in the article, and it makes sense to change the style of the rest of the code (such that it all matches), you may do so. The purpose of this restriction is to keep the peace, some people are really quite attached to their style. Considering that style is a personal preference of little consequence, nothing is gained by forcing one style onto the community, especially when they will go ahead and use whatever style they want disregarding what we mandate. When in doubt or conflict please use the discussion page, a majority are monitored and will be responded to.

If you find yourself desiring to make small changes to white-space despite it being frowned upon, we will ask you to first consider adding an example to one of the articles that [[:Category:LSL_Needs_Example|needs an example]] or is missing some [[:Category:LSL FixMe|key content]].

LSL Style Guide

2022-06-12T11:41:42Z

Sei Lisa: /* Separating code: */ Fix the examples

{{LSL Header|ml=*}}{{RightToc}}

Every major open-source project has its own style guide: a '''set of conventions''' (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a '''consistent style'''. These guidelines, referred to collectively as a Style Guide, are not as rigid as the rules required by the language compiler but nonetheless are critical to creating maintainable code. The most critical aspect of a style is that you apply it consistently to the code you write.

Effective programming in [[LSL Portal|LSL]] requires that developers use a disciplined approach towards formatting and other conventions in their scripts.

{{LSL Tip| Applying a style guide to your code does not only help others read your code. '''It helps you as well''', because in future when you return to the code you wrote before, you'll appreciate reading formatted and annotated code.}}

== Use third party editors: ==

There are many [[LSL Alternate Editors|third party editors]] with [[LSL Portal|LSL]] syntax files available. See an example below of what your workflow would look like using an editor that has syntax highlighting and autocomplete and also applies an indent style to your code.

Using [[LSL Alternate Editors|third party editors]] has a few advantages over using the editor in the viewers:
* Autocompletion helps you avoid typos.
* Autocompletion sometimes not only does a linear autocompletion as in autocompleting <code>llS</code> to <code>llSay</code> but sometimes works even with fuzzy search by autocompleting <code>llslppf</code> to <code>llSetLinkPrimitiveParamsFast</code>.
* The syntax highlighting file colors the code exactly like the code you see in the official Linden Lab viewer making you not having to learn or adapt to a different coloring scheme.
* Autocompletion might also preformat code with indent styles when autocompleting states, events, conditional clauses etc.

== [http://en.wikipedia.org/wiki/Indent_style Indent styles]: ==

Most people, when they start programming on their own, will have programs that are UGLY to look at - to put it nicely, sometimes mistakenly thinking that such scripts occupy less space when compiled. Such scripts typically look like the following:

{| width="100%" {{Prettytable}}
|- {{Hl2}}
! '''unstyled source code'''
|-
||
<syntaxhighlight lang="lsl2">default {state_entry(){llSay(0,"Hello World.");}}</syntaxhighlight>
|}

However, that code is difficult to read (or at least to '''follow''') - even more so when one is writing a couple hundred lines program. There are several [http://en.wikipedia.org/wiki/Indent_style indent styles] with the two most common styles being:

{| width="100%" {{Prettytable}}
|- {{Hl2}}
! '''[http://en.wikipedia.org/wiki/Indent_style#K.26R_style K&R style] (used in Javascript based languages)'''
! '''[http://en.wikipedia.org/wiki/Indent_style#Allman_style Allman style] (used in C based languages)'''
|-
||<syntaxhighlight lang="lsl2">
default {
state_entry() {
llSay(0, "Hello World.");
}
}
</syntaxhighlight>
||
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSay(0, "Hello World.");
}
}
</syntaxhighlight>
|}

The '''K&R style''' conserves space - IN THE SOURCE CODE ONLY, however the '''Allman style''' is easier to read and easier to visually bracket-match. Once a scripter is in the practice of using a particular style, reading code in that style will become easier.

Consistent indenting makes reading both styles easier that's why it '''really comes down to whatever works for you'''. In both methods, indenting is the key indicating factor of levels of scope.

== Naming conventions: ==

There are many naming conventions in Second Life. Only the most used ones will be listed below.

Global Variables (variables used throughout the entire program) should be lowercase. For example:

<syntaxhighlight lang="lsl2">
integer index = 0;
string name = "Please set one";
</syntaxhighlight>

Others prefer to distinguish between global and local variables by prefixing variable names with a character, defining globals in the following manner:

<syntaxhighlight lang="lsl2">
integer gIndex;
string gName = "Please set one";
</syntaxhighlight>

Constant variables should be in ALL CAPS following the style guide used by Linden Labs. For example:

<syntaxhighlight lang="lsl2">
integer DIALOG_CHANNEL = -517265;
vector RED = <1.0, 0.0, 0.0>;
</syntaxhighlight>

Arguments used within a [[Category:LSL User-Defined Functions|user defined function]] or one of the standard [[Event|events]] should be named with '''easily readable and meaningful''' names. When using [[Event|events]], please use the standard names as listed here on the official wiki. An [[Event|overview of all events can be found here]]. Below is an example as can be found for the [[Listen|listen event]]:

<syntaxhighlight lang="lsl2">
// ...

listen(integer channel, string name, key id, string message)
{
key OwnerKey = llGetOwner();

if (channel == 1 && id == OwnerKey)
llOwnerSay("Hello Avatar");
}

// ...
</syntaxhighlight>

== Separating code: ==
Some people put too many function calls on one line. As shown in this example, too many function calls on a single line makes the code hard to read and almost impossible to debug.

<syntaxhighlight lang="lsl2">
list lst;
integer NUM_DIGITS = 10;

default {
touch_start(integer n) {
string name = llToLower(llGetSubString(llList2String(llParseString2List(llDetectedName(0), [" "], []), 0), 0, NUM_DIGITS - 1));
if (!~llListFindList(lst, (list)name))
lst += name;
// send a message to the owner, only reaches owner if online and within the same sim
llOwnerSay(llList2CSV(lst));
}
}
</syntaxhighlight>

Now here is the code, with the exact same features, in a simpler way. While hardly anyone could tell you what the above code did, almost everyone can figure out what the below code does.

<syntaxhighlight lang="lsl2">
list listOfStrings;
integer NUM_DIGITS = 10;

default
{
touch_start(integer n)
{
string name = llDetectedName(0);
list nameAsList = llParseString2List(name, [" "], []);
string firstName = llList2String(nameAsList, 0);
string startPart = llToLower(llGetSubString(firstName, 0, NUM_DIGITS - 1));
integer index = llListFindList(listOfStrings, [startPart]);

if (index == -1)
listOfStrings += startPart;

// send a message to the owner, only reaches owner if online and within the same sim
llOwnerSay(llList2CSV(listOfStrings));
}
}
</syntaxhighlight>

LSL lacks an optimizing compiler. For this reason, it may be necessary to balance the two styles to get faster, more compact executable code. Line combination optimization should only be done after the code is working & bug free. Improper optimization can lead to wrong results. Always test optimized code thoroughly.

==Script Structure==
LSL scripts are comprised of expressions, functions, statements, event handlers and states. The LSL compiler mandates a certain structure to scripts:

#User Defined Variables (see [[LSL_Variables]])
#User Defined Functions (see [[User-defined_functions]])
#[[default]] State (see [[State]])
#User Defined States

==LSL Portal Style==

Here in the [[LSL Portal]] we expect consistent white-spacing, and it should look similar to either '''K&R''' or '''Allman'''. We do not require strict adherence to either. We do not use tabs (as they take up an exorbitant amount of screen space) but some number of spaces, usually between 2 and 6, 4 being the most popular value and the value you will see almost everywhere. Generally speaking, it's taboo to edit an article just to fix the white-spacing, unless it's inconsistent (the edit should make it consistent, it should not change the style). Generally speaking, it's taboo to edit an article to change the style. Exceptions do exist, if you are making substantial changes to most of the code in the article, and it makes sense to change the style of the rest of the code (such that it all matches), you may do so. The purpose of this restriction is to keep the peace, some people are really quite attached to their style. Considering that style is a personal preference of little consequence, nothing is gained by forcing one style onto the community, especially when they will go ahead and use whatever style they want disregarding what we mandate. When in doubt or conflict please use the discussion page, a majority are monitored and will be responded to.

If you find yourself desiring to make small changes to white-space despite it being frowned upon, we will ask you to first consider adding an example to one of the articles that [[:Category:LSL_Needs_Example|needs an example]] or is missing some [[:Category:LSL FixMe|key content]].

Talk:LSL Style Guide

2022-06-12T11:33:02Z

Sei Lisa: Reply to Gwyneth

==Changes to the Style Guide==
I would like to propose that any amendments to the style guide page should FIRST be discussed and approved by others here in this discussion page. Otherwise we can have individuals imposing their eccentric practices willy-nilly. [[User:Omei Qunhua|Omei Qunhua]] 04:35, 24 December 2013 (PST)

:Yeah. The latest change is a prime example of this. It will take some work to neuter it. I don't want to outright revert it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:22, 6 September 2014 (PDT)

::Reverting it is a good starting point. From there, the additions can be discussed, as they should have been in the first place, and the relevant parts added. --[[User:Pedro Oval|Pedro Oval]] 10:33, 7 September 2014 (PDT)

==Script Formatting==
I've recently looked more at ways to keep SL scripts easily readable, and I found that good formatting can be a very positive influence on readability.
Would it be worthwhile to advertise it? basic example:
<syntaxhighlight lang="lsl">integer number = 14;
string something = "test";</syntaxhighlight>
and instead, with formatting:
<syntaxhighlight lang="lsl">integer number = 14;
string something = "test";</syntaxhighlight>
I personally find this a lot faster to take in, and this might be good to pick up for the wiki, possibly making the code pieces here easier readable for the beginning scripter.
especially the article on [[LSL_Variables|variables]] has a block of definitions right at the start, for example, which is a bit confusing to read, but significantly improved by formatting - compare to earlier versions, I went and formatted the text, which, imho, greatly helped readability in that particular case. feel free to revert if theres issues, I consider it a good improvement however, and wouldnt mind bringing more articles to that kind of formatting style if its approved on.
its a thought i wanted to throw in here, and might improve the experience for the readers in general.

[[User:Psistorm Ikura|Psistorm Ikura]] 15:28, 15 April 2009 (UTC)

::I agree with the above,and illustrate it further here, tho' I would have my doubts that others could be persuaded to follow suit. Rigorous alignment makes it so much easier to take in the code's effects quickly. I also prefer to have a space following any comma, for readability.
<syntaxhighlight lang="lsl">
string name = "The Name";
integer index = 1;
list days = ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat"];
rotation MyRot;

if (msg == "Vol+") ++gVol;
else if (msg == "Vol-") --gVol;

else if (msg == "Red") gColour = <1, 0, 0>;
else if (msg == "Green") gColour = <0, 1, 0>;
else if (msg == "Blue") gColour = <0, 0, 1>;
</syntaxhighlight>
[[User:Omei Qunhua|Omei Qunhua]] 04:35, 24 December 2013 (PST)

:::Space following comma: Good. Putting your conditional execution blocks on the same line as your condition: THE GOGGLES! THEY DO NOTHING! I just find the latter makes my brain itch. It complicates the parsing for me. That said, it's a personal preference thing... and I would have trouble not going through and putting them on their own line. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 01:43, 25 December 2013 (PST)

:But it's soooooo beautiful! Like a mini-database, the columnar nature giving it such regularity, such clarity, such a poetic architectural feel! The format you wants breaks up the logic unnecessarily, confusing the eye. But then ... I've only been programming for 52 years. (I have to pull that one out from time to time ^^ ) [[User:Omei Qunhua|Omei Qunhua]] 16:16, 26 December 2013 (PST)

::It makes me think of Basic when I see it (QBasic actually) where THEN is like "{", and ENDIF is like "}". If there wasn't a new line following your THEN you don't need an ENDIF and you give the appearance of an unclosed block.
::I've come up with a reason for why I shouldn't like it. It has to do with Order of Execution in LSL, which is to say, it is backwards. Every other language I have seen executes the left operand first and then the right, LSL is the complete opposite, which means that you execute statements right to left. If your expression has side-effects, they will happen in right to left order (though a literal list elements expressions and function parameter expressions are executed in left to right order (though the actual execution of each expression is still executed in right to left order)). This means a paranoid LSL scripter reads their expressions right to left, and if you place two expressions on the same line, you run the risk of reading the later expressions before it should be read. I don't think (but I could be wrong) this really describes how I work. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:45, 26 December 2013 (PST)

==Script Structure==
Mandating event order seems a little retentive to me. I don't think any scripter who is going to post code onto the wiki is going to be keen on rewriting their code to fit the pattern. Being flexible to other scripters styles is a key to success (especially with regards to collaborative projects). They should be grouped in a fashion that makes sense to the script and scripter. Seeing as this section is going to be a hot topic, maybe it shouldn't be included or make it very short? [[User:Strife Onizuka|Strife Onizuka]] 22:29, 14 February 2007 (PST)
: I agree that mandating event order would be a pain in the ass.
: I personally put events in the order they're first used throughout the process of a script's life cycle.
: If a Resident is learning to script from a [[:Category:LSL Mentors|mentor]] or [[:Category:LSL Teachers|teacher]], they're likely to be using snippets of code they're sent in-world. For them to see a different structure in LSL Library code would be confusing
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 05:44, 15 February 2007 (PST)

::Residents start with the default "Hello World" script with touch event. Finding the Wiki examples at odds with that script (through the use of PUBIC_CHANNEL for example) will be confusing for them The Wiki should follow the pattern of the vast majority, unless it's clearly wrong in some way. [[User:Omei Qunhua|Omei Qunhua]] 04:35, 24 December 2013 (PST)

== ''' Re: General Guidelines''' ==

Would suggest that the virtues of the second style shown be amended. Saving space is a pointless exercise if LSL code is truly compiled rather than interpreted. The overhead needed to compile a few extra carriage returns has to be trivial in all but the most monumentally huge scripts.

Second virtue of the "parallel brackets" style (the second type shown) is that the nesting of logical modules is far more clear, and is effectively a form of self-documentation that is often more effective than text comments, especially when code is likely to be rewritten, revised or adapted to another purpose by individuals other than the original author. It can even help the original author understand her own code better, faster, if she is returning to a bit of code written in the relatively dim past.

Would take a shot at saying this more concisely, but first want to see if there are other views that should also be reflected in any revision to the text.

This is my first contribution here. Please forgive any unintentional breeches of protocol and etiquette.
--[[User:Azadine Umarov|Azadine Umarov]] 17:49, 7 May 2007 (PDT)

: Good comment. Bracketing style is an old debate in programing (20 years at least). Both styles have their advantages as long as the scripter is consistent with the style they pick. The key in programing is consistency in style, not so much what the style is. -- [[User:Strife Onizuka|Strife Onizuka]] 12:11, 8 May 2007 (PDT)

:: I wonder if we should just show the two ways of bracketing and let the readers decide which to use, with out giving any description of which one is "Better", even though everyone knows the brackets go on the same line as the code. ;P [[User:Xaviar Czervik|Xaviar Czervik]]

== Some of my pet peeves with this article... ==

Hey there, fellow LSLwiktors!

So, I've done the unthinkable: edited the Style Guide ''without discussing it first''. 😅

Rest assured, everything is just a simple revert away. Also, essentially, I get annoyed by an article being flagged for using the obsolete <code><source></code> tag, so I simply change it to the current <code><syntaxhighlight></code> tag instead. Why? Well, I actually ''like'' the <code><source></code> tag more. Long story, but I come from the days when SGML/HTML tags were about ''structure'', not ''visual rendering'' — <code><source></code> ''describes'' the content within those tags (it's source code!), while <code><syntaxhighlight></code> implies a specific type of rendering; it would be something to avoid in Ye Olde Days and banned to [[the Corn Field]] together with the [https://www.w3docs.com/learn-html/html-blink-tag.html <code><blink></code>] tag and similar Cthulhuesque abominations.

'''Colon after section headers'''

Personally, I dislike the colons at the end of some of the headers; they look terrible on the ToC. But this is a matter of personal opinion. So, I suggest that either ''all'' headers have colons at the end (for consistency's sake), or ''none'' have colons, just like all other headers in the Wiki. A third alternative would be disabling the ToC, to get rid of those annoying violation of æsthetic rules...

'''Use third party editors'''

Regarding this section, I propose a very slight (but reasonable!) change, namely, adding that one advantage ''today'' of 3rd-party editors is that it's far easier (and faster) to edit long sections of code, and just keep loading and saving the file from/to the local disk.

Under the Firestorm Viewer, it's even better — you can open the script ''directly'' on an external editor, and, when saving, you get a button to save directly to that external file; conversely, you can do all your edits on the external editor, and, when saving, those changes will immediately reflect on the in-world LSL script (at least, that's the result from my experiments).

The ability to integrate with a 3rd-party editor so closely means that, in areas with high lag, you can continue to do all your scripting in the ''external?? editor — thus, not being subjected to the fickleness of the built-in LSL editor, which will become more and more lagged, so far as conditions continue to deteriorate in the region. It takes not much lag to reach a certain threshold that makes scripting inside SL a prefect nightmare... while external editors, of course, are not affected by in-world lag.

'''LSL lacks an optimizing compiler.'''

Are we really sure about this? It's just because that LL originally used their own, home-grown interpreter/compiler for [[LSO]] bytecode, which was deemed not to be very good at its job. Nowadays, however, I would say that the Mono compiler makes a respectable job of optimizing things, and, as such, this comment should be revised/redacted.

'''Fixing old-style <code><lsl></code> tags in the ''comments'' section'''

I felt tempted, for more than once, to break the Wiki taboo of 'never changing someone else's comments', but decided to ask first. :)

Here is my dilemma: on this talk page, there are a few examples that are of historic value, they came from the earlier Wiki, which used the tag <code><lsl></code> to do the syntax highlighting. This tag does not work anymore under the current MediaWiki version. As a consequence, those examples, which illustrate some formatting styles, are next to unreadable.

I therefore propose to (exceptionally) allow these to be edited in order to show those lines of code in context, formatted according to what the original intention of the commenter was. But this is a violation of the trust they placed in the community, that nobody would change their comments, no matter what.

What do you think?

— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 02:37, 15 April 2022 (PDT)

:I'm neutral about most of your post and won't comment on it. Things have changed since Linden Lab made the wiki closed due to a fierce spam attack some years ago, and there's very few people remaining to enforce any rules. I totally agree that editing <lsl> tags is clearly an exception to the rule not to edit anyone's comments; I've gone ahead and made that change.

:What I can tell you for sure is that LSL ''does'' indeed lack an optimizing compiler. That's the very reason why [http://lsl.blacktulip-virtual.com/lsl-pyoptimizer/ LSL-PyOptimizer] exists. It optimizes for size only and is designed for Mono only; for LSO it can make programs grow instead of reduce in size, or even stop working due to triggering LSO bugs. The point is that Mono is definitively affected. I studied Mono bytecode in depth while writing the optimizer, and was horrified by what I found.

:Linden Lab's compiler generates bytecode for basically everything you write, except labels. Even the ''names'' of global variables, functions, events, parameters or states use up code memory; only the names of local variables and labels are free from that madness. Given the 64KB limit imposed to Mono scripts, saving memory is crucial for some applications.

:Anyway, the example about optimization vs readability is crap and I'm going to edit it. It declares a variable and then uses it without assigning any value to it; it assigns a long expression to another variable that it doesn't use either, and repeats a long common subexpression twice that anyone would realize is wasting, rather than saving, memory. It also uses llKey2Name(llDetectedKey(x)) instead of llDetectedName(x); if it's an example of the loss of readability when optimizing code, it's not a good example of such optimization.

:--[[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 04:33, 12 June 2022 (PDT)

Talk:UUID

2022-02-02T00:52:39Z

Sei Lisa: /* UUIDs are v4... or not!? */

RFC specification website is changed. Link appears to want https://datatracker.ietf.org/doc/html/rfc4122#section-4.1.3

== UUIDs are v4... or not!? ==

This page claims:

<blockquote>SL uses Version 4 UUIDs as defined in RFC-4122, though there are some that are not V4.</blockquote>

Except for <code>NULL_KEY</code> (which is separately defined in RFC-4122), what are those UUIDs that are not V4? Where are they used? When were they generated, and for which purpose? What version do they conform to, if not 4?

The issue is only important for me to validate UUIDs coming from SL and making sure they conform to whatever UUID specification SL uses. The statement on this page implies that SL uses UUIDs from different sources, possibly different versions, and possibly even UUIDs which are not technically UUIDs (as understood by RFC-4122), they just ''look'' like UUIDs (humans may not be able to spot the difference visually).

How, then, can we validate if an UUID is valid? :)

[[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 12:33, 27 January 2022 (PST)

:Most, but not all, avatar UUIDs are V4. A few of the earliest ones aren't, like 3de27254-3baa-31fd-2d41-4ff10c86717e.
:Most other UUIDs are NOT v4, including groups, animations, textures, sounds, inworld object IDs...
:The only way to validate them, besides checking the 8-4-4-4-12 format (<code>if (my_key_value)</code> in LSL comes handy for that), is checking if they exist in the database. A certain UUID may not be valid today and may be valid tomorrow.
:
:[[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 16:52, 1 February 2022 (PST)

Talk:Listen

2021-06-04T01:35:36Z

Sei Lisa: Reply to Joanne

It has come up in Script Academy that listen events cannot receive group chat messages, and thus the key parameter description is incorrect. I've been trying to update this description, but I don't know where to find the UUID description page/template that is used for the key parameter. Can someone explain how to find it? [[User:Joanne Furlough|Joanne Furlough]] ([[User talk:Joanne Furlough|talk]]) 04:08, 31 May 2021 (PDT)

: There are several hoops. I couldn't trace them all, but the immediate one is that Template:LSL_Event introduces it. It can be worked around by changing this:
: <code>|p3_type=key|p3_name=id|p3_desc</code>
: so that p3_name is no longer id, and then you can add a description with p3_desc=<free text>.
: Hope that helps. [[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 18:35, 3 June 2021 (PDT)

LlHash

2021-05-21T16:42:40Z

Sei Lisa: fix link

{{LSL Function
|func_sleep=0.0|func_energy=10.0
|func=llHash|sort=Hash
|func_desc=Returns a 32bit hash for the provided string. Returns 0 if the input string is empty.
|return_type=integer
|p1_type=string|p1_name=val|p1_desc=String to hash.
|p1_hover=String to hash.
|return_text=
|func_footnote=
|spec=
The SDBM algorithm provides a good general purpose hash function with a fairly even distribution across the 32 bit space in the general case.
The characters fed into the hash function are 32bit wide.

<source lang="cpp">
U32 SDBMHash(const std::wstring &val)
{
U32 hash(0);

for(const wchar_t &c: val)
{
hash = c + (hash << 6) + (hash << 16) - hash;
}
return hash;
}
</source>

In LSL:
<source lang="lsl2">
integer llSDBMHash(string value)
{
integer hash = 0;
integer index = 0;
for (index = 0; index < llStringLength(value); ++index)
{
hash = llOrd(value, index) + (hash << 6) + (hash << 16) - hash;
}

return hash;
}

</source>

|caveats=
This hash value is not cryptographically secure and should not be used as part of any security protocol.
SDBM provides a good distribution of hash values across its range, however with only
32 bits the chance of a collision is unacceptably high.(with 1000 entries, the odds for a collision are about 1 in 10000.)
|examples=
Given the combination of the object name and the owner's key generate a unique number. This number could be used for things
like selecting a chat channel that has a low probability of colliding with another object.
<source lang="lsl2">
integer pickIDForObject()
{
/* Generate an arbitrary integer ID for the combination of the
* object name and the ower's key. This value could be used
* for selecting a chat/listen channel.
*/
string obj_name = llGetObjectName();
key obj_owner = llGetOwner();

integer hash = llHash(obj_name + (string)obj_owner);

return hash;
}
</source>
|helpers|related
|also_functions=
{{LSL DefineRow|[[llOrd]]|Convert a character into an ordinal}}
{{LSL DefineRow|[[llChar]]|Convert an ordinal into a character}}
|also_articles={{LSL DefineRow||{{wikipedia|List of hash functions}}|}}
{{LSL DefineRow||[https://preshing.com/20110504/hash-collision-probabilities/ Hash Collision Probabilities]|}}
|notes
|cat1
|cat2
|cat3
|cat4
}}

Template:LSL Constants/PrimitiveParams

2021-01-25T23:54:39Z

Sei Lisa: add missing params

<noinclude>{{multi-lang}}</noinclude>{{#if:

{{Footnote|When LL deprecated this flag they stripped it of it's name, however they did not remove the functionality. To aid in documenting the functionality, the value was given a new name in the documentation only. That is why PRIM_TYPE_LEGACY is not recognized by the compiler.|handle=ptl}}

{{:PRIM_NAME|{{{1|}}}}}
{{:PRIM_DESC|{{{1|}}}}}
{{:PRIM_SLICE|{{{1|}}}}}
{{:PRIM_COLOR|{{{1|}}}}}
{{:PRIM_GLOW|{{{1|}}}}}
{{:PRIM_TEXGEN|{{{1|}}}}}
{{:PRIM_TEXTURE|{{{1|}}}}}
{{:PRIM_TEXT|{{{1|}}}}}
{{:PRIM_FULLBRIGHT|{{{1|}}}}}
{{:PRIM_BUMP_SHINY|{{{1|}}}}}
{{:PRIM_MATERIAL|{{{1|}}}}}
{{:PRIM_TYPE|{{{1|}}}}}
{{:PRIM_TYPE_BOX|{{{1|}}}}}
{{:PRIM_TYPE_SCULPT|{{{1|}}}}}
{{:PRIM_PHANTOM|{{{1|}}}}}
{{:PRIM_TEMP_ON_REZ|{{{1|}}}}}
{{:PRIM_PHYSICS|{{{1|}}}}}
{{:PRIM_SIZE|{{{1|}}}}}
{{:PRIM_POSITION|{{{1|}}}}}
{{:PRIM_POS_LOCAL|{{{1|}}}}}
{{:PRIM_ROTATION|{{{1|}}}}}
{{:PRIM_ROT_LOCAL|{{{1|}}}}}
{{:PRIM_FLEXIBLE|{{{1|}}}}}
{{:PRIM_POINT_LIGHT|{{{1|}}}}}
{{:PRIM_OMEGA|{{{1|}}}}}
{{:PRIM_PHYSICS_SHAPE_TYPE|{{{1|}}}}}
{{:PRIM_NORMAL|{{{1|}}}}}
{{:PRIM_SPECULAR|{{{1|}}}}}
{{:PRIM_ALPHA_MODE|{{{1|}}}}}

{{:PRIM_LINK_TARGET|{{{1|}}}|{{{2|}}}}}<--Must be last-->

{{LSL_Function/color|color}}
{{LSL_Function/alpha|alpha}}
{{LSL_Function/boolean|boolean}}
{{LSL_Function/face|face|flag|!footer=*|returns={{#ifeq:{{{1|<noinclude>get</noinclude>}}}|get|nothing.}}}}

}}{{#ifeq:{{{1|<noinclude>set</noinclude>}}}|set|
{{{!}} class="sortable" {{Prettytable|style=margin: 0px 0px 10px 1pt;}}
{{!}}- {{Hl2}}
! class="sortable" {{!}}Flag
! class="sortable" title="Value" style="cursor: help;" {{!}}V
! class="sortable" {{!}}Description
! class="unsortable" {{!}}Usage
{{!}}-
{{!}} [[#PRIM_NAME|PRIM_NAME]]
{{!}} 27
{{!}} Sets the prim's name.
{{!}} [ {{#var:name_const}}, [[string]] {{LSL Param|name}} ]
{{!}}-
{{!}} [[#PRIM_DESC|PRIM_DESC]]
{{!}} 28
{{!}} Sets the prim's description.
{{!}} [ {{#var:desc_const}}, [[string]] {{LSL Param|description}} ]
{{!}}-
{{!}} [[#PRIM_TYPE|PRIM_TYPE]]
{{!}} 9
{{!}} Sets the prim's shape.
{{!}} [ {{#var:type_const}}, [[integer]] {{HoverText|flag|PRIM_TYPE_* flag}} ] + {{HoverLink|#PRIM_TYPE_flag_parameters|Additional parameters required by the flag|flag_parameters}}
{{!}}-
{{!}} [[#PRIM_SLICE|PRIM_SLICE]]
{{!}} 35
{{!}} Sets the prim's slice (a shape attribute).
{{!}} [ {{#var:slice_const}}, [[vector]] {{LSL Param|cut|slice}} ]
{{!}}-
{{!}} [[#PRIM_PHYSICS_SHAPE_TYPE|PRIM_PHYSICS_SHAPE_TYPE]]
{{!}} 30
{{!}} Sets the prim's physics shape type.
{{!}} [ {{#var:physics_shape_type_const}}, [[integer]] {{LSL Param|pstype|type}} ]
{{!}}-
{{!}} [[#PRIM_MATERIAL|PRIM_MATERIAL]]
{{!}} 2
{{!}} Sets the prim's material.
{{!}} [ {{#var:material_const}}, [[integer]] {{HoverText|flag|PRIM_MATERIAL_* flag}} ]
{{!}}-

{{!}}-
{{!}} [[#PRIM_PHYSICS|PRIM_PHYSICS]]
{{!}} 3
{{!}} Sets the object's physics status.
{{!}} [ {{#var:physics_const}}, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[#PRIM_TEMP_ON_REZ|PRIM_TEMP_ON_REZ]]
{{!}} 4
{{!}} Sets the object's {{LSLGC|Temporary|temporary}} attribute.
{{!}} [ {{#var:temponrez_const}}, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[#PRIM_PHANTOM|PRIM_PHANTOM]]
{{!}} 5
{{!}} Sets the object's phantom status.
{{!}} [ {{#var:phantom_const}}, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[#PRIM_POSITION|PRIM_POSITION]]
{{!}} 6
{{!}} Sets the prim's position.
{{!}} [ {{#var:position_const}}, [[vector]] {{LSL Param|position{{{1|}}}|position}} ]
{{!}}-
{{!}} [[#PRIM_POS_LOCAL|PRIM_POS_LOCAL]]
{{!}} 33
{{!}} Sets the prim's local position.
{{!}} [ {{#var:pos_local_const}}, [[vector]] {{LSL Param|pos|position}} ]
{{!}}-
{{!}} [[#PRIM_ROTATION|PRIM_ROTATION]]
{{!}} 8
{{!}} Sets the prim's global rotation.
{{!}} [ {{#var:rotation_const}}, [[rotation]] {{LSL Param|rot}} ]
{{!}}-
{{!}} [[#PRIM_ROT_LOCAL|PRIM_ROT_LOCAL]]
{{!}} 29
{{!}} Sets the prim's local rotation.
{{!}} [ {{#var:rot_local_const}}, [[rotation]] {{LSL Param|rot_local|rot}} ]
{{!}}-
{{!}} [[#PRIM_SIZE|PRIM_SIZE]]
{{!}} 7
{{!}} Sets the prim's size.
{{!}} [ {{#var:size_const}}, [[vector]] {{LSL Param|size}} ]
{{!}}-
{{!}} [[#PRIM_TEXTURE|PRIM_TEXTURE]]
{{!}} 17
{{!}} Sets the prim's texture attributes.
{{!}} [ {{#var:texture_const}}, [[integer]] {{LSL Param|face}}, [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}} ]
{{!}}-
{{!}} [[#PRIM_TEXT|PRIM_TEXT]]
{{!}} 26
{{!}} Sets the prim's floating text.
{{!}} [ {{#var:text_const}}, [[string]] {{LSL Param|text}}, [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|alpha}} ]
{{!}}-
{{!}} [[#PRIM_COLOR|PRIM_COLOR]]
{{!}} 18
{{!}} Sets the face's color.
{{!}} [ {{#var:color_const}}, [[integer]] {{LSL Param|face}}, [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|alpha}} ]
{{!}}-
{{!}} [[#PRIM_BUMP_SHINY|PRIM_BUMP_SHINY]]
{{!}} 19
{{!}} Sets the face's shiny & bump.
{{!}} [ {{#var:bumpshiny_const}}, [[integer]] {{LSL Param|face}}, [[integer]] {{LSL Param|shiny}}, [[integer]] {{LSL Param|bump}} ]
{{!}}-
{{!}} [[#PRIM_POINT_LIGHT|PRIM_POINT_LIGHT]]
{{!}} 23
{{!}} Sets the prim as a point light.
{{!}} [ {{#var:light_const}}, [[integer]] {{LSL Param|boolean}}, [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|intensity}}, [[float]] {{LSL Param|radius}}, [[float]] {{LSL Param|falloff}} ]
{{!}}-
{{!}} [[#PRIM_FULLBRIGHT|PRIM_FULLBRIGHT]]
{{!}} 20
{{!}} Sets the face's full bright flag.
{{!}} [ {{#var:fullbright_const}}, [[integer]] {{LSL Param|face}}, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[#PRIM_FLEXIBLE|PRIM_FLEXIBLE]]
{{!}} 21
{{!}} Sets the prim as flexible.
{{!}} [ {{#var:flexible_const}}, [[integer]] {{LSL Param|boolean}}, [[integer]] {{LSL Param|softness}}, [[float]] {{LSL Param|flex_float|gravity}}, [[float]] {{LSL Param|flex_float|friction}}, [[float]] {{LSL Param|flex_float|wind}}, [[float]] {{LSL Param|flex_float|tension}}, [[vector]] {{LSL Param|force}} ]
{{!}}-
{{!}} [[#PRIM_TEXGEN|PRIM_TEXGEN]]
{{!}} 22
{{!}} Sets the face's texture mode.
{{!}} [ {{#var:texgen_const}}, [[integer]] {{LSL Param|face}}, [[integer]] {{HoverText|type|PRIM_TEXGEN_* flag}} ]
{{!}}-
{{!}} [[#PRIM_GLOW|PRIM_GLOW]]
{{!}} 25
{{!}} Sets the face's glow attribute.
{{!}} [ {{#var:glow_const}}, [[integer]] {{LSL Param|face}}, [[float]] {{LSL Param|intensity}} ]
{{!}}-
{{!}} [[#PRIM_OMEGA|PRIM_OMEGA]]
{{!}} 32
{{!}} Sets the prim's spin to the specified axis and rate.
{{!}} [ {{#var:omega_const}}, [[vector]] {{LSL Param|axis}}, [[float]] {{LSL Param|spinrate}}, [[float]] {{LSL Param|gain}} ]
{{!}}-
{{!}} [[#PRIM_NORMAL|PRIM_NORMAL]]
{{!}} 37
{{!}} Sets the prim's normal map attributes.
{{!}} [ {{#var:normal_const}}, [[integer]] {{LSL Param|face}}, [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}} ]
{{!}}-
{{!}} [[#PRIM_SPECULAR|PRIM_SPECULAR]]
{{!}} 36
{{!}} Sets the prim's specular map attributes.
{{!}} [ {{#var:specular_const}}, [[integer]] {{LSL Param|face}}, [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}}, [[vector]] {{LSL Param|color}}, [[integer]] {{LSL Param|glossiness}}, [[integer]] {{LSL Param|environment}} ]
{{!}}-
{{!}} [[#PRIM_ALPHA_MODE|PRIM_ALPHA_MODE]]
{{!}} 38
{{!}} Sets the prim's diffuse texture alpha rendering mode attributes.
{{!}} [ {{#var:alpha_mode_const}}, [[integer]] {{LSL Param|face}}, [[integer]] {{LSL Param|alpha_mode}}, [[integer]] {{LSL Param|mask_cutoff}} ]
{{!}}-
{{!}} [[#PRIM_LINK_TARGET|PRIM_LINK_TARGET]]
{{!}} 34
{{!}} Sets the next linknumber to use in the linkset.
{{!}} [ {{#var:link_target_const}}, [[integer]] {{LSL Param|link_target}} ]
{{!}}-
{{!}} [[#PRIM_CAST_SHADOWS|PRIM_CAST_SHADOWS]]
{{!}} 24
{{!}} Sets the prim's cast shadow attribute. ('''DEPRECATED''')
{{!}} [ {{LSL Const|PRIM_CAST_SHADOWS|integer|24}}, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[#PRIM_TYPE_LEGACY|PRIM_TYPE_LEGACY]]{{Footnote|handle=ptl}}
{{!}} 1
{{!}} Sets the prim's shape (legacy mode, '''DEPRECATED''').
{{!}} [ 1, [[integer]] {{HoverText|flag|PRIM_TYPE_* flag}} ] + {{HoverLink|#PRIM_TYPE_LEGACY_flag_parameters|Additional parameters required by the flag|flag_parameters}}
{{!}}-
{{!}} [[PRIM_ALLOW_UNSIT]]
{{!}} 39
{{!}} Avatars are allowed to manually stand up when seated on this prim. Only valid for prims in a valid experience.
{{!}} [ PRIM_ALLOW_UNSIT, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[PRIM_SCRIPTED_SIT_ONLY]]
{{!}} 40
{{!}} Avatars are not permitted to manually sit on this prim.
{{!}} [ PRIM_SCRIPTED_SIT_ONLY, [[integer]] {{LSL Param|boolean}} ]
{{!}}-
{{!}} [[PRIM_SIT_TARGET]]
{{!}} 41
{{!}} The sit target, if any defined for this prim.
{{!}} [ PRIM_SIT_TARGET, [[integer]] {{LSL Param|boolean}}, [[vector]] {{LSL Param|pos|offset}}, [[rotation]] {{LSL Param|rot}} ]
{{!}}} }}
{{{!}} {{Prettytable|style=margin: 0px 0px 10px 1pt;}} {{#switch:{{NAMESPACE}}|Template=|User=|{{LSLC|Light}}}}
{{!}}- {{Hl2}}
! colspan="2" {{!}} Parameter
! colspan="2" {{!}} {{GetSet|{{{1|}}}|Return Values|Additional Parameters}}
! colspan="6" {{!}} Description
{{!}}-
{{LSL ConstTB|PRIM_NAME|integer|27|b=[ |e= ]|s1=id="PRIM_NAME"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|name}} ]
{{!}} colspan="3" {{!}} Name: {{GetSet|{{{1|}}}|[[llGetObjectName]]|[[llSetObjectName]]}}
{{!}}-
{{LSL ConstTB|PRIM_DESC|integer|28|b=[ |e= ]|s1=id="PRIM_DESC"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|description}} ]
{{!}} colspan="3" {{!}} Description: {{GetSet|{{{1|}}}|[[llGetObjectDesc]]|[[llSetObjectDesc]]}}
{{!}}-
{{LSL ConstTB|PRIM_TYPE|integer|9|b=[ |e= ]|s1=id="PRIM_TYPE"}}
{{!}} colspan="2" {{!}} [ [[integer]] {{HoverText|flag|PRIM_TYPE_* flag}} ] + flag_parameters
{{!}} colspan="6" {{!}} {{GetSet|{{{1|}}}|Gets|Sets}} the prim shape. {{CustomToggle|PRIM_TYPE|show=Would you like to know more?|link=PRIM_TYPE}}
{{!}}- {{CustomToggle/Collapsible|PRIM_TYPE}}
{{!}} colspan="2" {{!}}
{{!}} colspan="8" {{!}}
{{LSL Constants/PrimitiveParams/type|{{{1|}}}|table=*|sortable=*}}
{{!}}-
{{LSL ConstTB|PRIM_SLICE|integer|35|b=[ |e= ]|s1=id="PRIM_SLICE"}}
{{!}} colspan="2" {{!}} [ [[vector]] {{LSL Param|cut|slice}} ]
{{!}} colspan="6" {{!}} {{GetSet|{{{1|}}}|Gets|Sets}} the prim's slice (a shape attribute).
{{!}}-
{{LSL ConstTB|PRIM_PHYSICS_SHAPE_TYPE|integer|30|b=[ |e= ]|s=rowspan="5"|s1=id="PRIM_PHYSICS_SHAPE_TYPE"}}
{{!}} colspan="2" {{!}} [ [[integer]] {{LSL Param|pstype|type}} ]
{{!}} colspan="6" {{!}} {{GetSet|{{{1|}}}|Gets|Sets}} the prim's physics shape type.
{{!}}-
{{#var:physics_shape_type_rows}}
{{!}}-
{{LSL ConstTB|PRIM_MATERIAL|integer|2|b=[ |e= ]|s=rowspan="10"|s1=id="PRIM_MATERIAL"}}
{{!}} colspan="2" {{!}} [ [[integer]] {{LSL Param|material}} ]
{{!}} colspan="6" {{!}} {{GetSet|{{{1|}}}|Gets|Sets}} the prim's material. The material determines the default [[llCollisionSound|collision sound]], [[llCollisionSprite|sprite]], [[llSetPhysicsMaterial|{{LSLP|friction}} coefficient and {{LSLP|restitution}} coefficient]].
{{!}}-
{{LSL Constants/PrimitiveParams/materials}}
{{!}}-

{{!}}-
{{LSL ConstTB|PRIM_PHYSICS|integer|3|b=[ |e= ]|s1=id="PRIM_PHYSICS"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}} Physics status {{GetSet|{{{1|}}}|[[llGetStatus]]|[[llSetStatus]]}}
{{!}}-
{{LSL ConstTB|PRIM_TEMP_ON_REZ|integer|4|b=[ |e= ]|s1=id="PRIM_TEMP_ON_REZ"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}} {{LSLGC|Temporary}} attribute
{{!}}-
{{LSL ConstTB|PRIM_PHANTOM|integer|5|b=[ |e= ]|s1=id="PRIM_PHANTOM"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}} Phantom status {{GetSet|{{{1|}}}|[[llGetStatus]]|[[llSetStatus]]}}
{{!}}-
{{LSL ConstTB|PRIM_POSITION|integer|6|b=[ |e= ]|s1=id="PRIM_POSITION"}}
{{!}} colspan="5" {{!}} [ [[vector]] {{LSL Param|position{{{1|}}}|position}} ]
{{!}} colspan="3" {{!}} Position, {{GetSet|{{{1|}}}|[[llGetPos]]|[[llSetPos]]}}
{{!}}-
{{LSL ConstTB|PRIM_POS_LOCAL|integer|33|b=[ |e= ]|s1=id="PRIM_POS_LOCAL"}}
{{!}} colspan="5" {{!}} [ [[vector]] {{LSL Param|pos|position}} ]
{{!}} colspan="3" {{!}} Local position, {{GetSet|{{{1|}}}|[[llGetLocalPos]]|[[llSetPos]]}}
{{!}}-
{{LSL ConstTB|PRIM_ROTATION|integer|8|b=[ |e= ]|s1=id="PRIM_ROTATION"}}
{{!}} colspan="5" {{!}} [ [[rotation]] {{LSL Param|rot}} ]
{{!}} colspan="3" {{!}} Global rotation, {{GetSet|{{{1|}}}|[[llGetRot]]|[[llSetRot]] (broken for child prims)}}
{{!}}-
{{LSL ConstTB|PRIM_ROT_LOCAL|integer|29|b=[ |e= ]|s1=id="PRIM_ROT_LOCAL"}}
{{!}} colspan="5" {{!}} [ [[rotation]] {{LSL Param|rot_local|rot}} ]
{{!}} colspan="3" {{!}} Local rotation, {{GetSet|{{{1|}}}|[[llGetLocalRot]]|[[llSetLocalRot]]}}
{{!}}-
{{LSL ConstTB|PRIM_SIZE|integer|7|b=[ |e= ]|s1=id="PRIM_SIZE"}}
{{!}} colspan="5" {{!}} [ [[vector]] {{LSL Param|size}} ]
{{!}} colspan="3" {{!}} Size, {{GetSet|{{{1|}}}|[[llGetScale]]|[[llSetScale]]}}
{{!}}-
{{LSL ConstTB|PRIM_TEXTURE|integer|17|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_TEXTURE"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}} ]
{{!}} colspan="3" {{!}}
{{{!}} style="background-color:#F9F9F9;"
{{!}}{{!}}{{LSLGC|Texture}}: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetTexture]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llSetTexture]]}}
{{!}}-
{{!!}}Repeats: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetTextureScale]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llScaleTexture]]}}
{{!}}-
{{!!}}Offset: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetTextureOffset]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llOffsetTexture]]}}
{{!}}-
{{!!}}Rotation: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetTextureRot]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llRotateTexture]]}}
{{!}}}
{{!}}-
{{LSL ConstTB|PRIM_TEXT|integer|26|b=[ |e= ]|s1=id="PRIM_TEXT"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|text}}, [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|alpha}} ]
{{!}} colspan="3" {{!}} Floating Text: {{GetSet|{{{1|}}}|NA|[[llSetText]]}}
{{!}}-
{{LSL ConstTB|PRIM_COLOR|integer|18|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_COLOR"}}
{{!}} colspan="5" {{!}} [ [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|alpha}} ]
{{!}} colspan="3" {{!}}
{{{!}} style="background-color:#F9F9F9;"
{{!!}}{{LSLGC|Alpha}}: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetAlpha]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llSetAlpha]]}}
{{!}}-
{{!!}}{{LSLGC|Color}}: {{!}}{{!}} {{#ifeq:{{{1|get}}}|get|[[llGetColor]]}} {{!}}{{!}} {{#ifeq:{{{1|set}}}|set|[[llSetColor]]}}
{{!}}}
{{!}}-
{{LSL ConstTB|PRIM_BUMP_SHINY|integer|19|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s=rowspan="25"|s1=id="PRIM_BUMP_SHINY"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|shiny}}, [[integer]] {{LSL Param|bump}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL_Constants/PrimitiveParams/bumpshiny}}
{{!}}-
{{LSL ConstTB|PRIM_FULLBRIGHT|integer|20|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_FULLBRIGHT"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_FLEXIBLE|integer|21|b=[ |e= ]|s1=id="PRIM_FLEXIBLE"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}}, [[integer]] {{LSL Param|softness}}, [[float]] {{LSL Param|flex_float|gravity}}, [[float]] {{LSL Param|flex_float|friction}}, [[float]] {{LSL Param|flex_float|wind}}, [[float]] {{LSL Param|flex_float|tension}}, [[vector]] {{LSL Param|force}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_TEXGEN|integer|22|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s=rowspan="4"|s1=id="PRIM_TEXGEN"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|tg_type|mode}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL Constants/PrimitiveParams/texgen}}
{{!}}-
{{LSL ConstTB|PRIM_POINT_LIGHT|integer|23|b=[ |e= ]|s1=id="PRIM_POINT_LIGHT"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}}, [[vector]] {{LSL Param|color}}, [[float]] {{LSL Param|intensity}}, [[float]] {{LSL Param|radius}}, [[float]] {{LSL Param|falloff}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_GLOW|integer|25|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_GLOW"}}
{{!}} colspan="5" {{!}} [ [[float]] {{LSL Param|intensity}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_OMEGA|integer|32|b=[ |e= ]|s1=id="PRIM_OMEGA"}}
{{!}} colspan="5" {{!}} [ [[vector]] {{LSL Param|axis}}, [[float]] {{LSL Param|spinrate}}, [[float]] {{LSL Param|gain}} ]
{{!}} colspan="4" {{!}} [[llTargetOmega]]
{{!}}-
{{LSL ConstTB|PRIM_NORMAL|integer|37|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_NORMAL"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_SPECULAR|integer|36|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_SPECULAR"}}
{{!}} colspan="5" {{!}} [ [[string]] {{LSL Param|texture}}, [[vector]] {{LSL Param|repeats}}, [[vector]] {{LSL Param|offsets}}, [[float]] {{LSL Param|rotation_in_radians}}, [[vector]] {{LSL Param|color}}, [[integer]] {{LSL Param|glossiness}} [[integer]] {{LSL Param|environment}} ]
{{!}}-
{{LSL ConstTB|PRIM_ALPHA_MODE|integer|38|b=[ |e=, [[integer]] {{LSL Param|face}} ]|s1=id="PRIM_ALPHA_MODE"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|alpha_mode}}, [[integer]] {{LSL Param|mask_cutoff}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_LINK_TARGET|integer|34|b=[ |e=, [[integer]] {{LSL Param|link_target}} ]|s1=id="PRIM_LINK_TARGET"}}
{{!}} colspan="5" {{!}} []
{{!}} colspan="4" {{!}} Multiple {{GetSet|{{{1|}}}|[[llGetLinkPrimitiveParams]]|[[llSetLinkPrimitiveParams]]}} calls.
{{!}}-
{{LSL ConstTB|PRIM_CAST_SHADOWS|integer|24|b=[ <s>|e=</s> ]|s1=id="PRIM_CAST_SHADOWS"}}
{{!}} colspan="2" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="6" {{!}} '''DEPRECATED''': Shadow casting for the primitive
{{!}}-
{{#ifeq:{{{1|set}}}|set|
{{!}} rowspan="8" id="PRIM_TYPE_LEGACY"{{!}} [ 1 ] <s>{{LSL Const|PRIM_TYPE_LEGACY|integer|1|nolink=*|c=The value is real, the name is not, merely a placeholder.}}</s>{{Footnote|handle=ptl}}
{{!}} rowspan="8" {{!}} {{#var:value}}
{{!}} colspan="8" {{!}} [ [[integer]] {{HoverText|flag|PRIM_TYPE_* flag}}] + flag_parameters
{{!}}-
! colspan="2" {{!}} {{HoverText|flag|PRIM_TYPE_* flag}} Constants
! colspan="6" id="PRIM_TYPE_LEGACY_flag_parameters"{{!}} Flag Parameters
{{!}}-
{{LSL ConstTB|PRIM_TYPE_BOX|integer|0}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[float]] {{LSL Param|twist_end}}, [[vector]] {{LSL Param|top_size}}, [[vector]] {{LSL Param|top_shear}} ]
{{!}}-
{{LSL ConstTB|PRIM_TYPE_CYLINDER|integer|1}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[float]] {{LSL Param|twist_end}}, [[vector]] {{LSL Param|top_size}}, [[vector]] {{LSL Param|top_shear}} ]
{{!}}-
{{LSL ConstTB|PRIM_TYPE_PRISM|integer|2}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[float]] {{LSL Param|twist_end}}, [[vector]] {{LSL Param|top_size}}, [[vector]] {{LSL Param|top_shear}} ]
{{!}}-
{{LSL ConstTB|PRIM_TYPE_SPHERE|integer|3}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[vector]] {{LSL Param|cut|dimple}} ]
{{!}}-
{{LSL ConstTB|PRIM_TYPE_TORUS|integer|4}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[float]] {{LSL Param|twist_end}}, [[float]] {{LSL Param|hole_size_y}}, [[vector]] {{LSL Param|top_shear}}, [[vector]] {{LSL Param|cut|advanced_cut}} ]
{{!}}-
{{LSL ConstTB|PRIM_TYPE_TUBE|integer|5}}
{{!}} colspan="6" {{!}} [ [[vector]] {{LSL Param|cut}}, [[float]] {{LSL Param|hollow}}, [[float]] {{LSL Param|twist_end}}, [[float]] {{LSL Param|topshear_x}} ]
}}
{{!}}-
{{LSL ConstTB|PRIM_ALLOW_UNSIT|integer|39|b=[ |e= ]|s1=id="PRIM_ALLOW_UNSIT"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_SCRIPTED_SIT_ONLY|integer|40|b=[ |e= ]|s1=id="PRIM_SCRIPTED_SIT_ONLY"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} ]
{{!}} colspan="3" {{!}}
{{!}}-
{{LSL ConstTB|PRIM_SIT_TARGET|integer|41|b=[ |e= ]|s1=id="PRIM_SIT_TARGET"}}
{{!}} colspan="5" {{!}} [ [[integer]] {{LSL Param|boolean}} , [[vector]] {{LSL Param|pos|offset}}, [[rotation]] {{LSL Param|rot}} ]
{{!}} colspan="3" {{!}} Sit target, [[llSitTarget]]. The position can be [[ZERO_VECTOR]].
{{!}}-
{{!}}}
<noinclude>
<div id="box">
== Caveats ==
<div style="padding: 0.5em;">
{{#var:caveats}}
</div></div>
</noinclude>

Limits

2021-01-12T14:31:14Z

Sei Lisa: /* Animation */

<noinclude>{{KBmaster}}</noinclude>
== Summary ==
{{RightToc}}
The Second Life Viewer and simulators have a division of labor, keeping track of the data that makes Second Life run. The Viewer's job is to:

* Handle locations of objects.
* Get velocities and other physics information, and does simple physics to keep track of what is moving where.

The simulator's job is to:

* Run the physics engine.
* Detect collisions.
* Keep track of where everything is
* Send locations of content to the Viewer along with updates when certain changes occur.

Limits are necessary for all of these components to work together. The list below outlines many of the '''Second Life numerical limits that affect your inworld experience'''. Some of these will likely change over time, so if you spot something incorrect/outdated, please take a moment to update it.

{{KBcaution|1=The scope of this page is focused on Linden Lab's official Viewers, keeping in mind [[Third_Party_Viewer_Directory|3rd-party viewers may differ]]. Cite sources and provide substantiation for limits that aren't provided by Linden Lab. Also, unconfirmed speculation [[Talk:Limits|goes on this discussion page]]. Don't add data without a hard limit, and don't add obscure trivia that doesn't practically affect the general inworld experience.|width=80%}}

== [[Avatar]] ==

* '''Max. # of attachments''' - 38 combined [[HUD]] or body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Edit My Outfit'''.
** With the formal introduction of [[multiple attachments|multiple attachments to a single point]] in Viewer 2.4, you can attach up to 38 total objects, and they can all be attached to a single point.
** With the introduction of the Bento armature, there are 47 attachment points available.
** With the introduction of Animesh, there is a limit of 1 Animesh attachment, 2 if the resident has premium.
* '''Max. # of clothing layers''' - 60 including alpha, tattoo, shoe base, physics, socks, gloves, undershirt, underpants, shirt, pants, jacket, skirt
** On viewers before Second Life Release 3.7.29.301305, the potential total was still 60, but limited to 5 items of each type.
** In any case, only one each of shape, skin, eyes and hair base may be worn. These 4 basic body parts are in addition to the 60 clothing layers.
* '''Max Clothing Texture''' - 1024x1024 px (except 128x128 px for eyes) - Server Side Appearance (and legacy baking on outside grids) will downsize larger textures.
* '''Max. unassisted fly height''' - Stable hover at current ground elevation ''plus'' 5020m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Traditionally, most women's shoes were designed for a size 0 (zero) foot. Men's generally scale up to 14. Newer items (mesh and some sculpted) replace the system feet or conform to the avatar's shape, so adjustments may be necessary.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.

* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).

* '''Max. length of {{LSLGC|Username}}''' - All lower case and a maximum of 63 including the '.'(eg; firstname.lastname)
**Older account user names are a combination of the First and last name in lower case separated by a period(.)(eg; lilmix.pixelmaid)
**Modern user names are a single name(no period)(eg; john1234) - '''Max.''' length is 31 characters
**The {{LSLGC|Legacy Name}}s for modern user names always shows Resident as the last name. So the Max is 40 characters in total for a new avatar's legacy name(including the space and last name 'Resident')
*'''Min. length of [[Display_Names]]''' - At least one script character
*'''Max. length of Display Names''' - 31 characters
**Display Names can include most Unicode script characters, spaces, and some punctuation.

* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed''' - 10 teleports per 15 seconds, since SL server 1.27.1

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Length of animation
| n/a
| {{no|60.0 seconds}}
| Limited by length or Size, whichever is reached first
| n/a
|-
||Size of Animation
| n/a
| {{no|250k bytes}}
| Limited by length or Size, whichever is reached first. Size is after conversion to SL [[Internal Animation Format|internal animaton format]], not BVH source which can be much larger.
| n/a
|-
||Distance an Animation Can Travel
| n/a
| {{no|10 meters}}
| n/a
| n/a

|-
||animation priority
| {{no|0}}
| {{no|4, with custom tools 6}}
| n/a
| [[Animation_Priority]]
|-
||Number of unique joints per animation
| n/a
| {{no|216}}
| n/a
| n/a
|-
||Number of simultaneous animations playing
| n/a
| {{no|30}}
| n/a
| n/a
|}

== [http://community.secondlife.com/t5/English-Knowledge-Base/Build-Tools/ta-p/700039 Building] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Prim]] dimensions
| {{no|<0.01, 0.01, 0.01>}}
| {{no|<64.0, 64.0, 64.0>}}
| Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770
| [[llSetScale]], [[PRIM_SIZE]] and [[Megaprim]]
|-
||Number of prims in a linkset
| n/a
| {{no|256 prims}}
| Used to be 255 prior to Second Life Server version 1.26
| n/a
|-
||Linking distance
| n/a
| {{no|[[Linkability_Rules]]}}
| n/a
| n/a
|-
||[[Mesh/Mesh_physics#Physics_Resource_Cost|Physics cost]] for a physical object
| n/a
| {{no|32.0}}
||Additional notes:
* If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
* On server versions 1.38 and below, each sitting avatar counted as 1 prim. From 1.40.2 the limit is only on actual prims.
| [[OBJECT_PHYSICS_COST]]
|-
||Build or rez height
| n/a
| {{no|4096.0 meters}}
| 768.0 meters for Viewers prior to version 1.20
| n/a
|-
||Prim name length
| n/a
| {{no|63 bytes UTF-8 [[String|string]]}}
| same limit for {{LSLGC|Avatar/Name|avatar names}}, although the character set for avatar names is significantly limited.
| n/a
|-
||Prim description length
| n/a
| {{no|127 bytes UTF-8 [[String|string]]}}
| n/a
| n/a
|-
||Temporary prims' lifetime
| n/a
| {{no|up to around 60 seconds}}
| depends upon when the next garbage collector cycle is
| n/a
|-
||Number of temporary prims
| n/a
| {{no|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| n/a
| n/a
|-
||Length of hovertext
| n/a
| {{no|254 bytes UTF-8 [[String|string]]}}
| n/a
| [[llSetText]] and [[PRIM_TEXT]]
|}

== [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/ Lighting] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of projectors rendered at full detail
| n/a
| 2
| Only the 2 projectors closest to an object will cause it to cast shadows.
| [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/#Projectors Knowledge Base > Lighting > Projectors]

|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Whisper distance
| n/a
| {{no|10 meters}}
| <code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Chat distance
| n/a
| {{no|20 meters}}
| text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered. /whisper and /shout ''can'' be used in the "Replace with" field.
| n/a
|-
||Shout distance
| n/a
| {{no|100 meters}}
| <code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Length of a chat message and whether or not it is truncated
| {{no|1 byte or single-byte character}}
| {{no|1024 bytes or single-byte characters}}
| Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1023 bytes or single-byte characters.
The viewer-to-server communication on ''negative'' channels is truncated to 254 bytes, and on ''positive'' channels, to 1023 bytes. These limits do not affect communication between scripts.
| [[llInstantMessage]]
|-
||Maximum events
| n/a
| {{no|64 events}}
| Events are stored in a 64 bit bitmap. Events happening when the bitmap is full, will get discarded.
| n/a
|-
||Number of offline messages
| n/a
| {{no|Capped at 15 messages, unless the account has a Premium Subscription, in which case the cap raises to 80 messages.}}
| Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped. Note: If autoAcceptNewInventory (debug setting) is set to TRUE (the default is FALSE), then all inventory offers, even above 15 (or 80 in the case of Premium members), go directly to inventory and do not count against the cap on offline messages.
| [[IM]] - [https://community.secondlife.com/blogs/entry/2559-group-limits-update-no-changes-for-basic-members/ Blog Post]
|-
||Length of a properly delivered email reply to an [[IM]]
| n/a
| {{no|1023 bytes or single-byte characters}}
| n/a
| n/a
|-
||Time after which a reply to an [[IM]] can be sent via email.
| {{no|when receiving the IM via email.}}
| {{no|5 days after receiving the offline IM via email.}}
| n/a
| [https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]
|-
||Time period for which [[IM|IMs]] are stored within Second Life.
| n/a
| {{no|31 days after receiving the [[IM]]}}
| [[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]
| n/a
|-
||Number of [[IM|IMs]] sent by an object within an hour
| n/a
| {{no|5000 per hour}}
| n/a
| n/a
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Shortcut key mappings
| n/a
| {{no|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| n/a
| [[All_keyboard_shortcut_keys]] and [http://community.secondlife.com/t5/English-Knowledge-Base/Keyboard-shortcuts/ta-p/1086557 the knowledge base]
|-
||Chat step length
| n/a
| {{no|127 bytes or single-byte characters}}
| n/a
| n/a
|-
||Wait time
| n/a
| {{no|3600 seconds (which is one hour)}}
| n/a
| n/a
|-
| Maximum steps data
| n/a
| {{no|1000 bytes}} of packed data; saving with more data returns the message "Gesture save failed. This gesture has too many steps. Try removing some steps, then save again." Shorter text, for example, will allow more steps.
| n/a
| n/a
|-
||Length of included assets
| n/a
| see sections for [[#Animation|animation]], [[#Sound|sound]]
| n/a
| n/a
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42 for Basic accounts, 70 for Premium accounts.
** After downgrading from a Premium account to a Basic account, you may not join any new groups until you are a member of fewer than 42 groups.
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Minimum number of members in a group:''' 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Maximum number of roles allowed in a group:''' 10 (including "Owners" and "Everyone", which cannot be deleted)
* '''Maximum Group Name:''' 35 single-byte characters.
* '''Maximum Group Title:''' 20 single-byte characters.
* '''Maximum Length of a Group Notice:''' 512 single-byte characters.
* '''Maximum Age of a Group Notice:''' 14 days.

== [[Inventory]] ==

* '''Maximum number of inventory items that can be sent in a folder:''' 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references.
* '''Maximum number of inventory items that can be contained in a prim:''' 10,000
* '''Maximum characters in an inventory item name:''' 63
* '''Maximum notecard line:''' None, but scripts can only read the first 255 bytes.
* '''Maximum notecard size:''' 65,536 bytes

* '''Number of items in the Library:''' 3,500 as of 2019-08-10
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.
* '''Maximum number of inventory items displayed in a single inventory folder:''' Several thousand. 
** This was discussed during [http://wiki.secondlife.com/wiki/Simulator_User_Group/Transcripts/2011.03.08] "the folder will load up to the limit number of items, and remaining ones won't show up in the viewer. you still own them, they aren't lost, but they will be hidden until the folder size is reduced."
** There is no specified limit for total avatar inventory, very large folders can be split.
** There was discussion in the Third Party Developers' UG (4/10/2015) meeting about new inventory and login problems from having large numbers of items in a single folder. AISv3 ''removed'' server-side limits on the number of items in a folder. Flat inventories are bad. No one is certain at what number of items in a folder cause a login problem. The fix is to clear the inventory cache (not the viewer cache) and log into a deserted, empty region then move inventory items into folders and sub-folders. - The problem appears at different a number of items depending on your computer and connection speed. Hopefully being on an empty region will give one enough edge to get logged in and do some corrective work before being dropped. If not, you will need to contact support for help. They will divide large folders into smaller groups so you can log in.

== [[Land]] ==

* '''Maximum [[Land#Parcel|parcel]] size:''' 65,536 meters²
** Covering a whole region, or square on the World Map.
* '''Minimum parcel size:''' 16 meters²
* '''Maximum parcel name length:''' 63 single-byte characters
* '''Maximum parcel description length:''' 255 characters
* '''Region name length:''' Linden Concierge policy states a minimum of 3 characters, and a maximum of 25 characters (including spaces). See [[Linden Lab Official:Guidelines for Private Region Naming|Guidelines for Private Region Naming]]. However, the technical maximum limit is 35 characters, and exceptions to the concierge policy do exist (e.g [http://maps.secondlife.com/secondlife/Sandbox%20-%20Weapons%20testing%20%28no%20damag/128/128/2 Sandbox - Weapons testing (no damag] and [http://slurl.com/secondlife/X/128/128/24 X])
* '''Ban line height for "no entry" or "pay to access"''' (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation ''plus'' 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is '''explicitly banned by name''', the height is the parcel's ground elevation ''plus'' 5000 meters. On current viewers this is visible to the full extent.
* '''Maximum prims in a [[Land#Region|region]]:'''
** "Mainland / Full Region" and "Linden Homes / Full Region": 22,500
** Full Regions in private estates: 20,000 with an [https://community.secondlife.com/t5/Featured-News/Upgrade-Your-Full-Private-Region-to-30-000-Land-Impact-Today/ba-p/3086162 option for 30,000]
** Homestead: 5,000
** Openspace : 1,000
:: To check a region's capacity, use <tt>[[llGetEnv]]("region_max_prims")</tt>.
::''(Region types are as found in the General tab of World > About Land, or returned by ''<tt>llGetEnv("region_product_name")</tt>'')''
* '''Maximum auto return value''': Besides "0" (which means ''never''), {{HoverText|999,999|Almost 23 months}} minutes is the highest auto return value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by 4 meters (+/-).
** Some mainland cannot be terraformed, including: Bay City regions, Boardman, Brown, De Haro, Horizons, Kama City regions, Nautilus City regions, Nova Albion regions, and Shermerville regions.
** [http://community.secondlife.com/t5/English-Knowledge-Base/Linden-Homes/ta-p/700103 Linden Homes] do not allow terraforming.
** A few, very old mainland Regions like Da Boom have a terraform range of 40 meters (+/-).
** Estate (private island) terraformability is settable to a maximum of 100 meters (+/-) by the estate owner or managers.
* '''Maximum water height:''' 100 meters using inworld controls, 255 meters by using a *.raw file upload.
** Region water height is usually 20 meters, and adjacent regions should have the same water height, or else they will look discontinuous.
* '''Maximum terrain height:''' 255 meters using inworld controls (mainland limit), 510 meters by using a *.raw file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 15 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Maximum number of agents'''
** Full region: 100 (Typically set to 40 on mainland, 55 on Linden Homes regions, but this does vary. Some meeting areas have this set to 60 and higher.)
*** Recent server performance improvements make regions with 60 agents in them perform quite well.
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Freeze Time:''' Land owners can [[freeze]] other Residents for up to 30 seconds. Members of land owning groups can also be granted this ability.
* '''Minimum parcel that can be listed in Places or All search:''' 144 meters² 
* '''Minimum parcel that can be listed in Events:''' 512 meters²
* '''Maximum altitude for event listings:''' 768 meters ({{JIRA|WEB-814}})
* '''Maximum heights that objects can be seen on the [[World Map]]:''' 400.005m

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of vertices
| n/a
| {{no|65536 vertices per LOD for each [[mesh]] - See [[Talk:Limits#Mesh_Limits|discussion page]]}}
| n/a
| n/a
|-
||COLLADA file size
| n/a
| {{no|Maximum mesh asset size after compression is 8 MB, roughly equivalent to a 256 MB Raw COLLADA file.}}
| n/a
| n/a
|-
||Bone influence weights per vertex
| n/a
| {{no|4}}
| n/a
| n/a
|-
||Number of materials per mesh
| n/a
| {{no|8}}
| n/a
| n/a
|-
||Number of materials per face
| n/a
| {{no|1}}
| n/a
| n/a
|-
||Physics weight for a vehicle
| n/a
| {{no|32.0}}
| n/a
| n/a
|-
||Maximum number of triangles for Animesh
| n/a
| {{no|10000}}
| n/a
| n/a
|}

===User Found Temporary Mesh limits:===
''Because of an apparent bug in the importer stay within these limits.''
* 174,752 triangles, beyond which additional triangles will appear as holes.
* The 64k vertices per material is pre-empted by a limit of 21,844 triangles per material, which is presently reported as {{Jira|BUG-1001}}. (4/2014 - See [[Talk:Limits#Mesh_Limits|discussion page]])

:: The import process will continue making new materials beyond 8 x 21,844 (=174,752) triangles, but the extra triangles then get dropped by the limitation to 8 materials, causing holes in the resulting object. Over the 21,844 triangle limit, the vertex count will start to climb steeply, even with smooth shading, because the materials get highly interspersed. So the same vertices have to appear in multiple material lists. So the moral of the story is to stay below 21,844 triangles per material, for now, if you want to avoid some unexpected effects.

::Since viewer release 3.8.4, processing of meshes in the Collada file that have faces assigned to more than 8 materials has changed. Instead of simply dropping the extra material faces, the uploader now creates a new object to accommodate them. The result is that the single mesh is divided into multiple objects (prims) in a linkset. Thus the limitation to 8 materials is removed as far as input is concerned, but still applies to each of the resulting linked objects actually uploaded. As a consequence it is now possible to upload a mesh with more than 174,752 triangles, although it will be divided into multiple objects.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.

== Navigation ==

[[File:Max Alt.jpg|thumb|right|435px|'''Height counter error above 2147483647 meters''']]
* '''Absolute height limit:''' [http://en.wikipedia.org/wiki/2147483647#2147483647_in_computing 2147483647] = 231 − 1 meters, which causes the altitude counter to roll over. Altitudes well below this cause graphics errors probably due to limited floating point number precision.
* '''Highest z-value of an [[SLurl]], that will still teleport you to a positive altitude:''' 4096
** This used to be much higher, but is clamped in late model viewers.

== [[Profile]] ==

Each 7-bit ASCII character is encoded in one byte. International characters might need more bytes. When pasting text instead of typing, you can get in one byte more into each of the below.

* '''2nd Life tab's About field''' - 510 bytes
* '''Picks tab''' - 10 picks with 1022 bytes each
* '''1st Life tab's Info field''' - 253 bytes
* '''Classified tab''' - 100 listings with x bytes each
* '''My Notes''' - 1022 bytes

== Performance ==

* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via [[Advanced]] menu > Performance Tools > Lag Meter, or for more advanced usage, see Advanced > Performance Tools > Statistics Bar.
* '''Avatar Rendering Cost scores''' - [[Avatar Rendering Cost|Learn all about it!]]

== [[Scripting]] == 

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls will keep running when you fly down or enter a no-script parcel. (If scripts are disabled in the region debug panel, they will not run at any height.)
* '''Maximum height where scripts can run''' - none, as long as the object remains rezzed or attached.
* '''Maximum script source code size''' - 65536 single byte characters (that's a viewer limit and can be changed in the config file 'panel_script_ed.xml').
* '''Maximum script memory size (LSO)''' - 16384 bytes.
* '''Maximum script memory size (Mono)''' - 65536 bytes (the maximum memory available to Mono scripts can be constrained via [[llSetMemoryLimit]]).
* '''Maximum active [[llListen|listeners]] per script''' - 65.
** '''Usable channel for each listener''' - ''min.'' -2147483648, ''max.'' 2147483647, including the following special channels: [[PUBLIC_CHANNEL]] ''and'' [[DEBUG_CHANNEL]].
* For specific scripting limits, look up calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Sound length
| n/a
| {{no|10.00000 seconds (441,000 samples)}}
| 441,001 samples (10.00002 seconds) won't work. You're advised to cut longer sounds into 9.9-second-pieces.
| n/a
|}

== [[Textures]] ==
* '''[http://en.wikipedia.org/wiki/Aspect_ratio Aspect ratios]''' of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000:

=== Second Life Viewer 3.6 ===

* '''Search > Classifieds thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (159×120 pixels)
* '''Search > Classifieds expanded > More Info''' - native aspect ratio
* '''Search > Destination Guide thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Destination Guide expanded''' - ~4:3 (159×120 pixels)
* '''Search > People''' - 1:1 (100×100 pixels)
* '''Search > Places expanded''' ~4:3 (159×120 pixels)
* '''Place Profile''' - ~3:2 (290×197 pixels)
* '''About Land > Options tab''' - ~4:3 (195×150 pixels)
* '''Profile > Picture''' - native aspect ratio; thumbnail cropped to 72×72 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Real world picture''' - native aspect ratio; thumbnail cropped to 45×45 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Picks thumbnail''' - 4:3 (60×45 pixels)
* '''Profile > Pick expanded''' - 4:3 (320×240 pixels)

=== 1.x Series Viewers ===
(official Viewer up to 1.23.5, still used by some [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pi×els)
* '''Search > Places and Classified tabs''' - ~7:5 (398×282 pixels)
* '''Search > Land tab''' - ~7:5 (358×252 pixels)
* '''Profile > 2nd Life tab''' - ~4:3 (178×133 pixels)
* '''Profile > Picks tab''' - 16:9 (288×162 pixels)
* '''Profile > 1st Life tab''' - 1:1 (133×133 pixels)
* '''Profile > Classifieds tab''' - ~3:2 (206×137 pixels)
* '''Profile > Web tab''' - 1:1 (400×400 pixels)
** A scrollbar uses 15 pixels on the right-hand side.
* '''About Land > Options tab''' - ~3:2 (178×117 pixels)
* '''Group Information > General tab's "Group Insignia"''' - 1:1 (126×126 pixels)
** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.
** [[Texture_aspect_ratios|Learn how to get correct texture aspect ratios when editing images.]]

=== All Viewers ===

* '''Maximum texture size''' - 1024×1024 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** Some textures inworld have a resolution as high as 2048×2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load.
** Where large textures are being forced by import to only 512×512, lower your ...> Preferences >...> UI Size under 1.0, to increase import size to the max 1024×1024.

* '''Minimum texture size''' - 4×4 pixels
** This means that there are nine possible image dimensions: 4, 8, 16, 32, 64, 128, 256, 512, and 1024 pixels, either horizontal or vertical.

[[Category:Creation]] [[Category:Tutorials]] [[Category:Lists]]

=== Notes ===
In general 1 byte is enough to contain one character.

User:Sei Lisa

2020-09-13T16:50:44Z

Sei Lisa: Add regex engine, fix minor stuff

Scripter. SL is currently my job. I take custom orders.

I am the maintainer of the following tools for scripters:

* [http://lsl.blacktulip-virtual.com/lsl-pyoptimizer/ LSL-PyOptimizer], a tool written in Python that optimizes scripts for size.
* [http://lsl.blacktulip-virtual.com/lslcalc/lslcalc.php LSL Calculator] calculates expressions using LSL syntax. It is able to perform calculations with all LSL types.
* [https://bitbucket.org/Sei_Lisa/kwdb kwdb], a LSL keywords database that can generate syntax for various editors and tools, for SL and OpenSim.
* [http://lsl.blacktulip-virtual.com/lsl/ Unofficial LSL Reference Wiki], an alternative wiki for LSL reference. Work-in-progress. Sort of stalled at present.
* [http://lsl.blacktulip-virtual.com/lsl/articles/regex Regular expression engine] for LSL.

I am not the maintainer of this one, but kind of a "de-facto maintainer":

* [https://github.com/makopo/lslint lslint], a tool to check your script for errors and common mistakes, catching them all in one go instead of stopping at the first one. I was told there was a plug-in for SublimeText but it seems to no longer be usable.

My store in Marketplace is [https://marketplace.secondlife.com/stores/92293 <SeiS>].

LlSetClickAction

2020-06-12T18:47:25Z

Sei Lisa: Implemented now - Undo revision 1209352 by XylaAodha Resident (talk)

{{LSL_Function
|inject-2={{Issues/VWR-640}}{{Issues/VWR-10829}}
|func_id=333|func_sleep=0.0|func_energy=10.0
|func=llSetClickAction
|p1_type=integer|p1_subtype=click_action|p1_name=action|p1_desc=CLICK_ACTION_* flag
|func_desc=Sets the action performed when a prim is clicked upon (aka [[click action]]).
|func_footnote=When the cursor hovers over the prim, its image changes to reflect the action.
|caveats= *When set in the root of an object the chosen CLICK_ACTION_* will be that for the children also even if they have their own [[llSetClickAction]] set (it will be over-ridden). However (in the case of [[touch]] for example) if the CLICK_ACTION_* is set in the root but not at all in the children (including not having [[touch]] [[event]] [[script]]s in them (this creates a default CLICK_ACTION_TOUCH)) the effect of the roots CLICK_ACTION_* is not ''seen'' but the CLICK_ACTION_* is ''used'' on clicking. To both use '''and see''' the correct cursor the CLICK_ACTION_* flags must match in the children and root.
*If [[llSetClickAction]] is [[CLICK_ACTION_PAY]] then you must have a [[money]] event, or it will revert to [[CLICK_ACTION_NONE]].
*While this function works or attached objects (click action can be changed), the configured click action of an attachment is ignored by the viewer. The viewer always behaves as though an attached object has [[CLICK_ACTION_TOUCH]] set.
|examples={{{!}} width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''make sitting easier'''
! '''make unpaking for next owner easier'''
! '''make buying for customers easier'''
{{!}}- valign="bottom"
{{!!}}<source lang="lsl2">
default
{
state_entry()
{
llSetClickAction(CLICK_ACTION_SIT);
llRemoveInventory(llGetScriptName());
}
}
</source>
{{!!}}
<source lang="lsl2">
default
{
state_entry()
{
llSetClickAction(CLICK_ACTION_OPEN);
llRemoveInventory(llGetScriptName());
}
}
</source>
{{!!}}
<source lang="lsl2">
// remember you'll have to set a price
// in the general tab of the edit window
// for your object before using this script

default
{
state_entry()
{
llSetClickAction(CLICK_ACTION_BUY);
llRemoveInventory(llGetScriptName());
}
}
</source>
{{!}}}
<source lang="lsl2">
// simple tipjar

default
{
state_entry()
{
llSetClickAction(CLICK_ACTION_BUY);

// enabled edit field to put own amount, all quick-pay-buttons hidden
llSetPayPrice(PAY_DEFAULT, [PAY_HIDE, PAY_HIDE, PAY_HIDE, PAY_HIDE]);
}

money(key id, integer amount)
{
string name = llKey2Name(id);

llInstantMessage(id, "Thank you for the tip, " + name + "!");
}
}
</source>

<source lang="lsl2">
//Sit Only with Permission

list gAvWhitelist = ["953d10f1-44ce-462a-8bc1-f634333ee031","599dce91-a2b8-48c5-b96d-54965433022b"];

default
{
state_entry()
{
llSitTarget(<0.0,0.0,0.5>,ZERO_ROTATION);
}

changed(integer change)
{
if(change & CHANGED_LINK)
{
list Properties = llGetObjectDetails(llGetKey(),[OBJECT_CLICK_ACTION]);
integer Click = llList2Integer(Properties,0);
key Av = llAvatarOnSitTarget();
if ((Av != NULL_KEY) && (!Click))
{
llSay(0,"Please click first for permission to sit.");
llUnSit(Av);
}
}
}
touch_start(integer total_number)
{
list Properties = llGetObjectDetails(llGetKey(),[OBJECT_CLICK_ACTION]);
integer Click = llList2Integer(Properties,0);
if (!Click && (~llListFindList(gAvWhitelist,[(string)llDetectedKey(0)])) )
{
llSetClickAction(CLICK_ACTION_SIT);
llSetTimerEvent(10.0);
llSay(0,"Please take a seat.");
}
else
{
llSetClickAction(CLICK_ACTION_TOUCH);
if (llAvatarOnSitTarget() != NULL_KEY)
{
llSay(0,"Good bye!");
}
else
{
llSay(0,"Sorry. You are not allowed to sit here.");
}
llUnSit(llDetectedKey(0));
}
}

timer()
{
llSetTimerEvent(0.0);
llSetClickAction(CLICK_ACTION_TOUCH);
}
}
</source>

|spec
|constants=<div id="box">
==Constants==
<div style="padding: 0.5em;">
{{{!}} class="sortable" {{Prettytable}}
{{!}}- {{Hl2}}
! {{!}} Flag
! title="Value" {{!}}
! class="unsortable" {{!}} Description
! class="unsortable" {{!}} Cursor
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_NONE|integer|0|c=Performs the default action: when the prim is touched, touch events are triggered}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_TOUCH|integer|0|c=When the prim is touched, touch events are triggered}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_SIT|integer|1|c=When the prim is touched, the avatar sits upon it}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[File:SitActionCursor.png‎]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_BUY|integer|2|c=When the prim is touched, the buy dialog is opened}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[File:SaleOneclickCursor.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_PAY|integer|3|c=When the prim is touched, the pay dialog is opened}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[File:SaleOneclickCursor.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_OPEN|integer|4|c=When the prim is touched, the object inventory dialog is opened}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[File:OpenOneclickCursor.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_PLAY|integer|5|c=Play or pause parcel media on touch}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[Image:Toolplay.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_OPEN_MEDIA|integer|6|c=Play parcel media on touch, no pause}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}[[Image:Toolmediaopen.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_ZOOM|integer|7|c=Zoom}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}} ([[Viewer_2_Help|Viewer 2]])
{{!}}[[Image:Toolzoom.png]]
{{!}}-
{{!}}{{LSL Const|CLICK_ACTION_DISABLED|integer|8|c=No click action. No touches detected or passed.}}
{{!}}{{#var:value}}
{{!}}{{#var:comment}}
{{!}}
{{!}}}
</div></div>
|signature=
{{LSL Const/Signature|CLICK_ACTION_ZOOM|integer|7|c=Zoom}}
|helpers
|also_functions={{LSL DefineRow||[[llPassTouches]]}}
|also_tests
|also_events=
{{LSL DefineRow||[[touch_start]]}}
{{LSL DefineRow||[[touch]]}}
{{LSL DefineRow||[[touch_end]]}}
|also_articles={{LSL DefineRow||{{LSLGC|Detected}}}}

|history=
* Introduced in SL Client 1.19.1(0)
* [[CLICK_ACTION_ZOOM]] added in SL Server 1.32 and [[Viewer_2_Help|Viewer 2]]
|cat1=Prim
|cat2=Touch
|cat3=Sit
|cat4=Money
|cat5=Media
|cat6=Effects
|cat7=Click Action
|cat8
}}

Internal Textures

2019-10-03T17:59:05Z

Sei Lisa: typo

__NOTOC__ {{Multi-lang|category=LSL}}{{LSL Header}}

Various Textures built into the viewer

{| class="sortable" {{prettytable}}
|-{{Hl2}}
!Texture Name
![[UUID]]
!Description
|-
|[[TEXTURE_DEFAULT]]
|89556747-24cb-43ed-920b-47caed15465f
|Default plywood texture
|-
|[[TEXTURE_PLYWOOD]]
|89556747-24cb-43ed-920b-47caed15465f
|Default plywood texture
|-
|[[TEXTURE_BLANK]]
|5748decc-f629-461c-9a36-a35a221fe21f
|Blank, all white texture in the Texture window
|-
|[[TEXTURE_TRANSPARENT]]
|8dcd4a48-2d37-4909-9f78-f7a9eb4ef903
|*Default Transparent Texture
|-
|[[TEXTURE_MEDIA]]
|8b5fec65-8d8d-9dc5-cda8-8fdf2716e361
|Also triggers targeting
|-
|[[Invisiprim]] 1
|38b86f85-2575-52a9-a531-23108d8da837
|Hides alpha textures behind it
|-
|[[Invisiprim]] 2
|e97cf410-8e61-7005-ec06-629eba4cd1fb
|Hides alpha textures behind it
|-
|IMG_USE_BAKED_HEAD
|5a9f4a74-30f2-821c-b88d-70499d3e7183
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_UPPER
|ae2de45c-d252-50b8-5c6e-19f39ce79317
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_LOWER
|24daea5f-0539-cfcf-047f-fbc40b2786ba
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_EYES
|52cc6bb6-2ee5-e632-d3ad-50197b1dcb8a
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_SKIRT
|43529ce8-7faa-ad92-165a-bc4078371687
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_HAIR
|09aac1fb-6bce-0bee-7d44-caac6dbb6c63
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_LEFTARM
|ff62763f-d60a-9855-890b-0c96f8f8cd98
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_LEFTLEG
|8e915e25-31d1-cc95-ae08-d58a47488251
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_AUX1
|9742065b-19b5-297c-858a-29711d539043
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_AUX2
|03642e83-2bd1-4eb9-34b4-4c47ed586d2d
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|-
|IMG_USE_BAKED_AUX3
|edd51b77-fc10-ce7a-4b3d-011dfc349e4f
|Sets face to use specified channel for [https://community.secondlife.com/knowledgebase/english/bakes-on-mesh-r1512/ Bakes on Mesh]
|}

== Related Articles ==

* [[llSetTexture]]

[[Category:LSL Texture]]

LlSetVelocity

2019-09-12T23:43:05Z

Sei Lisa: Rename argument, removing confusing references to force

{{LSL_Function
|inject-2={{LSL_Function/velocity|velocity|local=local}}{{LSL_Function/physical}}
|func=llSetVelocity
|func_id=???|func_sleep=0.0|func_energy=???
|p1_type=vector|p1_name=velocity
|p2_type=integer|p2_subtype=boolean|p2_name=local
|func_footnote=Instantaneous velocity not dependent on object energy or mass.
|func_desc=Applies velocity to object
|return_text|spec
|caveats=
|examples=
|helpers
|also_functions=
{{LSL DefineRow||[[llSetAngularVelocity]]|}}
{{LSL DefineRow||[[llApplyImpulse]]}}
|notes
|cat1=Physics
|cat2=Movement
|cat3
|cat4
|history = Date of Release [[ Release_Notes/Second_Life_Server/11#11.08.10.238207 | 10/08/2011 ]]
}}

LlJsonSetValue

2019-06-20T09:56:46Z

Sei Lisa: Undo misleading caveat

{{LSL Function
|inject-2={{Issues/BUG-3692}}
|inject-3={{LSL_Function/negative index|false|specifiers|nc=*}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJsonSetValue
|return_type=string
|p1_type=string|p1_name=json|p1_desc=source JSON data
|p2_type=list|p2_name=specifiers|p2_desc=location of the of the value to be added, updated or deleted.
|p3_type=string|p3_name=value|p3_desc=new value or [[JSON_DELETE]] flag.|p3_hover=new value or JSON_DELETE flag.
|func_footnote
|func_desc=Returns, if successful, a new [http://json.org JSON] text ''string'' which is {{LSLPT|json}} with the value indicated by the {{LSLPT|specifiers}} list set to {{LSLPT|value}}.

If unsuccessful (usually because of specifying an out of range array index) it returns [[JSON_INVALID]].

An "out of range array index" is defined to be any Integer {{LSLPT|specifiers}} greater than the length of an existing array at that level within the Json text or greater than 0 (zero) at a level an array doesn't exist.

A special {{LSLPT|specifiers}}, [[JSON_APPEND]], is accepted which appends the {{LSLPT|value}} to the end of the array at the {{LSLPT|specifiers}} level. Care should be taken- if that level is not an array, the existing Value there will be overwritten and replaced with an array containing {{LSLPT|value}} at it's first (0) index.

Contrary to [[list]]s and [[string]]s, negative indexing of Json arrays is '''not''' supported.

If an existing "Key" is {{LSLPT|specifiers}} at that level, its Value will be overwritten by {{LSLPT|value}} unless {{LSLPT|value}} is the magic value [[JSON_DELETE]]. If a value does not exist at {{LSLPT|specifiers}}, a new Key:Value pair will be formed within the Json object.

To delete an existing value at {{LSLPT|specifiers}}, use [[JSON_DELETE]] as the {{LSLPT|value}}. Note it will not prune empty objects or arrays at higher levels.

If {{LSLPT|value}} is [[JSON_TRUE]], [[JSON_FALSE]] or [[JSON_NULL]], the Value set will be the bare words 'true', 'false' or 'null', respectively, at the {{LSLPT|specifiers}} location within {{LSLPT|json}}.
|return_text=
|spec=See [[Json_usage_in_LSL]]
|constants
|examples=
<source lang="lsl2">
string TEST_STRING_JSON;

init()
{
TEST_STRING_JSON = "[9,\"<1,1,1>\",false,{\"A\":8,\"Z\":9}]";

// [9,"<1,1,1>",false,{"A":8,"Z":9}]
say("Original TEST_STRING_JSON: " + TEST_STRING_JSON);
}

run_json_test(string input)
{
string output;

// changing values within the json string

// change the first value in the array to 10
output = llJsonSetValue(input, [0], "10");

// [10,"<1,1,1>",false,{"A":8,"Z":9}]
say("( 1): " + output);

// change the third value in the array to 'true'
output = llJsonSetValue(input, [2], JSON_TRUE);

// [9,"<1,1,1>",true,{"A":8,"Z":9}]
say("( 2): " + output);

// change the value of "A" within the Json object to 3
output = llJsonSetValue(input, [3, "A"], "3");

// [9,"<1,1,1>",false,{"A":3,"Z":9}]
say("( 3): " + output);

// adding a value or new key-value-pair within the input

// add the value "Hello" to the end of the array
// NOTE: One cannot insert, only add to the end
output = llJsonSetValue(input, [JSON_APPEND], "Hello");

// [9,"<1,1,1>",false,{"A":8,"Z":9},"Hello"]
say("( 4): " + output);

// add the key-value-pair "B":10 to the object
output = llJsonSetValue(input, [3, "B"], "10");

// [9,"<1,1,1>",false,{"A":8,"B":10,"Z":9}]
say("( 5): " + output);

// Things to look out for when modifying Json text
// ~!~ Be careful when using this function ~!~

// out of bounds array assignment:
// defined as attempting to add a value to a position ...
// ...greater than the length of the array (which may be 0)
// JSON_APPEND is ALWAYS the preferred way to add to an array
output = llJsonSetValue(input, [5], "10");

// %EF%B7%90 (URL escaped JSON_INVALID)
say("( 6): " + llEscapeURL(output));

// BUT, this works, since it is in bounds
// (eqivalent to JSON_APPEND in this case)
output = llJsonSetValue(input, [4], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},10]
say("( 7): " + output);

// careless formation of new arrays
// ( the 4 and all subsequent 0's are all in bounds.)
output = llJsonSetValue(input, [4, 0, 0, 0], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},[[[10]]]]
say("( 8): " + output);

// overwriting an object with an array:
// ~!~ mistaken use of JSON_APPEND on an object ~!~
output = llJsonSetValue(input, [3, JSON_APPEND], "10");

// [9,"<1,1,1>",false,[10]]
say("( 9): " + output);

// careless formation of new objects
// NOTE: "Key" assignemts will NEVER result in a return of JSON_INVALID!
output = llJsonSetValue(input, [3, "W", "X"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":10},"Z":9}]
say("(10): " + output);

output = llJsonSetValue(input, [3, "W", "X", "Y"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":{"Y":10}},"Z":9}]
say("(11): " + output);

// overwriting an array with an object
output = llJsonSetValue(input, ["X"], "10");

// {"X":10}
say("(12): " + output);

// special case considerations:

// BUG-3692: (NOTE: Corrected in release 13.09.21.281328!)
// a bug where, instead of JSON_INVALID being returned, if the out of
// bounds index is at a lower level than the topmost (root) level, a
// non-compliant JSON text would be formed
output = llJsonSetValue(input, [1, 7], "Disappearing Text");

// Note the "empty" second position that resulted in the returned array
// [9,,false,{"A":8,"Z":9}]
// (But now correctly shows JSON_INVALID)
say("(13): " + output);

// though there is no way to directly delete a key-value-pair
// nor remove a value from an array,
// the use of JSON_NULL may prove adequate
output = llJsonSetValue(input, [3, "A"], JSON_NULL);

// [9,"<1,1,1>",false,{"A":null,"Z":9}]
say("(14): " + output);

// if a JSON text object has been formed with llList2Json()
// that contains one or more duplicated "Keys", (allowable
// but NOT recommended!) ANY change
// made to that object will correct the condition,
// with all but the last such "Key" being removed
output = llList2Json(JSON_OBJECT, ["A", 1, "A", 2, "A", 3, "B", 4, "B", 4]);

// both Keys "A" and "B" are duplicated
// {"A":1,"A":2,"A":3,"B":4,"B":4}
say("(15): " + output);

// only the last value of the duplications is accessable though

// 3
say("(16): " + llJsonGetValue(output, ["A"]));

// condition corrected by adding a key-value-pair...

// {"A":3,"B":4,"Z":5}
say("(17): " + llJsonSetValue(output, ["Z"], "5"));

// ... or by changing a value

// {"A":5,"B":4}
say("(18): " + llJsonSetValue(output, ["A"], "5"));
}

say(string message)
{
llOwnerSay(message);
// llRegionSayTo(llGetOwner(), PUBLIC_CHANNEL, message);
// llWhisper(PUBLIC_CHANNEL, message);
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

state_entry()
{
init();
}

touch_end(integer num_detected)
{
// copy 'TEST_STRING_JSON' from the following function call
// to the string 'input' in the function declaration
// and run a test on 'input' to not (!) modify 'TEST_STRING_JSON'
// but its copy instead
run_json_test(TEST_STRING_JSON);
}
}
</source>
|caveats=

llListReplaceList() is roughly 2,8x as fast in replacing a single value of a list than LlJsonSetValue() is to replace a single value in a json.
The length of the list/json are irrelevant here.

|helpers
|also_functions={{LSL DefineRow||[[llList2Json]]|}}
{{LSL DefineRow||[[llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|permission
|negative_index
|sort=JsonSetValue
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=JSON
|history = Date of Release [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 | 20/05/2013 ]]
}}

Talk:LlGetTime

2019-05-11T21:51:21Z

Sei Lisa:

The last edit lost the point that llGetTime returns results more precise than whole seconds, such as results that differ by more than zero yet less than one. -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 13:26, 24 October 2007 (PDT)

== svc-3293 ==

is there any special reason we're keeping a reference to this jira (which was marked expected behavior)? -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 03:50, 17 October 2011 (PDT)

:[[Template:Issues/SVC-3293]] just needed updating so that it would only show in the All Issues section. The reason for keeping dead bugs listed in the documentation is so that anyone who knew about the bug can find out from the documentation the status of the bug. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:47, 17 October 2011 (PDT)
:P.S. We should also prune them periodically but only as needed.

that makes sense, and now I know what to change to keep it in the deep notes, thanks =) -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 22:11, 19 October 2011 (PDT)

:It isn't advertised but there is a field that can force it to show in Caveats or for it to not show in Caveats. Everything always shows up in Deep Notes. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:40, 21 October 2011 (PDT)

== Conflict in descriptions ==

The page for llGetRegionTimeDilation says "affects llGetTime & llGetAndResetTime". However, the pages for llGetTime & llGetAndResetTime say that "script time [as returned by these two functions] is unaffected by time dilation. Unless I misunderstand something, these two statements conflict.
[[User:Len Lectar|Len Lectar]] 19:17, 14 November 2012 (PST)
:Honestly don't know why why it says that... one of them is wrong, someone can feel free to test which by comparing to a time/date function under heavy lag and report back. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 16:40, 10 May 2019 (PDT)

::[[llGetRegionTimeDilation]] is wrong. Only [[llSensorRepeat]] is affected. [[llSetTimerEvent]] and [[llGetTime]] aren't. [[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 14:51, 11 May 2019 (PDT)

== Accuracy loss ==
"at Best" implies that it can be worse. Suggest wording change to "x/y Sec under z days" with no qualifiers. Don't have time for an edit war over minutiae -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 16:40, 10 May 2019 (PDT)

:Agreed. I was thinking of simulator frame time on top of that, but 1/45 is anyway < 1/32 so the precision is still around 1/32. [[User:Sei Lisa|Sei Lisa]] ([[User talk:Sei Lisa|talk]]) 11:49, 11 May 2019 (PDT)