Second Life Wiki - User contributions [en]

Talk:LlRemoteLoadScriptPin

2016-07-27T18:25:03Z

Omei Qunhua: Application script relocation request

What happens when 'target' is an avatar key? That makes no sense to me: an avatar can't run a script, only an object can. {{Unsigned}}
:Sorry that was an editing mistake I made a couple days ago when I changed the template (I forgot the template defaults to avatar and prim). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:50, 17 May 2009 (UTC)

----

I have an object that spawns another object and then puts a script in it. It works until I deed the object to a group. Then I constantly get this error from the Spawner.

"Unable to add item!"

Anyone have a clue why this might happen?{{unsigned|Paradigm Brodsky|01:14, 18 February 2009}}

:When you set it to group, the next owner permissions should apply. So it can be that it is no mod and therefor doesn't accept a script.
:[[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 01:52, 18 February 2009 (UTC)

The rezzed object has transfer, modify, and copy permissions.{{unsigned|Paradigm Brodsky|04:26, 18 February 2009}}

:Hmm... How about the script you'd like to transfer. Is it copyable? I guess I'm clueless otherwise...
:You deeded the spawner to the group, right? Otherwise you might need modifiy permissions on group items and (maybe) your group activated... But I'm just guessing here, to be honest.
:[[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 04:57, 18 February 2009 (UTC)

Thanks for your help. I've got it. The script was copyable, but not transferable. You need copy and transfer permissions if it's deeded to a group. Odd thing is that transfer permission isn't required for the script if you transfer the device to another ave.{{unsigned|Paradigm Brodsky|05:22, 18 February 2009}}

:Very welcome =) I added the caveat to the article. Wouldn't have imagined that it needs this permission... Nice to know!
:Btw: You can sign your comments in the Wiki with four tildes (<nowiki>~~~~</nowiki>). They will automatically be converted into your username as well as a timestamp. That helps to keep track on discussion pages.
:Greetz :-) [[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 06:22, 18 February 2009 (UTC)

== I was just wondering.... ==

I couldn't think of a better place to ask this soo...

In what way can a [[script]] [[UUID]] be useful to a scripter? Can it be used to access the script in any way? -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 07:05, 8 August 2009 (UTC)

== RE: examples section ==

Can anyone please post a example for using actually llRemoteLoadScriptPin() ?? The current example is not for this but in fact for llSetRemoteScriptAccessPin. I am copying this example to the proper function page and will leave this one in place for now till hopefully someone or myself can post up a example for this.

[[User:Bato Brendel|Bato Brendel]] 19:27, 9 December 2010 (UTC) Bato Brendel

:It's not great but it's hard to do a good example for this IMHO. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 07:35, 10 December 2010 (UTC)

== RE: examples section ==

Please can the section headed "Rez and copy a file from a control object" be moved elsewhere. I suggest this is a demonstration of all that is worst about this Wiki. It is full of mumbo-jumbo magic numbers, has absolutely no explanations supplied in the scripts, and, I submit, 95% of it has nothing to do with explaining the function in question. And what is the point in setting the timer to zero, and then to a non-zero value later in the same UDF? If the purpose of the Wiki is to totally confuse readers, then by all means carry on :) [[User:Omei Qunhua|Omei Qunhua]] ([[User talk:Omei Qunhua|talk]]) 11:25, 27 July 2016 (PDT)

LSL 101/The touch start Event

2016-04-18T13:34:38Z

Omei Qunhua: Correct some misconceptions

[[Category:LSL 101]]
{{NavNextPrev|prev=Event Handler Parameters|next=Variables}}
{{LSL Wikibook Index}}

===[[Touch_start | The Touch Start Event]]===

Here's our sample program, with a second event handler added. The touch_start event occurs whenever any avatar clicks on the object containing the script. Note again that the name of the event must be typed touch_start, with the underscore. (The underscore doesn't show up in the title of this page just because the Wiki software displays underscores in titles as spaces.)

<source lang="lsl2">
default
{
state_entry()
{
// Let the object's owner know the script is working
llOwnerSay( "Congratulations! Your script has started to execute." );
}

touch_start( integer num_detected )
{
// Let the object's owner know the script is working
llOwnerSay( "I've been touched!" );
}
}
</source>

The event is called "touch_start" because it is the event that is raised at the beginning of a left mouse click on the object. If you want an event to occur when the click ends (when the mouse button is released) you would use the event "touch_end". Also available is the event "touch" which keeps firing repeatedly during the time that the mouse button is depressed.

===integer num_detected===

By default, the script editing tools follow "touch_start" by (integer num_detected). This is telling you that the server is passing an integer value to your script as part of the touch event. This integer tells you how may avatars "simultaneously" clicked on the object during the last clock frame (22mS) - it is NOT necessarily a cumulative count of clicks since the last touch_event was raised.

You can rename the variable to any name of your own choosing, but it must be defined as being an integer. e.g. your could write: touch_start(integer num)
The major use of this integer is in determining what parameter values can be passed to any of the llDetected... functions when executing the touch event.

Consider this script:

<source lang="lsl2">integer TotalTouches = 0; // we set the initial touch value to zero
// Every time the box it touched, it will count up one round number ("integer")

default
{
touch_start( integer num_detected )
{
TotalTouches = TotalTouches + num_detected;
// Update the total number of touches

llOwnerSay( "I have been touched a total of " + (string)TotalTouches + " times." );
// Announce the current total
}
}</source>

The variable set above default (global variable) called ''TotalTouches'' counts the total number of times our object is touched. Each time the touch_start event handler is called, the sim server initializes ''num_detected'' to be the number of times the object was touched since the previous execution of ''touch_start''. If you test this by yourself, chances are that ''TotalTouches '' will always be incrementing by one. But if you get a bunch of your friends together and have them all touch the object as rapidly as they can, sometimes you will see ''TotalTouches'' incrementing by more than one.

If a user clicks on your object many times, the touch_start event handler code will generally get executed many times, once for each click. But if multiple users click on your object at approximately the same time, SL may not invoke your code for each one separately. Instead, it may combine two or more of the touches into one event. In case your script really needs to respond separately to each touch, SL will tell you how many touches an execution of the touch_start event handler represents. That's the purpose of the phrase "integer num_detected" between the parentheses following touch_start. But before fully explaining how that works, we need to learn some other things, so we won't elaborate on that yet.

== Summary ==
There are many events (about 38 different ones) and most of them have one or more parameters (that's those things like "integer num_detected" that follow them in the parenthesis). The details will differ with the event, but the idea is always the same. Each event handler handles one particular type of event and the parameters in the event handler provide the script with the specific details of the event.

'''Please continue this tutorial with [[LSL_101/Variables |Variables]].'''

LSL 101/LSL in Focus: Integers

2016-04-14T21:47:14Z

Omei Qunhua: Further corrections. x &&= y; and x ||=y; are invalid statements. "For Example" is written e.g.

{{NavNextPrev|prefix=LSL in Focus:_|prev=Types|topic=Language Topics in Focus|next=Floats}}

__TOC__

Integers in LSL roughly correspond to integers in mathematics. They can be written in either the familiar decimal (e.g. 20, 0, -1) or [[#Hexadecimal Notation|hexadecimal]] (e.g. 0x14, 0x0, 0xFFFFFFFF).

Integers in LSL are used in four distinct ways:
* Signed integers
* Truth values (Booleans)
* Enumerations
* Bit vectors

There are a three operators, namely = (assignment), == (test for equality) and != (test for inequality) that are common to all uses of integers. Other than those, the four different uses of integers generally involve separate sets of operators.

== Signed Integers ==
This is the use of integers that corresponds to the normal use in mathematics. The only substantive difference is that in mathematics, there are infinitely many integers, while in LSL integers are limited to the range −2,147,483,648 to 2,147,483,647. Also, in LSL, no commas or other separators are allowed when writing integers, so these numbers would be written −2147483648 and 2147483647.

=== Arithmetic Operators ===
LSL has the normal arithmetic operators +, -, * and / (for division). The first three have the same meaning as what you used in grade school '''as long as the result is in the range −2147483648 to 2147483647'''. If the result is outside that range, different rules apply. The typical scripter doesn't need to use numbers that are so big (or small), so there's nor reason to feel you need to learn the details of what happens when the limits are exceeded. But there are instances where it is actually useful to allow numbers to exceed the limits. For the details of what happens in that case, see the Integer Overflow section, below.

Division of integers in LSL is a variation on what you learned in elementary school. If the division results in a whole number, say 10/2, the answer is 5. But 15/2 is neither 7.5 nor 7 with a remainder of 1. Instead, it is exactly 7. Any remainder is simply thrown away. Alternatively, you can think of it as being rounded toward zero. It's more accurate to say "rounded toward zero" than "rounded down", because -15/2 is -7, not -8. If you're scripting something where you really want 15 divided by 2 to be 7.5, don't despair. You'll just need to use the "float" type instead of integers.

Closely related to integer division is the remainder operator, written as %. It gives you what would remain if you were to ask for integer division on the same numbers. Here are some examples:
<source lang="lsl2"> integer i;
i = 15 % 2; // i is assigned the value 1
i = 15 % 4; // i is assigned the value 3
i = -15 % 4; // i is assigned the value -3</source>

If an attempt is made to divide by 0 (using either / or %), a run-time error occurs and script execution halts.

Each of the arithmetic operators also has a corresponding assignment type operation. For example
<source lang="lsl2"> integer x;
integer y;
x += y; // Synonymous with x = x + y;
x -= y; // Synonymous with x = x - y;
x *= y; // Synonymous with x = x * y;
x /= y; // Synonymous with x = x / y;</source>

In addition, since incrementing or decrementing by 1 is quite common, is special unary operator for that. The operator is written ++ and is pronounced plus-plus. To increment the variable i by 1, we can write either ++i or i++. So for example

<source lang="lsl2"> integer i = 0;
i++; // i now has the value of 1
++i; // i now has the value of 2</source>

But the two operators are not identical, because i++ and ++i are expressions that can occur as part of a larger expression. When used as part of a larger expression, i++ contributes its value to the expression ''before'' it is incremented. For example, the fragment

<source lang="lsl2"> integer i = 0;
if (i++ == 0)
llSay( 0, "The value of i was 0 when the comparison was done" )
else
llSay( 0, "The value of i was 1 when the comparison was done" )</source>

would chat "The value of i was 0 when the comparison was done" even though i ends up with the value of 1. On the other hand, if we switch i++ to ++i, e.g.:

<source lang="lsl2"> integer i = 0;
if (++i == 0)
llSay( 0, "The value of i was 0 when the comparison was done" )
else
llSay( 0, "The value of i was 1 when the comparison was done" )</source>

the chat output would be "The value of i was 1 when the comparison was done".

The operator minus-minus (written --) works similarly, but by decrementing (-1) rather than incrementing (+1).

=== Comparison Operators ===
In addition to the arithmetic operators, there are also the normal integer comparison operators < (less than) and > (greater than). For "less than or equal", or "greater than or equal", there are two-character operators <= and >=. There can't be any space between the two characters of a two-character operator.

The result of a comparison operator is either 0 (representing '''FALSE''') or 1 (representing '''TRUE'''). See [[#Truth Values (Booleans)|Truth Values (Booleans)]].

=== Integer Overflow ===
* During script execution, integers wraps from 2147483647 to -2147483648 in the normal way
* The compiler treats integers outside the range -2147483648 to 2147483647 somewhat strangely. No compile time warning or error is generated. (If the following explanation, doesn't make sense to you don't worry -- just know to avoid using numbers outside the valid range in your script.)
** For an integer outside the range -2147483648 to 2147483647, the absolute value of the number is reduced to fall in the range 0 to 4294967295 (0xFFFFFFFF).
** This number is then parsed as an unsigned 32 bit integer and cast to the corresponding signed integer.
** If the value in the script had a negative sign, the sign of the internal representation is switched.
** The net effect is that very large positive numbers get mapped to -1 and very large negative numbers get mapped to 1.

== Truth Values (Booleans) ==
There is not a special type for TRUE and FALSE in LSL. Instead, TRUE is defined to be the integer 1 and FALSE is defined to be the integer 0.

This has an interesting consequence in a conditional statement. Consider the following example

<source lang="lsl2"> integer i = 3; // 3 is neither TRUE nor FALSE
if (i)
llSay( 0, "i is treated as being true." );
else
llSay( 0, "i is treated as being false." );
if (i == TRUE)
llSay( 0, "i is equal to TRUE." );
else
llSay( 0, "i is not equal to TRUE." );</source>

When run, the output will be

i is treated as being true.
i is not equal to TRUE.

This is because the condition in the '''if''' statement can be any integer. Any non-zero value will cause the ''true'' block or statement to be executed, while a zero value will cause the ''false'' block or statement to be executed.

The same zero/non-zero distinction is made wherever a truth value is expected. In what follows, we'll use the word '''true''' and '''false''' to mean non-zero versus zero, while '''TRUE''' and '''FALSE''' will mean one and zero.

=== Truth Value Operators ===

There are three truth value operators in LSL:
* ! (representing '''not''')
* && (representing '''and''')
* || (representing '''or''')

The ! operator takes a single operand and evaluates to '''TRUE''' if the operand is false, and '''FALSE''' otherwise. For example

<source lang="lsl2"> integer i;
i = !(3 == 7); // 3 == 7 is FALSE, so i gets the value TRUE</source>

The && operator takes two operands and evaluates to '''TRUE''' if both its operands are true, and '''FALSE''' otherwise.

<source lang="lsl2"> i = (3 < 7) && (3 > 7); // 3 < 7 is TRUE, but (3 > 7) is FALSE, so i gets the value FALSE</source>

The || operator takes two operands and evaluates to '''TRUE''' if either one of its operands are true, and '''FALSE''' otherwise.

<source lang="lsl2"> i = (3 < 7) || (3 > 7); // one of the operands (3 < 7) is TRUE, so i gets the value TRUE</source>

=== Statements Requiring Truth Values ===
There are four statement types that require a truth value condition:
* if
* for
* while
* do-while

== Enumerations ==
Many built-in functions have a parameter or return value that takes one of a fixed number of alternatives. For example, [[llAttachToAvatar]] has a single parameter which specifies the attachment point. The attachment point is specified to be an integer, but the specific integer corresponding to each attachment point is arbitrary. Since the numbers themselves have no significance, LSL defines names such as [[ATTACH_HEAD]], [[ATTACH_LFOOT]] and [[ATTACH_BELLY]], which are simply meaningful names for the arbitrary integers. Integers used in this way are called '''enumerations'''.

Generally, no operators besides the ubiquitous =, == and != are used with enumerations because there is no expected relationship between the arbitrarily selected integer values.

== Bit Vectors ==

=== Bit Vector Operators ===
Analogous to the truth value operators, LSL defines four operators specifically for bit vectors:

* ~ (bitwise not)
* & (bitwise and)
* | (bitwise or)
* ^ (bitwise exclusive or)

In contrast to the truth value operators, these operate independently on each bit position.

The corresponding assignment operators such as |= are not supported in LSL.

== Other Uses of Integers ==

Although the four uses described above cover all the ways that integers are used with LSL built-in functions, they are not really exhaustive of the ways integers ''can'' be used. There are algorithms in mathematics and computer science that mix arithmetic and bit vector operations, along with bit shift operators. LSL supports this kind of computation with the bit shift operators inherited from C:

* << shift bits left
* >> shift bits right

Contrary to previous information on this page, bit shift assignment operators, >>= and <<= are not permitted in LSL.

Discussion of these algorithms is beyond the scope of this article, but see [http://graphics.stanford.edu/~seander/bithacks.html Bit Twiddling Hacks] for some examples.

== Type conversions ==
=== Other types to integers ===
Casting a positive float to an integer has the same end effect as using the [[llFloor]] function. A negative float can produce different results from the two operations.

=== Integers to other types ===

== Differences between Integers in LSL and in C ==
Much of LSL is patterned after the C programming language, and integers are no exception. Programmers who already know C can immediately apply most of their understanding of integers to LSL.

Differences to note are
* The type must be spelled ''integer'' instead of ''int''.
* There are no size modifiers (short, long, ...). All integers are 32 bits.
* There is no unsigned modifier. All integers are signed.
* Comparison operators evaluate to an integer (1 or 0), as they did in C prior to C99.
* The && and || operators are strict, i.e. both operands are always evaluated, even if the result can be determined after evaluating the left operand.

== Hexadecimal Notation ==
There's actually not much use for hexadecimal notation in LSL. If you do feel a need to use it, you probably already know how it works. If not, you can consult {{Wikipedia|Hexadecimal notation|Wikipedia}}.

Basic Notecard Reader

2016-03-24T20:24:20Z

Omei Qunhua: dupl. tag

{{LSL Header}}
=Basic Notecard Reader=

==Introduction==

Quite often i read in configuration settings from a notecard. I thought i should stick up the core part of my notecard reading script. It's not exactly rocket science but hoepfully it's useful.

==The Script==

<source lang="lsl2">
string NOTECARD = "notecard";
integer intLine1;
key keyConfigQueryhandle;
key keyConfigUUID;

default
{
state_entry()
{
if (llGetInventoryType(NOTECARD) == INVENTORY_NONE)
{
llSay(DEBUG_CHANNEL, "The notecard '"+NOTECARD+"' is missing!");
state main;
}
keyConfigQueryhandle = llGetNotecardLine(NOTECARD, intLine1);
keyConfigUUID = llGetInventoryKey(NOTECARD);
}

dataserver(key keyQueryId, string strData)
{
if (keyQueryId == keyConfigQueryhandle)
{
if (strData == EOF)
state main;

keyConfigQueryhandle = llGetNotecardLine(NOTECARD, ++intLine1);

strData = llStringTrim(strData, STRING_TRIM_HEAD); // Trim Whitespace; (not mandatory; if you use a space as marker you must erase this line
if (llGetSubString (strData, 0, 0) != "#") // is it a comment?
{
// OK .. now we do somthing in here with our notecard
}
}
}
}

state main
{
state_entry()
{
// rest of script execution here
}
changed(integer intChange)
{
if (intChange & CHANGED_INVENTORY)
{ // If the notecard has changed, then reload the notecard
if (keyConfigUUID != llGetInventoryKey(NOTECARD))
llResetScript();
}
}
}
</source>

==See also==
*[[ Script_Library | Script Library ]]

Basic Notecard Reader

2016-03-24T20:22:35Z

Omei Qunhua: Script diddn't compile ... etc. etc.

{{LSL Header}}
=Basic Notecard Reader=

==Introduction==

Quite often i read in configuration settings from a notecard. I thought i should stick up the core part of my notecard reading script. It's not exactly rocket science but hoepfully it's useful.

==The Script==

<source lang="lsl2">
<source lang="lsl2">
string NOTECARD = "notecard";
integer intLine1;
key keyConfigQueryhandle;
key keyConfigUUID;

default
{
state_entry()
{
if (llGetInventoryType(NOTECARD) == INVENTORY_NONE)
{
llSay(DEBUG_CHANNEL, "The notecard '"+NOTECARD+"' is missing!");
state main;
}
keyConfigQueryhandle = llGetNotecardLine(NOTECARD, intLine1);
keyConfigUUID = llGetInventoryKey(NOTECARD);
}

dataserver(key keyQueryId, string strData)
{
if (keyQueryId == keyConfigQueryhandle)
{
if (strData == EOF)
state main;

keyConfigQueryhandle = llGetNotecardLine(NOTECARD, ++intLine1);

strData = llStringTrim(strData, STRING_TRIM_HEAD); // Trim Whitespace; (not mandatory; if you use a space as marker you must erase this line
if (llGetSubString (strData, 0, 0) != "#") // is it a comment?
{
// OK .. now we do somthing in here with our notecard
}
}
}
}

state main
{
state_entry()
{
// rest of script execution here
}
changed(integer intChange)
{
if (intChange & CHANGED_INVENTORY)
{ // If the notecard has changed, then reload the notecard
if (keyConfigUUID != llGetInventoryKey(NOTECARD))
llResetScript();
}
}
}
</source>

==See also==
*[[ Script_Library | Script Library ]]

At target

2016-02-22T22:32:11Z

Omei Qunhua: Complete the example so that the object actually moves to the target

{{LSL_Event|event_id=16|event_delay|event=at_target
|p1_type=integer|p1_name=tnum|p1_desc=[[llTarget]] return
|p2_type=vector|p2_name=targetpos|p2_desc=[[llTarget]] position parameter
|p3_type=vector|p3_name=ourpos|p3_desc=current position (similar to [[llGetPos]])
|event_desc=Result of {{LSLG|llTarget}} library function call
|constants
|spec
|caveats
|examples=
<source lang="lsl2">
integer target_id;
vector target_pos;

default
{
state_entry()
{
target_pos = llGetPos() + <5.0, 0.0, 0.0>;
target_id = llTarget(target_pos, 0.5);
llSetStatus(STATUS_PHYSICS, TRUE);
llMoveToTarget(target_pos, 0.4);
}
at_target(integer tnum, vector targetpos, vector ourpos)
{
if (tnum == target_id)
{
llOwnerSay("object is within range of target");
llOwnerSay("target position: " + (string)targetpos + ", object is now at: " + (string)ourpos);
llOwnerSay("this is " + (string)llVecDist(targetpos, ourpos) + " meters from the target");
llTargetRemove(target_id);
}
}
not_at_target()
{
llOwnerSay(
"not there yet - object is at " + (string)llGetPos() +
", which is " + (string)llVecDist(target_pos, llGetPos()) +
" meters from the target (" + (string)target_pos + ")"
);
}
}
</source>
|helpers
|also_header
|also_events={{LSL DefineRow||[[not_at_target]]|}}
{{LSL DefineRow||[[at_rot_target]]|}}
{{LSL DefineRow||[[not_at_rot_target]]|}}
|also_functions={{LSL DefineRow||[[llTarget]]|Setup a target position}}
{{LSL DefineRow||[[llTargetRemove]]|Stop a target position}}
{{LSL DefineRow||[[llRotTarget]]|Setup a target rotation}}
{{LSL DefineRow||[[llRotTargetRemove]]|Stop a target rotation}}
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Target
|cat2=Physics
|cat3=At Target
|cat4
}}

Not at target

2016-02-21T22:20:22Z

Omei Qunhua: Complete the example so that the object actually moves

{{LSL_Event
|event_id=17
|event_delay
|event=not_at_target
|event_desc=Triggered if an object has not yet reached the target set by the call to [[llTarget]].
|event_footnote=This event may be triggered multiple times if the target has not been reached.
|constants
|spec
|caveats
|examples=
<source lang="lsl2">
integer target_id;
vector target_pos;

default
{
state_entry()
{
target_pos = llGetPos() + <5.0, 0.0, 0.0>;
target_id = llTarget(target_pos, 0.5);
llSetStatus(STATUS_PHYSICS, TRUE);
llMoveToTarget(target_pos, 0.4);
}
at_target(integer tnum, vector targetpos, vector ourpos)
{
if (tnum == target_id)
{
llOwnerSay("object is within range of target");
llOwnerSay("target position: " + (string)targetpos + ", object is now at: " + (string)ourpos);
llOwnerSay("this is " + (string)llVecDist(targetpos, ourpos) + " meters from the target");
llTargetRemove(target_id);
}
}
not_at_target()
{
llOwnerSay(
"not there yet - object is at " + (string)llGetPos() +
", which is " + (string)llVecDist(target_pos, llGetPos()) +
" meters from the target (" + (string)target_pos + ")"
);
}
}
</source>
|helpers
|also_header
|also_events={{LSL DefineRow||[[at_target]]|}}
{{LSL DefineRow||[[at_rot_target]]|}}
{{LSL DefineRow||[[not_at_rot_target]]|}}
|also_functions={{LSL DefineRow||[[llTarget]]|Setup a target position}}
{{LSL DefineRow||[[llTargetRemove]]|Stop a target position}}
{{LSL DefineRow||[[llRotTarget]]|Setup a target rotation}}
{{LSL DefineRow||[[llRotTargetRemove]]|Stop a target rotation}}
|also_articles
|also_footer
|notes
|mode
|deprecated
|cat1=Target
|cat2=Physics
|cat3=At Target
|cat4
}}

Talk:PRIM POINT LIGHT

2016-02-17T12:14:07Z

Omei Qunhua:

== Multiplying Colour? ==

In the compact version example is there a reason for multiplying the colour in this line:

<source lang="lsl2">PRIM_POINT_LIGHT, switch, <1, 0.5, 0.1> * switch, 1, 10, 0.6 </source>

If the light is being switched off then the colour will be multiplied down to <0,0,0> (black), but it seems that this is set when a light is disabled anyway (if you turn a light off then back on via script, it will be coloured black, with 0 for all values). -- --'''[[User:Haravikk_Mistral|Haravikk]]''' 03:10, 17 February 2016 (PST)

You are right. I guess I was concentrating on a compact version that faithfully replicated what the original script did, and not on the minimum to achieve the desired effect! [[User:Omei Qunhua|Omei Qunhua]] ([[User talk:Omei Qunhua|talk]]) 04:14, 17 February 2016 (PST)

Talk:Main Page/Archive 1

2016-02-10T22:52:45Z

Omei Qunhua: Undo revision 1199070 by Sandeepkumar2255 Resident (talk)

== request for categories to be added to the "About this Wiki" box ==

Would it be possible to have the [[:Category:Articles in need of updating|Articles in need of updating]] and [[:Category:Articles in need of expansion|Category:Articles in need of expansion]] categories added to the About this Wiki box so as to direct people towards articles in need of some wiki-love ?

[[User:SignpostMarv Martin|SignpostMarv Martin]] 23:14, 8 January 2007 (PST)
== Headline ==

I would very strongly suggest that (a) directly under the page name ('Main Page' - which could do with being changed anyway) is a statement along the lines of '''''"This wiki relates to the Open Source client and protocols for Second Life only. If you are looking for assistance regarding Second Life please refer to '''(whatever page is felt best)"'' as it is clear from the comments on the announcement thread on the SL Blog that there are an awful lot of people who do not understand what this is all about and it will probably scare some of them! If I had sysop status I'd add it myself ... --[[User:Alison Wheels|Alison Wheels]] 07:31, 9 January 2007 (PST)

:The wiki isn't just for the client though.
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 09:19, 9 January 2007 (PST)

::Indeed, however I do believe ''something'' is needed there to make it clear to the neophyte SL-standard-user who has no interest at all in these 'behind the scenes' activities but clicks on the link here because it is there that there is nothing for them to get worried about. --[[User:Alison Wheels|Alison Wheels]] 13:26, 9 January 2007 (PST)

:::Heh, yeah, it is really in need of a title and some introductory text.
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 14:14, 9 January 2007 (PST)

::::Could someone mock up what they think the homepage should look like? Sorry that the homepage has to be protected, but I figured it's such a vandalism target that I couldn't avoid that. -- [[User:Rob Linden|Rob Linden]] 14:20, 9 January 2007 (PST)

:::::[[User:SignpostMarv Martin/Sandbox/Main Page|Done]]
:::::[[User:SignpostMarv Martin|SignpostMarv Martin]] 03:25, 10 January 2007 (PST)

=== Removed Main Page title ===
Since the title "Main Page" doesn't add anything, it's just deadwood. So, I made a change to the stylesheet to make the Main Page title invisible. This will not affect any other pages. If anyone has an issue with this, please discuss or ping me directly.

Thanks,
Rand

--[[User:Rand Linden|Rand Linden]] 18:20, 28 January 2009 (UTC)

== What is this wiki for ? ==

What is this wiki for? Is it a general purpose wiki, where information like the old support wiki had? Would it be appropriate for someone to start a page on Groups, and Land, and Animations, etc.? A page similar to the LSL wiki for the main page would be logical, providing a list of topics, categories, etc. to guide people in the right path. A search box doesn't help if you don't know the right term to search for. Was this wiki's creation announced? If this is a general help wiki, might it make sense to put the F1 help in here to be used and worked on? If this is supposed to be a general help reference shouldn't it be listed on the support page: http://secondlife.com/community/support.php and have a separate item in the dropdown box to make it a simple as humanly possible for people to find this?
 [[User:SuezanneC Baskerville|SuezanneC Baskerville]] 08:26, 11 January 2007

:The wiki currently seems to be being used for the OSSL (Open-Source Second Life) project, and for Volunteers.
:However, with some of the work being done in [[:Category:Linden Lab Employees]], it's slowly expanding into other areas.
:With regards to improving the main page, I invite you to take a look at the wiki-code I've used on my demo, copy it over to [[User:SuezanneC Baskerville|your user-space]], and showing off your ideas.
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 09:57, 11 January 2007 (PST)

I agree with SuzanneC that this wiki needs to be much more accessible to the average user/newbie, and that the link to this wiki needs to be MUCH MORE visible on www.secondlife.com. People want to find information, and that's what a wiki is for. Do I have permission to create a "General Knowledge" Portal? Any "general knowledge" for the average user does not seem to fit into any current portals. Please advise! [[User:Oryx Tempel|Oryx Tempel]] 21:51 08 August 2007

:The [[Volunteer Portal|Volunteer wiki]] was announced on the 8th, and Pathfinder is due to make another announcement soon, in case anyone missed the first one. Below is a copy of the original announcement (modified for wikification purposes):
<blockquote style="font-style:italic;font-size:120%;font-weight: bolder ;">
::Greetings!

::I'd like to announce that our [[Volunteer Portal|Volunteer Wiki]] is now open and ready to go. It primarily contains [[:Category:Text from In-world Notecards|information collected from inworld notecards]], but this is *your* resource to contribute to and organize however you feel works best. Feel free to experiment, edit existing content, or add some completely new pages!

::Just log into the wiki with your SL username and password, and feel free to start adding or reorganizing. [[User:Amber Linden|Amber]] and [[User:Pathfinder Linden|I]] will also continue to watch it and add whatever resources we find.

::I noticed that a few of you have already started editing and contributing to it, having discovered it via the new [[Open Source Portal|Open Source wiki]] (both wikis are on the same server). Outstanding initiative, and thank you.

::Also, please be sure to visit the new [https://lists.secondlife.com/cgi-bin/mailman/listinfo/slvolunteers Volunteers mailing list page] and subscribe yourself to it. I will be using this list as a key way to communicate directly with Volunteers. I also think it will be a great way for all of you to communicate with each other and share ideas without being interrupted by Group IM's inworld.

::'''Volunteer Wiki'''
:::http://wiki.secondlife.com/wiki/Volunteer_Portal

::'''Volunteer Mailing List'''
::https://lists.secondlife.com/cgi-bin/mailman/listinfo/slvolunteers

::Onward and upward!
::-[[User:Pathfinder Linden|Pathfinder]]
</blockquote>

::*--If the Volunteer Portal is supposed to be the answer to SuezanneC Baskerville & Oryx Tempel posts about thinking we need more general help available in this wiki, then I'd have to say that the the Volunteer portal is not good as a resource for newbies, and not really even for vets either (because it's too hard to find and too sparse). I know about the newbie side, because I'm a newbie, I never thought to look in the Volunteer Portal, I doubt anyone else does either. I've spoken to other newbies in-world, they've visited this wiki too, and also thought there was absolutely nothing here of any value to newbies. Because they couldn't find it.
:::--And we need more stuff for newbies. After talking with Jeremy & Jon Linden Friday during office hours, it's clear LL offers next to nothing in the way of documentation for newbies. There is nothing good for newbies on secondlife.com or in-world. The 1 thing LL offers, is when you first login to the Second Life Support Center there's a link titled "New to Second Life? Find out how to get started." But the info offered there is WAY too brief!!!
:::--LL doesn't give a dictionary. LL doesn't give a browse-able overview of the client, so you could just poke through a table of contents and read-up about the features in the viewer. LL gives no intro for newbies (though there are some pretty good, outdated, & disorganized notecards kicking-around that do this...but how many newbies ever find/read those?).
:::--If LL, or this wiki, offered better docs for new users, Mentors might be less overwhelmed handling basic problems, Help Island would probably be less crowded, and other citizens might spend less time hand-holding newbies and more time doing more advanced, satisfying activities. I bet SL loses confused newbies in droves over the lack of docs.
:::--Since newbies don't know what questions to ask, the stuff at secondlife.com/support isn't too useful...because they don't know what search terms to type in. Lots of people don't even like to search. Why not a table of contents? What this wiki could offer is ONE point for ALL newbies to click..."Help with Second Life". From that ONE click, it should be possible to browse to EVERY article of interest to newbies. Just by browsing from ONE point they should get an overview of SL, FAQs, dictionary, info on the viewer, more in-depth info, etc. Perhaps something like this:
:::https://wiki.secondlife.com/wiki/User:Jaszon_Maynard/Proposed_Second_Life_Help_Portal
:::--Jeremy said I should look again in the wiki for docs that are good for new users. And there are some...but they're only linked to the Volunteer portal. If the Volunteer portal is supposed to be helpful to newbies, well, first of all, it's called the "Volunteer" portal (!!!). I wasn't looking to be a volunteer, or to find one...I was looking for help text. The description on the main wiki page says "Learn more about our Resident Volunteer program and access shared Volunteer resources. Resident Volunteers are participants in our Official Volunteer Program, providing guidance and assistance to Residents blah blah blah....". By the time any newbie reads 2 lines in, it seems pretty clear that the volunteer portal does not offer what they're looking for. It doesn't say "general help in here!".
:::--And the Volunteer portal is, for newbies, not organized well at all for them, and is missing all kinds of things it would have to have. I'll post about that in the Volunteer portal talk page.
:::http://wiki.secondlife.com/wiki/Talk:Volunteer_Portal
:::--And what if I don't want to join any organization (I don't, yet), but I do want to add/edit articles in the Volunteer portal? Am I allowed to? The descriptions & posts I've read implies I should not. There needs to be a freely-editable help wiki or people aren't going to edit it.
:::--Also, as a computer veteran, programmer, gamer, & user of many products...it is WAY weird to have to login to a support system before being allowed to read basic help info (which is what you have to do at secondlife.com). I am accustomed to only logging into anything if I want to make posts (forums) or submit tickets. But not just read help!!! Probably 2 kinds of people come to SL Support...those, like me, who aren't used to logging-in just to read basic help...and those who aren't used to logging into anything at all ever. Either kind of person will be confused by SL Support. They're just looking for basic help. They're asked to login to something?!? I wonder how many of them are annoyed & confused.
:::--LL is offering nothing for newbies, and I'm pretty shocked. It's probably losing them lots of potential customers. But the community could take up that slack. We can do their work for them, and maybe even do it better. We can be pretty responsive to comments from actual newbies. And we're the ones doing the most socializing, buying/selling, role-playing, setting-up businesses, etc. So we'll have a different perspective than LL. It's a user-created world, there probably should be a user-created guide to it. And hey, it's the internet, users SHOULD have a robust wiki, and LL should take advantage of that interest. I've already got some great notecards to start with and some great ideas to add in. But this wiki needs some changes first. I would start putting some of my ideas in, but there's no point unless we either make changes to the Volunteer portal, or make a new portal. Otherwise newbies will have a hard time finding what I add-in, even if they're given the URL to this wiki. I'm willing to WRITE the 1st draft of the intro for newbies, I'm willing to setup the structure for the dictionary and make the first entry in it, I'm willing to setup the structure so others can fill in the details about the client (menus, dialogs, etc), and I'm willing to setup the structure so others can write about everything else in SL (socializing, avatar customization, sight-seeing, classes, Events, money, land, building, scripting, role-playing, businesses, etc) and it'll be find-able easily in a browse-able format to newbies.
:::--I really think we need either a NEW portal called "Second Life Help", or the Volunteer portal needs a new name, new description, and new layout.
:::--If what people want is a new portal, I'd try making one myself. It would need a lot of helpful edits from others though.
:::--[[User:Jaszon Maynard|Jaszon Maynard]] 21:56, 25 February 2008 (PST)
::::To point this out: the Volunteer Portal is '''not''' the help resource for newbies. It is supposed to provide information for '''Second Life Mentors'''. But yes, I would like to see an official Help Category for newbies on the wiki. As far as I know, there are just articles in the users namespace such as the very helpful newbies guide by [[User:Tid_Kidd|on Tid Kidds Userspage]] or the growing subpages on [[User:Lum_Pfohl|Lum Pfohl]]s site. If newbies are searching for in-world help they can have a look at the official public orientation and help islands or the well made private ones like the [http://slurl.com/secondlife/Scholar/111/85/26 Orientation Station in Scholar] or the [http://slurl.com/secondlife/NMC%20Orientation/128/128/0 NMC Orientation Island] (to just name two of them). We could name and link them there as well. The problem might also be that there are not many people aware of the wiki. So i would like to see a ''Tip of the week'' and/or Video Tutorial ([[User_talk:Torley_Linden#VidTut_Request|like requested by Marv here]]) on it to make it public. But it would be nice to see this help category put up first so newbies can actually find help. By now, it might only be interesting for scripters or volunteers. Greetings, --[[User:Zai Lynch|Zai Lynch]] 15:17, 26 February 2008 (PST)

:::::*--Ok, thanks for the reply. So I gather I can create my own portal, that's allowable? Will it automatically end up on the Main Page or would I have to request someone to put it there?
::::::--[[User:Jaszon Maynard|Jaszon Maynard]] 16:14, 26 February 2008 (PST)

:::::::I ''think'' you can create your own one but it won't be added automatically nor can you add it since the main page can only be edited by wiki moderators (Lindens only?) at the moment. So I would recommend to check back with [[User:Rob_Linden|Rob]] on this. --[[User:Zai Lynch|Zai Lynch]] 20:01, 26 February 2008 (PST)

== upload directory needs chmod ==

DOWNTIME NOTICE: we'll be performing maintenance on wiki.secondlife.com on Thursday, May 31 at 10pm for up to two hours. The site may be unavailable during this time.
Upload file
From Second Life Wiki
Jump to: navigation, search

The upload directory (/shared/mediawiki_prod/wiki.secondlife.com/w/images) is not writable by the webserver.

will someone please chmod 777 the directory??? ([[User:Ina Centaur|Ina Centaur]] 05:11, 1 June 2007 (PDT))

== Translation ==
I plan on translating this page to Dutch (Main_Page/nl) objections anyone? --[[User:Aidamina Hunt|Aidamina Hunt]] 00:03, 30 August 2007 (PDT)

Plan on finishing the [[Main_Page/nl]] soon --[[User:Aidamina Hunt|Aidamina Hunt]] 07:06, 11 April 2008 (PDT)

== secondlife.com/support no longer links to the wiki? ==

*--secondlife.com/support used to have a link to the wiki...not anymore?
:--[[User:Jaszon Maynard|Jaszon Maynard]] 16:56, 26 March 2008 (PDT)

::There is a link in the footer but I know what you mean. :/ -- [[User:Strife Onizuka|Strife Onizuka]] 08:54, 28 March 2008 (PDT)

== Queries ==

*Where can I ask technical queries about Second Life? The email address support@ secondlife.com has disappeared. I was directed to http://secondlife.com/support/ , which does not seem to have anywhere to send messages and queries. There is a Yahoo email group http://groups.yahoo.com/group/Second_Life , but it is moderated and its moderator seems to be on holiday or AWOL.

I was given two USA phone numbers, but I am in England.

I was told to go to https://support.secondlife.com/ics/support/security.asp , which displayed only "Insufficient Account Information deptID is empty!".

[[User:CaptainJack Grauman|CaptainJack Grauman]] 05:40, 1 April 2008 (PDT)

:I would say it depends on what your question is related to. If it is a support question for ''your'' SL, then https://support.secondlife.com/ is the page to look at. The portal got a revision [http://blog.secondlife.com/2008/03/17/support-navigation-changes-coming-tomorrow/ lately] so that might be the reason why the link mentioned above is out-of-date. In case your problem isn't listed there, you might file a support ticket (service varies for account type basic/premium). If it is a bug report or the request of a new feature, have a look at Second Lifes public issue tracker at [http://jira.secondlife.com http://jira.secondlife.com]. If it is a question about SL in general, you might want to visit an [[Office_Hours|in-world office hour]] with a Linden who is responsible for that specific technical field where your question is related to. Greetings, --[[User:Zai Lynch|Zai Lynch]] 06:25, 1 April 2008 (PDT)

== Where is the Teen Grid Section? ==

Would it be possible to add the Teen Grid Wiki on the Main Page of the Second Life Wiki? {{Unsigned|Daniel Voyager|13:54, 7 May 2008}}
:This might be something to ask a TSL VTeam Linden. I would recommend [[User:Lexie Linden|Lexie]] since she seems to be the VTeam-Wiki Linden or [[User:Blue Linden|Blue]] as allrounder. I got the feeling that the links are missing to not make it ''to easy'' for adult Residents to contact TSL Residents (via talk pages etc.) since it's some kind of intergrid communication. But well, TSL Portal and TSL Blog aren't really hidden, just unmentioned. So if you got the O.K. for the legal stuff, you could create a [[Template:Main Page/TSL Portal]] that fits the design of the other involved templates and ask Lexie/Blue to add it to the [[Main Page]] since they should have SysOp status and would know that they gave you the previous O.K. (so you wouldn't have the same discussion with [[User:Rob Linden|Rob]] again). If you got problems by creating the template, please provide the links you'd like to see displayed and poke [[User:SignpostMarv Martin|Marv]], me or one of the other [[:Category:SL Mentor Scribes|Scribes]] to this.
:Greetz, [[User:Zai_Lynch|Zai Lynch]]([[User_talk:Zai_Lynch|talk]]|[[Special:Contributions/Zai_Lynch|contribs]]) 09:14, 7 May 2008 (PDT)

== Making the Main Page portal "boxes" more compact ==

Most of the portal "boxes" (templates) on the main page have a title (with the light blue background) and then a link to the portal as the first words in the body of the box (white background). In most cases, the text of the two is the same or very similar. I'd like to eliminate the redundancy by making the link be the title. For example, see the "Web Services Portal" box at lower right. I also modified the "Help Portal" box to be along these lines.

In general, screen real estate on the Main Page is a valuable commodity and should be used parsimoniously.

Does anyone have an objection?

--[[User:Rand Linden|Rand Linden]] 07:34, 1 February 2009 (UTC)

"Parsimoniously" ? *lolz and heads for Google* -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 19:54, 23 April 2010 (UTC)

== LSL Portal "box" should have links to pages that are helpful and often used ==

* The guidelines shown is for editing the LSL portal and not about LSL script it self. Instead it should link to say [[LSL Style Guide]] or just be removed.
* The same thing with the to do link. I would just remove it.
* I most often use [[:Category:LSL Functions]]. When I first was looking for information on how to script in LSL this is what I wanted. I think it should be the first link. Looking at [[Special:Statistics]] it is the 5th most viewed page with 708,956 views.
* Next I think [[LSL Tutorial]] should be added as it is a great place for people who have never scripted before and even for those who work in other languages. This is also the 8th most viewed page on the wiki.
* The last link I would add [[:Category:LSL_Library]] which is a list of scripts that show off how LSL works or does a common task.

:* For the the two categories you may want to use [[Template:LSLGC]].
[[User:Master Starship|Master Starship]] 17:34, 23 April 2010 (UTC)

:I move the conversation back. I am talking about the main page box labeled LSL Portal with the two links. Not the actual LSL Portal page. -- [[User:Master Starship|Master Starship]] 19:07, 23 April 2010 (UTC)

All the links you could ever want are on the LSL Portal Main Page. If anything further is needed at all on the Wiki/KB Main Page (portal box) it could be a few words of explanation of what "LSL" is (EDIT TO SUGGEST: A reference guide to Linden Scripting Language. "LSL" is used to [[script]] behavior in SL objects.) so visitors are more enlightened about why they might want to visit the portal. Then the portal itself could be a little more "friendly". The Wiki/KB Main Page shouldn't be over complicated. -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 19:42, 23 April 2010 (UTC)

:I was looking at the Creation Portal box and all the links in there are also on the Creation Portal Main Page. Looking at the other boxes' links it looked like none of there were to information about how to edit that portal which is what the LSL Portal box has. All the others linked to what the summery said. The two pages currently linked are not references for LSL. I can see changing Guidelines so it says Portal Guidelines and then adding the ones I suggested. -- [[User:Master Starship|Master Starship]] 16:45, 25 April 2010 (UTC)

Ohh I see what you mean, considering what's in the other boxes, the links are inappropriate. IMO, they should be the header links. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:37, 25 April 2010 (UTC)

If no one has a problem with that I will make the changes tomorrow. -- [[User:Master Starship|Master Starship]] 12:53, 27 April 2010 (UTC)
:Just to be clear I will made it so the box has the same links as the LSL header. -- [[User:Master Starship|Master Starship]] 13:08, 27 April 2010 (UTC)

== category poisoning? ==
there seems to be some kind of error in the sub categorization causing the marketplace to be read as top level to a great majority of pages in the wiki, including all user pages, and even this main page... I thought maybe is was some recursion in the marketplace nav template, but that doesn't seem to be it... the category:marketplace contains itself as a sub category though, and I can't figure out where the problem is (maybe the marketplace page being in and redirecting to the category:marketplace?)... at any rate it's goin to take someone that knows this software better than I to fix it -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 02:00, 16 December 2010 (UTC)
: [[MediaWiki:Breadcrumbs]] was the culprit, something got confused and the bolded self-links showed it as a subpage of Marketplace. A purge half fixed it, more on [[Talk:Second Life Wiki Known Issues]]. --[[User:Cerise Resident|Cerise]] 07:26, 16 December 2010 (UTC)

Group Privacy

2016-01-21T18:31:37Z

Omei Qunhua: Reduce obfuscation

{{LSL Header}}
Many landlords do not allow residents to have security devices that are continuously operating. This device is activated manually, and only operates so long as avatars are present. When avatars leave the vicinity, the device turns off. To turn on again, the device needs to be touched by an authorised person.

Place this script into a single prim, and decorate to taste.

Requirements:

# Edit script range and timer frequency to suit
# Deed to match the land group

Operation:

# Insure that group members have the group tag active
# Touch to activate; touch to deactivate
<source lang="lsl2">
//////////////////////////////////////////////////////////////////////////////////////
//
// Version 1.0 Release
// Copyright (C) 2007, Chance Unknown
//
// This library is free software; you can redistribute it and/or
// modify it under the terms of the GNU Lesser General Public License
// as published by the Free Software Foundation; either
// version 2.1 of the License, or (at your option) any later version.
//
// This library is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with this library; if not, write to the Free Software
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
//
//////////////////////////////////////////////////////////////////////////////////////

float duration = 60.0; // Duration of Land Ban Following the Eject (1Hr)
float RANGE = 40.0; // Scan Range (40m)
float RATE = 10.0; // Scan Rate (10 Sec)

integer status;

off()
{
status = FALSE;
llSensorRemove();
llSetColor(<1,1,1>, ALL_SIDES);
llSay(0, "Deactivated.");
llSetText("Group Privacy\nOff\n\nTouch to Turn On", <1,1,1>, 1);
}

on()
{
status = TRUE;
llSensorRepeat("", NULL_KEY, AGENT, RANGE, PI, RATE);
llSetColor(<1,0,0>, ALL_SIDES);
llSay(0, "Activated while group memebers are present.");
llSetText("Group Privacy\nOn\n\nTouch to Turn Off", <1,1,1>, 0.5);
}

boot(key id)
{
if (llOverMyLand(id) == TRUE)
{
llUnSit(id);
llEjectFromLand(id);
llAddToLandBanList(id, duration); // Hour of Ban
}
}

default
{
state_entry()
{
off();
}

touch_start(integer num_detected)
{
if (llGetLandOwnerAt(llGetPos()) != llGetOwner())
llSay(0, "Deed device to match land group.");
else
{
if (llSameGroup(llDetectedKey(0)))
{
if (status)
off();
else
on();
}
else
llSay(0, "Authorized to group members only.");
}
}

sensor(integer num_detected)
{
integer group_members;
key id;

integer i;
for ( ; i < num_detected; ++i)
{
id = llDetectedKey(i);

if (llSameGroup(id))
{
llRemoveFromLandBanList(id);
++group_members;
}
else
boot(id);
}

if (!group_members)
off();
}

no_sensor()
{
off();
}
}
</source>

{{LSLC|Library}}

Describe Chatter

2016-01-21T17:41:42Z

Omei Qunhua: Clean up code. Avoid double click issues.

{{LSL Header}}

= Introduction =

Another avatar or object can ask what your avatar's name is, what your avatar's date-of-birth is, whether payment info is on file for your avatar, etc. The Linden servers will return this information without asking you for permission and without notifying you.

If you can see an avatar's profile, then Profile > 2nd Life will tell you things like Currently Online, Born mm/dd/yyyy, No Payment Info On File. If you can't, then this script can tell you those kinds of things.

= Sample Results =

<pre>
---
Avatar info:
Name: John Doe
Birthday: 2007-09-23
Payinfo: Has unused payment info on file.
Online status: Offline
---
</pre>

= Code =

<source lang="lsl2">
// Touch prim to get avatar info as shown in the profile
//
// http://wiki.secondlife.com/wiki/Describe_Chatter

key nameRequestId;
key birthdayRequestId;
key payinfoRequestId;
key onlineStatusRequestId;

string avatarLegacyName;
string avatarBirthday;
string avatarPayinfo;
string avatarOnlineStatus;

integer gEventsReceived; // Bit pattern of received dataserver events
integer gMaskName = 1;
integer gMaskBirthday = 2;
integer gMaskPayinfo = 4;
integer gMaskOnline = 8;

key gToucher;

clear_cache()
{
gEventsReceived = 0;
avatarLegacyName = "";
avatarBirthday = "";
avatarPayinfo = "";
avatarOnlineStatus = "";
}

default
{
state_entry()
{
llSetTimerEvent(0);
// yellow and opaque
llSetText("<~!~ touch to get avatar info ~!~>", <1, 1, 0>, 1);
}
on_rez(integer start_param)
{
llResetScript();
}

changed(integer change)
{
if (change & (CHANGED_OWNER | CHANGED_INVENTORY))
llResetScript();
}

touch_end(integer num_detected)
{
gToucher = llDetectedKey(0);
state working;
}
}

state working
{
state_entry()
{
llSetText("=== please wait ===", <1, 0, 0>, 1);
clear_cache();
nameRequestId = llRequestAgentData(gToucher, DATA_NAME);
birthdayRequestId = llRequestAgentData(gToucher, DATA_BORN);
payinfoRequestId = llRequestAgentData(gToucher, DATA_PAYINFO);
onlineStatusRequestId = llRequestAgentData(gToucher, DATA_ONLINE);
llSetTimerEvent(10);
}

dataserver(key query_id, string data)
{
if (query_id == NULL_KEY)
return;

if (query_id == nameRequestId)
{
gEventsReceived = gEventsReceived | gMaskName;
avatarLegacyName = data;
}
else if (query_id == birthdayRequestId)
{
gEventsReceived = gEventsReceived | gMaskBirthday;
avatarBirthday = data;
}
else if (query_id == payinfoRequestId)
{
gEventsReceived = gEventsReceived | gMaskPayinfo;
integer payInfo = (integer)data;
if (payInfo & ~(PAYMENT_INFO_ON_FILE | PAYMENT_INFO_USED))
avatarPayinfo = "- payinfo request failed -";

else
{
integer hasPayinfo = (payInfo & PAYMENT_INFO_ON_FILE);
integer usedPayinfo = (payInfo & PAYMENT_INFO_USED);
avatarPayinfo = "Has no payment info on file.";
if (hasPayinfo)
{
avatarPayinfo = "Has unused payment info on file.";
if (usedPayinfo)
avatarPayinfo = "Has used payment info on file.";
}
}
}
else if (query_id == onlineStatusRequestId)
{
gEventsReceived = gEventsReceived | gMaskOnline;
avatarOnlineStatus = "Offline";
if ( (integer) data )
avatarOnlineStatus = "Online";
}

if (gEventsReceived == (gMaskName | gMaskBirthday | gMaskPayinfo | gMaskOnline ) )
{
llSay(0, "Avatar info:"
+ "\n\tName: " + avatarLegacyName
+ "\n\tBirthday: " + avatarBirthday
+ "\n\tPayinfo: " + avatarPayinfo
+ "\n\tOnline status: " + avatarOnlineStatus);
state default;
}
}

timer()
{
llSay(0, "Sorry, did not get a response for all requested info. Please try again!");
state default;
}
}
</source>

= See Also =

'''Functions'''

[[llRequestAgentData]] - ask to receive information about of an agent, such as birth date

[[llSetText]] - float text over a prim

{{LSLC|Library}}{{LSLC|Examples}}

Teleport HUD

2016-01-21T14:51:02Z

Omei Qunhua: Correct syntax error. Avoid misrepresentative (float)TRUE / (float)FALSE

{{LSL Header}}
== Gridwide Teleport HUD (works in no-script areas) ==

# Link 9 prims.
# Drop this script.
# Add up to 8 landmarks.
# Attach to HUD and enjoy!

<source lang="lsl2">
key owner;
integer gotTPperms;
integer isShowing;

toggle(integer inputInteger)
{
if (inputInteger)
{
integer numOfPrims = llGetNumberOfPrims();
rotation currentRot = llGetRot();

vector white = <1.0, 1.0, 1.0>;
vector orange = <1.0, 0.4, 0.0>;

integer index = 1;// root of linkset
do
{
string linkName = llGetLinkName(index);

if (linkName == "TP HUD for landmarks")
{
llSetLinkPrimitiveParamsFast(index,
[PRIM_COLOR, ALL_SIDES, ZERO_VECTOR, 1,
PRIM_COLOR, 3, <0.0, 1.0, 0.0>, 1,
// green and opaque floattext
PRIM_TEXT, "click green button to close\n"
+ "or select TP destination", <0.0, 1.0, 0.0>, 1]);
}
else if (linkName == "tp1")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, white, 1,
PRIM_POSITION, <0.0, 0.0, -0.0475>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.010>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 0), white, 1]);
}
else if (linkName == "tp2")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, orange, 1,
PRIM_POSITION, <0.0, 0.0, -0.0875>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 1), orange, 1]);
}
else if (linkName == "tp3")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, white, 1,
PRIM_POSITION, <0.0, 0.0, -0.1275>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 2), white, 1]);
}
else if (linkName == "tp4")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, orange, 1,
PRIM_POSITION, <0.0, 0.0, -0.1675>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 3), orange, 1]);
}
else if (linkName == "tp5")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, white, 1,
PRIM_POSITION, <0.0, 0.0, -0.2075>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 4), white, 1]);
}
else if (linkName == "tp6")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, orange, 1,
PRIM_POSITION, <0.0, 0.0, -0.2475>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 5), orange, 1]);
}
else if (linkName == "tp7")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, white, 1,
PRIM_POSITION, <0.0, 0.0, -0.2875>*currentRot,
PRIM_SIZE, <0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 6), white, 1]);
}
else if (linkName == "tp8")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, orange, 1,
PRIM_POSITION, <0.0, 0.0, -0.3275>*currentRot,
PRIM_SIZE,<0.025, 0.025, 0.01>,
PRIM_TEXT, llGetInventoryName(INVENTORY_LANDMARK, 7), orange, 1]);
}
}
while (++index <= numOfPrims);
}
else
{
rotation currentRot = llGetRot();
integer numOfPrims = llGetNumberOfPrims();

integer index = 1;// root of linkset
do
{
string linkName = llGetLinkName(index);

if (linkName == "TP HUD for landmarks")
{
llSetLinkPrimitiveParamsFast(index,
[PRIM_COLOR, ALL_SIDES, ZERO_VECTOR, 1,
PRIM_COLOR, 3, <1.0, 0.0, 0.0>, 1,
// red and opaque floattext
PRIM_TEXT, "<~!~ TP HUD ~!~>", <1.0, 0.0, 0.0>, 1]);
}
else if (linkName == "tp1" || linkName == "tp2"
|| linkName == "tp3" || linkName == "tp4"
|| linkName == "tp5" || linkName == "tp6"
|| linkName == "tp7" || linkName == "tp8")
{
llSetLinkPrimitiveParamsFast(index, [
PRIM_COLOR, ALL_SIDES, ZERO_VECTOR, 0,
PRIM_POSITION, ZERO_VECTOR*currentRot,
PRIM_SIZE, <0.01, 0.01, 0.01>,
// black and transparent floattext
PRIM_TEXT, "", ZERO_VECTOR, 0]);
}
}
while (++index <= numOfPrims);
}
}

default
{
changed(integer change)
{
if (change & (CHANGED_OWNER | CHANGED_INVENTORY))
llResetScript();
}

attach(key attached)
{
if (attached != NULL_KEY)
llResetScript();
}

state_entry()
{
llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_NAME, "TP HUD for landmarks",
PRIM_LINK_TARGET, 2,
PRIM_NAME, "tp1",
PRIM_LINK_TARGET, 3,
PRIM_NAME, "tp2",
PRIM_LINK_TARGET, 4,
PRIM_NAME, "tp3",
PRIM_LINK_TARGET, 5,
PRIM_NAME, "tp4",
PRIM_LINK_TARGET, 6,
PRIM_NAME, "tp5",
PRIM_LINK_TARGET, 7,
PRIM_NAME, "tp6",
PRIM_LINK_TARGET, 8,
PRIM_NAME, "tp7",
PRIM_LINK_TARGET, 9,
PRIM_NAME, "tp8" ]);

owner = llGetOwner();
gotTPperms = FALSE;

isShowing = FALSE;
toggle(isShowing);

// request teleport perms and controls perms for no-script area hack
llRequestPermissions(owner, (PERMISSION_TELEPORT | PERMISSION_TAKE_CONTROLS));
}

touch_start(integer num_detected)
{
key id = llDetectedKey(0);
string linkName = llGetLinkName(llDetectedLinkNumber(0));
string tpDestination;

if (id != owner)
return;

if (gotTPperms && linkName == "TP HUD for landmarks")
{
isShowing = !isShowing;
toggle(isShowing);
}
else if (linkName == "tp1")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 0);
else if (linkName == "tp2")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 1);
else if (linkName == "tp3")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 2);
else if (linkName == "tp4")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 3);
else if (linkName == "tp5")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 4);
else if (linkName == "tp6")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 5);
else if (linkName == "tp7")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 6);
else if (linkName == "tp8")
tpDestination = llGetInventoryName(INVENTORY_LANDMARK, 7);

if (tpDestination == "")
llOwnerSay("Invalid destination!");
else
llTeleportAgent(owner, tpDestination, ZERO_VECTOR, ZERO_VECTOR);
}

// no-script area hack
control(key id,integer held, integer change)
{
return;
}

run_time_permissions(integer perm)
{
if (perm & PERMISSION_TAKE_CONTROLS)
llTakeControls(CONTROL_UP,TRUE,TRUE);
if (perm & PERMISSION_TELEPORT)
gotTPperms = TRUE;
}
}
</source>
{{LSLC|Library|Teleport HUD}}

LlDetectedVel

2016-01-18T16:46:13Z

Omei Qunhua: Make example match the description

{{LSL_Function
|inject-2={{Issues/SVC-5821}}{{LSL_Function/detected|number|vel|error=[[ZERO_VECTOR|<0.0, 0.0, 0.0>]]}}
|func_id=36|func_sleep=0.0|func_energy=10.0
|sort=DetectedVel|func=llDetectedVel|return_type=vector
|p1_type=integer|p1_name=number
|func_footnote=Returns {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} if {{LSLP|number}} is not valid sensed object or avatar.
|func_desc
|Return_text=velocity of {{LSLGC|Detected|detected}} object or avatar {{LSLP|number}}.
|spec
|caveats
|constants
|examples=
<source lang="lsl2">
//Tells the name and velocity of all near-by avatars.
default
{
state_entry()
{
// Scan once for avatars within a 96 metre radius sphere
llSensor("", "", AGENT, 96, PI);
}
sensor(integer num)
{
// num will initially be 1 or more. When num is 1, the index of the detected avatar will be zero
while(num--)
{
llOwnerSay(llDetectedName(num) + " is moving at " + (string)llVecMag(llDetectedVel(num)) + " m/s.");
}
}
}
</source>
|helpers
|also_functions
|also_events
|also_articles
|notes
}}

LlDetectedOwner

2016-01-18T12:45:47Z

Omei Qunhua: English. Promote function in question within the example

{{LSL_Function
|inject-2={{LSL_Function/detected|number|owner}}
|func_id=33|func_sleep=0.0|func_energy=10.0
|sort=DetectedOwner
|func=llDetectedOwner|return_type=key|p1_type=integer|p1_name=number
|func_footnote=Returns an {{HoverText|empty key|{{String}}}} if {{LSLP|number}} does not relate to a valid sensed object
|func_desc
|Return_text=([[UUID]]) of the {{LSLGC|Owner|owner}} of the [[object]].
|spec
|caveats
|constants
|examples=
<source lang="lsl2">
default
{
collision_start(integer num_detected)
{
string output =
"\nkey of colliding object's owner ... or the colliding avatar: " + (string)llDetectedOwner(0)
+ "\nkey of this object's owner: " + (string)llGetOwner()
+ "\nname of colliding object/avatar: " + llDetectedName(0)
+ "\nkey of colliding object/avatar: " + (string)llDetectedKey(0)
+ "\nkey of the prim containing this script: " + (string)llGetKey()
+ "\nkey of this object's root prim: " + (string)llGetLinkKey(LINK_ROOT);
llSay(0, output);
}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGetOwnerKey]]|llGetOwnerKey(llDetectedKey(number)) is the same as llDetectedOwner(number) only if the detected object is in the same region.}}
{{LSL DefineRow||[[llGetOwner]]|}}
|also_events
|also_articles
|notes=If the [[llDetectedType|detected type]] is an [[AGENT_BY_LEGACY_NAME|avatar]] the key of that avatar is returned. Avatars are owned by themselves. [[llGetOwnerKey]] works the same way with regards to avatar UUIDs.
|cat1=Owner
|cat2
|cat3
|cat4
}}

LlDetectedPos

2016-01-17T22:50:40Z

Omei Qunhua: Start with a simple focussed example

{{LSL_Function
|inject-2={{LSL_Function/detected|number|pos|error=[[ZERO_VECTOR|<0.0, 0.0, 0.0>]]}}
|func_id=35|func_sleep=0.0|func_energy=10.0
|sort=DetectedPos|func=llDetectedPos
|return_type=vector
|p1_type=integer|p1_name=number
|func_footnote=Returns {{LSLG|ZERO_VECTOR|<0.0, 0.0, 0.0>}} if number is not valid sensed object.
|func_desc
|return_text=that is the position (in [[Viewer_coordinate_frames#Region|region coordinates]]) of {{LSLGC|Detected|detected}} object number.
|spec
|caveats
|constants
|examples=

<source lang="lsl2">// Get position and distance of toucher

default
{
touch_start(integer total_number)
{
// get the position of the avatar touching this prim
vector pos = llDetectedPos(0);

// compute how far away they are
float dist = llVecDist(pos, llGetPos() );

llSay(0, "You are " + (string) dist + " metres from me, at coordinates " + (string) pos);
}
}</source>

<source lang="lsl2">// get name and sim position of Avatars within "say" range

default
{
state_entry()
{
llOwnerSay( "Touch me to get the positions of avatars in 'Say' range" );
}

touch_start( integer vIntTouchCount )
{
// Do a one-off sensor sweep over a 20m radius sphere for avatars
llSensor( "", "", AGENT, 20, PI );
}

sensor( integer vIntFound )
{
integer vIntCounter = 0;
//-- loop through all avatars found
do
{
llOwnerSay( llDetectedName( vIntCounter )
// get the position of this detected avatar
+ (string) llDetectedPos( vIntCounter ) );
} while (++vIntCounter < vIntFound);
}

// sensor does not detect owner if it's attached
no_sensor()
{
llOwnerSay( "I couldn't find anybody" );
}
}</source>
|helpers
|also_functions
|also_events
|also_articles
|notes
|permission
|cat1
|cat2
|cat3
|cat4
}}

LlSensorRemove

2016-01-17T20:19:34Z

Omei Qunhua: Focus example 1 on demonstrating the function in question. Example 2 added nothing to the understanding of llSensorRemove() and is available elsewhere.

{{LSL Function
|func_id=30
|func_sleep=0.0
|func_energy=10.0
|func=llSensorRemove
|func_desc=Removes the sensor setup by [[llSensorRepeat]].
|func_footnote=There are no parameters or return value for this function, as only one [[llSensorRepeat]] can be specified per script.
|spec
|caveats=*If called within the [[sensor]] event then it also removes all of the sensor data that is accessed by the {{LSLGC|Detected|detection}} functions.
|constants
|examples=The following basic example shows an object that when touched starts scanning for avatars in 10m every 30 seconds, and stops as soon as at least one is found, and returns their name.
<source lang="lsl2">default {
touch_start(integer x) {
llSensorRepeat("", NULL_KEY, AGENT, 10.0, PI, 30.0);
}

sensor(integer x) {
llSay(0, llDetectedName(0) + " was found first!");
llSensorRemove();
}
}
</source>

|helpers
|also_functions=
{{LSL DefineRow||[[llSensorRepeat]]|Scans for agents or objects every time period}}
{{LSL DefineRow||[[llSensor]]| Runs a sensor once}}
|also_tests
|also_events=
{{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}
{{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}
|also_articles
|notes
|cat1=Sensor
|haiku={{Haiku|Call off the hounds.|The quarry has escaped us.|Back to the stables.}}
|cat2
|cat3
|cat4
}}

LlSqrt

2016-01-13T21:35:59Z

Omei Qunhua: NaN returned under Mono

{{LSL_Function
|func=llSqrt|sort=Sqrt
|func_id=4|func_sleep=0.0|func_energy=10.0
|func_footnote=For imaginary results (val < 0.0), a {{LSLGC|Error/Math|Math Error}} is triggered under LSO , or 'NaN' (Not A Number) is returned under Mono
|p1_type=float|p1_name=val|p1_desc=positive number (val >= 0.0)
|return_type=float
|return_text=that is the square root of {{LSLP|val}}.
|spec
|caveats=* Crashes the script if passed a negative number.
|constants
|examples=
<source lang="lsl2">
default
{
state_entry()
{
float num1 = llFrand(100.0);

llOwnerSay("The square root of " + (string)num1 + " is " + (string)llSqrt(num1));
}
}
</source>
|helpers
|also_functions={{LSL DefineRow||[[llLog]]|}}
{{LSL DefineRow||[[llLog10]]|}}
{{LSL DefineRow||[[llPow]]|}}
|also_events
|also_articles
|also_tests
|notes=If you need the square root of two use [[SQRT2]].
|permission
|negative_index
|cat1=Math
|cat2=Error/Math
|cat3
|cat4
|haiku={{Haiku|Gleaming in the sun|the water gun lays broken.|It's SQuare RooT not SQuiRT.}}
}}

LlListStatistics

2016-01-13T14:41:52Z

Omei Qunhua: Add an example showing expected results for each statistical operation on a sample list

{{LSL_Function
|func_id=315|func_sleep=0.0|func_energy=10.0
|func=llListStatistics|return_type=float|p1_type=integer|p1_name=operation|p1_desc=a LIST_STAT_* flag
|p2_type=list|p2_name=src
|func_footnote=If a list entry type is not a float or an integer it is silently ignored.
|func_desc
|return_text=that is the result of performing statistical aggregate function {{LSLP|operation}} on {{LSLP|src}}.
|spec
|caveats
|constants={{{!}} class="sortable" {{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
!Constant
! title="Value" {{!}}
! class="unsortable" {{!}} Description
{{!}}-
{{!}} {{LSL Const|LIST_STAT_RANGE|integer|0|c=Calculates the range.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_MIN|integer|1|c=Calculates the smallest number.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_MAX|integer|2|c=Calculates the largest number.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_MEAN|integer|3|c=Calculates the mean (average).}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_MEDIAN|integer|4|c=Calculates the median number.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_STD_DEV|integer|5|c=Calculates the standard deviation.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_SUM|integer|6|c=Calculates the sum.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_SUM_SQUARES|integer|7|c=Calculates the sum of the squares.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}-
{{!}} {{LSL Const|LIST_STAT_NUM_COUNT|integer|8|c=Determines the number of float and integer elements.}}
{{!}} {{#var:value}}
{{!}} Determines the number of [[float]] and [[integer]] elements.
{{!}}-
{{!}} {{LSL Const|LIST_STAT_GEOMETRIC_MEAN|integer|9|c=Calculates the geometric mean.}}
{{!}} {{#var:value}}
{{!}} {{#var:comment}}
{{!}}}
|examples=
<source lang="lsl2">// Show results for each operation for a sample list
default
{
state_entry()
{
list LX = [-1, 3.33, 17, "object", -4.5, 0.8675 ];

llSay(0, "G.Mean= " + (string) llListStatistics(LIST_STAT_GEOMETRIC_MEAN, LX) ); // 0. 000000
llSay(0, "Max= " + (string) llListStatistics(LIST_STAT_MAX, LX) ); // 17.000000
llSay(0, "Min= " + (string) llListStatistics(LIST_STAT_MIN, LX) ); // -4.500000
llSay(0, "Mean= " + (string) llListStatistics(LIST_STAT_MEAN, LX) ); // 3.139500
llSay(0, "Median= " + (string) llListStatistics(LIST_STAT_MEDIAN, LX) ); // 0.867500
llSay(0, "Count= " + (string) llListStatistics(LIST_STAT_NUM_COUNT, LX) ); // 5.000000
llSay(0, "Range= " + (string) llListStatistics(LIST_STAT_RANGE, LX) ); // 21.500000
llSay(0, "Std.Dev= " + (string) llListStatistics(LIST_STAT_STD_DEV, LX) ); // 8.258468
llSay(0, "Sum= " + (string) llListStatistics(LIST_STAT_SUM, LX) ); // 15.697500
llSay(0, "Sum of squares= " + (string) llListStatistics(LIST_STAT_SUM_SQUARES, LX) ); // 322.091500

}
}
// Note that LSLEditor produces "NaN" (Not A Number) for the geometric mean above. Geometric mean applies only to numbers of the same sign.
</source>

<source lang="lsl2">// shows just how bad SL is behaving and demonstrates the use of llListStatistics()
list dil_s;
list fps_s;
integer ticks = 0;

default
{
state_entry()
{
llSetTimerEvent(1.0);
}

on_rez (integer parm)
{
llResetScript();
}

timer()
{
dil_s = llList2List(dil_s + llGetRegionTimeDilation(), -60, -1);
fps_s = llList2List(fps_s + llGetRegionFPS(), -60, -1);
if(3 <= ++ticks)
{
llSetText(
"Dilation: min="+(string) llListStatistics(LIST_STAT_MIN, dil_s) + ", mean=" +
(string) llListStatistics(LIST_STAT_MEAN, dil_s) + ", max=" +
(string) llListStatistics(LIST_STAT_MAX, dil_s) + ", std.dev=" +
(string) llListStatistics(LIST_STAT_STD_DEV, dil_s) + "\n" +
"FPS: min="+(string) llListStatistics(LIST_STAT_MIN, fps_s) + ", mean=" +
(string) llListStatistics(LIST_STAT_MEAN, fps_s) + ", max=" +
(string) llListStatistics(LIST_STAT_MAX, fps_s) + ", std.dev=" +
(string) llListStatistics(LIST_STAT_STD_DEV, fps_s),
<1.0, 1.0, 0.0>, //yellow
1.0);
}
}

changed(integer change)
{
if(change & CHANGED_REGION)
{
llResetScript();
}
}
}</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGetListEntryType]]|}}
|also_events
|also_tests=
{{LSL DefineRow||[[llListStatistics Test]]|}}
|also_articles
|notes=Given that this operation ignores any non-numbers in a list, it can be used to tell you, in a mixed list, how many of the elements in a list are numbers (when used with the [[LIST_STAT_NUM_COUNT]] parameter.)
|permission
|negative_index
|sort=ListStatistics
|cat1=List
|cat2=Math
|cat3
|cat4
}}

LlSensorRepeat

2016-01-10T22:57:56Z

Omei Qunhua: Remove unused variable, avoid redefinition of a variable, avoid un-necessary variables. Scanning for agents ten times per second is excessive.

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|object=*}}{{LSL Constants/Sensing|type}}
|inject-3={{Issues/SVC-2409}}{{Issues/SVC-4301}}{{Issues/SVC-6662}}{{Issues/BUG-2366}}
|func=llSensorRepeat|sort=SensorRepeat
|func_id=29|func_sleep=0.0|func_energy=10.0
|p1_type=string|p1_name=name|p1_hover=Object or avatar name|p1_desc=Object or avatar name[[#NameFormat|!]]
|p2_type=key|p2_name=id
|p3_type=integer|p3_name=type|p3_desc=mask ({{#var:AGENT_BY_LEGACY_NAME}}, {{#var:AGENT_BY_USERNAME}}, {{#var:ACTIVE}}, {{#var:PASSIVE}}, and/or {{#var:SCRIPTED}})|p3_hover=mask (AGENT_BY_LEGACY_NAME, AGENT_BY_USERNAME, ACTIVE, PASSIVE, and/or SCRIPTED)
|p4_type=float|p4_name=range|p4_desc=range in meters, {{Interval|gte=0.0|lte=96.0|center=range}}|p4_hover=range in meters, {{Interval/Hover|gte=0.0|lte=96.0|center=range}}
|p5_type=float|p5_name=arc|p5_desc=the max angle between the local x-axis of the prim and detectable objects, range {{Interval|gte=0.0|lteh=PI|lte={{#var:PI}}|center=arc}}|p5_hover=the max angle between the local x-axis of the prim and detectable objects, range {{Interval/Hover|gte=0.0|lte=PI|center=arc}}
|p6_type=float|p6_name=rate|p6_desc=How often a [[sensor]]/[[no_sensor]] will be queued.
|func_footnote=If {{LSLP|name}}, {{LSLP|id}}, and/or {{LSLP|type}} are empty or 0, they are ignored. If {{LSLP|id}} is an invalid key or [[NULL_KEY]] it is treated as empty. Depending upon which AGENT* flag is used determines the format requirements for {{LSLP|name}}

See: [http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSensor llSensor] for an excellent explanation of {{LSLP|arc}}.
|func_desc=Performs a single scan for {{LSLP|name}} and {{LSLP|id}} with {{LSLP|type}} within {{LSLP|range}} meters and {{LSLP|arc}} radians of forward vector and repeats every {{LSLP|rate}} seconds. It does not perform the first scan until {{LSLP|rate}} seconds have passed.
|return_text
|spec
|caveats=*The repeat of the sensor event is adversely affected by [[llGetRegionTimeDilation|time dilation]] (lag).
*Sensors placed in the root prim of attachments will use the direction the avatar is facing as their forward vector. In mouselook, this means that it will be wherever the avatar is looking, while out of mouselook, this means whichever way the avatar is pointing. This does not include where the avatar's head is pointing, or what animation the avatar is doing, just the direction the avatar would move in if you walked forward. This is the case, regardless of where the object is attached.
*Sensors placed in prims other than the root prim of an attachment will have their forward direction offset relative to the root prim's forward direction, e.g. a sensor in a prim whose +X direction is the reverse of the root +X will look backward.
* Only the most recent [[sensor]] event is queued. Previous sensor events are replaced.
* A repeating sensor does not persist across a state change.
* [[llSensorRepeat]] can occasionally detect outside of it's specified range every few cycles when used near sim borders. [[llSensor]] in a [[timer]] does not.
|examples=
<source lang="lsl2">// Written by Steamy Latte.
// Scans every 30 seconds for visitors within 10 meters.
// Reports new visitors to object owner when she is in range.

string AllAgents;

default
{
state_entry()
{
// arc=PI is a sphere, you could look more narrowly in the direction object is facing with PI/2, PI/4 etc.
// don't repeat this too often to avoid lag.
llSensorRepeat("", "", AGENT_BY_LEGACY_NAME, 10.0, PI, 30.0);
}
sensor(integer num_detected)
{
string thisAgent;
integer agentNum;
for (agentNum=0; agentNum<num_detected; agentNum++)
{
thisAgent = llDetectedName(agentNum);
if (llDetectedKey(agentNum) == llGetOwner())
{
if (AllAgents != "")
{
llOwnerSay("We've had the following visitors:" + AllAgents);
AllAgents = "";
}
}
else if (llSubStringIndex(AllAgents+"\n", "\n"+thisAgent+"\n") < 0)
{
AllAgents = AllAgents + "\n" + thisAgent;
}
}
}
}</source>

<source lang="lsl2">
// Written by Evans Love.
// (Limited to most recent 200 names by Void Singer to prevent eventual Stack/Heap Collision + clean up)
// Continuously scans for visitors within 10 meters and reports new visitors to object owner.
//-------------------------------------------------------------------------------------

integer RESPONSE_CHANNEL = -100;
float SCAN_RANGE = 10.0;
float SCAN_INTERVAL = 20.0;
list VISITOR_LIST;

default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT_BY_LEGACY_NAME, SCAN_RANGE, PI, SCAN_INTERVAL);
}

sensor(integer number_detected)
{
integer agent_number;

// iterate through all detected agents
for (; agent_number < number_detected; agent_number++)
{
string this_agent_name = llDetectedName(agent_number);
key this_agent_key = llDetectedKey(agent_number);

// if the agent is not found on the list
if (llListFindList(VISITOR_LIST, [this_agent_name]) == -1)
{
// add her/him and make the list hold the last 200 visitors
VISITOR_LIST = [this_agent_name] + llList2List(VISITOR_LIST, 0, 198);

llDialog(this_agent_key, "Welcome!", ["Ok"], RESPONSE_CHANNEL);

llOwnerSay(this_agent_name);
}
// else agent is already on the list
}

}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llSensor]]| Runs a sensor once}}
{{LSL DefineRow||[[llSensorRemove]]| Stops the llSensorRepeat timer}}
{{LSL DefineRow||[[llOverMyLand]]| What happens over owners land}}
|also_events=
{{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}
{{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}
|also_articles
|notes=
{{LSL Tip|You might want to use [[llGetAgentList]] instead of using sensors to get a list of all avatars within the same parcel or region.}}
|cat1=Sensor
|cat2=Detected
|cat3=Username/As A Parameter
|cat4=Legacy Name/As A Parameter
|haiku={{Haiku|Binoculars raised,|All eyes scan the horizon.|Ever vigilant.}}
}}

LlRequestURL

2015-12-14T22:22:03Z

Omei Qunhua: Reduce the first example script to the essentials.

{{LSL_Function
|inject-2={{Issues/BUG-3813}}
|func_id=345|func_sleep=0.0|func_energy=10.0|mode
|func=llRequestURL
|return_type=key|return_subtype=handle
|func_footnote=
|func_desc=Requests one HTTP:// url for use by this [[object]]. The [[http_request]] [[event]] is triggered with the result of the request. HTTP-in uses port 12046.
|return_text=used for identifying the result of the request in the [[http_request]] [[event]].
|spec
|caveats=*HTTP-in uses port 12046.
*Use of this function is throttled. Although it has no forced sleep time, too many requests (5 ish) in a short period will cause all further requests to be denied until the script stops requesting urls for at least 1 second. Using an [[llSleep]] of 0.6 seconds or greater between each request will prevent you from being throttled.
*When a region is (re)started all [[http_request|HTTP server]] URLs are automatically released and invalidated.
**Use [[CHANGED_REGION_START]] to detect this so new URL can be requested.
*The number of available URLs is a limited resource, that is to say, a script can only have so many open URLs. See [[LSL http_server#Resource Limitations]] for details.
*When abandoning a URL, release it with [[llReleaseURL]], to avoid leaks. Resetting the script, or deleting the prim will also suffice to release URLs.

|constants
|examples=
This script requests a new URL after region restart.

See the discussion page for explanations as to why this particular script never needs to use llReleaseURL().
<source lang="lsl2">
string url;
key urlRequestId;

default
{
state_entry()
{
urlRequestId = llRequestURL();
}
on_rez(integer start_param)
{
llResetScript();
}

changed(integer change)
{
if (change & (CHANGED_OWNER | CHANGED_INVENTORY))
llResetScript();

if (change & (CHANGED_REGION | CHANGED_REGION_START | CHANGED_TELEPORT))
urlRequestId = llRequestURL();
}

http_request(key id, string method, string body)
{
if (id == urlRequestId)
{
if (method == URL_REQUEST_DENIED)
llOwnerSay("The following error occurred while attempting to get a free URL for this device:\n \n" + body);

else if (method == URL_REQUEST_GRANTED)
{
url = body;
llLoadURL(llGetOwner(), "Click to visit my URL!", url);
}
}
}
}
</source>
It's important to keep in mind that if you request another URL, that the old one will not be released, it will remain active. The following script drives home this point.

Try the following code ONLY if you can use all your URLs on your land.
Removing the prim/script will release all URLs previous assigned.
<source lang="lsl2">
// WARNING:
//
// This script is only for proof-of-concept (demo purposes).
// DO NOT use it if you don't have the sim owners and/or
// estate managers OK to test this script.
// This script can possibly block HTTP communication from and to the sim.
// ...bringing down all networked vendors and/or similar machines.
//
// This script allocates all available URLs.
// Deleting the script and/or derezzing the object containing the script,
// will release all previously taken URLs.

default
{
state_entry()
{
llRequestURL();
}

http_request(key id, string method, string body)
{
if (method == URL_REQUEST_DENIED)
llSetText("No free URLs!", <1.0, 0.0, 0.0>, 1.0);

else if (method == URL_REQUEST_GRANTED)
{
llSetText( (string)llGetFreeURLs() + " URLs left\n" + body, <1.0, 1.0, 1.0>, 1.0);

llRequestURL();
}
else if (method == "GET")
llHTTPResponse(id, 200, "Hello there!");
}
}
</source>
This script will, as you can see, use all URLs available on your land because it does not remove the old URLs before requesting a new one.
Just store the old URL in a global variable and release it with [[llReleaseURL]].
|helpers
|also_functions=
{{LSL DefineRow||[[llRequestSecureURL]]}}
{{LSL DefineRow||[[llGetFreeURLs]]}}
{{LSL DefineRow||[[llReleaseURL]]}}
{{LSL DefineRow||[[llHTTPResponse]]}}
{{LSL DefineRow||[[llGetHTTPHeader]]}}
|also_tests
|also_events
|also_articles=
{{LSL DefineRow||[[LSL http server]]}}
|notes=
{{Quote|Another comment on resilient programming: getting a global resource, an HTTP listener in this case, should always be considered an operation that can fail for transitory reasons (as well as permanent ones). In this case, LSL folds retryable and permanent errors into the same error status and there's no opportunity for a script writer to distinguish the two cases. But a reasonable way to handle this is sleeping with limited retries before failing hard in the LSL code.|2=[https://jira.secondlife.com/browse/BUG-3813?focusedCommentId=399955&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-399955 Monty Linden]}}
|deepnotes=
|history=
*{{SVN|1836|rev=112899 |trunk=*|anchor=file22|ver=|ser=}}
|comments
|cat1=HTTP
|cat2=HTTP/Server
|cat3
|cat4
}}

Talk:LlRequestURL

2015-12-14T22:06:56Z

Omei Qunhua: Explanation for code changes

One thing I couldn't help but notice - The URL generates a UUID as a specific URL, but from what I can tell, it's not a correctly formatted one - The version digit is just as random as the others. Not really an issue, but I do find it odd that they didn't even use version 4, as they did with inworld IDs.

[[User:Hg Beeks|Hg Beeks]] 09:41, 10 August 2009 (UTC)

== Are URLs automatically released when the script is reset? ==

I tend to assume so, since otherwise they'll be constantly leaking when one edits and tests scripts that request URLs. But is that a good assumption? [[User:Dale Innis|Dale Innis]] 19:38, 3 November 2009 (UTC)

: According to my testing on Second Life Server 14.06.20.291351 yes; the URL is released upon reset. I've also written a LOT of code that uses URLs all running in the same simulator for quite a while and I've not run into a URL outage yet. In fact the available count showed over 14000 left! [[User:Cron Stardust|Cron Stardust]] 18:21, 11 July 2014 (PDT)

== Minimal example? ==

Is the example given on this page the minimal recommended script? I don't see why I need to re-acquire a URL on CHANGED_INVENTORY.

== Unnecessary code ==

The first example never needs to use llReleaseURL() because the script only requests URLs under these three circumstances:
a) in state_entry() which in this script only happens when the script is reset, and resetting the script inherently releases URLs
b) after a region restart. But that process will have released all URLs
c) on change of Region ... but the URL will have been released from the old region by virtue of the object exiting that region, and attempting to release a URL after detecting a change of region is pointless, or down-right in error, as the URL you are trying to release belonged to the region the object is no longer in.

The code to check for "dropped URLs" at five minute intervals seems bizarre and superfluous. [[User:Omei Qunhua|Omei Qunhua]] ([[User talk:Omei Qunhua|talk]]) 14:06, 14 December 2015 (PST)

LlRequestURL

2015-12-12T23:14:50Z

Omei Qunhua: Resetting a script releases URLs, so no need to formally release them before llResetScript()

{{LSL_Function
|inject-2={{Issues/BUG-3813}}
|func_id=345|func_sleep=0.0|func_energy=10.0|mode
|func=llRequestURL
|return_type=key|return_subtype=handle
|func_footnote=
|func_desc=Requests one HTTP:// url for use by this [[object]]. The [[http_request]] [[event]] is triggered with the result of the request. HTTP-in uses port 12046.
|return_text=used for identifying the result of the request in the [[http_request]] [[event]].
|spec
|caveats=*HTTP-in uses port 12046.
*Use of this function is throttled. Although it has no forced sleep time, too many requests (5 ish) in a short period will cause all further requests to be denied until the script stops requesting urls for at least 1 second. Using an [[llSleep]] of 0.6 seconds or greater between each request will prevent you from being throttled.
*When a region is (re)started all [[http_request|HTTP server]] URLs are automatically released and invalidated.
**Use [[CHANGED_REGION_START]] to detect this so new URL can be requested.
*The number of available URLs is a limited resource, that is to say, a script can only have so many open URLs. See [[LSL http_server#Resource Limitations]] for details.
*When abandoning a URL, release it with [[llReleaseURL]], to avoid leaks. Resetting the script, or deleting the prim will also suffice to release URLs.

|constants
|examples=
This script requests a new URL after region restart:
<source lang="lsl2">
string url;
key urlRequestId;
key selfCheckRequestId;

request_url()
{
llReleaseURL(url);
url = "";

urlRequestId = llRequestURL();
}

throw_exception(string inputString)
{
key owner = llGetOwner();
llInstantMessage(owner, inputString);

// yeah, bad way to handle exceptions by restarting.
// However this is just a demo script...

llResetScript();
}

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

changed(integer change)
{
if (change & (CHANGED_OWNER | CHANGED_INVENTORY))
llResetScript();

if (change & (CHANGED_REGION | CHANGED_REGION_START | CHANGED_TELEPORT))
request_url();
}

state_entry()
{
request_url();
}

http_request(key id, string method, string body)
{
integer responseStatus = 400;
string responseBody = "Unsupported method";

if (method == URL_REQUEST_DENIED)
throw_exception("The following error occurred while attempting to get a free URL for this device:\n \n" + body);

else if (method == URL_REQUEST_GRANTED)
{
url = body;
key owner = llGetOwner();
llLoadURL(owner, "Click to visit my URL!", url);

// check every 5 mins for dropped URL
llSetTimerEvent(300.0);
}
else if (method == "GET")
{
responseStatus = 200;
responseBody = "Hello world!";
}
// else if (method == "POST") ...;
// else if (method == "PUT") ...;
// else if (method == "DELETE") { responseStatus = 403; responseBody = "forbidden"; }

llHTTPResponse(id, responseStatus, responseBody);
}

http_response(key id, integer status, list metaData, string body)
{
if (id == selfCheckRequestId)
{
// If you're not usually doing this,
// now is a good time to get used to doing it!
selfCheckRequestId = NULL_KEY;

if (status != 200)
request_url();
}

else if (id == NULL_KEY)
throw_exception("Too many HTTP requests too fast!");
}

timer()
{
selfCheckRequestId = llHTTPRequest(url,
[HTTP_METHOD, "GET",
HTTP_VERBOSE_THROTTLE, FALSE,
HTTP_BODY_MAXLENGTH, 16384],
"");
}
}
</source>
It's important to keep in mind that if you request another URL, that the old one will not be released, it will remain active. The following script drives home this point.

Try the following code ONLY if you can use all your URLs on your land.
Removing the prim/script will release all URLs previous assigned.
<source lang="lsl2">
// WARNING:
//
// This script is only for proof-of-concept (demo purposes).
// DO NOT use it if you don't have the sim owners and/or
// estate managers OK to test this script.
// This script can possibly block HTTP communication from and to the sim.
// ...bringing down all networked vendors and/or similar machines.
//
// This script allocates all available URLs.
// Deleting the script and/or derezzing the object containing the script,
// will release all previously taken URLs.

default
{
state_entry()
{
llRequestURL();
}

http_request(key id, string method, string body)
{
if (method == URL_REQUEST_DENIED)
llSetText("No free URLs!", <1.0, 0.0, 0.0>, 1.0);

else if (method == URL_REQUEST_GRANTED)
{
llSetText( (string)llGetFreeURLs() + " URLs left\n" + body, <1.0, 1.0, 1.0>, 1.0);

llRequestURL();
}
else if (method == "GET")
llHTTPResponse(id, 200, "Hello there!");
}
}
</source>
This script will, as you can see, use all URLs available on your land because it does not remove the old URLs before requesting a new one.
Just store the old URL in a global variable and release it with [[llReleaseURL]].
|helpers
|also_functions=
{{LSL DefineRow||[[llRequestSecureURL]]}}
{{LSL DefineRow||[[llGetFreeURLs]]}}
{{LSL DefineRow||[[llReleaseURL]]}}
{{LSL DefineRow||[[llHTTPResponse]]}}
{{LSL DefineRow||[[llGetHTTPHeader]]}}
|also_tests
|also_events
|also_articles=
{{LSL DefineRow||[[LSL http server]]}}
|notes=
{{Quote|Another comment on resilient programming: getting a global resource, an HTTP listener in this case, should always be considered an operation that can fail for transitory reasons (as well as permanent ones). In this case, LSL folds retryable and permanent errors into the same error status and there's no opportunity for a script writer to distinguish the two cases. But a reasonable way to handle this is sleeping with limited retries before failing hard in the LSL code.|2=[https://jira.secondlife.com/browse/BUG-3813?focusedCommentId=399955&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-399955 Monty Linden]}}
|deepnotes=
|history=
*{{SVN|1836|rev=112899 |trunk=*|anchor=file22|ver=|ser=}}
|comments
|cat1=HTTP
|cat2=HTTP/Server
|cat3
|cat4
}}

LlRemoveInventory

2015-04-06T21:00:39Z

Omei Qunhua: Added Caveat re changed event

{{LSL_Function
|inject-2={{Issues/SVC-304}}{{LSL_Function/inventory|item|uuid=false|type}}
|func_id=151|func_sleep=0.0|func_energy=10.0
|func=llRemoveInventory|p1_type=string|p1_name=item
|func_footnote
|func_desc=Remove the named inventory {{LSLP|item}}
|return_text
|spec
|caveats=*If the current script is removed it will continue to run for a short period of time after this call.
*With multiple executions an llSleep(0.1) after llRemoveInventory will allow edit window contents to refresh correctly and avoid errors on phantom contents.
*llRemoveInventory will not trigger a changed event.
|constants
|examples=
<source lang="lsl2">
// Remove the current script from the object

default
{
state_entry()
{
llRemoveInventory(llGetScriptName());
}
}
</source>
<source lang="lsl2">
// user-function to include in your script
// deletes all other contents of any type except the script itself
delete_all_other_contents()
{
string thisScript = llGetScriptName();
string inventoryItemName;

integer index = llGetInventoryNumber(INVENTORY_ALL);
while (index)
{
--index; // (faster than index--;)

inventoryItemName = llGetInventoryName(INVENTORY_ALL, index);

if (inventoryItemName != thisScript)
llRemoveInventory(inventoryItemName);
}
}

default
{
state_entry()
{
delete_all_other_contents();
}
}
</source>
|helpers
|also_functions
|also_events
|also_tests
|also_articles
|notes
|permission
|negative_index
|sort=RemoveInventory
|cat1=Inventory
|cat2
|cat3
|cat4
}}

Talk:LlSameGroup

2015-03-20T12:07:28Z

Omei Qunhua:

According to LSLWiki, "Passing NULL_KEY as id will return TRUE if the object's active group is set to "none", FALSE otherwise". If this is indeed a solid specification, it should be mentioned here. You often need to recognize this, particularly because of the "no group is same group" behavior, necessitating this extra check if you want to restrict some functionality to an actual group. -- [[User:Tali Rosca|Tali Rosca]] 14:40, 29 January 2009 (UTC)
:Tested and added =) --[[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 15:34, 29 January 2009 (UTC)

A small test suggests that llSameGroup tests against the prim's group, not the object's. The main page explains that a child prim may be of a different group than the root. If the script is in the child, the test is against the child prim's group, not the root's. [[User:Jonno Stromfield|Jonno Stromfield]] 10:31, 27 August 2010 (UTC)

The description says "Returns an integer boolean, that is TRUE if uuid has the same active group, otherwise FALSE". When using the word "same" you need to say what 2 things are the same. In this case it's the group of the uuid passed to this function, and the group of the prim the script is in. Unfortunately it appears to be totally impossible for a mere mortal make the needed change on the page. [[User:Omei Qunhua|Omei Qunhua]] ([[User talk:Omei Qunhua|talk]]) 05:07, 20 March 2015 (PDT)

LlSameGroup

2015-03-20T12:01:56Z

Omei Qunhua:

{{LSL Function
|inject-2={{LSL Function/uuid|uuid|sim=*}}{{LSL Function/group}}
|func=llSameGroup
|sort=SameGroup
|func_id=219|func_sleep=0.0|func_energy=10.0
|return_type=integer
|p1_type=key|p1_name=uuid
|func_desc
Returns "TRUE" if the detected object has the same active group as the prim the script is in.
|func_footnote=Also returns [[TRUE]] if the object is deeded to the same active group as '''uuid'''{{PBR}}
Also returns [[TRUE]] if the object is "set to" or deeded to the same group as '''group''' [[UUID]] (i.e. key [[OBJECT_GROUP]])
|return_text=boolean, that is [[TRUE]] if '''uuid''' has the same active group, otherwise [[FALSE]]
|spec
|caveats=*Also returns [[TRUE]] if the object is not set to a group (i.e. "(none)") and either the AV with the given key has no group active or the function is called with a [[NULL_KEY]]
|constants
|examples=
<source lang="lsl2">
// Gives inventory object only to agents with the same active group

default
{
touch_start(integer total_number)
{
key id = llDetectedKey(0);

integer sameGroup = llSameGroup(id);
// same as llDetectedGroup(i) (with llDetectedGroup, detected does not need to be in the sim)

if (sameGroup)
{
integer numberOfObjectsInPrim = llGetInventoryNumber(INVENTORY_OBJECT);

if (numberOfObjectsInPrim)
llGiveInventory(id, llGetInventoryName(INVENTORY_OBJECT, 0));
}
else
{
llRegionSayTo(id, 0, "Wrong active group!");
}
}
}
</source>
|helpers=
To determine if an avatar is an object's owner when deeded to group, you should use a function similar to that provided for [[LlGetOwner#Useful_Snippets|llGetOwner]]().

The following uses llSameGroup() to determine if a parcel is rezzable based on the object's active group and parcel details. Useful for preventing unnecessary rez failure notices from various types of attached objects (e.g. guns, water/skywalk HUDs, etc).
<source lang="lsl2">
/*
By Aryn Gellner
pos - position (in region coordinates) to check against.
*/

integer is_rezzable(vector pos)
{
key group_id = llList2Key(llGetParcelDetails(pos, [PARCEL_DETAILS_GROUP]), 0);

integer parcel_flags = llGetParcelFlags(pos);

if(parcel_flags & PARCEL_FLAG_ALLOW_CREATE_OBJECTS)
{
return TRUE;
}
else if((parcel_flags & PARCEL_FLAG_ALLOW_CREATE_GROUP_OBJECTS) && llSameGroup(group_id))
{
return TRUE;
}
else
{
return FALSE;
}
}
</source>
|also_functions={{LSL DefineRow||[[llDetectedGroup]]|Used in conjunction with {{LSLGC|Detected|detection}} events}}
|also_tests=
{{LSL DefineRow||[[llSameGroup Test]]}}
|also_events
|also_articles
|notes
|cat1=Avatar
|cat2=Group
|haiku={{Haiku|Do you belong or|Are you alien, unknown|To us, unwanted?}}
|cat3
|cat4
}}

LlGetPermissionsKey

2015-02-06T16:30:09Z

Omei Qunhua:

{{Issues/SVC-4862}}{{LSL_Function
|func_id=137|func_sleep=0.0|func_energy=10.0
|func=llGetPermissionsKey|sort=GetPermissionsKey
|return_type=key
|func_footnote=Returns {{LSL Const|NULL_KEY|key|"00000000-0000-0000-0000-000000000000"|c=Evaluates to false in conditionals just like invalid keys.}} if permissions were neither granted nor declined (e.g., the permissions dialog was cancelled or otherwise ignored).
|func_desc
|Return_text=of the avatar that last granted or declined permissions to the script.
|spec
|caveats
|constants
|examples=
<source lang="lsl2">
// 1. rez a cube
// 2. create a new script and paste this
// 3. save script
// 4. right-click the prim and choose attach
// 5. touch the prim

announce_permissions_key()
{
key permissionsKey = llGetPermissionsKey();

llSay(0, "key llGetPermissionsKey() = '" + (string)permissionsKey + "'");
}

default
{
state_entry()
{
announce_permissions_key();

key owner = llGetOwner();
llRequestPermissions(owner, PERMISSION_ATTACH);
}

touch_start(integer num_detected)
{
key id = llDetectedKey(0);
key owner = llGetOwner();
key permissionsKey = llGetPermissionsKey();

if (id == owner)
{
if (permissionsKey == owner)
llDetachFromAvatar();
else
llSay(0, "Can't detach from you, you have not granted ATTACH perms.");
}
else
llSay(0, "Sorry, you're not the owner!");
}

run_time_permissions(integer perm)
{
if (perm & PERMISSION_ATTACH)
announce_permissions_key();
}
}
</source>
|helpers
|also_functions={{LSL DefineRow||[[llGetPermissions]]|}}
{{LSL DefineRow||[[llRequestPermissions]]|}}
|also_tests
|also_events={{LSL DefineRow||[[run_time_permissions]]|}}
|also_articles
|notes
|cat1=Permissions/Script
|cat2
|cat3
|cat4
}}

LlJsonValueType

2014-09-17T22:23:23Z

Omei Qunhua: JSON entities count from zero, not 1. The examples are not pseudo code, but LSL code fragments

{{LSL Function
|inject-2={{Issues/BUG-3692}}
|func_id=|func_sleep=0.0|func_energy=0.0
|func=llJsonValueType|return_type=string
|p1_type=string|p1_name=json|p1_desc=A string serialization of a json object.
|p2_type=list|p2_name=specifiers|p2_desc=A path to a value in the json parameter.
|func_footnote
|func_desc=Gets the [http://json.org JSON] type for the value in {{LSLPT|json}} at the location {{LSLPT|specifiers}}.
|Return_text=specifying the type of the value at {{LSLPT|specifiers}} in {{LSLPT|json}}.
|spec=See [[Json_usage_in_LSL]]
|constants={{LSL_Constants/JSON}}
|examples=<lsl>

//all these functions are untested functions that may have some very strange cases were they acd badly or where the comments are wrong
//see them as buggy PSEUDO-code and consider yourself lucky if there are less than 2 wrong counters and 4 bad pointers/names.
//they are more an example and a concept and unlikely fully functional AS IS.

string JisN(string j){if(llJsonValueType(j,[])==JSON_NUMBER )return llJsonGetValue(j,[]);return "";}
//return the JSON if "j" is a JSON_NUMBER, like j="10.1234" j="-0.1234" j="3.14159" j="-1" j="123456" otherwise return "";
//these would be sting representations of a float because j is a string.
//storing floats in a JSON will easily lose you a lot of accuracy. Integers stored in JSON may have a smaller range than 32-bit signed integers.

string JisA(string j){if(llJsonValueType(j,[])==JSON_ARRAY )return llJsonGetValue(j,[]);return "";}
//return the JSON if "j" is a JSON_ARRAY, like j="[]" j="[1,2]" j="[[1],[3,4]]" otherwise return "";
//these would be string representations of a (nested) list because j is a string.

string JisS(string j){if(llJsonValueType(j,[])==JSON_STRING )return llJsonGetValue(j,[]);return "";}
//return the string that is stored in "j" if "j" is a JSON_STRING, like j="\"PI\"" j="\"3.14\"" j="\"-1\"" otherwise return "";
//these would be string representations of a string, typecast with \" as that within itself,
//because j is a string that is also able to store numbers and floats and (nested) lists ... as strings.
//this returns the string within "j" if "j" is "A string within a string".

/*the above functions return strings to be used in simple
if(JisN(j)){}
if(JisA(j)){}
if(JisS(j)){}
//conditions as if they are booleans. //the boolean-ish condition works because "" equals FALSE within LSL.
The functions MAY return a JSON_STRING or JSON_ARRAY can be useful recursively as shown below:
*/

JstringPARSED(string j){
//j="\"PI\"";
//j="\"3.14\"";
//j="\"-1\"";
string JayWeHaveToGoDeeperS = JisS(JisS(j));
llOwnerSay( JayWeHaveToGoDeeperS ); // says "PI", or "" , or "" , because "3.14" is a JSON_NUMBER and "-1" is a JSON_NUMBER but not a JSON_STRING
string JayWeHaveToGoDeeperN = JisN(JisS(j));
llOwnerSay( JayWeHaveToGoDeeperN ); // says "" , or "3.14000" , or "-1.0000", because "PI" is a JSON_STRING but "PI" is not a JSON_NUMBER

if (llJsonValueType(j,[])==JSON_INVALID){}//would be TRUE for j="";
}

//==== End of JstringPARSED(j) ===== start of Jnested(j) for nested/recursive lists =====

Jnested(string j){
//j="[]";
//j="[[1],[2]]";
//j="[-1,[2]]";
//j="[[1],-2]";
//j="[[-3,-4]]"; //the only true case HERE for = JisA(JisA(j)); below
string JayWeHaveToGoDeeperA = JisA(JisA(j));

string subJ=JisA(j);
if (subJ){
//here you actually have to loop trough each entry of the subJ JSON_LIST to test its TYPE for each entry (if we want to go deeper recursively)
//You can go deeper once you know if entry number x is a JSON_LIST (NESTED!!!) or JSON_STRING (for some reason)
//first see how many list entries there are; we go trough entries of subJ starting on the left until its a JSON_INVALID
list types;
integer i = -1;
while (++i != -1){
string type=llJsonValueType(j,[i]);//stores the TYPE of "j"'s entry at position i as "type"
if (type==JSON_INVALID) i=-1; //this exits this the while-loop
else types += type; // the list "types" will store all the JSON types, until the first invalid one is reached. (which which should also be for "out of bounds"
}

//this is split in 2 loops to explain 1 task by splitting it in 2 smaller tasks. Actually the loops above and below could be merged easily.

i=llGetListLength(types);//we now have a list that lists all JSON types of j; lets see how long it is;
//and we loop trough all types, calling THIS function recursively if the list contains another nested list in it at position i
while (i--){//I like to go reverse from right to left when ever possible, its faster (??) and costs less memory in LSL (??)
if (llList2String(types,i)==JSON_ARRAY){
Jnested(llJsonGetValue(j,[i]));//the function calls itself here, recursively...
//but only sends the i#th SUB.list of itself trough an instance of itself.
}
else{
//read from your list what json type is at this position and do something with it.
//maybe you need a global counter that increases each time you go "one nested list deeper" and decreases when you go "one nested list back up"
//otherwise you may not know how deep you are within nested lists.
}
}
}

}
//Jnested(j) should be useful to read from large matrices (as in 300x300 fields) that may even contain complex numbers at some places.
//I tried to read very long JSONs with llGetSubString(), but llGetSubString() too easily stack-heap collides on very long strings,
//so you have to go trough the nested list using Jnested(j) to read and print it per entry.

</lsl>
|caveats=
|helpers
|also_functions={{LSL DefineRow||[[llList2Json]]|}}
{{LSL DefineRow||[[llJson2List]]|}}
{{LSL DefineRow||[[llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonGetValue]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|permission
|negative_index
|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 ]]
}}

LlList2Json

2014-09-17T17:29:20Z

Omei Qunhua: fix "typos"

{{LSL Function
|func_id=|func_sleep=0.0|func_energy
|func=llList2Json|return_type=string
|p1_type=string|p1_name=type|p1_desc=
|p2_type=list|p2_name=values|p2_desc=
|func_footnote=
To convert a json formatted string into a list use [[llJson2List]].
|func_desc=This function takes a list and returns a [http://json.org JSON] string of that list as either a json object or json array.
|return_text=that is either {{LSLPT|values}} serialized as a JSON {{LSLPT|type}}, or if an error was encountered [[JSON_INVALID]].
|spec=See [[Json_usage_in_LSL]]
* If type is [[JSON_OBJECT]] the list must be a strided list of key, value pairs and a string representing a json object will be returned.
* If type is [[JSON_ARRAY]] then a string representing a json array will be returned.
* If type is any other string then [[JSON_INVALID]] will be returned.
* Json types from the input list are inferred from the LSL data type
** [[integer]] and [[float]] types are encoded as [[JSON_NUMBER]]
** "true" and "false" are encoded as [[JSON_TRUE]] and [[JSON_FALSE]], respectively
** "null" is encoded as [[JSON_NULL]]
** properly-formatted json strings in the input are kept as-is (will either be [[JSON_STRING]], [[JSON_OBJECT]], or [[JSON_ARRAY]])
** all other strings encoded as [[JSON_STRING]]
** Note in particular that strings containing valid JSON numbers are converted to JSON strings, not left as JSON numbers ({{Jira|BUG-6284}}). This differs to the treatment that [[llJsonSetValue]] gives to strings that contain JSON numbers, which leaves them as numbers.
|constants={{LSL Constants/JSON|subset=*}}
|examples=
<lsl>
string CSV2Json(string csv)
{
list li = llCSV2List(csv);
return llList2Json(JSON_ARRAY, li);
}
// This function converts a comma separated values string to a Json array string.
// CSV strings are often used for link-messages, notecards and they are easier to type as input commands.
// A Json-Array can store multiple of those as a nested list within the same Json-string via JSON_APPEND.
</lsl>
* You could store multiple lists that set different particle effects in the same string. Use LlList2Json() to write the string and llJson2List() to read the particle system defining lists from it. The loss in float-accuracy (Json has BAD float-to-string-conversion) does not matter as much for particle effects.

* You could store multiple lists, that set different llSetPrimitiveparamsFast() values for different situation (like different animation key frames), in the same Json String.

|helpers
|also_functions={{LSL DefineRow||[[llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType]]|}}
|also_constants={{LSL DefineRow||[[JSON_ARRAY]]}}
{{LSL DefineRow||[[JSON_OBJECT]]}}
{{LSL DefineRow||[[JSON_INVALID]]}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|caveats=* Note that string '''values''' items are interpreted as JSON, not LSL, strings. Quotation marks, if required, must be added explicitly. For example, <code>[[llJson2List]]([[llList2Json]]([[JSON_ARRAY]], ["bacon", "true", "false", "null"]))</code> returns the LSL list <code>["bacon", [[JSON_TRUE]], [[JSON_FALSE]], [[JSON_NULL]]]</code>, while <code>[[llJson2List]]([[llList2Json]]([[JSON_ARRAY]], ["\"bacon\"", "\"true\"", "\"false\"", "\"null\""]))</code> returns the LSL list <code>["bacon", "true", "false", "null"]</code>
|permission
|negative_index
|sort=List2Json
|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 ]]
|haiku={{Haiku|Their ships list to port|for what reason I know not|we list to JSON}}
{{Haiku|Listen to Jason|cryptically my sensei said|I must have misheard}}
}}

LlJson2List

2014-09-16T22:52:13Z

Omei Qunhua: Sundry "typos". Personally, I can't see the point in putting up un-compiled examples

{{LSL Function
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJson2List|return_type=list|p1_type=string|p1_name=src
|func_footnote=
To convert a list into a json formatted string use [[llList2Json]].
|func_desc=This function takes a string representing [http://json.org JSON], and returns a list of the top level.
|return_text=made by parsing '''src''', a string representing json.
|spec=See [[Json_usage_in_LSL]]
* If the json represents a single item (number, string, true, false or null) then a list with 1 item will be returned.
* If the json represents an object then a strided list of key, value pairs is returned. All values that are objects or arrays are returned as json strings.
* If the json represents an array then a list of all items is returned. All values that are objects or arrays are returned as json strings.
|constants
|examples=
<lsl>
string Json2CSV(string jcsv){//Converts a Json into a string of comma separated values. == Removes the top level [ and ] and all " from top level JSON_STRING values.
list li = llJson2List(jcsv);
return llList2CSV(li);
}
//If the Json is a 1-dimensional array of strings like "[\"a\",\"b\",\"c\"]", the returned CSV-string will be: "a,b,c" //This is a much shorter CSV that will save some memory.
//If the Json contains a nested arrays like "[[1,2],[\"PI\",4]]", the returned csv string will be : "[1,2],[\"Pi\",4]"
//"[1,2],[\"Pi\",4]" is not a very readable CSV-string and not shortened by much. "PI" is not a top level string value because it is nested 1 level deeper. llJson2List unescapes those.
</lsl>

|helpers
|also_functions={{LSL DefineRow||[[llList2Json]]|}}
{{LSL DefineRow||[[llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|permission
|negative_index
|sort=Json2List
|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 ]]
}}

Pointing Stick

2014-09-14T21:19:23Z

Omei Qunhua: Fix sundry formatting / indenting errors

Made this to point at folk when its their turn at games lolz right. the useful tidbit is how it goes in the direction of what ever angle its pointing in.

<lsl>
integer switch = TRUE;
key user;

default
{
state_entry()
{
vector goal = <90, 0, 90>;
llSetRot(llEuler2Rot(goal*DEG_TO_RAD));
llSetText("Touch to activate", <0,1,0>, 1);
}
on_rez(integer x)
{
llResetScript();
}
touch_start(integer y)
{
if (switch)
{
user = llDetectedKey(0);
llRequestPermissions(user, PERMISSION_TAKE_CONTROLS);
llSetText("Touch to Release Controls", <1,0,0>, 1);
}
else
{
if (llDetectedKey(0) != user) return;
llReleaseControls();
llRegionSayTo(user, 0, "Controls Released");
llSetText("Touch to activate", <0,1,0>, 1);
}
switch = !switch;
}
run_time_permissions(integer perm)
{
if (perm & PERMISSION_TAKE_CONTROLS)
{
llTakeControls( CONTROL_FWD|CONTROL_BACK|CONTROL_ROT_LEFT|CONTROL_ROT_RIGHT|CONTROL_UP|CONTROL_DOWN,TRUE,FALSE);
}
}
control(key id, integer level, integer edge)
{
if (level & CONTROL_UP)
{
llSetLinkPrimitiveParamsFast(-4,[ PRIM_POSITION, llGetPos() +<0,0,0.20> ]);
}
if (level & CONTROL_DOWN)
{
llSetLinkPrimitiveParamsFast(-4,[ PRIM_POSITION, llGetPos() +<0,0,-0.20> ]);
}
if (level & CONTROL_FWD)
{
llSetLinkPrimitiveParamsFast(-4,[ PRIM_POSITION, llGetPos() +<0,0,0.20> * llGetLocalRot()]);
}
if (level & CONTROL_BACK)
{
llSetLinkPrimitiveParamsFast(-4,[ PRIM_POSITION, llGetPos() +<0,0,-0.20> * llGetLocalRot()]);
}
if(level & CONTROL_ROT_LEFT)
{
llSetLinkPrimitiveParamsFast(-4,[PRIM_ROT_LOCAL, llGetLocalRot() * llEuler2Rot(<0,0,4>*DEG_TO_RAD)]);
}
if (level& CONTROL_ROT_RIGHT)
{
llSetLinkPrimitiveParamsFast(-4,[PRIM_ROT_LOCAL, llGetLocalRot() * llEuler2Rot(<0,0,-4>*DEG_TO_RAD)]);
}
}
}

LlJsonGetValue

2014-09-11T16:05:48Z

Omei Qunhua: Problems with JSON_TRUE in examples. Not fully solved.

{{LSL Function
|inject-2={{Issues/BUG-3692}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJsonGetValue|return_type=string|p1_type=string|p1_name=json|p2_type=list|p2_name=specifiers
|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.
|return_text=made by parsing '''json''', a string representing json and traversing as specified by specifiers.
|func_footnote=When the input is invalid or no result can be found this function returns [[JSON_INVALID]]. If the result is <code>null</code> the function returns [[JSON_NULL]].
|spec=See [[Json_usage_in_LSL]]
|constants
|examples=
<lsl>
JGetValTest(){
string j="[[1,2],[4,5,6]]"; //JSON may be written directly as a string like this in sl.
string k; //this will change with each command below;
k=llJsonGetValue(j,[]); //returns the whole "list" of a JSON. It might just be one entry or a whole nested list or whole nested object.
//if "j" is a single JSON_STRING, this may return what the string represents as a JSON within a string; a JSON_NUMBER , JSON_TRUE, TRUE ...

k=llJsonGetValue("\"3.14\"",[]); //==k="3,14" //float that was stored in a JSON_STRING within a JSON. and not as JSON_NUMBER for no good reason

k=llJsonGetValue("\"TRUE\"" ,[]); //==k="TRUE" which may be important to communicate with a java application

k=llJsonGetValue("JSON_TRUE",[]); // gives k=JSON_INVALID="�";
k = llEscapeURL(k) ; // k = "%EF%B7%90"

k=llJsonGetValue("\"JSON_TRUE\"",[]); // k will contain the 9-character text string "JSON_TRUE"

k=llJsonGetValue(j,[0]); //returns only the first entry (at offset 0). An entry can be many things, a string, a float stored as string,
//a [list] or {object}, each entry being separated by a comma from other entries.
//list and object entries may contain multiple comma separated entries within them.
k=llJsonGetValue(j,[1]);//returns only the second entry... (all the above still applies) k="[4,5,6]";

k=llJsonGetValue(llJsonGetValue(j,[1]),[2]);
//instead of getting an entry from "j" we get a sub-entry from llJsonGetValue(j,[1]),
//assuming the sub-entry is a JSON_LIST. It returns the 3rd sub-entry of the second entry,
//that is a list with 3 entries. it would make k="6".
//it will return JSON_INVALID if there is no 3rd entry in no 2nd sub-list.
}
</lsl>
See also [[llJsonValueType]] for examples where the value type is checked before getting the value as that type.

|caveats
|helpers
|also_functions={{LSL DefineRow||[[llList2Json]]|}}
{{LSL DefineRow||[[llJson2List]]|}}
{{LSL DefineRow||[[llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|permission
|negative_index
|sort=JsonGetValue
|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 ]]
}}

LlJsonGetValue

2014-09-11T15:24:58Z

Omei Qunhua: Correct examples. JSON entries count from zero, not 1

{{LSL Function
|inject-2={{Issues/BUG-3692}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJsonGetValue|return_type=string|p1_type=string|p1_name=json|p2_type=list|p2_name=specifiers
|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.
|return_text=made by parsing '''json''', a string representing json and traversing as specified by specifiers.
|func_footnote=When the input is invalid or no result can be found this function returns [[JSON_INVALID]]. If the result is <code>null</code> the function returns [[JSON_NULL]].
|spec=See [[Json_usage_in_LSL]]
|constants
|examples=
<lsl>
JGetValTest(){
string j="[[1,2],[4,5,6]]"; //JSON may be written directly as a string like this in sl.
string k; //this will change with each command below;
k=llJsonGetValue(j,[]); //returns the whole "list" of a JSON. It might just be one entry or a whole nested list or whole nested object.
//if "j" is a single JSON_STRING, this may return what the string represents as a JSON within a string; a JSON_NUMBER , JSON_TRUE, TRUE ...

k=llJsonGetValue("\"3.14\"",[]); //==k="3,14" //float that was stored in a JSON_STRING within a JSON. and not as JSON_NUMBER for no good reason
k=llJsonGetValue("\"TRUE\"" ,[]); //==k="TRUE" which may be important to communicate with a java application
k=llJsonGetValue("\"JSON_TRUE\"",[]); //==k=JSON_TRUE="�"; //which is the reverse part for an sl scripts "true" states
k=llJsonGetValue(j,[0]); //returns only the first entry (at offset 0). An entry can be many things, a string, a float stored as string,
//a [list] or {object}, each entry being separated by a comma from other entries.
//list and object entries may contain multiple comma separated entries within them.
k=llJsonGetValue(j,[1]);//returns only the second entry... (all the above still applies) k="[4,5,6]";
k=llJsonGetValue(llJsonGetValue(j,[1]),[2]);
//instead of getting an entry from "j" we get a sub-entry from llJsonGetValue(j,[1]),
//assuming the sub-entry is a JSON_LIST. It returns the 3rd sub-entry of the second entry,
//that is a list with 3 entries. it would make k="6".
//it will return JSON_INVALID if there is no 3rd entry in no 2nd sub-list.
}
</lsl>
see [[LlJsonValueType]] for LlJsonGetValue()-examples, because its better to test if the LlJsonValueType() is correct before getting its value as that type.

|caveats
|helpers
|also_functions={{LSL DefineRow||[[llList2Json]]|}}
{{LSL DefineRow||[[llJson2List]]|}}
{{LSL DefineRow||[[llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=
|permission
|negative_index
|sort=JsonGetValue
|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 ]]
}}

LlListFindList/fr

2014-09-10T13:27:14Z

Omei Qunhua: not found is not a generic error, and often not any kind of error.

{{LSL_Function/fr
|func=llListFindList
|sort=ListFindList
|func_id=201|func_sleep=0.0|func_energy=10.0
|return_type=integer|p1_type=list|p1_name=src|p2_type=list|p2_name=test
|func_footnote=Si '''test''' n’est pas trouvé dans le list '''src''', la fonction renvoie la valeur -1. 
L’index du premier élément d’un list est l’index {{HoverText|0|zéro}}
|func_desc
|return_text=correspondant à l’index du premier élément du list '''test''' dans '''src''' ''la fonction contrôle l'existence d'un list dans un autre list.''
|spec
|caveats=*La fonction effectue une comparaison stricte des strings
|constants
|examples=<lsl>list numbers = [1, 2, 3, 4, 5];
default
{
state_entry()
{
integer index = llListFindList(numbers, [3]);
if (index != -1)
{
list three_four = llList2List(numbers, index, index + 1);
llOwnerSay(llDumpList2String(three_four, ","));
// Object: 3,4
}
}
}</lsl>
<lsl>// Gestion d'une liste d'acces by staxx Hird
// Complètement gratuit vous pouvez utilisez ce script comme vous le souhaitez
// la revente est interdite ceci à pour but de comprendre le système de liste avec un example concret.
// tapez le nom de l'avatar qui sera autorisé

list acces;
default
{
state_entry()
{
acces = []; // au chargement la liste est vide
llListen(0,"",llGetOwner(),""); // ecoute sur le canal 0 (chat)
}

listen( integer channel, string name, key id, string message )
{
if(llGetOwnerKey(id) == llGetOwner())// on verifie que c'est bien le owner de l'objet qui ajoute l'avatar
{
integer index = llListFindList(acces, [message]);// on cherche si l'avatar est déjà présent dans le liste
if (index == -1)
{
string av = llToUpper(message);// on enregistre le nom en majuscule
acces += av;// on ajoute l'avatar autorisé
llOwnerSay(message+" à été ajouter à la liste d'accès !");
}
else
{
// si il est déjà dans la liste on le lui dit
llOwnerSay(message+" se trouve déjà dans la liste d'accès");
}

}
}
touch_start(integer total_number)
{
string alt = llToUpper(llDetectedName(0)); // on passe le nom de l'avatar qui à cliquer en majuscule
integer index = llListFindList(acces, [alt]); // on cherche si il fait partie de la liste
if (index == -1)
{
llSay(0,"Vous n'avez pas l'accès à cette zone"); // pas trouver donc pas d'accès
}
else
{
llSay(0,"Bienvenue: "+llDetectedName(0));// on la trouver il peux avoir accès
}
}
}
</lsl>
|helpers=
Une façon simple de vérifier l’existence d’un élément dans un list...
<lsl>if(~llListFindList(myList, (list)item))
{//il existe
//cela fonction car ~(-1) == 0
//cela permet de sauver de l’espace et c’est plus rapide que != -1
}</lsl>
|also_functions=
{{LSL DefineRow||[[llSubStringIndex/fr|llSubStringIndex]]|Trouve un string dans un autre string}}
|also_events
|also_tests
|also_articles
|notes
|permission
|negative_index
|sort=ListFindList
|cat1=List/fr
|cat2
|cat3
|cat4
}}

User:Kephra Nurmi/lsDialog

2014-09-10T13:21:45Z

Omei Qunhua: Undo revision 1182277 by Kireji Haiku (Talk) Mis-use of ERR_GENERIC

{{LSL Header}}

== lsDialog ==

lsDialog is an universal notecard driven menu dialog system. lsDialog could be used in a HUD or rezzed objects, providing one prim dialog trees or multi prim button dialogs. You can restrict usage to owner, group, named avatars or everybody. lsDialog is using llSay or llMessageLinked to comunicate with other scripts.

== Script: .lsDialog 09124 ==
<lsl>
// .lsDialog 09124 (c) 2007-2009 by Kephra Nurmi under Creative Commons Attribution-Share Alike 3.0 License

string configName = ".lsDialog";
string configKey = NULL_KEY;
integer configLine = 0;
key configReq = NULL_KEY;
integer avChannel;

list dialogNames = [];
list dialogLines = [];
string currentName = "";
string currentLines = "";

string currentMenu = "";
list currentOptions = [];
list currentValues = [];
list simpleOptions = [];
list simpleActions = [];

integer djChannel = 0;
integer djListen = 0;
key djKey = NULL_KEY;
string djName = "";
list guests = [ ];
integer everybody = FALSE;
integer samegroup = FALSE;
integer again = TRUE;
integer linked = FALSE;

integer permissions(key id) {
return (everybody
|| (samegroup && llSameGroup(id))
|| (llGetOwner() == id)
|| ((NULL_KEY != djKey) && (djKey == id))
|| (llListFindList(guests, [ llKey2Name(id) ])>=0));
}

configRestart() {
configName = ".lsDialog";
key conf = llGetInventoryKey(configName);
if ((string)conf == configKey) return;
if ((NULL_KEY != configKey) && (llGetFreeMemory() < 6000)) llResetScript();
dialogNames = [];
dialogLines = [];
simpleOptions = [];
simpleActions = [];
currentName = "";
currentLines = "";
djChannel = 0;
djKey = NULL_KEY;
djName = "";
guests = [ ];
everybody = FALSE;
samegroup = FALSE;
if (conf == NULL_KEY) return;
configKey = conf;
configLine = 0;
configReq = llGetNotecardLine(configName,configLine);
}

flushDialog() {
if ("" == currentName) return;
if ("" == currentLines) return;
integer i = llListFindList(dialogNames,[ currentName ]);
if (i>=0) {
dialogNames = llDeleteSubList(dialogNames,i,i);
dialogLines = llDeleteSubList(dialogLines,i,i);
}
dialogNames = dialogNames + [ currentName ];
dialogLines = dialogLines + [ currentLines ];
currentName = "";
currentLines = "";
}

parseDialogRC(string data) {
if (llStringLength(data) == 0) return;
if (llGetSubString(data,0,0) == "#") return;
if ((llGetSubString(data,0,0) == "[") && (llSubStringIndex(data,"]") >= 0)) {
flushDialog();
currentName = llGetSubString(data,1,llSubStringIndex(data,"]")-1);
return;
}
if ("" == currentName) {
if ("Allow=Owner" == data) { everybody = FALSE; samegroup = FALSE; }
else
if ("Allow=Group" == data) { everybody = FALSE; samegroup = TRUE; }
else
if ("Allow=All" == data) { everybody = TRUE; samegroup = FALSE; }
else
if ("Allow=" == llGetSubString(data,0,5)) { guests = guests + [ llGetSubString(data,6,-1) ]; }
else
if ("LSDJ=" == llGetSubString(data,0,4)) { djChannel = (integer)llGetSubString(data,5,-1); }
else
if ("Dialog=Again" == data) { again = TRUE; }
else
if ("Dialog=Once" == data) { again = FALSE; }
else
if ("Dialog=Link" == data) { linked = TRUE; }
} else
if ("*" == currentName) {
integer p = llSubStringIndex(data,"=");
if (0 < p) {
simpleOptions = simpleOptions + [ llGetSubString(data, 0, p-1) ];
simpleActions = simpleActions + [ llGetSubString(data, p+1, -1) ];
}
} else
if (llSubStringIndex(data,"=") >= 0) {
if ("" == currentLines)
currentLines = data;
else
currentLines = currentLines+"\n"+data;
}
}

parseDialogLines(string menu) {
currentMenu = menu;
currentOptions = [];
currentValues = [];
integer i = llListFindList(dialogNames, [ menu ]);
if (i < 0) return;
list l = llParseString2List(llList2String(dialogLines,i),[ "\n" ], []);
integer n = llGetListLength(l);
integer k;
string s;
for (i = 0; i<n; i++) {
s = llList2String(l, i);
k = llSubStringIndex(s,"=");
if (k>0) {
currentOptions = currentOptions + [ llGetSubString(s,0,k-1) ];
currentValues = currentValues + [ llGetSubString(s,k+1,-1) ];
}
}
}

action(string s, key id) {
integer q = -1;
integer r = -1;
q = llSubStringIndex(s," ");
if (0 < q) { r = q+llSubStringIndex(llGetSubString(s,q+1,-1)," ")+1; }
if (q < r) {
string cmd = llGetSubString(s,0,q-1);
integer ch = (integer)llGetSubString(s,q+1,r-1);
string val = llGetSubString(s,r+1,-1);
if ("say" == cmd) llSay(ch,val);
if ("shout" == cmd) llShout(ch,val);
if ("whisper" == cmd) llWhisper(ch,val);
if ("region" == cmd) llRegionSay(ch,val);
if ("root" == cmd) llMessageLinked(LINK_ROOT,ch,val,id);
if ("link" == cmd) llMessageLinked(LINK_SET,ch,val,id);
if ("this" == cmd) llMessageLinked(LINK_THIS,ch,val,id);
}
}

default {
state_entry() {
configRestart();
avChannel = 1000+(integer)llFrand(3000.0);
llListen( avChannel, "", NULL_KEY, "" );
}
changed(integer type) {
if (type & CHANGED_OWNER) llResetScript();
if (type & CHANGED_INVENTORY) configRestart();
}
dataserver(key queryId, string data) {
if (queryId != configReq) return;
if (data != EOF) {
llSetText("parsing line "+(string)configLine,<1,0,0>,1);
parseDialogRC(data);
configReq = llGetNotecardLine(configName,++configLine);
} else {
if (0 != djListen)
llListenRemove(djListen);
if (0 != djChannel)
djListen = llListen( djChannel, "", NULL_KEY, "" );
llSetText("",<1,0,0>,1);
flushDialog();
llOwnerSay("ready, "+(string)llGetFreeMemory()+" free memory, listen on channel: "+(string)avChannel);
}
}
touch_start(integer num) {
key id = llDetectedKey(0);
if (!permissions(id)) return;
if (linked) {
integer l = llDetectedLinkNumber(0);
integer p = llListFindList(simpleOptions, [ llGetLinkName(l) ]);
if (0 <= p)
action(llList2String(simpleActions, p), id);
else {
p = llListFindList(dialogNames, [ llGetLinkName(l) ]);
if (p >= 0) {
parseDialogLines(llList2String(dialogNames,p));
llDialog(id,llList2String(dialogNames,p),currentOptions,avChannel);
}
}
} else
if ((llGetListLength(dialogNames) > 1) || (llGetListLength(simpleActions) > 0)) {
currentMenu = "";
string s = llGetObjectDesc();
if ("" == s) s = "your command?";
llDialog(id,s,dialogNames+simpleOptions,avChannel);
} else
if (llGetListLength(dialogNames) == 1) {
parseDialogLines(llList2String(dialogNames,0));
llDialog(id,llList2String(dialogNames,0),currentOptions,avChannel);
}
}
listen(integer channel, string name, key id, string message) {
if (djChannel == channel) {
key k = id;
if (llGetAgentInfo(id)<=0) k = llGetOwnerKey(k);
if (k != llGetOwner()) return;
list tmp = llCSV2List(message);
if ("DJ" == llList2String(tmp,0))
djKey = llList2String(tmp,1);
return;
}
if (!permissions(id)) return;
if ("" == currentMenu) {
integer i = llListFindList(simpleOptions,[ message ]);
if (i>=0) action(llList2String(simpleActions, i), id);
else {
parseDialogLines(message);
llDialog(id,currentMenu,currentOptions + [ "Back" ],avChannel);
}
} else
if ("Back" == message) {
currentMenu = "";
string s = llGetObjectDesc();
if ("" == s) s = "your command?";
llDialog(id,s,dialogNames+simpleOptions,avChannel);
} else {
integer i = llListFindList(currentOptions,[ message ]);
if (i>=0) action(llList2String(currentValues, i), id);
if (again) {
if (llGetListLength(dialogNames) > 1)
llDialog(id,currentMenu,currentOptions + [ "Back" ],avChannel);
else
llDialog(id,currentMenu,currentOptions,avChannel);
}
}
}
}
</lsl>

== Notecard: .lsDialog ==

The .lsDialog notecard defines the menu dialog tree. A typical simple notecard could look like:

<ini>
# default is to ask repeating ... remove comment if
#Dialog=Once
#Dialog=Link

# allow only one of the following
#Allow=Owner
#Allow=Group
#Allow=All

# and in addition several named avatars
#Allow=Kephra Nurmi
#Allow=Alez Ember

[*]
Reset=link 0 reset

[Size]
90%=link 0 *,size,90
95%=link 0 *,size,95
100%=link 0 *,size,100
105%=link 0 *,size,105
110%=link 0 *,size,110

[Color]
Lime=link 0 glass,color,Lime
Ivory=link 0 glass,color,Ivory
Cyan=link 0 glass,color,Cyan
</ini>

This notecard will define a single prim dialog system with one top menu called 'Reset' and two sub menus called 'Size' and 'Color' with link action on channel 0 and default permissions. The object description defines the name for the top menu dialog. Each menu starts with a section header in brackets followed lines to define the dialog entries. Each entry has a name equal to an action, a channel and a string.

Possible actions are:

* say - llSay(ch,val);
* shout - llShout(ch,val);
* whisper - llWhisper(ch,val);
* region - llRegionSay(ch,val);
* root - llMessageLinked(LINK_ROOT,ch,val,id);
* link - llMessageLinked(LINK_SET,ch,val,id);
* this - llMessageLinked(LINK_THIS,ch,val,id);

The top of the notecard, before any sections in brackets start, defines the permission and behavior. The hash marks lines as comments. Uncommenting Dialog=Once will cause to ask only one once, and not repeatingly. Dialog=Linked would need a 4 prim object, with buttons named 'Reset', 'Size' and 'Color'. The Allow= statements change the default permissions.

{{LSLC|Library}}

User talk:Omei Qunhua

2014-09-10T13:17:11Z

Omei Qunhua:

An appeal:

When submitting sample scripts (or editing existing samples) PLEASE ensure you've tested the resulting script.
There can be no excuse for blindly editing and not testing, and certainly no excuse for submitting scripts that won't even compile!
[[User:Omei Qunhua|Omei Qunhua]] 09:02, 9 December 2012 (PST)

:I wholeheartedly agree. I have been guilty of the sin but I agree. lslint and lsleditor are our friends. I noticed you mentioned that some edits have been breaking examples. If that happens, please make a note of it somewhere, we need to keep track of this so we can halt any negative trends. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:34, 14 December 2012 (PST)

::Well if you want to observe a negative trend, the following Wiki pages / examples were all corrupted by the same person :)
<pre>
Wiki Page Date Corrupted Nature of Error

Gun Script 18-Oct-12 Compile error

llGetAgentList 8-Dec-12 Compile error

llGetAgentList 9-Dec-12 Run-time bad results

llDialog 24-Sept-12 Compile error

11SetLinkAlpha 30-Sept-12 Compile error

llGetLinkInventoryPermMask 25-Nov-12 Compile error

llResetOtherScript 24-Sept-12 Run-time error

llGetSimStats 8-Dec-12 Compile error

llRequestURL 24-Sep-12 Compile error

llSetKeyframedMotion 24-Sep-12 Run-time error

llEvade 4-Dec-12 Compile error

llGetClosestNavPoint 4-Dec-12 Compile error

llGetNotecardLine 23-Sept-12 Run-time bad results

StringIsNum 7-Oct-12 Compile error

Sensor 28-Oct-12 Compile error and Run time wrong results

</pre>

(I've also corrected 4 other non-compilable or faulty example scripts by other editors, where the errors have existed since July 2012, March 2008, and Sept 2007)

[[User:Omei Qunhua|Omei Qunhua]] 15:26, 18 December 2012 (PST)

:I have take a look at all his changeings in the example scripts and do not agree with the most, Everywhere he remove inside the sub-if's the clamps and resort the events. The most of the experienced scripters do not realy read it, but for beginners i think its bad when they not see where are the clamps necessary and where not. [[User:Daemonika Nightfire|Daemonika Nightfire]] 10:19, 20 December 2012 (PST)

:I disagree with the way you say a script is "faulty" You do not clearly state your reasoning which is debatable because it's based on your own personal preference. --[[User:Ackley Bing|Ackley Bing]] 10:12, 14 February 2013 (PST)

::It's not a matter of "personal preference". If a script doesn't compile, or gives wrong results at run-time, then it's faulty. [[User:Omei Qunhua|Omei Qunhua]] 03:22, 15 February 2013 (PST)

== More size constructs ==

I've confirmed your results and made a few more tests of size optimization constructs.

x=-~x; 6 bytes (equivalent to ++x)
x=~-x; 6 bytes (equivalent to --x)
y=-~x; 6 bytes (equivalent to y=x+1)
if(~x); 7 bytes (equivalent to if(x!=-1))
x*2; 8 bytes (equivalent to x<<1)
x=-~-~x; 8 bytes (equivalent to x+=2)
x=~-~-x; 8 bytes (equivalent to x-=2)
y=x+1; 10 bytes
x=x*2; 10 bytes (equivalent to x=x<<1)
x*=2; 10 bytes
if (!~x); 10 bytes (equivalent to if(x==-1))
if(x&0x80000000) 12 bytes (equivalent to if(x<0) for integers)
if(x<0); 13 bytes
x=x<<1; 14 bytes
if(x!=-1); 17 bytes

For float x:

x=0; 9 bytes
x=0.0; 12 bytes

For vector x:

x=<0, 0, 0>; 27 bytes
x=<0.0, 0.0, 0.0>; 36 bytes
x=ZERO_VECTOR; 36 bytes

for list x:

llGetListLength(x); 40 bytes
x!=[]; 13 bytes (note: only list LENGTH is compared - actually subtracted. That returns 0 for empty list.)
x==[]; 13 bytes
if(x==[]); 17 bytes
if(x!=[]); 17 bytes
x!=[""]; 23 bytes (note: only list LENGTH is compared - actually subtracted. That returns -1 for empty list.)
x==[""]; 23 bytes (true if x has 1 element)
x!=[[]]; 23 bytes (list may not contain lists but this is allowed?!?!)
x==[[]]; 23 bytes
if(x==[""]); 27 bytes
x!=[1]; 28 bytes (true if x has 1 element)
if(x==["","",""]); 47 bytes
if(x!=["","",""]); 47 bytes
if(llGetListLengt(x)==1); 53 bytes
if(llGetListLengt(x)!=1); 56 bytes
if(x==["","","",""]); 57 bytes

Some of those may be worth being included in [[LSL Hacks]], which I'd say is the place for code size optimization. Your list results are run time size related and thus worth being included as an update to [[LSL Script Memory]]. --[[User:Pedro Oval|Pedro Oval]] 09:35, 29 December 2012 (PST)

:Wow some of those are really interesting. I would venture the reason float zero is so expensive is how it's being encoded (there are several ways to encode floats in IL). They haven't optimized the zero case. I'm very surprised that x * 2 is less than x << 2. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:28, 29 December 2012 (PST)
::Well try these for size ... x+x; 4 bytes, x=x+x; 6 bytes, x=x^x; 6 bytes. Food for thought! [[User:Omei Qunhua|Omei Qunhua]] 06:05, 30 December 2012 (PST)
:::VERY interesting, thank you!!! --[[User:Pedro Oval|Pedro Oval]] 12:11, 30 December 2012 (PST)

Some more interesting results (all for LOCAL variables) [WITHDRAWN - SEE BELOW]

<strike>integer a; 49 bytes
integer a=0; 53 bytes
string a=""; 53? 55? bytes (I'm unsure if there's a preexisting instance of "" or not - my measuring method can't tell)
string a; 53? 55? bytes
string a="a"; 53 bytes plus 2*(num characters+1) per each different string (equal strings are referenced just once)
float a=0; 54 bytes
list a; 55 bytes
list a=[]; 55 bytes
float a; 57 bytes
float a=0.0; 57 bytes
key a=""; 60? 61? 62? bytes (same problem as string)
key a="string"; 60? bytes + 2*(num_characters+1) per each different string</strike>

Braces don't seem to add anything: <code>{integer a;}</code> occupies the same size as <code>integer a;</code> and so on. Since the string case is complex, let me put an example. <code>string a="aaa"; string b="aaa";</code> will use 53+53+2*(3+1)=114 bytes, because the string is the same in both cases and it's reused, but <code>string a="aaa"; string b="bbb";</code> will use 53+53+2*(3+1)+2*(3+1)=122 bytes because the strings are different.

I'm getting inconsistent results with the keys. Something else seems to be going on. I get 61 bytes sometimes and 60 others. Wonder if there's a byte alignment problem. If so, that could make some of the previous measurements incorrect, even if they looked consistent. --[[User:Pedro Oval|Pedro Oval]] 13:40, 29 December 2012 (PST)

:Using the measurement method you suggested (or perhaps a variation), I have determined that an empty string uses 6 bytes always, while a 1 or 2 character string uses 10 bytes for the first appearance and 6 for the rest, and a 3 or 4 character string uses 14 bytes for the first appearance and 6 for the rest. Further testing suggests that string constants in code are allocated 4 bytes at a time.

:The previous results for local variable declarations can't be considered reliable. With this measurement method I get many variations for keys and strings: 132 bytes for the first appearance of <code>key x=""</code>, 56 for the second, 66 for the third... and also crazy for strings. I just withdraw the results. With integer I also got inconsistencies.: 43 bytes when measured with this method. What seems clear is that there's one implicit assumption wrong and I don't know which one or why. I guess a better understanding of CIL would help me interpret those results. Not sure if I'm willing to dive into that though. --[[User:Pedro Oval|Pedro Oval]] 14:44, 1 January 2013 (PST)

== llGetSubString ==

I obviously did not review that edit! wtf were they thinking? Thank you. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:08, 3 January 2013 (PST)

== UTF-8 ==

UTF-8 characters can be more than 2 bytes, by the original standard, used by LSO, they can by 5 bytes. UTF-8 supported by Mono supports up to 4 bytes per character. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:31, 14 January 2013 (PST)

::Yes I know. That's why I quoted an example of a 2-byte UTF-8 when giving 512 as a UTF-8 limit. I didn't want to go into a full explanation on every page. Just wanted to give some clue that 1024 bytes doesn't necessarily give 1024 characters (and an opportunity to correct the 1023 to 1024). Maybe a link to a page on UTF-8 would be appropriate. But I think the current UTF-8 page needs overhauling. It starts by saying "SL uses UTF-8 for storing and transmitting strings" which I think is no longer always true (i.e. storage in Mono) then the UTF-8 page gets hijacked with complex code examples concerning Unicode which maybe appeal to 0.1% of Wiki's users. We need to sort the basics out on SO MANY Wiki pages, before leaping into hyperspace. And that's been the impetus behind my sudden burst of editing activity over 5 weeks. (IMHO, LOL) [[User:Omei Qunhua|Omei Qunhua]] 00:26, 15 January 2013 (PST)

== Wiki editing ==

I'm not sure why you feel the need to insult other editors with every other edit summary but I wish you all the best and merry christmas. Hopefully you can find some time to loosen up during the holidays. Best regards -- [[User:Kireji Haiku|Kireji Haiku]] 14:29, 19 December 2013 (PST)

::I just stated a fact. If you find that insulting, well ....

::I don't understand why you are intent on driving the Wiki further and further from reality. You're just making it an academic non-practical source of your own personal preferences, at odds with what 99.9% of coders do and I'm sure will continue to do. [[User:Omei Qunhua|Omei Qunhua]] 16:00, 21 December 2013 (PST)

I personally don't care either way with PUBLIC_CHANNEL and I didn't view the edit comments as insulting (the field encourages brevity, which can be mistaken as insult). I don't use it myself and I doubt many people do but many people don't use <code>~llSubStringIndex()</code>, they use <code>llSubStringIndex() != -1</code> or the new fangled <code>llSubStringIndex() != [[ERR_GENERIC]]</code>. Just because it's "ugly" doesn't make it wrong. So that we don't fight over these trivialities we should take the viewpoint that if they are already existing in articles we should not change them unless we are replacing the entire line. I'm ok with grammar and punctuation getting corrected but do keep in mind that grammar and punctuation are artificial rules created by man, and these rules can be redefined at anytime as well. What is grammatically incorrect today may be grammatically correct tomorrow, so grammatical correctness isn't the most important thing. There are however about 600 unloved articles in {{LSLGC|Needs Example}} (I'm amazed it's only 600 btw). So if you get bored and feel the desire to correct something minor, consider writing an example and spread a little joy to the unloved. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 15:15, 19 December 2013 (PST)

::I feel passionately that PUBLIC_CHANNEL should NOT be promoted in the Wiki - and this is NOT because that is my own personal preference, but it is the established preference of thousands of scripters as demonstrated in millions of scripts in-world and on script libraries. Kireji I am sure feels passionately that PUBLIC_CHANNEL should be promoted - but I venture to suggest that that IS due to his own individual and personal preference. I've noticed ERR_GENERIC creeping in, and that again is at odds with practically all actual scripts, although I'm less unhappy about it, in some situations. Sure I love mnemonics like CHANGED_REGION_START as most scripters would. As I say, the Wiki is in danger of becoming an academic tome, divorced from reality. :( Also, as pointed out before, we tend to have to explain that PUBLIC_CHANNEL means 0, whereas for example one would need to explain that 0x400 means CHANGED_REGION_START. That difference highlights the problem in a nutshell. Oh, and following on from your comments, Strife, the same logic dictates that where llSay(0, .... etc. exist in Wiki articles, they shouldn't be routinely changed to PUBLIC_CHANNEL. [[User:Omei Qunhua|Omei Qunhua]] 16:04, 19 December 2013 (PST)

:::Yes, the logic does, my condemnation is not aimed at any one party. But we have bigger problems. Dryness is one of those problems. The small number of editors is another. I'd say that Examples should be a top priority but I've never been able to make it one of mine. I don't have solutions to these problems. At some point we should have a meeting. My current projects include: parameter/subtype categories and haiku. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:04, 19 December 2013 (PST)

::::"unless we are replacing the whole line" - and please, only replace that line if it's faulty, not just to propagate a personal style. Unfortunately that propagation has been going on for 15 months without anyone commenting until I started squirming a bit and seemed to become the target for criticism (the current condemnatory remarks appear in my own talk page). You say you have no preference, Strife, but your consistent use of llSay(0, in your own examples does suggest a preference. There are so many other unnecessary edits that have taken place over the same period, where there has been no corrective aspect. (float) FALSE is horrid, as are inserted lines of // { or // } ... or just adding the //. Awful. By all means, let's use our favoured styles on our own pages, or in examples that we originate ourselves. Enough. I'll go look at your list of the 600 unloved ... LOL. (But perhaps all those corrupted examples should be returned to their pristine states ^^). [[User:Omei Qunhua|Omei Qunhua]] 09:19, 20 December 2013 (PST)

:::::Yeah the (float)FALSE thing... I have trouble seeing a good reason to use it. Oh I can understand that it might uses less bytecode but for the love of monkeys put it in the optimization article. That said, I am guilty of using (integer)"" in the past in code that was highly optimized (for LSO, yes I really did need every byte). Not really keen on whitespace changes either but I don't have a strong feeling. I wonder if we should considering protecting the diversity of programming styles in the articles. This way it gives the wiki a feel that real people actually wrote the examples and that they weren't extruded from some hideous creature's bum. It will be dangerous as it will be hard to define what is good diversity and what is bad content but it should be interesting. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:30, 20 December 2013 (PST)

::"What is grammatically incorrect today may be grammatically correct tomorrow" - LOL. So that's an excuse to write appallingly? No thanks! But I do think there could be a lot of merit in preserving the programming styles exhibited by example originators, as you suggest. [[User:Omei Qunhua|Omei Qunhua]] 16:00, 21 December 2013 (PST)

:::Fixed a bug in Constants, fewer articles should be showing up now in {{LSLGC|Needs Example}}. {{LSLGC|FixMe}} if you are wondering is where all the broken articles go. Most are constants in need of descriptions (others are constants in need of syntax examples like you would see on the like [[PRIM_NAME]]). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:28, 23 December 2013 (PST)
:::P.S. Yeah it's a slippery slope and I don't buy it entirely either.

Further to suggesting that editors try to stick with the coding style used by an article originator, I was going to say that first of all the original writers should abide by an overall style guide agreed for the Wiki, such as [[https://wiki.secondlife.com/w/index.php?title=LSL_Style_Guide&oldid=1181778 StyleGuide]]. Unfortunately I see that that page has been 'hijacked' to promote one person's eccentric views. Proposed changes to the main style guide should FIRST be discussed in the corresponding discussion page. We can't have one person unilaterally declaring a style without discussion. So ... first we seriously need a 'committee' approach to defining an overall style guide. It's been said elsewhere that contributors are not going to want to rewrite their programs to comply with a Wiki style different to their usual practice. Personally I don't find that onerous, and I favour a more rigorous insistence on a unified style throughout. [[User:Omei Qunhua|Omei Qunhua]] 04:04, 24 December 2013 (PST)

: I do not know how I overlooked this but It appears I forgot to codify any syntax guidelines into the [[LSL Portal Guidelines]]. For now I'll just shove something onto [[LSL_Style_Guide#LSL_Portal_Style]]. Thoughts? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 02:19, 25 December 2013 (PST)

I started tackling some of the "need examples" pages, but quickly felt that adding an example for each individual mnemonic constant was not necessary. Indeed having a separate page for each seems seriously OTT. [[User:Omei Qunhua|Omei Qunhua]] 06:01, 27 December 2013 (PST)

:Do what you think is best, if it doesn't really need an example, skip it. I will not deny it was OCD to mandate that every constant have an article, nor that it might be a tiny bit excessive but I will argue with it being Over The Top.

:For some constants there is no benefit to having individual articles. If we were to deny all constant articles, we would end up with all function articles being at best [[llParticleSystem]] and at worst double what [[llSetPrimitiveParams]] (because llSetPrimitiveParams would become even worse). In the beginning I pushed for articles for constants because on the LSL Wiki it was hard to find information about constants. Not only was the information buried in function articles (which had no unifying layout so it could by literally be anywhere in the article), if the constant was used by multiple overlapping functions the information might be out of sync. It made maintaining the content very annoying. Personally I'd rather fill the wiki with stubs and let people flesh them out into articles if they want, than leave them digging and wishing for more. While we could come up with rules o how to decide which constants get articles and which don't, I don't think we gain anything by doing so ([[llParticleSystem]] is not one of my articles and I view it as grandfathered).

:Trying to shoe horn information about constants into articles has always been hard and it was especially hard on the LSL Wiki. You might want to add a single sentence of information but to do so might require refactoring a significant amount of the article. Here you can just post the sentence to the dedicated article and not have to worry so much about squeezing it in. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:08, 27 December 2013 (PST)

:Again, not sure why you feel the need to undo wiki contributions. Replacing channel 0 with [[PUBLIC_CHANNEL]] does not change the code style. If you strongly believe such edits shouldn't be done by others, same would go for your edits ... which go the other way around. The reason using constants is to enhance readability, making it easier for beginners. It's a lot easier to do a find and replace to get rid of [[PUBLIC_CHANNEL]] and to save byte-code than to look up what channel 0 is. Just my two cents. -- [[User:Kireji Haiku|Kireji Haiku]] 06:54, 31 December 2013 (PST)

::Kireji, YOU are the one undoing Wiki contributions. I am merely agreeing that the original style (I use the word loosely) chosen by contributors should be preserved unless there is a very good reason (basically an error) that needs correction. Your use of PUBLIC_CHANNEL is nothing more than a personal fad, and the Wiki is not the place for such indulgences. [[User:Omei Qunhua|Omei Qunhua]] 07:28, 31 December 2013 (PST)

:::I understand the point that in certain usage cases where using values instead of constant would have an advantage like when there's an [[integer]] [[Bit_field]]. However constants were created for reasons. And if you'd know nothing about LSL (but you've experienced Second Life and how scripts work) and had <code>llSay(PUBLIC_CHANNEL, "Hello!");</code> versus <code>llSay(0, "Hello!");</code>, I guess we can both agree that the first is easier to understand effect-wise. Now is there any non-personal arguement you'd want to bring up against this? Or can we move on and keep the use of [[PUBLIC_CHANNEL]] for the simpler example scripts? -- '''[[User:Kireji_Haiku|Kireji Haiku]]''' ([[User talk:Kireji_Haiku|talk]]|[[Special:Contributions/Kireji_Haiku|contribs]]) 09:53, 2 May 2014 (PDT)

== PUBLIC_CHANNEL vs Zero ==
Seeing as this topic hasn't settled down, it's time for the larger community to choose. I view their decision (even if it's Pie) as binding.
http://www.sluniverse.com/php/vb/scripting/91061-wiki-public_channel-vs-zero.html
-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 00:15, 1 January 2014 (PST)

:It isn't just about PUBLIC_CHANNEL. It is about one individual tampering with hundreds of perfectly valid existing scripts, purely to impose exceptional ideas they originated, regardless of the demonstrated preferences of hundreds of contributors, many of whom are probably no longer here to defend themselves. I thought you and I had agreed, Strife, that edits should not unnecessarily change script examples unless to correct definite errors. So, if I vote in your survey, it will be for zero, but the survey misses the important point. The survey should be "Should one individual be allowed to edit script examples purely to impose personal preferences, and not in order to fix problems?" A Wiki is supposed to be a collaborative project. When one person rampages through it, insisting on their own views on every conceivable page, it ceases to be collaborative. [[User:Omei Qunhua|Omei Qunhua]] 02:19, 1 January 2014 (PST)

::My goal is to start small and work our way up. If this gets things moving in a positive direction, good. If things degrade, the stage is set for the next act. Look at what Void said, we've got the community thinking. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:50, 1 January 2014 (PST)

== llRezAtRoot ==

I think you missed the context, which is "offline building rights", you can't be offline and on the land at the same time. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 01:42, 4 January 2014 (PST)

:hummm. Well then, what is the correct wording for the note that effectively says "To have offline building rights, you need to allow everyone to build" ? And "Be" doesn't necessarily have to apply to an avatar, it can apply to the script doing the rezzing. No? [[User:Omei Qunhua|Omei Qunhua]] 03:46, 4 January 2014 (PST)

::Ahhh. I see my issue. I focused on the wrong part. It's still screwed up. I'll fix it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:07, 4 January 2014 (PST)

:That does look better. But i still don't fully understand (excuse me for being a bit thick). Why do I need OFFLINE building rights to run a script with llRezAtRoot? Only if I'm actually offline surely. Not while I'm scripting and testing while online? [[User:Omei Qunhua|Omei Qunhua]] 08:27, 5 January 2014 (PST)

::I can't think of a situation where you would have build rights online and not offline but there may be one. There may be a gray goo restriction. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:16, 5 January 2014 (PST)

:Oh dear :( Then what is the significance of calling it "offline"? I had started to think this related to the observed situation where a script of mine can't rezz a prim unless I'm online. If there's no difference between online and offline building rights, then just call it building rights, as it is usually known. No? [[User:Omei Qunhua|Omei Qunhua]] 11:54, 5 January 2014 (PST)

Thank you. Yes, English is not my native language. I know about my ortographic problems, but I don't know how to activate a corrector or something similar. How do I make errors to be highlighted? Please tell me, that will be a great help.

--[[User:Anaimfinity Resident|Rays of green light. Bright and proud to be a Circassian]] 10:44, 3 February 2014 (PST)

== Memory Module ==
I'm afraid your characterization of sim and viewer events as 'rare' is inaccurate. It happens to thousands on a daily basis. Not to mention, the statement "such an event is likely to be more catastrophic than just the loss of variables would imply, it may not be worth trying guard against it." is extremely misleading, bad practice, and really amounts to nothing more than an opinion. Script state rollbacks are not catastrophic. They only result in a lack of data. Data which could be safeguarded against with the techniques described on the page. They certainly aren't the *only* way such safeguards can be implemented, but they are a valid way. If you think you know a better way, it would be more constructive to make a page about that, instead of vandalizing someone else's page.

I had many problems with your original statements, but I had enough respect for you that I did not change any of your wording. I only added on balance. I expect the same respect from you. But if you touch it again, Gloves off.

{{Unsigned|Darien Caldwell|2014-02-05 13:30:31 SLT}}

::Please yourself. Care to sign your remarks here? And I certainly have problems with your wild assertions. You cannot possibly say categorically that "Script state rollbacks are not catastrophic." That's just ridiculous. "vandalizing someone else's page." A trifle over emotive? If you look at the page before I added the "tip" you'll see that seriously wrong impressions were given, i.e. that globals would always get reset on rezzing / logout-in. That needed addressing. "It happens to thousands on a daily basis. " That again sounds rather wild. Care to substantiate that? Fortunately never to me, nor to my clients that they have queried with me. [[User:Omei Qunhua|Omei Qunhua]] 15:54, 5 February 2014 (PST)

== re my script you corrected ==

I use scripts in that user space for teaching purposes. Thank you for posting the answers to what I expect the students to do to it in my user space, however I am taking that down so when I teach next week the page is waiting for them to fix it. Sorry if you misunderstood the use of teaching scripts in personal user space. [[User:Toady Nakamura|Toady Nakamura]] 14:14, 11 March 2014 (PDT)

::Could you point me to what you mean by "that user space", Toady? I would be most most surprised if I've edited any example within personal user space, as I've always taken great care not to do that on the Wiki. Your recent edits don't seem to be involved in undoing any edit of mine. Thanks. [[User:Omei Qunhua|Omei Qunhua]] 08:30, 12 March 2014 (PDT)

== Checking that a Notecard exists in object inventory ==

What if the notecard isn't full perms, will llGetInventoryKey return a non-null value? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:19, 1 May 2014 (PDT)

::Hummm, no, a no-mod NC returns a null key. So what is the best way of guarding against a never-saved nc? [[User:Omei Qunhua|Omei Qunhua]] 02:29, 2 May 2014 (PDT)

:::An asset is not created until a notecard is saved. -- '''[[User:Kireji_Haiku|Kireji Haiku]]''' ([[User talk:Kireji_Haiku|talk]]|[[Special:Contributions/Kireji_Haiku|contribs]]) 09:53, 2 May 2014 (PDT)

::LOL [[User:Omei Qunhua|Omei Qunhua]] 10:12, 2 May 2014 (PDT)

== ERR_GENERIC ==

Thanks for going through and cleaning that up. It fell off my todo list. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 17:38, 9 September 2014 (PDT)

:Applying the same kind of logic to channel <code>0</code> having to be explained as being [[PUBLIC_CHANNEL]] would make sense, too. But of course, you can't acknowledge that and I'm not going to edit stuff again to fix your rage. Cheers. -- '''[[User:Kireji_Haiku|Kireji Haiku]]''' ([[User talk:Kireji_Haiku|talk]]|[[Special:Contributions/Kireji_Haiku|contribs]]) 00:32, 10 September 2014 (PDT)

::Thanks Strife, no problem.

LlSensorRepeat

2014-09-10T13:15:06Z

Omei Qunhua: Determining that an agent has not been added to a visitor list is not any kind of error

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|object=*}}{{LSL Constants/Sensing|type}}
|inject-3={{Issues/SVC-2409}}{{Issues/SVC-4301}}{{Issues/SVC-6662}}{{Issues/BUG-2366}}
|func=llSensorRepeat|sort=SensorRepeat
|func_id=29|func_sleep=0.0|func_energy=10.0
|p1_type=string|p1_name=name|p1_hover=Object or avatar name|p1_desc=Object or avatar name[[#NameFormat|!]]
|p2_type=key|p2_name=id
|p3_type=integer|p3_name=type|p3_desc=mask ({{#var:AGENT_BY_LEGACY_NAME}}, {{#var:AGENT_BY_USERNAME}}, {{#var:ACTIVE}}, {{#var:PASSIVE}}, and/or {{#var:SCRIPTED}})|p3_hover=mask (AGENT_BY_LEGACY_NAME, AGENT_BY_USERNAME, ACTIVE, PASSIVE, and/or SCRIPTED)
|p4_type=float|p4_name=range|p4_desc=range in meters, {{Interval|gte=0.0|lte=96.0|center=range}}|p4_hover=range in meters, {{Interval/Hover|gte=0.0|lte=96.0|center=range}}
|p5_type=float|p5_name=arc|p5_desc=the max angle between the local x-axis of the prim and detectable objects, range {{Interval|gte=0.0|lteh=PI|lte={{#var:PI}}|center=arc}}|p5_hover=the max angle between the local x-axis of the prim and detectable objects, range {{Interval/Hover|gte=0.0|lte=PI|center=arc}}
|p6_type=float|p6_name=rate|p6_desc=How often a [[sensor]]/[[no_sensor]] will be queued.
|func_footnote=If {{LSLP|name}}, {{LSLP|id}}, and/or {{LSLP|type}} are empty or 0, they are ignored. If {{LSLP|id}} is an invalid key or [[NULL_KEY]] it is treated as empty. Depending upon which AGENT* flag is used determines the format requirements for {{LSLP|name}}

See: [http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSensor llSensor] for an excellent explanation of {{LSLP|arc}}.
|func_desc=Performs a single scan for {{LSLP|name}} and {{LSLP|id}} with {{LSLP|type}} within {{LSLP|range}} meters and {{LSLP|arc}} radians of forward vector and repeats every {{LSLP|rate}} seconds. It does not perform the first scan until {{LSLP|rate}} seconds have passed.
|return_text
|spec
|caveats=*The repeat of the sensor event is adversely affected by [[llGetRegionTimeDilation|time dilation]] (lag).
*Sensors placed in attachments will use the direction the avatar is facing as their forward vector. In mouselook, this means that it will be wherever the avatar is looking, while out of mouselook, this means whichever way the avatar is pointing. This does not include where the avatar's head is pointing, or what animation the avatar is doing, just the direction the avatar would move in if you walked forward. This is the case, regardless of where the object is attached.
* Only the most recent [[sensor]] event is queued. Previous sensor events are replaced.
* A repeating sensor does not persist across a state change.
* [[llSensorRepeat]] can occasionally detect outside of it's specified range every few cycles when used near sim borders. [[llSensor]] in a [[timer]] does not.
|examples=
<lsl>// Written by Steamy Latte.
// Scans every 30 seconds for visitors within 10 meters.
// Reports new visitors to object owner when she is in range.

string AllAgents;
string OwnerName;

default
{
state_entry()
{
// arc=PI is a sphere, you could look more narrowly in the direction object is facing with PI/2, PI/4 etc.
// don't repeat this too often to avoid lag.
llSensorRepeat("", "", AGENT_BY_LEGACY_NAME, 10.0, PI, 30.0);
}
sensor(integer num_detected)
{
string thisAgent = "";
integer agentNum;
for (agentNum=0; agentNum<num_detected; agentNum++)
{
key thisKey = llDetectedKey(agentNum);
string thisAgent = llDetectedName(agentNum);
if (thisKey == llGetOwner())
{
if (AllAgents != "")
{
llOwnerSay("We've had the following visitors:" + AllAgents);
AllAgents = "";
}
}
else if (llSubStringIndex(AllAgents+"\n", "\n"+thisAgent+"\n") < 0)
{
AllAgents = AllAgents + "\n" + thisAgent;
}
}
}
}</lsl>

<lsl>
// Written by Evans Love.
// (Limited to most recent 200 names by Void Singer to prevent eventual Stack/Heap Collision + clean up)
// Continuously scans for visitors within 10 meters and reports new visitors to object owner.
//-------------------------------------------------------------------------------------

integer RESPONSE_CHANNEL = -100;
float SCAN_RANGE = 10.0;
float SCAN_INTERVAL = 0.1;
list VISITOR_LIST;

default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT_BY_LEGACY_NAME, SCAN_RANGE, PI, SCAN_INTERVAL);
}

sensor(integer number_detected)
{
integer agent_number;

// iterate through all detected agents
for (; agent_number < number_detected; agent_number++)
{
string this_agent_name = llDetectedName(agent_number);
key this_agent_key = llDetectedKey(agent_number);
integer index = llListFindList(VISITOR_LIST, [this_agent_name]);

// if the agent is not found on the list
if (index == -1)
{
// add her/him and make the list hold the last 200 visitors
VISITOR_LIST = [this_agent_name] + llList2List(VISITOR_LIST, 0, 198);

llDialog(this_agent_key, "Welcome!", ["Ok"], RESPONSE_CHANNEL);

llOwnerSay(this_agent_name);
}
// else agent is already on the list
}

}
}
</lsl>
|helpers
|also_functions=
{{LSL DefineRow||[[llSensor]]| Runs a sensor once}}
{{LSL DefineRow||[[llSensorRemove]]| Stops the llSensorRepeat timer}}
{{LSL DefineRow||[[llOverMyLand]]| What happens over owners land}}
|also_events=
{{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}
{{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}
|also_articles
|notes=
{{LSL Tip|You might want to use [[llGetAgentList]] instead of using sensors to get a list of all avatars within the same parcel or region.}}
|cat1=Sensor
|cat2=Detected
|cat3=Username/As A Parameter
|cat4=Legacy Name/As A Parameter
|haiku={{Haiku|Binoculars raised,|All eyes scan the horizon.|Ever vigilant.}}
}}

Category:LSL Key

2014-09-09T21:26:49Z

Omei Qunhua: -1 meaning NOT FOUND is not a generic error. Having to explain that ERR_GENERIC has the value -1 demonstrates the futility of its use.

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

== Intro: ==

A key is a '''universal unique identifier''' in Second Life for anything mostly, be it a [[prim]], [[avatar]], [[:Category:LSL_Texture|texture]], etc.

You may see key referred to as [[UUID]], UID, "Asset UUID", or "asset-ID".

The key itself is formed of {{Wikipedia|Hexidecimal|hexadecimal}} characters <code>[0-9a-f]</code> and each section of the key is broken up by dashes (for a total amount of 36 characters).

<lsl>
key whatever = "01234567-89ab-cdef-0123-456789abcdef";
</lsl>

'''Some keys''' in Second Life are a [http://en.wikipedia.org/wiki/UUID#Version_4_.28random.29 UUID-4] as defined in {{RFC|4122|target=section-4.1.3}}.

<lsl>
key uuid = "xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx";

// where:
// 4 is 4
// x is [0-9a-f]
// y is [8-9a-b]
</lsl>

== Receiving keys: ==

There are several ways to acquire the key of something:

# Having someone supply it to you;
# Using a built-in [[LSL_Portal|LSL]] [[:Category:LSL_Functions|function]] such as [[llGetKey]], [[llGetLinkKey]] etc.
# In your inventory, right-clicking over something and choosing <code>Copy Asset UUID</code>. Note this will only work on items that you have full permissions to.

== Generating keys: ==

Built-in [[LSL_Portal|LSL]] [[:Category:LSL_Functions|functions]]:

{|{{Prettytable}}
|+
|-{{Hl2}}
!function
!purpose
|-
|| [[llGenerateKey]] || Generates a key using [http://en.wikipedia.org/wiki/UUID#Version_5_.28SHA-1_hash.29 Version 5 (SHA-1 hash)] [[UUID]] generation to create a unique key.
|}

User-defined functions:
{|{{Prettytable}}
|+
|-{{Hl2}}
!function
!purpose
|-
|| [[GenerateKey]] || Generates an MD5-based (version 3) type UUID. Useful for identifying link-messages and for other purposes.
|-
|| [[GenUUID]] || Generates a UUID based on PHP com_create_guid.
|}

== Converting Keys: ==

When a key is supplied to you as a text [[string]], you convert it to the key data-type like this:

<lsl>key whatever = (key)"01234567-89ab-cdef-0123-456789abcdef";</lsl>

Implicit conversion will happen automatically when supplying a string where a key is required.

<lsl>key uuid = "01234567-89ab-cdef-0123-456789abcdef";
llKey2Name("01234567-89ab-cdef-0123-456789abcdef");</lsl>

However there is no implicit conversion with [[llListFindList]]. [[llListFindList]] requires not only the values to match but also the types.

<lsl>llListFindList(["01234567-89ab-cdef-0123-456789abcdef"], [(key)"01234567-89ab-cdef-0123-456789abcdef"]) == -1;</lsl>

== Displaying avatar or group information: ==

If you know an avatar's key, you can display the avatar's name in the viewer window and chat history by using the following special URL:
<lsl>llOwnerSay("secondlife:///app/agent/" + (string)owner_key + "/about");</lsl>

This displays both [[Display names|display name]] and [[Usernames|username]] as a clickable link that brings up an avatar profile window when clicked. It is easier than using [[llRequestAgentData]] or [[llRequestUsername]] or [[llRequestDisplayName]], since there is no need to use a [[dataserver]] event.

If you know a group key (as a result of calling <code>[[llGetObjectDetails]]([[key]] id, <nowiki>[</nowiki>[[OBJECT_GROUP]]<nowiki>]</nowiki>)</code>, or calling <code>[[llGetParcelDetails]]([[vector]] pos, <nowiki>[</nowiki>[[PARCEL_DETAILS_GROUP]]<nowiki>]</nowiki>)</code>), you can display the group's name with the following special URL:
<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>

This displays the group name as a clickable link that brings up a group profile window when clicked. This is especially useful since there is no other way to do this; there is no LSL function to print out a group's name.

Finally, if you know a [[Land#Parcel|parcel]] key (as a result of calling <code>[[llGetParcelDetails]]([[vector]] pos, <nowiki>[</nowiki>[[PARCEL_DETAILS_ID]]<nowiki>]</nowiki>)</code>), you can create a clickable link that brings up a place profile window when clicked, using the following special URL:
<lsl>llOwnerSay("secondlife:///app/parcel/" + (string)parcel_key + "/about");</lsl>

== Testing for a valid key: ==

To test for a valid key, just do this:

<lsl>if(uuid){
//do something
}</lsl>

<code>if(uuid)</code> will only return true if it is supplied a key that is both (A) valid, and (B) NOT a [[NULL_KEY]].

Tip! In techy talk, this method is called "passing it as the parameter for a {{LSLGC|Conditional|conditional}}"

Note! It is important for the above example that <code>uuid</code> be defined as a key. It can of course be typecast to be a key as well: <code>if((key)uuid)</code>

Here is an example of how to build a function around this:

<lsl>
// 2: valid key, not NULL_KEY
// 1 (TRUE): NULL_KEY
// 0 (FALSE): not a key

integer isKey(key in)
{
if (in)
return 2;
return (in == NULL_KEY);
}
</lsl>

== Caveats: ==

* <lsl>if (uuid)</lsl> is a special case. Keys cannot be converted to [[Integer|integers]], so logical [[LSL_Operators|operators]] such as <code>!</code>, <code>||</code> and <code>&&</code> cannot be used with keys. If you wish to do <lsl>if (!uuid) { /* wont work */ }</lsl> then you can use a simple workaround like so: <lsl>if (uuid) { } else { /* will work */ }</lsl> This is particularly useful if we wish to discard invalid string content (i.e - ensure that a key is actually a key) like so:<lsl>if (uuid) ; else uuid = NULL_KEY;</lsl>
* Be careful when adding key literals to lists, no implicit typecasting will take place. Failing to ensure that key literals are keys will cause problems with [[llListFindList]].
* Further more LSO and Mono do not work the same when it comes to typecasting strings to keys.
** There is a bug in LSO that LL has declined to fix, the reason given is that fixing it would break existing content.

Give InvItem every n hours

2014-09-09T21:20:34Z

Omei Qunhua: -1 meaning not found, is not a generic error

{{LSL Header}}
This script will give an inventory item on touch only every n hours, even if somebody touches the object more than once.

<lsl>
// Idea and written by Criz Collins
// Don't sell this FREE script!!!

string giveitem = "name of item in objects inventory";
float giveevery = 24; // hours!

/////////////////////////////////////////////

list visitors;
list lastsent;
integer n;

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

changed(integer change)
{
if (change & CHANGED_INVENTORY)
{
llResetScript();
}
}

touch_start(integer total_number)
{
for (n=0; n<total_number; n++)
{
integer giveallowed = FALSE;
integer index = llListFindList( visitors, [ llDetectedKey(n) ] );
if (index == -1)
{
visitors = visitors + [ llDetectedKey(n) ];
lastsent = lastsent + [(integer)llGetUnixTime()];
giveallowed = TRUE;
}
else
{
if (llList2Integer(lastsent, index) <= ((integer)llGetUnixTime() - (giveevery * 60 * 60)))
{
list replacer = [(integer)llGetUnixTime()];
list newlastsent = llListReplaceList(lastsent, replacer, index, index);
lastsent = [];
lastsent = newlastsent;
giveallowed = TRUE;
}
// else giveallowed = FALSE;
}
if (giveallowed)// == TRUE
{
llGiveInventory(llDetectedKey(n), giveitem);
}
}
}
}
</lsl>

[[User:Criz Collins|Criz Collins]] 11:14, 11 June 2008 (PDT)

{{LSLC|Library|Give InvItem every n hours}}

One Script, many doors

2014-09-09T21:17:05Z

Omei Qunhua: -1 returned by llListFindList etc. is not a generic error. It has a specific known meaning.

This script is my attempt at solving the massive amount of simple door scripts one can have in a sim (I removed about 110 door scripts in my sim using this system)

It handles clockwise and counter clockwise door direction, a name-based access control list, play sounds, and the root prim reports memory free (useful for REALLY big door sets).

HOW TO USE IT
-------------

All your doors have to be one prim, typical cube with a path cut of 0.125 0.625 .

* All your doors must be linked to a root prim which won't be a door.
* All the doors must be uniquely named.
* All the doors must have "left" or "right" in their description depending on the direction you want them to swing to.

* In the root prim you will need 3 rezzable objects (simple cubes will do) named "open" , "close" and "lock" with, in them, the corresponding scripts (see at the bottom of the page) in order to play sounds at the right place.

* You need a configuration notecard called "config"

main door script: must be in the root prim of the door link set.
<lsl>
/*******************************************
Single script, linked, lockable, door system
by Kyrah Abattoir

allow you to control many doors from a single
core script, complete with sound projectors
and name based access control!
*******************************************/

float autoclose_time = 30.0;//define how long the script will wait before closing a door.
float activation_distance = 2.0;//define how long the script will wait before closing a door.

//This functions is from Nomad Padar, pretty awesome!
//encode from vector to integer
integer vec2int(vector v)
{
integer x = (integer)(v.x);
integer y = (integer)(v.y);
integer z = (integer)(v.z);
integer out;

//Rounds to 0, .5, or 1.0
float delta = v.x-x;

if((delta>.25) && (delta<.75))
out += 0x10000000;
else if(delta>.75)
out += 0x1;

delta = v.y-y;

if((delta>.25) && (delta<.75))
out += 0x20000000;
else if(delta>.75)
out += 0x100;

delta = v.z-z;

if((delta>.25) && (delta<.75))
out += 0x40000000;
else if(delta>.75)
out += 0x10000;

out += x+(y<<8)+(z<<16);
return out;
}

list door_names = [];//door list
list door_num = [];//corresponding link numbers
list door_closed_rot = [];//corresponding closed state rotation
list door_direction = [];//which direction the door spin open
list door_open = [];//is the door open?
list door_open_time = [];//when was it open?
list door_acl = [];//who can open the door (by user id)
list door_pos = [];//the position of the door

list user_indexes = [];//list of users (user ids)

integer is_active = FALSE;//if this is false the script ignore touches

recount_doors()
{
//this function recount the doors and record all the different door characteristics
//only ran after script reset/when an object is linked/unlinked
is_active = FALSE;
llSetText("recounting doors...",<1.0,1.0,1.0>,1.0);
integer prims = llGetNumberOfPrims();

integer i;
for(i=2;i<=prims;i++)
{
key prim = llGetLinkKey(i);
list tmp = llGetObjectDetails(prim,[OBJECT_NAME,OBJECT_DESC,OBJECT_ROT,OBJECT_POS]);
string prim_name = llList2String(tmp,0);
string prim_descr = llList2String(tmp,1);
rotation prim_rot = (rotation)llList2String(tmp,2);
vector prim_pos = (vector)llList2String(tmp,3);

door_num += [i];
door_names += [prim_name];
door_closed_rot += [prim_rot];
door_open += [FALSE];
door_open_time += [0];
if(prim_descr == "right")
door_direction += [TRUE];
else
door_direction += [FALSE];
door_acl += [""];
door_pos += [prim_pos];
}
llSetText("...done!",<1,1,1>,1.0);
reload_acl();
}

string config = "config";//name of the configuration file
integer nLine = 0;//current line we are reading

//this function re read the config notecard and populate the
//user list and acl table
reload_acl()
{

llSetText("reloading access controls...",<1,1,1>,1.0);
is_active = FALSE;
nLine = 0;
//remove all acl
integer i;
for(i=0;i<llGetListLength(door_num);i++)
door_acl = llListReplaceList(door_acl,[""],i,i);

user_indexes = [];
llGetNotecardLine(config,nLine);
}

//close a door (by index) using the stored rotation
close(integer index)
{
integer linknum = llList2Integer(door_num,index);

rotation closed = llList2Rot(door_closed_rot,index);
llSetLinkPrimitiveParams(linknum,[PRIM_ROTATION,closed]);

door_open = llListReplaceList(door_open,[FALSE],index,index);
}

//close a door (by index) using the stored rotation and adding or substracting 90 degrees
//on the Z world axis depending of the direction recorded for the door.
//also record it's opening time (unix timestamp)
open(integer index)
{
integer linknum = llList2Integer(door_num,index);
rotation closed = llList2Rot(door_closed_rot,index);
rotation open;
if( llList2Integer(door_direction,index) )
open = llEuler2Rot(llRot2Euler(closed)+ (<0,0,90> *DEG_TO_RAD));
else
open = llEuler2Rot(llRot2Euler(closed)+ (<0,0,-90> *DEG_TO_RAD));
llSetLinkPrimitiveParams(linknum,[PRIM_ROTATION,open]);

door_open_time = llListReplaceList(door_open_time,[llGetUnixTime()],index,index);
door_open = llListReplaceList(door_open,[TRUE],index,index);

llSetTimerEvent(1.0);
}

//those 3 functions rez a sound emitter with it's destination position encoded in integer
play_open(vector pos)
{
llRezObject("open",llGetPos(),ZERO_VECTOR,ZERO_ROTATION,vec2int(pos));
}
play_close(vector pos)
{
llRezObject("close",llGetPos(),ZERO_VECTOR,ZERO_ROTATION,vec2int(pos));
}
play_lock(vector pos)
{
llRezObject("lock",llGetPos(),ZERO_VECTOR,ZERO_ROTATION,vec2int(pos));
}

default
{
touch_start(integer total_number)
{
integer userid;

if(!is_active)
return;

//considering we MAY receive more than one touch at the same time since
//we can manage many doors.
for(userid=0;userid<total_number;userid++)
{
integer door_id = llDetectedLinkNumber(userid);
string clicker_name = llDetectedName(userid);

integer door_index = llListFindList(door_num,[door_id]);
if(door_index == -1)
return;//unknown door? do nothing

integer is_open = llList2Integer(door_open,door_index);
vector door_vec = llList2Vector(door_pos,door_index);

//we do not accept touches that are further away from activation_distance
if( llVecDist(door_vec,llDetectedPos(userid) )> activation_distance )
llInstantMessage(llDetectedKey(userid),"You can't use this from this distance.");
else
{
if(is_open)
{ //if the door is open, simply play sound and close it.
play_close(door_vec);
close(door_index);
}
else
{
string acl_string = llList2String(door_acl,door_index);

//if the acl string is empty for this door we simply open it
if(acl_string == "") //no specific locking
{
play_open(door_vec);
open(door_index);
}
else
{
//otherwise we lookup if the userid that correspond to the person who touched
//the door match any of the ones in the ACL string
integer user_index = llListFindList(user_indexes,[clicker_name]);

if(user_index == -1) //we don't even know this user? sure as hell there is no acl about him
play_lock(door_vec);
else
{
list acl_list = llParseString2List(acl_string,[","],[]);

if(llListFindList(acl_list,[(string)user_index]) != -1)
{
play_open(door_vec);
open(door_index);
}
else
play_lock(door_vec);
}
}
}
}
}
}
dataserver(key id,string data)
{
//notecard reading stuff
if(data != EOF)
{
if(data != "" && data != " " && llGetSubString(data,0,1) != "//")
{
list command_and_data = llParseString2List(data,["="],[]);
string door_name = llList2String(command_and_data,0);
string user_names_string = llList2String(command_and_data,1);

integer index = llListFindList(door_names,[door_name]);
if(index != -1)
{
list user_names_list = llParseString2List(user_names_string,[","],[]);
integer j;

list pre_acl_list;
for(j=0;j<llGetListLength(user_names_list);j++)
{
string user_name = llList2String(user_names_list,j);
integer index2 = llListFindList(user_indexes,[user_name]);
if( index2 == -1)
{
pre_acl_list += llGetListLength(user_indexes);
user_indexes += [user_name];
}
else
pre_acl_list += [index2];

}
string pre_acl_string = llDumpList2String(pre_acl_list,",");
door_acl = llListReplaceList(door_acl,[pre_acl_string],index,index);
}
}
nLine++;
llGetNotecardLine(config,nLine);
}
else
{
is_active = TRUE;
llOwnerSay("config reloaded");
llSetText((string)llGetFreeMemory()+"bits free",<.5,.5,.5>,.5);
}
}
state_entry()
{
recount_doors();
}
changed(integer change)
{
//if we detect an inventory change we reread the notecard
//if we detect a linkchange we reset the script and recount doors first
if( (change & CHANGED_INVENTORY) == CHANGED_INVENTORY)
reload_acl();
if( (change & CHANGED_LINK) == CHANGED_LINK)
llResetScript();
}
timer()
{
//timer will run once a second as long as at least one door is open.
if(llListFindList(door_open,[TRUE]) == -1)
{
llSetTimerEvent(0.0);
return;
}
integer i;

//each run of the timer we loop through the timestamps to check if one of them is too old
//(which means we can force close the associated door
for(i=0;i<llGetListLength(door_open_time);i++)
{
integer is_open = llList2Integer(door_open,i);
integer time = llList2Integer(door_open_time,i);
if( is_open && ((time + autoclose_time) < llGetUnixTime()))
{
vector door_vec = llList2Vector(door_pos,i);
llRezObject("close",llGetPos(),ZERO_VECTOR,ZERO_ROTATION,vec2int(door_vec));
close(i);
}
}
}
}
</lsl>

Sound emitter script
--------------------
You need this script in the 3 rezzable objects "open" "close" and "lock" in order to play your door sounds at the right place (At the time i wrote this , lsl doesn't allow yet to play sounds from an unscripted prim in a link set)

<lsl>
string sound_to_play = "my door sound";// put your sound name/key here

//This functions is from Nomad Padar, pretty awesome!
//decode from integer to vector
vector int2vec(integer n)
{
//0zyx ZZZZ ZZZZ ZZZZ YYYY YYYY XXXX XXXX
return <n&0xFF, (n>>8)&0xFF, ((n>>16)&0xFF)> + <((n&0x10000000)!=0)*.5,((n&0x20000000)!=0)*.5,((n&0x40000000)!=0)*.5>;
}

default
{
state_entry()
{
llSetStatus(STATUS_PHANTOM, TRUE);
llSetPrimitiveParams([PRIM_TEMP_ON_REZ, TRUE]);
llSetTexture(TEXTURE_TRANSPARENT,ALL_SIDES);
}
on_rez(integer a)
{
if(a == 0)
return;

vector destination = int2vec(a);

integer i;
for(i=0 ; i<50 && (llGetPos() != destination) ; i++)
llSetPos(destination);

if(llGetPos() == destination)
llTriggerSound(sound_to_play,1.0);
llDie();
}
}
</lsl>
Example "config" notecard:
//lines starting with "//" are ignored
//Syntax: one line per door in the format door_name=user name,user name

My fancy front door=Kyrah Abattoir
My secret playroom door=Kyrah Abattoir,Timeless Prototype

//of course if you want to lock a door from anybody you can set it to something like this:

Mine entrance=condemned until further notice
--[[User:Kyrah Abattoir|Kyrah Abattoir]] 18:46, 7 March 2010 (UTC)

Name2Key in LSL

2014-09-09T21:00:56Z

Omei Qunhua: Undo revision 1182279 usual reasons

{{LSL Header}}__NOTOC__

== Name2Key ==
Still missing Name2Key functions in your code? Still relying on external databases that are not always up to date with latest SL subscribers?

Well now you can solve this by yourself, within your LSL script! All you have to do is to rely on LL Search engine!

I put a kind of "library" and a sample of usage for your convenience

Takat Su: I placed an alternate implementation up that does not depend on the babelfish proxy nor having your own proxy here: [[User:Takat Su/Name2Key]]

<div id="box">

== Library ==

<lsl>
integer SERVICE_NAME2KEY = 19790;
integer SERVICE_NAME2KEY_RET = 19791;

string proxy = "http://66.196.80.202/babelfish/translate_url_content?&intl=us&lp=ko_en&trurl=";
string search = "http://vwrsearch.secondlife.com/client_search.php?session=00000000-0000-0000-0000-000000000000&q=";
string result = "secondlife:///app/agent/";
string profile = "Resident profile";
string notfound = "There were no matches for ";

list requests;

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

state_entry()
{
requests = [];
}

link_message(integer s, integer n, string m, key i)
{
if (n == SERVICE_NAME2KEY) {
if(llListFindList(requests,[m]) == -1) {
list Args=llParseString2List(m, [" "], []);

string FirstName = llList2String(Args, 0);
string LastName = llList2String(Args, 1);

string url = proxy+llEscapeURL(search)+FirstName+"%2520"+LastName;;
key id = llHTTPRequest(url, [], "");
requests += [id,m];
}
}
}

http_response(key request_id, integer status, list metadata, string body)
{
integer p = llListFindList(requests,[request_id]);
if (p != -1) {
string name = llList2String(requests,p+1);
integer find = llSubStringIndex(body,result);
if(find == -1) {
find = llSubStringIndex(body,notfound);
if(find == -1)
llMessageLinked(LINK_SET,SERVICE_NAME2KEY_RET,"Error with lookup!",NULL_KEY);
else
llMessageLinked(LINK_SET,SERVICE_NAME2KEY_RET,name+" not found.",NULL_KEY);
}
else
{
find += llStringLength(result);
string avKey = llGetSubString(body,find,find+35);
integer namePos = llSubStringIndex(body,profile)+17;
string foundName = llGetSubString(body, namePos+1,
namePos + llSubStringIndex(llGetSubString(body,namePos+1, llStringLength(body)-1),"<"));
if(llToLower(name) == llToLower(foundName))
llMessageLinked(LINK_SET,SERVICE_NAME2KEY_RET,foundName,(key)avKey);
else
llMessageLinked(LINK_SET,SERVICE_NAME2KEY_RET,name+" failed: Wrong found.",NULL_KEY);
}
requests = llDeleteSubList(requests,p,p+1);
}
}
}
</lsl>
</div>

<div id="box">
== Usage sample ==
<lsl>
integer SERVICE_NAME2KEY = 19790;
integer SERVICE_NAME2KEY_RET = 19791;

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

state_entry()
{
llListen(1, "", "", "");
}

listen(integer c, string n, key i, string m)
{
llSay(0,"Requesting key for "+m);
llMessageLinked(LINK_THIS, SERVICE_NAME2KEY, m, "");
}

link_message(integer f, integer n, string s, key i)
{
if(n == SERVICE_NAME2KEY_RET) {
if(i == NULL_KEY)
llSay(0,"Lookup failed. Returned: "+s);
else
llSay(0,s+": "+(string)i);
}
}
}
</lsl></div>

<div id="box">
== Comments ==
<div style="padding: 0.5em;">
Hope this helps !
[[User:Maeva Anatine|Maeva Anatine]]

EDIT : Looks like the Lindens have either broken or blocked this function. It works from my browser, however from LSL I get an error page containing this message "Access control configuration prevents your request from
being allowed at this time. Please contact your service provider if
you feel this is incorrect." - Darling Brody.

EDIT : Yes you're right Darling. It seems they've blocked this access from within the world... I still wonder why, especially as there are some workarounds to this...
Anyway I discovered there is a JIRA issue for this. Please vote for the unblock !
https://jira.secondlife.com/browse/SVC-3122
- Mae

EDIT : OK after having read this article from LL: [[SearchAPI]], it seems proxy usage is allowed. So I modified the upper code in order to go through a proxy machine and it works again :)
- Mae

EDIT: After review, it appears the Yahoo Babelfish proxy you are using above does not return the results expected. I rewrote this to allow different proxies by a simple configuration. This now uses Google instead of Babelfish by default. This does not, however, work for any avatars that do not have a Profile filled out (this is due to a limitation of the Googly proxy we're using here). I'm researching this and trying to see if there is a better proxy to use.

This version can handle multiple requests at once. Replies have changed slightly, as the found key is returned in the "key" field instead of the message field. In addition, failure of any kind results in a NULL_KEY being returned, and status information is returned in the message field. - [[User:Sensei Schism|Sensei Schism]]

EDIT 2009-Mar-08: Sensei, I reused your version here above and took back BabelFish as Google one is unable to retrieve all links (doesn't recognized correctly the secondlife:/// link). In addition, I made some slight changes as LL recently changed their search engine. This version now works properly.

EDIT 2009-Aug-27: LL changed the search URL from '''search'''.secondlife.com/client_search.php to '''vwrsearch'''.secondlife.com/client_search.php
[[User:ab Vanmoer|ab Vanmoer]]

EDIT 2009-Sep-04: The problem with the proxy you have there is that it translates the name as a french name, and if it happens to be a real french word, then the name gets changed to that. for example the last name of Vella got changed to Calved, so no match was made. PS. I also found some names had been surrounded by bold tags. So, since i have a few websites i can run PHP on i got [http://sourceforge.net/projects/php-proxy/ PHP Web Proxy] and point to it. Also, I used: body = llDumpList2String(llParseStringKeepNulls(body, ["", ""], []), ""); to remove the bold tags.
-Spritely Pixel

EDIT 2009-Sep-19: Changed the translation from French to Korean on the theory that there are very few names that contain valid Korean characters, thus the translation should just pass straight through. Changes were: 1. Change the proxy URL to use ko_en instead of fr_en. 2. Change the profile search string from "Resident profiles" to "Resident profile" (note change from plural to singular) and changed the name offset to account for the (now missing) 's'. Also note that Babel will sometimes return an advertising page instead of the translation. Thus, you should be prepared to retry the search a few times if you get a page that doesn't make sense.[[User:Takat Su|Takat Su]]

EDIT 2009-Sep-20: Got fed up with the babel translation thing. Apparently, if you make too many requests, Yahoo throttles you for between 2 and 24 hours. So I made a relay for the Google appspot engine and replicated this page with the new code here: [[User:Takat Su/Name2Key]] [[Takat Su|Takat Su]]

</div></div>
[[User:Maeva Anatine|Maeva Anatine]]

{{LSLC|Library}}{{LSLC|Examples|Name2Key}}

LSL Style Guide

2014-09-09T14:54:49Z

Omei Qunhua: -1 returned from llListFindList has a specific known meaning It is not a "generic error" covering a multitude of sins. PUBLIC_CHANNEL has been voted out

{{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'''
|-
||
<lsl>default {state_entry(){llSay(0,"Hello World.");}}</lsl>
|}

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)'''
|-
||<lsl>
default {
state_entry() {
llSay(0, "Hello World.");
}
}
</lsl>
||
<lsl>
default
{
state_entry()
{
llSay(0, "Hello World.");
}
}
</lsl>
|}

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 through out the entire program) should be lowercase. For example:

<lsl>
integer index = 0;
string name = "Please set one";
</lsl>

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

<lsl>
integer gIndex;
string gName = "Please set one";
</lsl>

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

<lsl>
integer DIALOG_CHANNEL = -517265;
vector RED = <1.0, 0.0, 0.0>;
</lsl>

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]]:

<lsl>
// ...

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

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

// ...
</lsl>

== 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.

<lsl>
list lst;
integer numDigits = 10;

default {
touch_start(integer n) {
integer i;
integer index = llListFindList(lst, [llToLower(llGetSubString(llList2String(llParseString2List(llKey2Name(llDetectedKey(i)), [" "], []), 0), 0, numDigits - 1))]);
if (!~llListFindList(lst, [llToLower(llGetSubString(llList2String(llParseString2List(llKey2Name(llDetectedKey(i)), [" "], []), 0), 0, numDigits - 1))]))
lst += llToLower(llGetSubString(llList2String(llParseString2List(llKey2Name(llDetectedKey(i)), [" "], []), 0), 0, numDigits - 1));
llOwnerSay(llList2CSV(lst));
}
}
</lsl>

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.

<lsl>
list listOfStrings;
integer numDigits = 10;

default
{
touch_start(integer n)
{
key owner = llGetOwner();
key id = llDetectedKey(0);
string name = llDetectedName(0);// or llKey2Name(id)

list nameAsList = llParseString2List(name, [" "], []);
string firstName = llList2String(nameAsList, 0);
string startPart = llToLower(llGetSubString(firstName, 0, numDigits - 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
llRegionSayTo(owner, 0, llList2CSV(listOfStrings));
}
}
</lsl>

LSL lacks an optimizing compiler. For this reason it may be necessary to balance the two style 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 the majority of 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 would ask you 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]].

3D Radar

2014-09-08T10:57:50Z

Omei Qunhua: Re-instate the object re-name. This does have a purpose. It obviates manually renaming "object" to "scan ball", as the comments said.

{{LSL Header}}

*[[User:Jesse_Barnett|Click Here]] To see my page and more of my scripts

==Scripts have been corrected and working properly now==

Rezzes a ball for each avatar in range. Each ball tracks it's on AV and displays distance.

==Scanner/Rezzer Script==
Place this script in a prim along with the scan ball. When touched it will scan the surrounding area and rezz a ball for each avatar.

Suggestion: Create a sphere with a diameter of 2 meters. Set transparency about 60. Create another sphere about 0.05 diameter, color a dark color and put it in the center of the large prim. Select small prim 1st and then large prim and link them. This will give you a center point to reference. The scan ball script is set to scan for it's avatar to a range of 96 meters.

This formula: vector avDivPos = (avPos - rPos) * 0.010417; Takes the (avatars position - position of scanner) & multiplies by (radius of the distance you want the balls to go(2 meter sphere = 1 meter radius)/scan range(96meters)):

1/96 = approximately 0.010417.

<lsl>
//////////////////////////////////////////////////////////////////////////////////////////////////////
// 3D Radar 2.5
// "Oct 15 2008", "18:43:28"
// Creator: Jesse Barnett
// Released into the Public Domain
//////////////////////////////////////////////////////////////////////////////////////////////////////

integer Scan = TRUE;
string avKey;
integer list_pos;
list key_list;
integer key_chan; //Key channel is generated randomly and passed to the scan ball
integer die_chan = -9423753; //Hey pick your own channels and be sure to paste them into the scan balls too!
integer key_rem_chan = -49222879;

default
{

touch_start(integer total_number)
{
if (Scan)
{
llSensorRepeat("", "", AGENT, 96, PI, 1);
key_list =[];
llListen(key_rem_chan, "", "", "");
llOwnerSay("on");
Scan = FALSE;
}
else
{
llSensorRemove();
llRegionSay(die_chan, "die");
llOwnerSay("off");
Scan = TRUE;
}
}

sensor(integer iNum)
{
integer p = 0;
for (p = 0; p < iNum; ++p)
{
avKey = llDetectedKey(p);
list_pos = llListFindList(key_list, (list)avKey);
if (list_pos == -1)
{
key_list += (list) avKey;
key_chan = (integer) llFrand(-1000000) - 1000000;
llRezObject("scan ball", llGetPos(), ZERO_VECTOR, ZERO_ROTATION, key_chan);
llSleep(.25);
llRegionSay(key_chan, avKey);
}
}
}

listen(integer c, string name, key id, string msg)
{
integer r = llListFindList(key_list,[(key)msg]);
key_list = llDeleteSubList(key_list, r, r);
}
}
</lsl>

==Scan Ball Script==
Place this script in a prim and then place the prim into the inventory of the Scanner/Rezzer. It will automatically name itself.

Suggestion; Create a sphere prim of 0.05 diameter with glow set about .80.
<lsl>
//////////////////////////////////////////////////////////////////////////////////////////////////////
// 3D Radar 2.5
// "Oct 15 2008", "18:44:36"
// Creator: Jesse Barnett
// Released into the Public Domain
//////////////////////////////////////////////////////////////////////////////////////////////////////

string avName;
integer avDistance;
key avKey;
integer avListen;
integer key_chan;
integer die_chan = -9423753;
integer key_rem_chan = -49222879;
vector avPos;
vector rPos;
key owner;

default
{

state_entry()
{
llSetObjectName("scan ball"); //Renames the object to "scan ball"
owner = llGetOwner(); // Lets check to see what the key of the owner of the object is and save it for later
}

on_rez(integer start_param)
{
rPos = llGetPos();
key_chan = start_param;
llListen(die_chan, "", "", "");
avListen = llListen(key_chan, "", "", "");
}

listen(integer c, string n, key id, string msg)
{
if (c == die_chan && msg == "die" && owner == llDetectedOwner(0)) //Lets check to see if the message we heard matches all the criteria for the kill command
{ //(Right channel, right message and from radar owned by same owner)
llDie();
}

else
{
avKey = (key) msg;
avName = llKey2Name(avKey);
llSensorRepeat("", avKey, AGENT, 96, PI, 1.0);
llListenRemove(avListen);
}
}

sensor(integer n)
{
avPos = llDetectedPos(0);
vector avDivPos = (avPos - rPos) / (96 / 1); //Scan range/Radius of large sphere
avDistance = (integer) llVecDist(rPos, llDetectedPos(0));
llSetPos(rPos + avDivPos);
llSetText(avName + "[" + (string) avDistance + "]", <1, 1, 1 >, 1);
}

no_sensor()
{
llRegionSay(key_rem_chan, avKey);
llDie();
}
}
</lsl>
{{LSLC|Library|3D Radar}}

3D Radar

2014-09-08T10:44:39Z

Omei Qunhua: Correct indenting tab size

{{LSL Header}}

*[[User:Jesse_Barnett|Click Here]] To see my page and more of my scripts

==Scripts have been corrected and working properly now==

Rezzes a ball for each avatar in range. Each ball tracks it's on AV and displays distance.

==Scanner/Rezzer Script==
Place this script in a prim along with the scan ball. When touched it will scan the surrounding area and rezz a ball for each avatar.

Suggestion: Create a sphere with a diameter of 2 meters. Set transparency about 60. Create another sphere about 0.05 diameter, color a dark color and put it in the center of the large prim. Select small prim 1st and then large prim and link them. This will give you a center point to reference. The scan ball script is set to scan for it's avatar to a range of 96 meters.

This formula: vector avDivPos = (avPos - rPos) * 0.010417; Takes the (avatars position - position of scanner) & multiplies by (radius of the distance you want the balls to go(2 meter sphere = 1 meter radius)/scan range(96meters)):

1/96 = approximately 0.010417.

<lsl>
//////////////////////////////////////////////////////////////////////////////////////////////////////
// 3D Radar 2.5
// "Oct 15 2008", "18:43:28"
// Creator: Jesse Barnett
// Released into the Public Domain
//////////////////////////////////////////////////////////////////////////////////////////////////////

integer Scan = TRUE;
string avKey;
integer list_pos;
list key_list;
integer key_chan; //Key channel is generated randomly and passed to the scan ball
integer die_chan = -9423753; //Hey pick your own channels and be sure to paste them into the scan balls too!
integer key_rem_chan = -49222879;

default
{

touch_start(integer total_number)
{
if (Scan)
{
llSensorRepeat("", "", AGENT, 96, PI, 1);
key_list =[];
llListen(key_rem_chan, "", "", "");
llOwnerSay("on");
Scan = FALSE;
}
else
{
llSensorRemove();
llRegionSay(die_chan, "die");
llOwnerSay("off");
Scan = TRUE;
}
}

sensor(integer iNum)
{
integer p = 0;
for (p = 0; p < iNum; ++p)
{
avKey = llDetectedKey(p);
list_pos = llListFindList(key_list, (list)avKey);
if (list_pos == -1)
{
key_list += (list) avKey;
key_chan = (integer) llFrand(-1000000) - 1000000;
llRezObject("scan ball", llGetPos(), ZERO_VECTOR, ZERO_ROTATION, key_chan);
llSleep(.25);
llRegionSay(key_chan, avKey);
}
}
}

listen(integer c, string name, key id, string msg)
{
integer r = llListFindList(key_list,[(key)msg]);
key_list = llDeleteSubList(key_list, r, r);
}
}
</lsl>

==Scan Ball Script==
Place this script in a prim and make sure to name it "scan ball". Then place the prim into the inventory of the Scanner/Rezzer.

Suggestion; Create a sphere prim of 0.05 diameter with glow set about .80.
<lsl>
//////////////////////////////////////////////////////////////////////////////////////////////////////
// 3D Radar 2.5
// "Oct 15 2008", "18:44:36"
// Creator: Jesse Barnett
// Released into the Public Domain
//////////////////////////////////////////////////////////////////////////////////////////////////////

string avName;
integer avDistance;
key avKey;
integer avListen;
integer key_chan;
integer die_chan = -9423753;
integer key_rem_chan = -49222879;
vector avPos;
vector rPos;
key owner;

default
{

state_entry()
{
owner = llGetOwner(); // Lets check to see what the key of the owner of the object is and save it for later
}

on_rez(integer start_param)
{
rPos = llGetPos();
key_chan = start_param;
llListen(die_chan, "", "", "");
avListen = llListen(key_chan, "", "", "");
}

listen(integer c, string n, key id, string msg)
{
if (c == die_chan && msg == "die" && owner == llDetectedOwner(0)) //Lets check to see if the message we heard matches all the criteria for the kill command
{ //(Right channel, right message and from radar owned by same owner)
llDie();
}

else
{
avKey = (key) msg;
avName = llKey2Name(avKey);
llSensorRepeat("", avKey, AGENT, 96, PI, 1.0);
llListenRemove(avListen);
}
}

sensor(integer n)
{
avPos = llDetectedPos(0);
vector avDivPos = (avPos - rPos) / (96 / 1); //Scan range/Radius of large sphere
avDistance = (integer) llVecDist(rPos, llDetectedPos(0));
llSetPos(rPos + avDivPos);
llSetText(avName + "[" + (string) avDistance + "]", <1, 1, 1 >, 1);
}

no_sensor()
{
llRegionSay(key_rem_chan, avKey);
llDie();
}
}
</lsl>
{{LSLC|Library|3D Radar}}

How to Earn Linden Dollars in Second Life

2014-07-06T13:19:23Z

Omei Qunhua: /* Lotteries */ It's not a violation of a game, it' a violation of LL's wagering policies.

{{KBcaution|The majority of this wiki's content (like SL itself) is Resident-created and while it may be helpful, Linden Labs won't vouch for its accuracy. For official documentation, see the '''[http://community.secondlife.com/t5/English-Knowledge-Base/tkb-p/English_KB%40tkb Second Life Knowledge Base]'''.}}

[[File:lindenrealms.png|frame|alt=linden realms|The [http://secondlife.com/destinations/realms Linden Realms] are a great way to earn linden while having fun exploring some beautiful fantasy sims.]]

[[File:goldhunt.png|frame|alt=gold hunt|The [http://www.goldtokens.net/games/gold-hunt Gold Hunt] game allows you to earn linden by searching for coins around the grid. It's a great way to explore the grid and take you to new places.]]
[[File:fishhunt.png|frame|alt=fish hunt|The [http://www.goldtokens.net/games/fish-hunt Fish Hunt] game is a great way to meet other players and compete. It's also really popular with players with disabilities as its very easy to play.]]
[[File:moneytrees.png|frame|alt=money trees|[http://moneytree.wolfhavenproductions.com Money Trees] are a great way for new players to earn linden by picking linden from trees around the grid. Older players aren't allowed to use Money Trees.]]
[[File:capexhq.png|frame|alt=capital exchange|The [http://www.slcapex.com/ Capital Exchange] allows you to invest and speculate on virtual companies in Second Life.]]
[[File:sploders.png|frame|alt=sploders|Sploders are a way of earning small amounts of linden when out at a club or party. They are a good way to meet other players and get chatting.]]

Second Life is full of opportunities to earn Linden Dollars, but it is also important to [https://wiki.secondlife.com/wiki/How_to_Have_Fun_in_Second_Life have fun] while earning. Some players make the mistake of thinking that they have to do something they don't enjoy to make money in Second Life. That's simply is not the case.

Sometimes it can feel overwhelmingly challenging to earn linden in Second Life, but with the right information to hand and some ample determination you can make money.

= Get Paid a Weekly Stipend =

Players who upgrade their account to be a [http://secondlife.com/premium/ Premium Account] are paid a stipend to their account on a weekly basis.

= Buy Linden on the LindeX =

You can buy linden whenever you want on the [https://secondlife.com/my/lindex/market.php LindeX] exchange. However, there are [https://secondlife.com/my/lindex/describe-limits.php billing and trading] limits.

= Earn Linden Playing Fun Games =

== ADS Goldtokens Gaming Network ==

The following games are run by ADS, the leader in earning linden games. The [http://www.goldtokens.net Goldtokens.net] Gaming Network was a community created by [http://www.secondads.com/ SecondAds] company with the goal of helping new players earn their first linden dollars. It's not just for new players though. Thousands of experienced players enjoy competing for leaderboard positions and earning large sums of linden in the process.

'''Gold Hunt'''

The [http://www.goldtokens.net/games/gold-hunt Gold Hunt] allows players to earn linden and win random gifts by hunting for coins and gems that are hidden by landowners. There are literally 1,000s of lands with coins available right across the grid, which can be discovered by using the player HUD.

'''Regulatory warning.''' For an active participation in this activity, it is necessary to make an upfront investment of Linden on a continued basis into virtual items, specifically worms bait. It is also possible to invest into virtual items that can enhance your performance in this activity either temporarily (e.g. premium worms bait, potions, etc.) or permanently (e.g. premium fishing rods; so called "Snubbies" etc.). You may get back less than what you invested.

'''Fish Hunt'''

The [http://www.goldtokens.net/games/fish-hunt Fish Hunt] allows players to earn Linden and win Random Gifts by fishing. There are literally 1,000s of lands with fish buoys available right across the grid, which can be discovered by using the player HUD. You'll also need to get a free beginner fishing rod too.

'''Farm Frenzy'''

[http://www.goldtokens.net/games/farm-frenzy Farm Frenzy] gives land owners the opportunity to earn linden by farming worms for use in the [http://www.goldtokens.net/games/fish-hunt Fish Hunt]. It takes time to develop your Farming Experience, but eventually you'll be able to dominate the farming industry and sell your produce to the masses. Fortunes have been made in the farming industry!

'''Regulatory warning.''' It is mandatory to make an upfront investment of Linden into virtual items, specifically worm farms, worm packs and clean water to participate in this activity, and you may get back less than what you invested.

'''Noob Hunt'''

The [http://www.goldtokens.net Noob Hunt] is an affiliate recruitment scheme for the Goldtokens.net gaming network which allows players to become masters and recruit apprentices for the various games hosted on the network. In return they earn a percentage of each of their apprentices' winnings. You can also sell your apprentices to other masters on the exchange.

== Bletaverse ==

[http://bletaverse.com/ Bletaverse] company have a number of ways of earning linden such as waiting at traffic cones and they also run a social network that players can get involved in.

== Dragons & Princesses ==

The [http://www.dragons.sl/docs/Index Dragons & Princesses] is a cool game developed by [http://www.e2l-net.com/ Earn2Life] company that allows you to earn linden by hunting for voids on different lands around Second Life.

== Linden Realms ==

The [http://secondlife.com/destinations/realms Linden Realms] were created by Linden Lab and are designed with a beautiful environment that has trees, cliffs, and lots of fun places to explore. You can use a teleporter to visit different areas of the Linden Realms. Each place has different quests and other activities that are fun and exciting to do. There are rock monsters that you will have to run away from and pools of toxic water to avoid.

== Money Trees ==

[http://moneytree.wolfhavenproductions.com Money Trees] were created by [http://wolfhavenproductions.com Wolfhaven Productions] and allow players to earn linden by plucking dollar bills and other game items from trees that are planted in sims all around the grid. There is a HUD you can wear to tell you where to find new trees. However, many trees are age-limited, so only very new players can use them.

== The Second Farm ==

The [http://thesecondfarm.com/ The Second Farm] is a campany that created Magic Crystal and Magic Fishing Games.
It is a great way to helping new Second Life Residents to earn linden dollars.

'''Magic Crystals'''

This is a very fun game, you meet wonderful places and can still make magic stars. With these stars you earn more money and even more points for the [http://www.thesecondfarm.com/rank/mctop.php Magic Crystal Rankings].

'''Magic Fishing'''

Magic fishing is a new way to earn lidens by fishing.
You need only a free rod to start and one HUD to find locations to fish.

= Earn Linden Working a Job =

A large proportion of players have some form of [https://wiki.secondlife.com/wiki/Guide_to_Jobs_in_Second_Life Second Life Job] as a means to earn linden. This can be a rewarding way to earn linden and if you have the right ideas you can even become an entrepreneur and start your own business.

= Activity Devices =

There are a wide range of devices that allow you to make money via certain activities. In the order of decreasing interactivity these are:

== Skill Games ==

There are a wide range of skill game machines where Linden can be earned. While these games may resemble real-world casino game machines, they should all comply with {{LLOlink|Policy Regarding Wagering in Second Life|Wagering policy}} and {{LLOlink|Skill Game Compliance}}.

'''Regulatory warning.''' It is mandatory to make an upfront investment of Linden into many of these game machines to play the skill game, and you may get back less than what you invested. The only exception is machines in 'free-play' mode, where an investment is either not required, or is guaranteed to be paid back to you, however no earnings can be achieved from machines operating in this mode.

== Chatting ==

There are a wide range of Chat Sploders such as the ever popular [http://www.secondads.com/chatsploder.php Chatsploder Network] available in various clubs and other areas. These allow you to earn linden by waiting for the 'explosion' which may take quite some time. In the mean time you can chat and make new friends.

== Lotteries ==

These are devices where players first make contributions to an aggregated pot. Once the pot exceeds a threshold, a countdown to an 'explosion' begins (such as 3 mins) during which further contributions are typically still accepted. At the 'explosion' the pot is randomly distributed between contributors.
UPDATE: Be aware of LL's wagering policies as paying to win on a game of chance such as a sploder or lottery can be interpreted as a violation.
There are free sploders which are used to generate traffic that cost nothing to play which are legal. {{LLOlink|Policy Regarding Wagering in Second Life|Wagering policy}} and {{LLOlink|Skill Game Compliance}}.

'''Regulatory warning.''' It is mandatory to make an upfront investment of Linden into the aggregated pot to participate in this activity, and generally you may get back less than what you invested. However there are some devices that guarantee a minimum payout that is equal to the minimum contribution, please check device-generated chat messages.

== Camping ==

These allow you to earn Linden or prizes for camping, e.g. sitting chairs or touch Sploders, which you have to touch to begin a countdown to an 'explosion' at the end of which a landowner's pot of money is randomly distributed between touchers. Some of these devices have you earn Linden, others have you earning other things such as new skins, clothes or other virtual game items. All you have to do touch them or sit on them, then continue camping on them (or reasonably close to some others) for the required amount of time to earn your prize. While some opine it is the least fun way to earn Linden ever invented due to lack of interaction with these devices during the camping time, others argue that it is just as much fun as any other activity, because while camping you are still free to chat and make new friends. A further advantage is that it is a relatively simpler way that does not require much time or physical input, and is therefore quite suitable for people with disabilities.

== Area Camping ==

These are similar to camping devices above, except that you simply need to be present on the land within a certain proximity of the device for the required amount of time to earn your prize, which is typically awarded to a resident chosen at random. These include Random Money Givers, and sometimes require that you become a member of the group owning the land, or add the land to the list of your SL Picks in order to be considered for an award.

= Completing Surveys, Surfing Sites & Web Offers =

It is possible to earn linden by completing surveys, surfing websites or filling web offers. Unfortunately this can be very haphazard and you may not receive payment if you don't fit the demographic that the company is looking for.

= Investing =

If you have some capital to invest you can simply invest in one of the companies listed on the [http://www.slcapex.com/ Capital Exchange] and then hope to earn dividends over time. You can either try to earn Linden by making a long term investment, or you can speculate on daily market movements.

'''Regulatory warning.''' The value of investments and the income from them can fall as well as rise, and you may get back less than what you invested.

= External Articles & Sites=

Please share your external sites and articles here with information on how to earn linden dollars in Second Life here:

== Sites ==
* [http://bletaverse.com/ Bletaverse] - Earn linden while exploring SL without having to make an investment.
* [http://www.e2l-net.com/ Earn2life] - Earn linden on earning programs
* [http://www.goldtokens.net Goldtokens] - Earn linden playing fun games (some games require an upfront investment).
* [http://www.thesecondfarm.com/ The Second Farm] - Earn linden Hunting Magic Crystals.
* [http://wolfhavenproductions.com Wolfhaven Productions] - The creators of money trees

== Articles ==

* [http://www.goldtokens.net/blogs/110/10-ways-to-earn-linden-in-second-life 10 Ways to Earn Linden in Second Life] - 10 ways to Earn Linden in Second Life
* [http://www.chickjunk.com/make-money-in-second-life/ How to Make Money In Second Life] - How to get started and earn linden in Second Life
* [http://personalweb.about.com/od/virtualworlds/a/sl_makemoney.htm Make Money in Second Life] - A good list of methods to earn money

LlUnSit

2014-07-04T22:50:53Z

Omei Qunhua: Clarify function description

{{LSL_Function
|inject-2={{Issues/SVC-924}}{{LSL_Function/avatar|id|sim=*}}
|func_id=220|func_sleep=0.0|func_energy=10.0
|sort=UnSit|func=llUnSit
|p1_type=key|p1_name=id
|func_footnote
|func_desc=The agent identified by {{LSLP|id}} is forced to stand up if any of the following apply:-
:1. The agent is sitting on the scripted object
:2. The agent is wearing the scripted object
:3. The agent is over land owned by the scripted object's owner
|return_text
|spec
|caveats
|constants
|examples=
<lsl>// UnSit on Sit, Using a sit target
default
{
state_entry()
{
llSitTarget(<0.0, 0.0, 0.1>, ZERO_ROTATION); // Needed for llAvatarOnSitTarget to work. The vectors components must not all be set to 0.0
}
changed(integer change) // Triggered when various changes are sensed.
{
if(change & CHANGED_LINK) // When an agent sits on an object they become a new link.
{
key user = llAvatarOnSitTarget(); // Store the UUID of any agent sitting on the sit target.
if(user) // An avatar is on the sit target.
llUnSit(user); // Un-Sit the avatar.
}
}
}</lsl>
<lsl>// UnSit on Sit, NOT using a sit target

default
{
changed(integer change) // Triggered when various changes are sensed.
{
if(change & CHANGED_LINK) // When an agent sits on an object they become a new link.
{
integer links = 0; // Create an integer type variable.
if(llGetObjectPrimCount(llGetKey()) < (links = llGetNumberOfPrims())) // During the check store the number of links.
// If the number of prims is fewer than the number of links, the last must be an avatar.
llUnSit(llGetLinkKey(links)); // Use the key of the last link to be added (the avatar) to call llUnSit().
else
llOwnerSay("Some kind of linking or unlinking has changed me but, I am not being sat on.");
// llUnSit() triggers the changed event too (the number of links is reduced by 1).
}
}
}</lsl>
<lsl>
unsit_all_avatars()
{
integer objectPrimCount = llGetObjectPrimCount(llGetKey());
integer currentLinkNumber = llGetNumberOfPrims();

for (; objectPrimCount < currentLinkNumber; --currentLinkNumber)
llUnSit(llGetLinkKey(currentLinkNumber));
}

default
{
touch_start(integer num_detected)
{
unsit_all_avatars();
}
}
</lsl>
<lsl>

// Unsit the attached Avatar
// Note this method is preferable to the RLV Command @unsit=force, due to it's success rate at actually completing

default {
touch_start(integer num_detected)
{
if(llGetAttached()!=0) llUnSit(llGetOwner());
}
}
</lsl>

|helpers
|also_functions={{LSL DefineRow||[[llAvatarOnSitTarget]]|}}
{{LSL DefineRow||[[llSitTarget]]|}}
|also_events={{LSL DefineRow||[[changed]]|}}
|also_articles
|also_tests
|notes
|permission
|negative_index
|cat1=Parcel
|cat2=Sit
|cat3
|cat4
|haiku={{Haiku|Beauty at the bar|Not an empty seat in sight.|Owner clears me one.}}
}}

Talk:LlUnSit

2014-07-04T09:24:44Z

Omei Qunhua: suggestion

Not having the conditionals indented is confusing to new scripters. [[User:Strife Onizuka|Strife Onizuka]] 00:47, 26 February 2007 (PST)

I am a ''somewhat'' novice scripter and I was wondering if there is any particular reason for adding the key rather just leaving it to identify llAvatarOnSitTarget the way it was before you edited it. --[[User:Carigorp Matzerath|Carigorp Matzerath]] 11:14, 26 February 2007 (PST)

The LSL compiler does not optimize code. It should make the code run faster. Keep up the good work writing examples, we need lots of them. [[User:Strife Onizuka|Strife Onizuka]] 11:39, 26 February 2007 (PST)

==Function description/caveat==
Would this be better wording for the description, and remove the caveat?

:The agent id is unseated if any of the following apply:-
::1. The agent is sitting on the scripted object
::2. The agent is wearing the scripted object
::3. The agent is over land owned by the scripted object's owner
:[[User:Omei Qunhua|Omei Qunhua]] 02:24, 4 July 2014 (PDT)

Talk:Jump Teleport

2014-06-30T15:06:06Z

Omei Qunhua: comments

Just happened by this page browsing for something else for someone and thought I should comment.

Teleporters in Second Life have been plagued with the use of warpPos function which, although it is supposed
to accomplish a simple task, the implementation is obfuscated with magic numbers, the design is very poor and
funny effects are acheived. Here is a rundown of the problems with warpPos:

First off, at the time it was written, "teleporting" was accomplished by sitting on a prim, and having it cycle through [[llSetPos]] 10m hops in a loop until [[llGetPos]] was very close to the destination, like so:

<lsl>OLD_teleport(vector dest) {
while (llVecDist(llGetPos(),dest) > 0.1)
llSetPos(dest);
}</lsl>

The movement was slow and jerky, and could take many seconds to complete long jumps, due to the enforced 0.2s delay on [[llSetPos]]. Then, [[llSetPrimitiveParams]] was introduced, and [[User:Keknehv Psaltery|Keknehv Psaltery]] discovered a rather amazing side-effect of it: when you put multiple [[PRIM_POSITION]] rules in a list, it would accumulate them and move the prim in one go. Each rule still had the 10m limit check, but it didn't apply the prim position move until it finished parsing the rule list, so it got around that issue. It was a fantastically useful and positive change, despite it essentially being a hack -- an endrun around LL's imposed limitations on prim movement.

After he published the discovery, other folks ([[User:Strife Onizuka|Strife]], [[User:Talarus Luan|myself]], and others) found ways to optimize the script for speed and to make sure to keep the number of generated rules to a minimum. Optimizing code has the unfortunate side-effect of making it more difficult to understand, but the goal was to make something that people could use with some degree of confidence that it was using the least resources possible.

When you say the "design is very poor", I think you may be judging it a) without knowing its history, and b) by comparing it to a more modern standard (6 years later, in fact). Also, pointing out obfuscation in highly-optimized code is a priori -- that's fairly typical. There have been a number of dissections and explanations of the code posted in various forums over the years for neophyte scripters, although there is little in it which should be opaque to scripters of intermediate skill. However, I am happy to address it here, once again, for the reader's satisfaction. :)

The code mentions:

// Try and avoid stack/heap collisions
if (jumps > 411)
jumps = 411

with no explanation whatsoever about what that means and why an overflow occurs.

Again, the goal of the optimized version of the code wasn't to educate, but to provide a useful, efficient, and effective drop-in function for people to use. Even still, it isn't difficult to discern why an overflow might occur from looking at the code, hence:

<lsl>
while ( ( count = count << 1 ) < jumps)
rules = (rules=[]) + rules + rules; //should tighten memory use.
</lsl>

It is building a list of rules, pretty much by doubling the size of the list every iteration through that loop. When it was written, Mono didn't exist yet, so each script had only 16k of memory. Building big lists like this was hazardous, and could easily cause out-of-memory errors for even a moderately long teleport. Thus, limiting the size of the list was pretty important, so that check was added in an attempt to curb the occurrence of such errors. The original limit was much lower, but once Mono came out, it allowed for longer jumps. The "magic number" originally was based on keeping the script within the 16k limit, but with Mono's quadrupling of available memory, it became more of an "oops" check. You see, non-physical movement is only possible up to 4096m in the Z. Thus, the largest non-physical teleport length is from <0.0, 0.0, 0.0> to <256.0, 256.0, 4096.0>, or approximately 4112m, which means that, with 10m jumps, the maximum would be ~411 jumps. So even though 411 jumps won't necessarily cause Mono to run out of memory (with a simple TP script, anyway), it prevents someone who might accidentally specify a far larger teleport distance from causing their script to crash in this function. Out of memory errors are notoriously difficult to debug, so reducing one avenue of cause was a worthwhile endeavor.

warpPos calculates the number of jumps necessary and then proceeds to jump 10 meters in the calculated direction without even accounting for affinity.

Unfortunately, I have no idea what "affinity" refers to in this context, so I can't really address this issue. However, WarpPos doesn't jump 10m at a time, it actually jumps the entire distance in a single jump -- in a single [[llSetPrimitiveParams]] call.

warpPos is based on a function that executes llSetPos calls which has the effect of timing out on OpenSim due to the timeout
imposed on event handlers: an event handler just goes away after some time and warpPos will fail for long distances.

While I can't address issues related to using WarpPos on OpenSim (as it wasn't written or intended for use on OpenSim), I can state that it does not (originally) use [[llSetPos]]. In more recent iterations of it, someone added a "fallback" to the OLD_Teleport method, which uses [[llSetPos]], mainly to get around the Lindens repeatedly "breaking" the [[llSetPrimitiveParams]] hack over the years, so they don't have to field lots of angry customer issues every time. Since WarpPos was an exploit of an unintended edge-case, Linden Lab had no responsibility to "fix" it if they "broke" it (except to quell massive resident backlash every time they did), it was conceivable that, at some point, they would leave it "broken", which meant that a very large number of items all over the grid would stop working. So, for some people, a fallback to the "old tried and true" method was prudent to add afterwards, just in case.

Lastly, I would like to point out that, as of the writing of your original article, WarpPos was already functionally obsolete. Linden Lab added llSetRegionPos(), which pretty much completely deprecated WarpPos. Even still, WarpPos is a [http://en.wikipedia.org/wiki/Lava_flow_%28programming%29 lavaflow] -- LL has broken it a number of times, but has "fixed" it, effectively making it a de facto supported feature. As one of the original scripters who worked on WarpPos, I tell everyone that it is obsolete and not to use it anymore (and have since [[llSetRegionPos]] hit the grid), so any issues with it in SL are effectively moot. Issues with OpenSim I can't speak to, but I would imagine that [[llSetRegionPos]] functionality has been implemented in the last two years, so even Jump Teleport may also be effectively obsolete as well.

----

Now, to be fair, I would like to offer a critique of your method. :)

The following code should solve those problems

OK, so to be clear, these are the problems you are addressing with your version:

# Use of undocumented "magic numbers"
# Jumping without accounting for "affinity"
# OpenSim event handler timeout issue

by using vector calculus

Really? O.o

"Vector calculus (or vector analysis) is a branch of mathematics concerned with differentiation and integration of vector fields, primarily in 3-dimensional Euclidean space {R}^3."

OK, so you probably didn't use the right word there, but no matter. I'll let you off the hook for that one. ;)

and calculating 10 meters in the direction towards the final destination

That sounds familiar. :)

(the math is explained in the Second Life category).

<nowiki>*chuckles*</nowiki>

The function doing that is jumpGates which recursively computes hops towards the final destination and returns them in a list

Oh dear. :-/ Recursive functions are an interesting CompSci source code "trick", but they are rarely efficient, and are often fraught with causing more frequent out-of-memory issues than using contextual looping.

which we process later using a timer. By using a timer we make sure that the handler does not time out and
we call that timer using the minimal float value (1.175494351E-38) since there are no limitations on the minimal timer interval.

Now, this part is a rather ingenious solution to the OpenSim event timeout issue, if I understand it correctly.

When jumping to the next gate, we additionally use the list as a stack in order to pop off the first coordinates and
discard them from the list entirely. This makes the script start with an initial memory pool and, as it runs, it frees
up memory instead of consuming more and more memory.

Well, while the function is in operation, it shouldn't use ''more'' memory; once you've built the jump list, it shouldn't grow beyond that. Also, repeated list manipulation is very heavy in terms of overhead -- LSL list manipulation functions do a lot of copying (which can cause out of memory conditions as well), which makes them quite slow. In a time- (as well as resource-)constrained environment, it might have been better to just use a "stack pointer" during the jumps, and then just free the list all at once at the end of the move.

Now, with regards to the actual code, you seem to have addressed the first issue ("magic numbers") adequately. You code would definitely qualify as an educational tool (in more ways than one, to be sure ;) ). I would argue that using the "smallest float" is a bit unnecessary in a practical sense; 0.001 (1 millisecond) is probably fast enough for practical use in either SL or OpenSim, for the life of those virtual worlds. If you really wanted to be "sure", using 1.0E-6 or 0.000001 would have been more than sufficient for any possible practical use in the lifetime of any virtual world for the next decade or two.

Regarding the second issue, since I don't understand the reference ("affinity"), I can't determine if your code meets that criterion or not.

Regarding the third issue, as I observed above, it appears to be an ingenious solution to that particular problem, so kudos for that, if it worked out. :)

The remaining misgivings I have are to the (unnecessary and expensive) use of recursion, and not addressing LSL's typically poor list management issues. More often than not, I would expect this code to crash with stack/heap issues, especially for long jumps (in fact, testing it under mono, in a script with just the jumpGates() recursive function and a basic call to it tends to fail on jumps above 3600m). Also, it appears the function always leaves you 1 meter short of your destination.

Using multiple states, beyond unnecessarily using up more memory, also requires a second expensive call to jumpGates(), when you could simply use a stack pointer/index and go in the reverse direction -- from the end of the list back to the beginning. Granted, WarpPos would also require a second list calculation/construction, but if the goal was to make a better WarpPos, might as well go with your strengths, no? (though, technically, WarpPos ''could'' be made to do the same thing with some minimal changes, but that's outside the scope of this critique).

That's pretty much all I see in terms of issues in your design and code. The only other issue I would point out is that you need to review your licenses -- the only people who can use your code are people who are also making and releasing open-source products, also under GPL v3.0. I think a more appropriate license would either be LGPL or MIT. However, that's entirely your call; just something to think about.

In closing, I would recommend to all who come after to consider using [[llSetRegionPos]] and '''NOT''' use WarpPos or similar kinds of functions (like this one), as they have been functionally obsoleted by it.
----
Now that I have had time to think about it, to solve the OpenSim issue really doesn't require a jump list at all. This script should effectively do the same thing on OpenSim:

<lsl>
// This code is an example -- no license is implied or claimed, treat as public domain by me, the author, Talarus Luan
vector vStartPos;
vector vEndPos;
integer bReverse;
float fDelay = 0.001; // Very fast timer - not normally recommended
float fDestEpsilon = 0.1; // "Fuzzy" destination distance to determine if we've arrived
// llSetPos and its ilk are not guaranteed to get to exact positions, so a fuzzy comparison is necessary
float fJumpDistance = 10.0; // Max SetPos jump distance per hop

default
{
state_entry() {
llSitTarget(<0,0.0,1>, ZERO_ROTATION);
}
changed(integer change) {
if (change & CHANGED_LINK) {
if(llAvatarOnSitTarget()) {
vStartPos = llGetPos();
vEndPos = (vector)llGetObjectDesc();
bReverse = false;
llSetTimerEvent(fDelay);
}
}
}
timer() {
key kAvatar;
float fRemainingDist;
vector vNextPos = ZERO_VECTOR;

if (bReverse) {
fRemainingDist = llVecDist(llGetPos(),vStartPos);
if (fRemainingDist < fDestEpsilon) {
bReverse = !bReverse;
llSetTimerEvent(0.0);
} else {
if (fRemainingDist > fJumpDistance)
vNextPos = llVecNorm(vStartPos-vEndPos) * fJumpDistance
else
vNextPos = vStartPos;
}
} else {
fRemainingDist = llVecDist(llGetPos(),vEndPos);
if (fRemainingDist < fDestEpsilon) {
bReverse = !bReverse;
kAvatar = llAvatarOnSitTarget();
if (kAvatar) llUnSit(kAvatar);
} else {
if (fRemainingDist > fJumpDistance)
vNextPos = llVecNorm(vEndPos-vStartPos) * fJumpDistance
else
vNextPos = vEndPos;
}
}
if (llVecMag(vNextPos) != 0.0)
llSetLinkPrimitiveParamsFast(LINK_THIS, [PRIM_POSITION, vNextPos]);
}
}
</lsl>

Note: Untested, so there may be a bug or two in it. Will revise as needed. :)

[[User:Talarus Luan|Talarus Luan]] 12:43, 29 June 2014 (PDT)

:a good response, Talarus. However Kira Komarov got kicked out of slWiki some time ago (tho' probably lurking as some Alt). Unfortunately some people decided to resurrect some of her pages that she had attempted to erase, many of which are not worth the paper they are written on IMHO.

:A couple of comments:-
::1) In SL at least, the minimum effective timer interval using llSetTimerEvent() is 2 frames, or about 44 mS.

::2) WarpPos always had a little buglet in that the line
<lsl>
llSetPrimitiveParams( rules + llList2List( rules, (count - jumps) << 1, count) );
</lsl>
::tries to access an element off the end of the list, fortuitously without mishap. The line could be better coded as
<lsl>
llSetPrimitiveParams( rules + llList2List( rules, (count - jumps) << 1, -1) );
</lsl>
[[User:Omei Qunhua|Omei Qunhua]] 08:06, 30 June 2014 (PDT)

Second Life bot software comparison

2014-06-18T16:57:44Z

Omei Qunhua: pricing correction

Second Life bots can perform the various operations (not available by LSL):
* Send direct group invitations (including closed groups)
* Automatically monitor the group chats, kick spammers, perform antispam checks
* Send automatic group notices and IMs
* Act as mannequin or model bot
* Serve as a secretary or support robot by using autoresponder AI or remote chat assistant.
* Be a non-personal character (NPC) in a roleplaying game.

== Classification ==

Every Second Life bot requires a special software running. This software can be run either on user's PC or hosted with Second Life bot hosting provider.

<div style="float: left; width: 49%">
== A. Hosting bot with provider ==

Pros:
* You don't care about PC consuming power around the clock.
* You don't have to choose, probably buy and update the bot software.
* Bot does not depends on your internet connection.

Cons:
* You have to pay a subscription fee (usually weekly)
</div>

<div style="float: right; width: 49%">
== B. Running bot on your own PC ==

Pros:
* You can launch the bot when you need it
* Usually no subscription fee (however, you may need to buy the software)

Cons:
* You have to keep your PC running all the time
* Bot hosting providers usually offer more features than standalone programs
</div>
<div style="clear: both"></div>

== Comparison ==

(Sorted naturally, new records are appended at the end)

{| width=100% border=1 cellspacing=0 cellpadding=4
|- bgcolor="#DDDDDD"
! width=20% |
! width=20% | SmartBots
! width=20% | PikkuBot
! width=20% | Corrade
! width=20% | SecondBot

|-
| colspan=5 | '''Hosting type'''
|-
| bgcolor="#DDDDDD" | Server hosting
| '''yes''' || '''yes''' || no || no
|-
| bgcolor="#DDDDDD" | Downloadable program
| no || '''yes''' || '''yes''' || '''yes'''
|-
| bgcolor="#DDDDDD" | Source-Code Available
| no || no || '''yes''' || no

|-
| colspan=5 | '''Purpose'''
|-
| bgcolor="#DDDDDD" | Used as:
| '''Multi-functional Bot''' || '''Multi-functional Bot''' || '''Multi-functional Bot''' || '''Multi-functional Bot'''

|-
| colspan=5 | '''Features'''
|-
| bgcolor="#DDDDDD" | Bot controlling approach
| web pages in-world HUD http API || chat commands || in-world primitives instant-messaging http API || instant-messaging http AI
|-
| bgcolor="#DDDDDD" | Group Inviter <ref>See [[Group inviters comparison]] for more info</ref>
| '''yes''' || '''yes''' || '''yes''' || '''yes'''
|-
| bgcolor="#DDDDDD" | Chat moderator
| '''yes, web interface''' || '''yes, bot commands''' || '''yes, bot commands''' || no
|-
| bgcolor="#DDDDDD" | Automatic chat antispam
| '''yes, using free device''' || no || no || no
|-
| bgcolor="#DDDDDD" | Group notices and IMs
| '''yes''' || '''yes''' || '''yes''' || '''yes'''
|-
| bgcolor="#DDDDDD" | Scheduled notices and IMs
| '''yes, web interface''' || no || '''yes, bot commands''' || '''yes groups only'''

|-
| colspan=5 | '''Add-ons'''
|-
| bgcolor="#DDDDDD" | Add-ons for other services
| LOW Industries devices SHX devices HippoRent Casper (Vend and others) AlikaRent IntelliAd || not announced || developers welcome :-) || StreamAdmin
|-
| bgcolor="#DDDDDD" | Devices and tools
| [https://marketplace.secondlife.com/stores/11457 Available at SL Marketplace] || [http://www.pikkubot.de/dokuwiki/doku.php?id=pikkushop Pikku-Shop] || [http://was.fm/secondlife:scripted_agents:corrade Wizardry and Steamworks - Corrade] || None yet

|-
| colspan=5 | '''Prices'''
|-
| bgcolor="#DDDDDD" | Setup fee
| '''free''' || L$6,000 (premium license) L$1,500 (light license) || '''free''' || '''free'''
|-
| bgcolor="#DDDDDD" | Bot hosting subscription
| L$479/week - fully-functional bot L$179/week - model bot || L$504/week || N/A || '''Not supported yet'''

|-
| colspan=5 | '''Programming'''
|-
| bgcolor="#DDDDDD" | LSL API<ref>The LSL library which allows to utilize bot's functionality from your LSL scripts</ref>
| '''[http://www.smartbots2life.com/docs/AdminBot AdminBot LSL Library]''': invite to group group chat talk group chat listen eject group members || no || invite to group eject from group leave group add members to roles remove members from roles update group profile || '''[http://secondbot.net/index.php?module=docs Full command control via scripts]'''
|-
| bgcolor="#DDDDDD" | Bot chat API
| no || '''yes''' || '''yes''' || '''yes'''
|-
| bgcolor="#DDDDDD" | HTTP API
| '''yes''' || no || '''yes''' || '''yes'''
|-
| bgcolor="#DDDDDD" | Other languages
| [http://www.smartbots2life.com/docs/SBSL Simple Bot Scripting Language] || no || '''possible''' || no

|-
| colspan=5 | '''Links'''
|-
| bgcolor="#DDDDDD" | URL
| [http://www.smartbots2life.com/ SmartBots: Second Life bot hosting] || [http://www.pikkubots.de/ PikkuBots website] || [http://was.fm/secondlife:scripted_agents:corrade Wizardry and Steamworks - Corrade] || [http://secondbot.net/ SecondBot website]
|-
| bgcolor="#DDDDDD" | SLURL
| [http://slurl.com/secondlife/DuoLife/200/99/32] || [http://slurl.com/secondlife/San/198/140/58] || --- || ---
|-
| bgcolor="#DDDDDD" | Other
| SmartBost is a publicly trading company, listed as [http://slcapex.com/symbol/BOTS BOTS] at SLCAPEX || --- || The source-code is released under the GNU GPLv3 license. For hosting, please contact [[Kira Komarov]] in-world. Free hosting may be available (within reason and at the mercy of resources). || ---
|}
<references/>

== See also ==
For more info on bots, visit the following pages:
* [[Group inviters comparison]] - the comparison table of the group inviter services
* [http://www.smartbots2life.com/docs/SmartBots_Documentation SmartBots services] - the general information about Second life bots and related services: group inviter, chat managing and group notices

[[Category: SL Bots]]

Talk:LlRound

2014-06-15T07:22:53Z

Omei Qunhua: /* Rounding direction */

In all seriousness, how does a "pretty table", which doubled the page width,
https://wiki.secondlife.com/w/index.php?title=LlRound&diff=next&oldid=1187121
fit in with the edit of https://wiki.secondlife.com/w/index.php?title=LlJsonSetValue&diff=prev&oldid=1181771 made for "...better readability on mobile screens..."??? [[User:LepreKhaun Resident|LepreKhaun Resident]] 20:47, 20 January 2014 (PST)

==Rounding direction==
I can see in retrospect of course that there's no problem in accurately holding -4.5 or -5 in a float. But as for rounding towards positive infinity, is the lslWiki page wrong too? http://lslwiki.net/lslwiki/wakka.php?wakka=llRound [[User:Omei Qunhua|Omei Qunhua]] 13:26, 14 June 2014 (PDT)
:Check what LSO does, this may be a difference between LSO and Mono that was never caught... or nobody noticed that llRound is not [http://www.cplusplus.com/reference/cmath/round/ cmath roundf] -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 18:54, 14 June 2014 (PDT)

Just checked ... LSO behaves the same as Mono. And the Mozilla Java Script page says math.round behaves like LSL. http://tinyurl.com/phsk5zy [[User:Omei Qunhua|Omei Qunhua]] 00:22, 15 June 2014 (PDT)

Talk:LlRound

2014-06-14T20:26:06Z

Omei Qunhua: Rounding query