Second Life Wiki - User contributions [en]

Talk:LlSensor

2015-08-16T03:14:38Z

Dale Innis:

{{talk}}
If PI/4 is a 45 degree cone: if the cone's axis is 1, does the base have a diameter of 2, or a diameter of ~0.82? --[[User:Asha Vultee|Asha Vultee]] 12:53, 19 November 2007 (PST)

:Strictly speaking, it's not a cone. If you want an idea of what the shape will look like run the following script. -- [[User:Strife Onizuka|Strife Onizuka]] 13:20, 19 November 2007 (PST)
<pre>
float arc;

default
{
state_entry()
{
llSetPrimitiveParams([PRIM_TYPE, PRIM_TYPE_SPHERE, 0, <0.,1.,0.>, 0.0, <0.,0.,0.>, <0.,arc/PI,0.>]);
}
}
</pre>

== Agent? ==

Hey everyone, don't you think the "AGENT" flag should have a description along the lines of "This is used to find avatars only". rather than a blank description? I tried to add it myself, but I'm afraid I'm too newbie to understand the formatting... I couldn't find that particular table.{{unsigned|Hikaru Dreadlow|17:31, 23 June 2008}}

:Will do, the table is in a template ([[Template:LSL_Constants_Sensor]]) so that it can be included on llSensorRepeat too. -- [[User:Strife Onizuka|Strife Onizuka]] 15:02, 23 June 2008 (PDT)

== All Object Sensor? ==

Hey, can anyone tell me how to make an llSensor() that will scan for ANY object? For example, both physical and nonphysical, scripted and nonscripted, any combination. I tried combining all the flags (besides AGENT) with bitwise |, but it didn't seem to pick up all objects in range.{{unsigned|Crystals Galicia|16:45, 22 September 2008}}

BloodyRain Rang: seems like LL screwed the sensors up cause 0 as type should find all things, even avatars but it doesnt work. And without that it seems impossible to detect any objects without going through all combinations of ACTIVE PASSIVE and SCRIPTED (7 combinations btw). Hope this get fixed someday. (2008-12-08){{unsigned|BloodyRain Rang|18:02, 8 December 2008}}

:My apologies for not catching this sooner (or seeing these comments). The documentation was in error about zero being an acceptable value for '''type'''. The error stemmed from the documentation being based initially on the tooltips from the client script editor. Most such errors were caught during the initial import but not all. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:21, 8 December 2008 (UTC)

== The return of NULL_KEY caveats are a little lacking ==

The sensor will not trigger if an invalid key (NULL_KEY) is "found" but if the structure of the script allows it the empty NULL_KEY can be returned. As with the simple following.<lsl>default
{
state_entry()
{
llSensorRepeat("", "", 3, 20.0, PI, 1.0);
}
sensor(integer detected)
{
llSay(0, (string)llDetectedName(0));
llSay(0, (string)llDetectedName(1));
llSay(0, (string)llDetectedName(2));
llSay(0, (string)llDetectedName(3));
llSay(0, (string)llDetectedName(4));
llSay(0, (string)llDetectedName(5));
}
}</lsl>I'm not saying this is good scripting but since it returns 5 null keys and 1 avatar (if it only finds one etc.) not being fully aware of the facts while compiling lists for eg. could get messy. Fact: If the event is not structured well to exclude NULL_KEYs they can be returned. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 21:21, 8 August 2009 (UTC)

== Agent's sit target no longer shows up? ==
This statement:
"If the agent is sitting on an object, the root prim of the sat upon object becomes a second sensor target for the agent (but not if the avatar is outside the sensor arc, see SVC-5145[c])."
no longer seems to be true - if you search for an agent, you only get the agent, and not the object it's sitting on. (No clue when this changed, I only tried it for the first time tonight).
[[User:Redwood Rhiadra|Redwood Rhiadra]] 01:22, 2 October 2010 (UTC)
: Hi, this feature is definitely confusing, that is what {{Jira|SVC-5145}} is, a request to make the behavior sensible and consistent. I will repeat the tests this weekend and see if it is broken in the same old way or if there are new ways too. --[[User:Cerise Sorbet|Cerise Sorbet]] 03:30, 2 October 2010 (UTC)

__________________________________

== examples on this page are inadequate. ==

And no, I don't dare try to add any more, because Strife the Control Queen doesn't need examples for himself, so he just deletes them all.

[[User:Chaz Longstaff|Chaz Longstaff]] 18:20, 19 September 2011 (PDT)
:The ad homimem attack is unnecessary. Taking a look at llListen which is another function that is paired with an event, I added an example script to showcase llSensor with the sensor event. Will that do? --[[User:Nexii Malthus|Nexii Malthus]] 19:45, 19 September 2011 (PDT)

I don't recall deleting any content recently, let alone an example. I remember once in the last year(or two?) deleting an entirely duplicate example (had been double pasted into the article?) but nothing more recent. So I'm at a bit of a loss for words.

I honestly wish people would post more examples, there is even a category for articles in need of examples: [[:Category:LSL_Needs_Example]] and general improvement [[:Category:LSL FixMe]]. I generally leave writing examples to others, not because I don't find them useful, I often can't think of a simple useful example, my examples tend to bury the usage in a script that is better placed in the Script Library (which no one ever sees or uses). I don't spend much time here and less time in SL, so I'm pretty cautious with my edits and unlikely to edit an example or script.

So I'm Currently working my way through the new functions and features from [[Release_Notes/Second_Life_RC_LeTigre/11#11.09.09.240509]] but I don't have a lot of time to devote to it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:21, 20 September 2011 (PDT)

== Error with sensor page ==

has anybody noticed that the sensor page shows up odd when not loged into the wiki?[[User:Tmzasz Luminos|Tmzasz Luminos]] 20:15, 14 February 2012 (PST)

:What browser are you using? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:21, 15 February 2012 (PST)

:Never mind, it's definitely a wiki engine issue. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:31, 15 February 2012 (PST)

:{{Jira|WEB-4489}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:34, 17 February 2012 (PST)

== AGENT vs AGENT_BY_LEGACY_NAME - No ambiguity if there's no name to filter by ==

The docs say: "If name, id, and/or type are empty or 0, they are ignored." In that case, the name is empty, it's ignored and not to be interpreted in any meaningful way. There is no possible ambiguity on how the name should be interpreted because there is no name to filter by. And please explain the removal of the text about how adding a name affects the result. It was a good example of how to use AGENT_BY_LEGACY_NAME to resolve the ambiguity. Maybe a fictitious name should be used instead of an existing one to prevent self-promotion. I'd agree with that, but that name wasn't even touched. I don't understand the reversal. -- [[User:Sei Lisa|Sei Lisa]] 10:00, 22 October 2013 (PDT)

: I think the example text rollback was an oversight. I shall put it back. I agree, we should choose someone else, for kicks we could make it the last person who edits the page. Thoughts?
: I'm going to split hairs a bit, the ambiguity does not go away, it just becomes meaningless. However when you edit the code to add a name, that is when the ambiguity matters and where AGENT bite you in the butt. I'd really would like to kill [[AGENT]] off to rid us of this problem. With AGENT we save in letters typed but we get burned by creating a lovely little "Gotcha": For the new users they would see the three flags and expect [[AGENT]] to be the generic form that allows you to search by either and most likely to be the one that searches by display name. No [[AGENT]], no misunderstanding in the mind of the reader. Hopefully when they encounter [[AGENT]] it will be on the documentation. Regardless, I find using the longer name with the null case distasteful but something I think is worth inflicting on new users. Like using [[run_time_permissions]].
: Your gallery solution is the most practical of them all. I not happy with how gallery breaks things but recreating gallery with templates is something I'm going to avoid. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:39, 22 October 2013 (PDT)

:: On names: using either a famous Linden name or a fictitious name feels better than a variable one. Governor Linden is one I'm considering, and John Doe is another. I'd lean towards the latter.
:: On the gallery: What I miss with the gallery is a reference in the text that says where to find it ("look at the bottom of this page...")
:: On the edit: Given that I have yet to see one use case for AGENT_BY_USERNAME, I would aim for readability, and AGENT is preferable not because it's shorter, but because it doesn't confuse with something that is very rarely if at all there (the username or the legacy name). Once you put a name, if that ever happens, which I doubt, especially for a new user, you can change it to the correct type of name. And of course, you can not "kill" AGENT, because AGENT_BY_USERNAME does simply not work at all with llDetectedType, and AGENT_BY_LEGACY_NAME is very clearly a misname for that case. The flags are shared with llDetectedType and there's even no indication in that page that AGENT_BY_USERNAME won't work at all with it. That is a separate issue, but the logic that leads to preferring AGENT there also applies to prefer AGENT when no name is specified in llSensor. -- [[User:Sei Lisa|Sei Lisa]] 01:16, 23 October 2013 (PDT)

:: <rant> I consider the introduction of AGENT_BY_LEGACY_NAME a mistake. The whole display name system has been a hack on top of the existing, now "legacy" name system, including the LSL additions. The same logic that led to the introduction of AGENT_BY_LEGACY_NAME should for example have led to deprecating llKey2Name and introducing llGetLegacyName as a synonym, yet that didn't happen. People are expected to know that llKey2Name returns a legacy name and not a display name or username. It shouldn't be any different with AGENT; just adding AGENT_BY_USERNAME to provide access to the new functionality should have been enough. The mere presence of AGENT_BY_LEGACY_NAME has proven to introduce more confusion than the one caused by forgetting to change it to AGENT_BY_USERNAME when using a username in the name (again, if that ever happens). The problem is that it references a name where it isn't applicable, leaving the reader of the code wondering: "Name? What name?" It's akin to giving instructions to someone having a step that is not applicable at all. Imagine telling someone "Go straight through this street; turn right when you see a sign that says 'X', and turn left when you see a sign that says 'Y'" but there is only an 'Y' sign and all that is needed to reach the destination is to turn left when reaching it. The instructions are logically impeccable, and anyone following them literally will reach the destination, but the receiver will wonder where is that 'X' sign. That's what I feel every time I see a llSensor call using "" as name and AGENT_BY_LEGACY_NAME as constant. If one is to be killed, it's AGENT_BY_LEGACY_NAME, not AGENT. </rant>
:: There, I said it. To elaborate on shortness, being shorter is not at all a reason to prefer it. I really wish that it at least had a namespace prefix like SENSOR_ or OBJECT_TYPE_ or the like, to reduce the chance of name collisions and clarify the scope of its applicability. It doesn't, sadly. -- [[User:Sei Lisa|Sei Lisa]] 02:00, 23 October 2013 (PDT)
:::Good point about directions.
:::llDetectedType: I'll poke the template so it does not show the AGENT_* constants there, only AGENT. I really wish they had prefixed them, also the texture animation constants, who would guess [[PING_PONG]] was a texture animation constant without looking it up? LSL was built before it was designed. Personally it all have been better if LSL was object oriented, you wouldn't have had so many silly lookup functions.
:::Governor Linden was actually who I was thinking of, that or Philip Linden. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:59, 23 October 2013 (PDT)

::::I have to agree with Sei on this one. It is clearly silly to say you are searching by a name when that is exactly what you are not doing. Like it or not, AGENT exists, and we should demonstrate it. I will continue to use AGENT where appropriate for as long as it compiles. I also belong to the school that feels that the whole display name idea was a stupid mistake. [[User:Omei Qunhua|Omei Qunhua]] 12:52, 23 October 2013 (PDT)

:::: @ Strife:
:::: On names: While I still would lean towards John Doe, I have no strong opinion; Governor Linden is fine with me. Philip Linden could potentially have political issues in future, I hope not.
:::: On prefixes: Sad thing is they made the same mistake recently when they introduced HORIZONTAL and VERTICAL for pathfinding. Talk about namespace pollution. Oh, well.
:::: On the change: would you consider re-applying my changes then?
:::: @ Omei: Thanks for the support :) I wouldn't go as far as calling it a stupid mistake, but it's a hack no matter how good or bad idea it is. -- [[User:Sei Lisa|Sei Lisa]] 13:20, 23 October 2013 (PDT)

:::: Thanks for the change, very appreciated! -- [[User:Sei Lisa|Sei Lisa]] 10:05, 24 October 2013 (PDT)

::::: You are welcome. I would be ok with causing a little political uproar. Streisand effect, would be good for the wiki. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:01, 25 October 2013 (PDT)

== Can it look the other way? ==

I'm trying to make a single prim see 30 things that are scattered symmetrically around it. A single sensor() call can't see them all, as there are too many. I thought I could look at the 15 in front, and then the 15 in back, but the arc is always in the forward direction. Is there any way (a negative arc?) to look just behind and not in front? I will do the experiment :) but if anyone knows... [[User:Dale Innis|Dale Innis]] ([[User talk:Dale Innis|talk]]) 20:08, 15 August 2015 (PDT)

== Diameter or Radius? ==

Why does this functions wiki page not explicitly state weather the float RANGE, is a Diameter, or a Radius?

Just calling it a Range, seems kinda ambiguous. Sure many of us can just assume, or experiment to be sure. But it seems like info that belongs on the upper most definition of the function.

Maybe I'm just missing it due to sleep deprivation. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 15:23, 18 March 2015 (PDT)

:"Range" means distance from the prim's or the wearer's center. That forms a sphere around said center, with the range's radius, within which everything is "in range" and everything outside is "out of range". Therefore it is the radius. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 04:44, 19 March 2015 (PDT)

::I submit my edit to the page for clarity. I was confident my mention of radius, and "distance from center" was sufficient, valid, and helpful. If it doesn't get changed back, then yay for a positive contribution! [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 07:33, 19 March 2015 (PDT)

::: I personally find it more confusing when put that way. It doesn't state the center of what, or the radius or what geometric figure or why it matters, while "range" is clearly implicitly referring to a distance, which logically must be from the script that has the sensor to the detected object. I don't know where did your confusion between radius and diameter come from, as not many people will realize immediately that the range volume forms a sphere. My vote is for that change to be reverted. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 08:57, 19 March 2015 (PDT)

:::: I fail to see where saying "Range" by itself is any more descriptive or accurate. It leaves more to the imagination then saying Radius, which by definition indicates from center point, inclusively to an end. Range, in fact can be easily misconstrued as a diameter, a square field, or a point at a variable distance forming a ring. Semantics are important and layman's terms such as "Range" when referring to a Radius, do not provide enough info for an accurate visualization of the procedure. I prefer to call a dog "a dog", rather then "the thing". One I know not to store in the attic for a few years, the other, not so much. If you don't understand what the word Radius means, you can easily look it up in a dictionary, but looking up "Range" in a dictionary wont provide you any insight as to weather this process uses a diameter or a radius. In fact many people who I've taught scripting to have asked me if "Range" was halved, when the Arc, was PI / 4. Implying they presumed "Range" to be a diameter. I wonder where they got that notion?? Perhaps it was from the lack of clarity in this functions description. I suppose Ray-Length could be another plausible word. but it's 2 words. and "Length", by itself would also not distinguish between diameter and radius as both are a measure of length. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 09:56, 19 March 2015 (PDT)

::::: {{quote|radius:

1. a straight line from the center to the circumference of a circle or sphere.
2. the thicker and shorter of the two bones in the human forearm.}}
There's no sphere here. There's a vector that goes from the sensor to the potentially sensed object, whose length can be in-range or out-of-range. And there's another vector, the X axis of the prim, whose angle with the first vector determines whether the arc is in-range or out-of-range. No idea where your pupils got the concept of radius from, but I'd bet that it's either from their own imagination or because you introduced it as a sphere in the first place. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 11:04, 19 March 2015 (PDT)

:::::: Quote: [ it's either from their own imagination or because you introduced it as a sphere in the first place. ] ~ Pedro Oval
:::::: Response: I'd say it's more probable they infer it from this image, which is part of the wiki for this function itself. http://wiki.secondlife.com/wiki/File:Sensor_pi.png [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 13:10, 19 March 2015 (PDT)

Talk:LlSensor

2015-08-16T03:12:39Z

Dale Innis: /* Diameter or Radius? */

{{talk}}
If PI/4 is a 45 degree cone: if the cone's axis is 1, does the base have a diameter of 2, or a diameter of ~0.82? --[[User:Asha Vultee|Asha Vultee]] 12:53, 19 November 2007 (PST)

:Strictly speaking, it's not a cone. If you want an idea of what the shape will look like run the following script. -- [[User:Strife Onizuka|Strife Onizuka]] 13:20, 19 November 2007 (PST)
<pre>
float arc;

default
{
state_entry()
{
llSetPrimitiveParams([PRIM_TYPE, PRIM_TYPE_SPHERE, 0, <0.,1.,0.>, 0.0, <0.,0.,0.>, <0.,arc/PI,0.>]);
}
}
</pre>

== Agent? ==

Hey everyone, don't you think the "AGENT" flag should have a description along the lines of "This is used to find avatars only". rather than a blank description? I tried to add it myself, but I'm afraid I'm too newbie to understand the formatting... I couldn't find that particular table.{{unsigned|Hikaru Dreadlow|17:31, 23 June 2008}}

:Will do, the table is in a template ([[Template:LSL_Constants_Sensor]]) so that it can be included on llSensorRepeat too. -- [[User:Strife Onizuka|Strife Onizuka]] 15:02, 23 June 2008 (PDT)

== All Object Sensor? ==

Hey, can anyone tell me how to make an llSensor() that will scan for ANY object? For example, both physical and nonphysical, scripted and nonscripted, any combination. I tried combining all the flags (besides AGENT) with bitwise |, but it didn't seem to pick up all objects in range.{{unsigned|Crystals Galicia|16:45, 22 September 2008}}

BloodyRain Rang: seems like LL screwed the sensors up cause 0 as type should find all things, even avatars but it doesnt work. And without that it seems impossible to detect any objects without going through all combinations of ACTIVE PASSIVE and SCRIPTED (7 combinations btw). Hope this get fixed someday. (2008-12-08){{unsigned|BloodyRain Rang|18:02, 8 December 2008}}

:My apologies for not catching this sooner (or seeing these comments). The documentation was in error about zero being an acceptable value for '''type'''. The error stemmed from the documentation being based initially on the tooltips from the client script editor. Most such errors were caught during the initial import but not all. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:21, 8 December 2008 (UTC)

== The return of NULL_KEY caveats are a little lacking ==

The sensor will not trigger if an invalid key (NULL_KEY) is "found" but if the structure of the script allows it the empty NULL_KEY can be returned. As with the simple following.<lsl>default
{
state_entry()
{
llSensorRepeat("", "", 3, 20.0, PI, 1.0);
}
sensor(integer detected)
{
llSay(0, (string)llDetectedName(0));
llSay(0, (string)llDetectedName(1));
llSay(0, (string)llDetectedName(2));
llSay(0, (string)llDetectedName(3));
llSay(0, (string)llDetectedName(4));
llSay(0, (string)llDetectedName(5));
}
}</lsl>I'm not saying this is good scripting but since it returns 5 null keys and 1 avatar (if it only finds one etc.) not being fully aware of the facts while compiling lists for eg. could get messy. Fact: If the event is not structured well to exclude NULL_KEYs they can be returned. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 21:21, 8 August 2009 (UTC)

== Agent's sit target no longer shows up? ==
This statement:
"If the agent is sitting on an object, the root prim of the sat upon object becomes a second sensor target for the agent (but not if the avatar is outside the sensor arc, see SVC-5145[c])."
no longer seems to be true - if you search for an agent, you only get the agent, and not the object it's sitting on. (No clue when this changed, I only tried it for the first time tonight).
[[User:Redwood Rhiadra|Redwood Rhiadra]] 01:22, 2 October 2010 (UTC)
: Hi, this feature is definitely confusing, that is what {{Jira|SVC-5145}} is, a request to make the behavior sensible and consistent. I will repeat the tests this weekend and see if it is broken in the same old way or if there are new ways too. --[[User:Cerise Sorbet|Cerise Sorbet]] 03:30, 2 October 2010 (UTC)

__________________________________

== examples on this page are inadequate. ==

And no, I don't dare try to add any more, because Strife the Control Queen doesn't need examples for himself, so he just deletes them all.

[[User:Chaz Longstaff|Chaz Longstaff]] 18:20, 19 September 2011 (PDT)
:The ad homimem attack is unnecessary. Taking a look at llListen which is another function that is paired with an event, I added an example script to showcase llSensor with the sensor event. Will that do? --[[User:Nexii Malthus|Nexii Malthus]] 19:45, 19 September 2011 (PDT)

I don't recall deleting any content recently, let alone an example. I remember once in the last year(or two?) deleting an entirely duplicate example (had been double pasted into the article?) but nothing more recent. So I'm at a bit of a loss for words.

I honestly wish people would post more examples, there is even a category for articles in need of examples: [[:Category:LSL_Needs_Example]] and general improvement [[:Category:LSL FixMe]]. I generally leave writing examples to others, not because I don't find them useful, I often can't think of a simple useful example, my examples tend to bury the usage in a script that is better placed in the Script Library (which no one ever sees or uses). I don't spend much time here and less time in SL, so I'm pretty cautious with my edits and unlikely to edit an example or script.

So I'm Currently working my way through the new functions and features from [[Release_Notes/Second_Life_RC_LeTigre/11#11.09.09.240509]] but I don't have a lot of time to devote to it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:21, 20 September 2011 (PDT)

== Error with sensor page ==

has anybody noticed that the sensor page shows up odd when not loged into the wiki?[[User:Tmzasz Luminos|Tmzasz Luminos]] 20:15, 14 February 2012 (PST)

:What browser are you using? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:21, 15 February 2012 (PST)

:Never mind, it's definitely a wiki engine issue. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:31, 15 February 2012 (PST)

:{{Jira|WEB-4489}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:34, 17 February 2012 (PST)

== AGENT vs AGENT_BY_LEGACY_NAME - No ambiguity if there's no name to filter by ==

The docs say: "If name, id, and/or type are empty or 0, they are ignored." In that case, the name is empty, it's ignored and not to be interpreted in any meaningful way. There is no possible ambiguity on how the name should be interpreted because there is no name to filter by. And please explain the removal of the text about how adding a name affects the result. It was a good example of how to use AGENT_BY_LEGACY_NAME to resolve the ambiguity. Maybe a fictitious name should be used instead of an existing one to prevent self-promotion. I'd agree with that, but that name wasn't even touched. I don't understand the reversal. -- [[User:Sei Lisa|Sei Lisa]] 10:00, 22 October 2013 (PDT)

: I think the example text rollback was an oversight. I shall put it back. I agree, we should choose someone else, for kicks we could make it the last person who edits the page. Thoughts?
: I'm going to split hairs a bit, the ambiguity does not go away, it just becomes meaningless. However when you edit the code to add a name, that is when the ambiguity matters and where AGENT bite you in the butt. I'd really would like to kill [[AGENT]] off to rid us of this problem. With AGENT we save in letters typed but we get burned by creating a lovely little "Gotcha": For the new users they would see the three flags and expect [[AGENT]] to be the generic form that allows you to search by either and most likely to be the one that searches by display name. No [[AGENT]], no misunderstanding in the mind of the reader. Hopefully when they encounter [[AGENT]] it will be on the documentation. Regardless, I find using the longer name with the null case distasteful but something I think is worth inflicting on new users. Like using [[run_time_permissions]].
: Your gallery solution is the most practical of them all. I not happy with how gallery breaks things but recreating gallery with templates is something I'm going to avoid. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:39, 22 October 2013 (PDT)

:: On names: using either a famous Linden name or a fictitious name feels better than a variable one. Governor Linden is one I'm considering, and John Doe is another. I'd lean towards the latter.
:: On the gallery: What I miss with the gallery is a reference in the text that says where to find it ("look at the bottom of this page...")
:: On the edit: Given that I have yet to see one use case for AGENT_BY_USERNAME, I would aim for readability, and AGENT is preferable not because it's shorter, but because it doesn't confuse with something that is very rarely if at all there (the username or the legacy name). Once you put a name, if that ever happens, which I doubt, especially for a new user, you can change it to the correct type of name. And of course, you can not "kill" AGENT, because AGENT_BY_USERNAME does simply not work at all with llDetectedType, and AGENT_BY_LEGACY_NAME is very clearly a misname for that case. The flags are shared with llDetectedType and there's even no indication in that page that AGENT_BY_USERNAME won't work at all with it. That is a separate issue, but the logic that leads to preferring AGENT there also applies to prefer AGENT when no name is specified in llSensor. -- [[User:Sei Lisa|Sei Lisa]] 01:16, 23 October 2013 (PDT)

:: <rant> I consider the introduction of AGENT_BY_LEGACY_NAME a mistake. The whole display name system has been a hack on top of the existing, now "legacy" name system, including the LSL additions. The same logic that led to the introduction of AGENT_BY_LEGACY_NAME should for example have led to deprecating llKey2Name and introducing llGetLegacyName as a synonym, yet that didn't happen. People are expected to know that llKey2Name returns a legacy name and not a display name or username. It shouldn't be any different with AGENT; just adding AGENT_BY_USERNAME to provide access to the new functionality should have been enough. The mere presence of AGENT_BY_LEGACY_NAME has proven to introduce more confusion than the one caused by forgetting to change it to AGENT_BY_USERNAME when using a username in the name (again, if that ever happens). The problem is that it references a name where it isn't applicable, leaving the reader of the code wondering: "Name? What name?" It's akin to giving instructions to someone having a step that is not applicable at all. Imagine telling someone "Go straight through this street; turn right when you see a sign that says 'X', and turn left when you see a sign that says 'Y'" but there is only an 'Y' sign and all that is needed to reach the destination is to turn left when reaching it. The instructions are logically impeccable, and anyone following them literally will reach the destination, but the receiver will wonder where is that 'X' sign. That's what I feel every time I see a llSensor call using "" as name and AGENT_BY_LEGACY_NAME as constant. If one is to be killed, it's AGENT_BY_LEGACY_NAME, not AGENT. </rant>
:: There, I said it. To elaborate on shortness, being shorter is not at all a reason to prefer it. I really wish that it at least had a namespace prefix like SENSOR_ or OBJECT_TYPE_ or the like, to reduce the chance of name collisions and clarify the scope of its applicability. It doesn't, sadly. -- [[User:Sei Lisa|Sei Lisa]] 02:00, 23 October 2013 (PDT)
:::Good point about directions.
:::llDetectedType: I'll poke the template so it does not show the AGENT_* constants there, only AGENT. I really wish they had prefixed them, also the texture animation constants, who would guess [[PING_PONG]] was a texture animation constant without looking it up? LSL was built before it was designed. Personally it all have been better if LSL was object oriented, you wouldn't have had so many silly lookup functions.
:::Governor Linden was actually who I was thinking of, that or Philip Linden. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:59, 23 October 2013 (PDT)

::::I have to agree with Sei on this one. It is clearly silly to say you are searching by a name when that is exactly what you are not doing. Like it or not, AGENT exists, and we should demonstrate it. I will continue to use AGENT where appropriate for as long as it compiles. I also belong to the school that feels that the whole display name idea was a stupid mistake. [[User:Omei Qunhua|Omei Qunhua]] 12:52, 23 October 2013 (PDT)

:::: @ Strife:
:::: On names: While I still would lean towards John Doe, I have no strong opinion; Governor Linden is fine with me. Philip Linden could potentially have political issues in future, I hope not.
:::: On prefixes: Sad thing is they made the same mistake recently when they introduced HORIZONTAL and VERTICAL for pathfinding. Talk about namespace pollution. Oh, well.
:::: On the change: would you consider re-applying my changes then?
:::: @ Omei: Thanks for the support :) I wouldn't go as far as calling it a stupid mistake, but it's a hack no matter how good or bad idea it is. -- [[User:Sei Lisa|Sei Lisa]] 13:20, 23 October 2013 (PDT)

:::: Thanks for the change, very appreciated! -- [[User:Sei Lisa|Sei Lisa]] 10:05, 24 October 2013 (PDT)

::::: You are welcome. I would be ok with causing a little political uproar. Streisand effect, would be good for the wiki. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:01, 25 October 2013 (PDT)

== Diameter or Radius? ==

Why does this functions wiki page not explicitly state weather the float RANGE, is a Diameter, or a Radius?

Just calling it a Range, seems kinda ambiguous. Sure many of us can just assume, or experiment to be sure. But it seems like info that belongs on the upper most definition of the function.

Maybe I'm just missing it due to sleep deprivation. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 15:23, 18 March 2015 (PDT)

:"Range" means distance from the prim's or the wearer's center. That forms a sphere around said center, with the range's radius, within which everything is "in range" and everything outside is "out of range". Therefore it is the radius. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 04:44, 19 March 2015 (PDT)

::I submit my edit to the page for clarity. I was confident my mention of radius, and "distance from center" was sufficient, valid, and helpful. If it doesn't get changed back, then yay for a positive contribution! [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 07:33, 19 March 2015 (PDT)

::: I personally find it more confusing when put that way. It doesn't state the center of what, or the radius or what geometric figure or why it matters, while "range" is clearly implicitly referring to a distance, which logically must be from the script that has the sensor to the detected object. I don't know where did your confusion between radius and diameter come from, as not many people will realize immediately that the range volume forms a sphere. My vote is for that change to be reverted. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 08:57, 19 March 2015 (PDT)

:::: I fail to see where saying "Range" by itself is any more descriptive or accurate. It leaves more to the imagination then saying Radius, which by definition indicates from center point, inclusively to an end. Range, in fact can be easily misconstrued as a diameter, a square field, or a point at a variable distance forming a ring. Semantics are important and layman's terms such as "Range" when referring to a Radius, do not provide enough info for an accurate visualization of the procedure. I prefer to call a dog "a dog", rather then "the thing". One I know not to store in the attic for a few years, the other, not so much. If you don't understand what the word Radius means, you can easily look it up in a dictionary, but looking up "Range" in a dictionary wont provide you any insight as to weather this process uses a diameter or a radius. In fact many people who I've taught scripting to have asked me if "Range" was halved, when the Arc, was PI / 4. Implying they presumed "Range" to be a diameter. I wonder where they got that notion?? Perhaps it was from the lack of clarity in this functions description. I suppose Ray-Length could be another plausible word. but it's 2 words. and "Length", by itself would also not distinguish between diameter and radius as both are a measure of length. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 09:56, 19 March 2015 (PDT)

::::: {{quote|radius:

1. a straight line from the center to the circumference of a circle or sphere.
2. the thicker and shorter of the two bones in the human forearm.}}
There's no sphere here. There's a vector that goes from the sensor to the potentially sensed object, whose length can be in-range or out-of-range. And there's another vector, the X axis of the prim, whose angle with the first vector determines whether the arc is in-range or out-of-range. No idea where your pupils got the concept of radius from, but I'd bet that it's either from their own imagination or because you introduced it as a sphere in the first place. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 11:04, 19 March 2015 (PDT)

:::::: Quote: [ it's either from their own imagination or because you introduced it as a sphere in the first place. ] ~ Pedro Oval
:::::: Response: I'd say it's more probable they infer it from this image, which is part of the wiki for this function itself. http://wiki.secondlife.com/wiki/File:Sensor_pi.png [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 13:10, 19 March 2015 (PDT)

(Why does this cause the rest of the page to be indented wildly?)

== Can it look the other way? ==

I'm trying to make a single prim see 30 things that are scattered symmetrically around it. A single sensor() call can't see them all, as there are too many. I thought I could look at the 15 in front, and then the 15 in back, but the arc is always in the forward direction. Is there any way (a negative arc?) to look just behind and not in front? I will do the experiment :) but if anyone knows... [[User:Dale Innis|Dale Innis]] ([[User talk:Dale Innis|talk]]) 20:08, 15 August 2015 (PDT)

Talk:LlSensor

2015-08-16T03:11:45Z

Dale Innis: /* Diameter or Radius? */

{{talk}}
If PI/4 is a 45 degree cone: if the cone's axis is 1, does the base have a diameter of 2, or a diameter of ~0.82? --[[User:Asha Vultee|Asha Vultee]] 12:53, 19 November 2007 (PST)

:Strictly speaking, it's not a cone. If you want an idea of what the shape will look like run the following script. -- [[User:Strife Onizuka|Strife Onizuka]] 13:20, 19 November 2007 (PST)
<pre>
float arc;

default
{
state_entry()
{
llSetPrimitiveParams([PRIM_TYPE, PRIM_TYPE_SPHERE, 0, <0.,1.,0.>, 0.0, <0.,0.,0.>, <0.,arc/PI,0.>]);
}
}
</pre>

== Agent? ==

Hey everyone, don't you think the "AGENT" flag should have a description along the lines of "This is used to find avatars only". rather than a blank description? I tried to add it myself, but I'm afraid I'm too newbie to understand the formatting... I couldn't find that particular table.{{unsigned|Hikaru Dreadlow|17:31, 23 June 2008}}

:Will do, the table is in a template ([[Template:LSL_Constants_Sensor]]) so that it can be included on llSensorRepeat too. -- [[User:Strife Onizuka|Strife Onizuka]] 15:02, 23 June 2008 (PDT)

== All Object Sensor? ==

Hey, can anyone tell me how to make an llSensor() that will scan for ANY object? For example, both physical and nonphysical, scripted and nonscripted, any combination. I tried combining all the flags (besides AGENT) with bitwise |, but it didn't seem to pick up all objects in range.{{unsigned|Crystals Galicia|16:45, 22 September 2008}}

BloodyRain Rang: seems like LL screwed the sensors up cause 0 as type should find all things, even avatars but it doesnt work. And without that it seems impossible to detect any objects without going through all combinations of ACTIVE PASSIVE and SCRIPTED (7 combinations btw). Hope this get fixed someday. (2008-12-08){{unsigned|BloodyRain Rang|18:02, 8 December 2008}}

:My apologies for not catching this sooner (or seeing these comments). The documentation was in error about zero being an acceptable value for '''type'''. The error stemmed from the documentation being based initially on the tooltips from the client script editor. Most such errors were caught during the initial import but not all. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:21, 8 December 2008 (UTC)

== The return of NULL_KEY caveats are a little lacking ==

The sensor will not trigger if an invalid key (NULL_KEY) is "found" but if the structure of the script allows it the empty NULL_KEY can be returned. As with the simple following.<lsl>default
{
state_entry()
{
llSensorRepeat("", "", 3, 20.0, PI, 1.0);
}
sensor(integer detected)
{
llSay(0, (string)llDetectedName(0));
llSay(0, (string)llDetectedName(1));
llSay(0, (string)llDetectedName(2));
llSay(0, (string)llDetectedName(3));
llSay(0, (string)llDetectedName(4));
llSay(0, (string)llDetectedName(5));
}
}</lsl>I'm not saying this is good scripting but since it returns 5 null keys and 1 avatar (if it only finds one etc.) not being fully aware of the facts while compiling lists for eg. could get messy. Fact: If the event is not structured well to exclude NULL_KEYs they can be returned. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 21:21, 8 August 2009 (UTC)

== Agent's sit target no longer shows up? ==
This statement:
"If the agent is sitting on an object, the root prim of the sat upon object becomes a second sensor target for the agent (but not if the avatar is outside the sensor arc, see SVC-5145[c])."
no longer seems to be true - if you search for an agent, you only get the agent, and not the object it's sitting on. (No clue when this changed, I only tried it for the first time tonight).
[[User:Redwood Rhiadra|Redwood Rhiadra]] 01:22, 2 October 2010 (UTC)
: Hi, this feature is definitely confusing, that is what {{Jira|SVC-5145}} is, a request to make the behavior sensible and consistent. I will repeat the tests this weekend and see if it is broken in the same old way or if there are new ways too. --[[User:Cerise Sorbet|Cerise Sorbet]] 03:30, 2 October 2010 (UTC)

__________________________________

== examples on this page are inadequate. ==

And no, I don't dare try to add any more, because Strife the Control Queen doesn't need examples for himself, so he just deletes them all.

[[User:Chaz Longstaff|Chaz Longstaff]] 18:20, 19 September 2011 (PDT)
:The ad homimem attack is unnecessary. Taking a look at llListen which is another function that is paired with an event, I added an example script to showcase llSensor with the sensor event. Will that do? --[[User:Nexii Malthus|Nexii Malthus]] 19:45, 19 September 2011 (PDT)

I don't recall deleting any content recently, let alone an example. I remember once in the last year(or two?) deleting an entirely duplicate example (had been double pasted into the article?) but nothing more recent. So I'm at a bit of a loss for words.

I honestly wish people would post more examples, there is even a category for articles in need of examples: [[:Category:LSL_Needs_Example]] and general improvement [[:Category:LSL FixMe]]. I generally leave writing examples to others, not because I don't find them useful, I often can't think of a simple useful example, my examples tend to bury the usage in a script that is better placed in the Script Library (which no one ever sees or uses). I don't spend much time here and less time in SL, so I'm pretty cautious with my edits and unlikely to edit an example or script.

So I'm Currently working my way through the new functions and features from [[Release_Notes/Second_Life_RC_LeTigre/11#11.09.09.240509]] but I don't have a lot of time to devote to it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:21, 20 September 2011 (PDT)

== Error with sensor page ==

has anybody noticed that the sensor page shows up odd when not loged into the wiki?[[User:Tmzasz Luminos|Tmzasz Luminos]] 20:15, 14 February 2012 (PST)

:What browser are you using? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:21, 15 February 2012 (PST)

:Never mind, it's definitely a wiki engine issue. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:31, 15 February 2012 (PST)

:{{Jira|WEB-4489}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:34, 17 February 2012 (PST)

== AGENT vs AGENT_BY_LEGACY_NAME - No ambiguity if there's no name to filter by ==

The docs say: "If name, id, and/or type are empty or 0, they are ignored." In that case, the name is empty, it's ignored and not to be interpreted in any meaningful way. There is no possible ambiguity on how the name should be interpreted because there is no name to filter by. And please explain the removal of the text about how adding a name affects the result. It was a good example of how to use AGENT_BY_LEGACY_NAME to resolve the ambiguity. Maybe a fictitious name should be used instead of an existing one to prevent self-promotion. I'd agree with that, but that name wasn't even touched. I don't understand the reversal. -- [[User:Sei Lisa|Sei Lisa]] 10:00, 22 October 2013 (PDT)

: I think the example text rollback was an oversight. I shall put it back. I agree, we should choose someone else, for kicks we could make it the last person who edits the page. Thoughts?
: I'm going to split hairs a bit, the ambiguity does not go away, it just becomes meaningless. However when you edit the code to add a name, that is when the ambiguity matters and where AGENT bite you in the butt. I'd really would like to kill [[AGENT]] off to rid us of this problem. With AGENT we save in letters typed but we get burned by creating a lovely little "Gotcha": For the new users they would see the three flags and expect [[AGENT]] to be the generic form that allows you to search by either and most likely to be the one that searches by display name. No [[AGENT]], no misunderstanding in the mind of the reader. Hopefully when they encounter [[AGENT]] it will be on the documentation. Regardless, I find using the longer name with the null case distasteful but something I think is worth inflicting on new users. Like using [[run_time_permissions]].
: Your gallery solution is the most practical of them all. I not happy with how gallery breaks things but recreating gallery with templates is something I'm going to avoid. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:39, 22 October 2013 (PDT)

:: On names: using either a famous Linden name or a fictitious name feels better than a variable one. Governor Linden is one I'm considering, and John Doe is another. I'd lean towards the latter.
:: On the gallery: What I miss with the gallery is a reference in the text that says where to find it ("look at the bottom of this page...")
:: On the edit: Given that I have yet to see one use case for AGENT_BY_USERNAME, I would aim for readability, and AGENT is preferable not because it's shorter, but because it doesn't confuse with something that is very rarely if at all there (the username or the legacy name). Once you put a name, if that ever happens, which I doubt, especially for a new user, you can change it to the correct type of name. And of course, you can not "kill" AGENT, because AGENT_BY_USERNAME does simply not work at all with llDetectedType, and AGENT_BY_LEGACY_NAME is very clearly a misname for that case. The flags are shared with llDetectedType and there's even no indication in that page that AGENT_BY_USERNAME won't work at all with it. That is a separate issue, but the logic that leads to preferring AGENT there also applies to prefer AGENT when no name is specified in llSensor. -- [[User:Sei Lisa|Sei Lisa]] 01:16, 23 October 2013 (PDT)

:: <rant> I consider the introduction of AGENT_BY_LEGACY_NAME a mistake. The whole display name system has been a hack on top of the existing, now "legacy" name system, including the LSL additions. The same logic that led to the introduction of AGENT_BY_LEGACY_NAME should for example have led to deprecating llKey2Name and introducing llGetLegacyName as a synonym, yet that didn't happen. People are expected to know that llKey2Name returns a legacy name and not a display name or username. It shouldn't be any different with AGENT; just adding AGENT_BY_USERNAME to provide access to the new functionality should have been enough. The mere presence of AGENT_BY_LEGACY_NAME has proven to introduce more confusion than the one caused by forgetting to change it to AGENT_BY_USERNAME when using a username in the name (again, if that ever happens). The problem is that it references a name where it isn't applicable, leaving the reader of the code wondering: "Name? What name?" It's akin to giving instructions to someone having a step that is not applicable at all. Imagine telling someone "Go straight through this street; turn right when you see a sign that says 'X', and turn left when you see a sign that says 'Y'" but there is only an 'Y' sign and all that is needed to reach the destination is to turn left when reaching it. The instructions are logically impeccable, and anyone following them literally will reach the destination, but the receiver will wonder where is that 'X' sign. That's what I feel every time I see a llSensor call using "" as name and AGENT_BY_LEGACY_NAME as constant. If one is to be killed, it's AGENT_BY_LEGACY_NAME, not AGENT. </rant>
:: There, I said it. To elaborate on shortness, being shorter is not at all a reason to prefer it. I really wish that it at least had a namespace prefix like SENSOR_ or OBJECT_TYPE_ or the like, to reduce the chance of name collisions and clarify the scope of its applicability. It doesn't, sadly. -- [[User:Sei Lisa|Sei Lisa]] 02:00, 23 October 2013 (PDT)
:::Good point about directions.
:::llDetectedType: I'll poke the template so it does not show the AGENT_* constants there, only AGENT. I really wish they had prefixed them, also the texture animation constants, who would guess [[PING_PONG]] was a texture animation constant without looking it up? LSL was built before it was designed. Personally it all have been better if LSL was object oriented, you wouldn't have had so many silly lookup functions.
:::Governor Linden was actually who I was thinking of, that or Philip Linden. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:59, 23 October 2013 (PDT)

::::I have to agree with Sei on this one. It is clearly silly to say you are searching by a name when that is exactly what you are not doing. Like it or not, AGENT exists, and we should demonstrate it. I will continue to use AGENT where appropriate for as long as it compiles. I also belong to the school that feels that the whole display name idea was a stupid mistake. [[User:Omei Qunhua|Omei Qunhua]] 12:52, 23 October 2013 (PDT)

:::: @ Strife:
:::: On names: While I still would lean towards John Doe, I have no strong opinion; Governor Linden is fine with me. Philip Linden could potentially have political issues in future, I hope not.
:::: On prefixes: Sad thing is they made the same mistake recently when they introduced HORIZONTAL and VERTICAL for pathfinding. Talk about namespace pollution. Oh, well.
:::: On the change: would you consider re-applying my changes then?
:::: @ Omei: Thanks for the support :) I wouldn't go as far as calling it a stupid mistake, but it's a hack no matter how good or bad idea it is. -- [[User:Sei Lisa|Sei Lisa]] 13:20, 23 October 2013 (PDT)

:::: Thanks for the change, very appreciated! -- [[User:Sei Lisa|Sei Lisa]] 10:05, 24 October 2013 (PDT)

::::: You are welcome. I would be ok with causing a little political uproar. Streisand effect, would be good for the wiki. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:01, 25 October 2013 (PDT)

== Diameter or Radius? ==

Why does this functions wiki page not explicitly state weather the float RANGE, is a Diameter, or a Radius?

Just calling it a Range, seems kinda ambiguous. Sure many of us can just assume, or experiment to be sure. But it seems like info that belongs on the upper most definition of the function.

Maybe I'm just missing it due to sleep deprivation. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 15:23, 18 March 2015 (PDT)

:"Range" means distance from the prim's or the wearer's center. That forms a sphere around said center, with the range's radius, within which everything is "in range" and everything outside is "out of range". Therefore it is the radius. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 04:44, 19 March 2015 (PDT)

::I submit my edit to the page for clarity. I was confident my mention of radius, and "distance from center" was sufficient, valid, and helpful. If it doesn't get changed back, then yay for a positive contribution! [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 07:33, 19 March 2015 (PDT)

::: I personally find it more confusing when put that way. It doesn't state the center of what, or the radius or what geometric figure or why it matters, while "range" is clearly implicitly referring to a distance, which logically must be from the script that has the sensor to the detected object. I don't know where did your confusion between radius and diameter come from, as not many people will realize immediately that the range volume forms a sphere. My vote is for that change to be reverted. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 08:57, 19 March 2015 (PDT)

:::: I fail to see where saying "Range" by itself is any more descriptive or accurate. It leaves more to the imagination then saying Radius, which by definition indicates from center point, inclusively to an end. Range, in fact can be easily misconstrued as a diameter, a square field, or a point at a variable distance forming a ring. Semantics are important and layman's terms such as "Range" when referring to a Radius, do not provide enough info for an accurate visualization of the procedure. I prefer to call a dog "a dog", rather then "the thing". One I know not to store in the attic for a few years, the other, not so much. If you don't understand what the word Radius means, you can easily look it up in a dictionary, but looking up "Range" in a dictionary wont provide you any insight as to weather this process uses a diameter or a radius. In fact many people who I've taught scripting to have asked me if "Range" was halved, when the Arc, was PI / 4. Implying they presumed "Range" to be a diameter. I wonder where they got that notion?? Perhaps it was from the lack of clarity in this functions description. I suppose Ray-Length could be another plausible word. but it's 2 words. and "Length", by itself would also not distinguish between diameter and radius as both are a measure of length. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 09:56, 19 March 2015 (PDT)

::::: {{quote|radius:

1. a straight line from the center to the circumference of a circle or sphere.
2. the thicker and shorter of the two bones in the human forearm.}}
There's no sphere here. There's a vector that goes from the sensor to the potentially sensed object, whose length can be in-range or out-of-range. And there's another vector, the X axis of the prim, whose angle with the first vector determines whether the arc is in-range or out-of-range. No idea where your pupils got the concept of radius from, but I'd bet that it's either from their own imagination or because you introduced it as a sphere in the first place. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 11:04, 19 March 2015 (PDT)

:::::: Quote: [ it's either from their own imagination or because you introduced it as a sphere in the first place. ] ~ Pedro Oval
:::::: Response: I'd say it's more probable they infer it from this image, which is part of the wiki for this function itself. http://wiki.secondlife.com/wiki/File:Sensor_pi.png [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 13:10, 19 March 2015 (PDT)

.

== Can it look the other way? ==

I'm trying to make a single prim see 30 things that are scattered symmetrically around it. A single sensor() call can't see them all, as there are too many. I thought I could look at the 15 in front, and then the 15 in back, but the arc is always in the forward direction. Is there any way (a negative arc?) to look just behind and not in front? I will do the experiment :) but if anyone knows... [[User:Dale Innis|Dale Innis]] ([[User talk:Dale Innis|talk]]) 20:08, 15 August 2015 (PDT)

Talk:LlSensor

2015-08-16T03:08:37Z

Dale Innis: /* Can it look the other way? */ new section

{{talk}}
If PI/4 is a 45 degree cone: if the cone's axis is 1, does the base have a diameter of 2, or a diameter of ~0.82? --[[User:Asha Vultee|Asha Vultee]] 12:53, 19 November 2007 (PST)

:Strictly speaking, it's not a cone. If you want an idea of what the shape will look like run the following script. -- [[User:Strife Onizuka|Strife Onizuka]] 13:20, 19 November 2007 (PST)
<pre>
float arc;

default
{
state_entry()
{
llSetPrimitiveParams([PRIM_TYPE, PRIM_TYPE_SPHERE, 0, <0.,1.,0.>, 0.0, <0.,0.,0.>, <0.,arc/PI,0.>]);
}
}
</pre>

== Agent? ==

Hey everyone, don't you think the "AGENT" flag should have a description along the lines of "This is used to find avatars only". rather than a blank description? I tried to add it myself, but I'm afraid I'm too newbie to understand the formatting... I couldn't find that particular table.{{unsigned|Hikaru Dreadlow|17:31, 23 June 2008}}

:Will do, the table is in a template ([[Template:LSL_Constants_Sensor]]) so that it can be included on llSensorRepeat too. -- [[User:Strife Onizuka|Strife Onizuka]] 15:02, 23 June 2008 (PDT)

== All Object Sensor? ==

Hey, can anyone tell me how to make an llSensor() that will scan for ANY object? For example, both physical and nonphysical, scripted and nonscripted, any combination. I tried combining all the flags (besides AGENT) with bitwise |, but it didn't seem to pick up all objects in range.{{unsigned|Crystals Galicia|16:45, 22 September 2008}}

BloodyRain Rang: seems like LL screwed the sensors up cause 0 as type should find all things, even avatars but it doesnt work. And without that it seems impossible to detect any objects without going through all combinations of ACTIVE PASSIVE and SCRIPTED (7 combinations btw). Hope this get fixed someday. (2008-12-08){{unsigned|BloodyRain Rang|18:02, 8 December 2008}}

:My apologies for not catching this sooner (or seeing these comments). The documentation was in error about zero being an acceptable value for '''type'''. The error stemmed from the documentation being based initially on the tooltips from the client script editor. Most such errors were caught during the initial import but not all. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:21, 8 December 2008 (UTC)

== The return of NULL_KEY caveats are a little lacking ==

The sensor will not trigger if an invalid key (NULL_KEY) is "found" but if the structure of the script allows it the empty NULL_KEY can be returned. As with the simple following.<lsl>default
{
state_entry()
{
llSensorRepeat("", "", 3, 20.0, PI, 1.0);
}
sensor(integer detected)
{
llSay(0, (string)llDetectedName(0));
llSay(0, (string)llDetectedName(1));
llSay(0, (string)llDetectedName(2));
llSay(0, (string)llDetectedName(3));
llSay(0, (string)llDetectedName(4));
llSay(0, (string)llDetectedName(5));
}
}</lsl>I'm not saying this is good scripting but since it returns 5 null keys and 1 avatar (if it only finds one etc.) not being fully aware of the facts while compiling lists for eg. could get messy. Fact: If the event is not structured well to exclude NULL_KEYs they can be returned. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 21:21, 8 August 2009 (UTC)

== Agent's sit target no longer shows up? ==
This statement:
"If the agent is sitting on an object, the root prim of the sat upon object becomes a second sensor target for the agent (but not if the avatar is outside the sensor arc, see SVC-5145[c])."
no longer seems to be true - if you search for an agent, you only get the agent, and not the object it's sitting on. (No clue when this changed, I only tried it for the first time tonight).
[[User:Redwood Rhiadra|Redwood Rhiadra]] 01:22, 2 October 2010 (UTC)
: Hi, this feature is definitely confusing, that is what {{Jira|SVC-5145}} is, a request to make the behavior sensible and consistent. I will repeat the tests this weekend and see if it is broken in the same old way or if there are new ways too. --[[User:Cerise Sorbet|Cerise Sorbet]] 03:30, 2 October 2010 (UTC)

__________________________________

== examples on this page are inadequate. ==

And no, I don't dare try to add any more, because Strife the Control Queen doesn't need examples for himself, so he just deletes them all.

[[User:Chaz Longstaff|Chaz Longstaff]] 18:20, 19 September 2011 (PDT)
:The ad homimem attack is unnecessary. Taking a look at llListen which is another function that is paired with an event, I added an example script to showcase llSensor with the sensor event. Will that do? --[[User:Nexii Malthus|Nexii Malthus]] 19:45, 19 September 2011 (PDT)

I don't recall deleting any content recently, let alone an example. I remember once in the last year(or two?) deleting an entirely duplicate example (had been double pasted into the article?) but nothing more recent. So I'm at a bit of a loss for words.

I honestly wish people would post more examples, there is even a category for articles in need of examples: [[:Category:LSL_Needs_Example]] and general improvement [[:Category:LSL FixMe]]. I generally leave writing examples to others, not because I don't find them useful, I often can't think of a simple useful example, my examples tend to bury the usage in a script that is better placed in the Script Library (which no one ever sees or uses). I don't spend much time here and less time in SL, so I'm pretty cautious with my edits and unlikely to edit an example or script.

So I'm Currently working my way through the new functions and features from [[Release_Notes/Second_Life_RC_LeTigre/11#11.09.09.240509]] but I don't have a lot of time to devote to it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:21, 20 September 2011 (PDT)

== Error with sensor page ==

has anybody noticed that the sensor page shows up odd when not loged into the wiki?[[User:Tmzasz Luminos|Tmzasz Luminos]] 20:15, 14 February 2012 (PST)

:What browser are you using? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:21, 15 February 2012 (PST)

:Never mind, it's definitely a wiki engine issue. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:31, 15 February 2012 (PST)

:{{Jira|WEB-4489}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:34, 17 February 2012 (PST)

== AGENT vs AGENT_BY_LEGACY_NAME - No ambiguity if there's no name to filter by ==

The docs say: "If name, id, and/or type are empty or 0, they are ignored." In that case, the name is empty, it's ignored and not to be interpreted in any meaningful way. There is no possible ambiguity on how the name should be interpreted because there is no name to filter by. And please explain the removal of the text about how adding a name affects the result. It was a good example of how to use AGENT_BY_LEGACY_NAME to resolve the ambiguity. Maybe a fictitious name should be used instead of an existing one to prevent self-promotion. I'd agree with that, but that name wasn't even touched. I don't understand the reversal. -- [[User:Sei Lisa|Sei Lisa]] 10:00, 22 October 2013 (PDT)

: I think the example text rollback was an oversight. I shall put it back. I agree, we should choose someone else, for kicks we could make it the last person who edits the page. Thoughts?
: I'm going to split hairs a bit, the ambiguity does not go away, it just becomes meaningless. However when you edit the code to add a name, that is when the ambiguity matters and where AGENT bite you in the butt. I'd really would like to kill [[AGENT]] off to rid us of this problem. With AGENT we save in letters typed but we get burned by creating a lovely little "Gotcha": For the new users they would see the three flags and expect [[AGENT]] to be the generic form that allows you to search by either and most likely to be the one that searches by display name. No [[AGENT]], no misunderstanding in the mind of the reader. Hopefully when they encounter [[AGENT]] it will be on the documentation. Regardless, I find using the longer name with the null case distasteful but something I think is worth inflicting on new users. Like using [[run_time_permissions]].
: Your gallery solution is the most practical of them all. I not happy with how gallery breaks things but recreating gallery with templates is something I'm going to avoid. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:39, 22 October 2013 (PDT)

:: On names: using either a famous Linden name or a fictitious name feels better than a variable one. Governor Linden is one I'm considering, and John Doe is another. I'd lean towards the latter.
:: On the gallery: What I miss with the gallery is a reference in the text that says where to find it ("look at the bottom of this page...")
:: On the edit: Given that I have yet to see one use case for AGENT_BY_USERNAME, I would aim for readability, and AGENT is preferable not because it's shorter, but because it doesn't confuse with something that is very rarely if at all there (the username or the legacy name). Once you put a name, if that ever happens, which I doubt, especially for a new user, you can change it to the correct type of name. And of course, you can not "kill" AGENT, because AGENT_BY_USERNAME does simply not work at all with llDetectedType, and AGENT_BY_LEGACY_NAME is very clearly a misname for that case. The flags are shared with llDetectedType and there's even no indication in that page that AGENT_BY_USERNAME won't work at all with it. That is a separate issue, but the logic that leads to preferring AGENT there also applies to prefer AGENT when no name is specified in llSensor. -- [[User:Sei Lisa|Sei Lisa]] 01:16, 23 October 2013 (PDT)

:: <rant> I consider the introduction of AGENT_BY_LEGACY_NAME a mistake. The whole display name system has been a hack on top of the existing, now "legacy" name system, including the LSL additions. The same logic that led to the introduction of AGENT_BY_LEGACY_NAME should for example have led to deprecating llKey2Name and introducing llGetLegacyName as a synonym, yet that didn't happen. People are expected to know that llKey2Name returns a legacy name and not a display name or username. It shouldn't be any different with AGENT; just adding AGENT_BY_USERNAME to provide access to the new functionality should have been enough. The mere presence of AGENT_BY_LEGACY_NAME has proven to introduce more confusion than the one caused by forgetting to change it to AGENT_BY_USERNAME when using a username in the name (again, if that ever happens). The problem is that it references a name where it isn't applicable, leaving the reader of the code wondering: "Name? What name?" It's akin to giving instructions to someone having a step that is not applicable at all. Imagine telling someone "Go straight through this street; turn right when you see a sign that says 'X', and turn left when you see a sign that says 'Y'" but there is only an 'Y' sign and all that is needed to reach the destination is to turn left when reaching it. The instructions are logically impeccable, and anyone following them literally will reach the destination, but the receiver will wonder where is that 'X' sign. That's what I feel every time I see a llSensor call using "" as name and AGENT_BY_LEGACY_NAME as constant. If one is to be killed, it's AGENT_BY_LEGACY_NAME, not AGENT. </rant>
:: There, I said it. To elaborate on shortness, being shorter is not at all a reason to prefer it. I really wish that it at least had a namespace prefix like SENSOR_ or OBJECT_TYPE_ or the like, to reduce the chance of name collisions and clarify the scope of its applicability. It doesn't, sadly. -- [[User:Sei Lisa|Sei Lisa]] 02:00, 23 October 2013 (PDT)
:::Good point about directions.
:::llDetectedType: I'll poke the template so it does not show the AGENT_* constants there, only AGENT. I really wish they had prefixed them, also the texture animation constants, who would guess [[PING_PONG]] was a texture animation constant without looking it up? LSL was built before it was designed. Personally it all have been better if LSL was object oriented, you wouldn't have had so many silly lookup functions.
:::Governor Linden was actually who I was thinking of, that or Philip Linden. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:59, 23 October 2013 (PDT)

::::I have to agree with Sei on this one. It is clearly silly to say you are searching by a name when that is exactly what you are not doing. Like it or not, AGENT exists, and we should demonstrate it. I will continue to use AGENT where appropriate for as long as it compiles. I also belong to the school that feels that the whole display name idea was a stupid mistake. [[User:Omei Qunhua|Omei Qunhua]] 12:52, 23 October 2013 (PDT)

:::: @ Strife:
:::: On names: While I still would lean towards John Doe, I have no strong opinion; Governor Linden is fine with me. Philip Linden could potentially have political issues in future, I hope not.
:::: On prefixes: Sad thing is they made the same mistake recently when they introduced HORIZONTAL and VERTICAL for pathfinding. Talk about namespace pollution. Oh, well.
:::: On the change: would you consider re-applying my changes then?
:::: @ Omei: Thanks for the support :) I wouldn't go as far as calling it a stupid mistake, but it's a hack no matter how good or bad idea it is. -- [[User:Sei Lisa|Sei Lisa]] 13:20, 23 October 2013 (PDT)

:::: Thanks for the change, very appreciated! -- [[User:Sei Lisa|Sei Lisa]] 10:05, 24 October 2013 (PDT)

::::: You are welcome. I would be ok with causing a little political uproar. Streisand effect, would be good for the wiki. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:01, 25 October 2013 (PDT)

== Diameter or Radius? ==

Why does this functions wiki page not explicitly state weather the float RANGE, is a Diameter, or a Radius?

Just calling it a Range, seems kinda ambiguous. Sure many of us can just assume, or experiment to be sure. But it seems like info that belongs on the upper most definition of the function.

Maybe I'm just missing it due to sleep deprivation. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 15:23, 18 March 2015 (PDT)

:"Range" means distance from the prim's or the wearer's center. That forms a sphere around said center, with the range's radius, within which everything is "in range" and everything outside is "out of range". Therefore it is the radius. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 04:44, 19 March 2015 (PDT)

::I submit my edit to the page for clarity. I was confident my mention of radius, and "distance from center" was sufficient, valid, and helpful. If it doesn't get changed back, then yay for a positive contribution! [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 07:33, 19 March 2015 (PDT)

::: I personally find it more confusing when put that way. It doesn't state the center of what, or the radius or what geometric figure or why it matters, while "range" is clearly implicitly referring to a distance, which logically must be from the script that has the sensor to the detected object. I don't know where did your confusion between radius and diameter come from, as not many people will realize immediately that the range volume forms a sphere. My vote is for that change to be reverted. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 08:57, 19 March 2015 (PDT)

:::: I fail to see where saying "Range" by itself is any more descriptive or accurate. It leaves more to the imagination then saying Radius, which by definition indicates from center point, inclusively to an end. Range, in fact can be easily misconstrued as a diameter, a square field, or a point at a variable distance forming a ring. Semantics are important and layman's terms such as "Range" when referring to a Radius, do not provide enough info for an accurate visualization of the procedure. I prefer to call a dog "a dog", rather then "the thing". One I know not to store in the attic for a few years, the other, not so much. If you don't understand what the word Radius means, you can easily look it up in a dictionary, but looking up "Range" in a dictionary wont provide you any insight as to weather this process uses a diameter or a radius. In fact many people who I've taught scripting to have asked me if "Range" was halved, when the Arc, was PI / 4. Implying they presumed "Range" to be a diameter. I wonder where they got that notion?? Perhaps it was from the lack of clarity in this functions description. I suppose Ray-Length could be another plausible word. but it's 2 words. and "Length", by itself would also not distinguish between diameter and radius as both are a measure of length. [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 09:56, 19 March 2015 (PDT)

::::: {{quote|radius:

1. a straight line from the center to the circumference of a circle or sphere.
2. the thicker and shorter of the two bones in the human forearm.}}
There's no sphere here. There's a vector that goes from the sensor to the potentially sensed object, whose length can be in-range or out-of-range. And there's another vector, the X axis of the prim, whose angle with the first vector determines whether the arc is in-range or out-of-range. No idea where your pupils got the concept of radius from, but I'd bet that it's either from their own imagination or because you introduced it as a sphere in the first place. --[[User:Pedro Oval|Pedro Oval]] ([[User talk:Pedro Oval|talk]]) 11:04, 19 March 2015 (PDT)

:::::: Quote: [ it's either from their own imagination or because you introduced it as a sphere in the first place. ] ~ Pedro Oval
:::::: Response: I'd say it's more probable they infer it from this image, which is part of the wiki for this function itself. http://wiki.secondlife.com/wiki/File:Sensor_pi.png [[User:ThumpieBunnyEve Hax|ThumpieBunnyEve Hax]] ([[User talk:ThumpieBunnyEve Hax|talk]]) 13:10, 19 March 2015 (PDT)

== Can it look the other way? ==

I'm trying to make a single prim see 30 things that are scattered symmetrically around it. A single sensor() call can't see them all, as there are too many. I thought I could look at the 15 in front, and then the 15 in back, but the arc is always in the forward direction. Is there any way (a negative arc?) to look just behind and not in front? I will do the experiment :) but if anyone knows... [[User:Dale Innis|Dale Innis]] ([[User talk:Dale Innis|talk]]) 20:08, 15 August 2015 (PDT)

Talk:AvatarFollower

2015-02-05T14:19:47Z

Dale Innis: yes, well

Hi

Can I get a full detail of how can I use this script and where should I add this script and the fundamentals .
Thank you.

Well, the "Usage" section is supposed to be that. If you have questions that it doesn't answer, feel free to ask! [[User:Dale Innis|Dale Innis]] ([[User talk:Dale Innis|talk]]) 06:19, 5 February 2015 (PST)

Talk:LlRequestAgentData

2014-10-04T17:56:36Z

Dale Innis: /* What happens with an invalid key? */

Is this function reporting properly? Specifically, I seem to get more "2"s than I should. My status is on file and use and it returns a 2 for me. Yet, I do see threes returned for some people. In fact, I see 0 (No info), 2 (No Info but Used(Weird)) and 3 (Info and used), but never 1 (Info filed). Were the bits repurposed and the docs not updated? --[[User:Clang Bailey|Clang Bailey]] 16:34, 29 January 2008 (PST)
:It is possible to remove the payment information from the file after it has been used. -- [[User:Strife Onizuka|Strife Onizuka]] 20:24, 29 January 2008 (PST)

== taking a byte out of the integer ==

The integer parameter, seems to actually be just the first 8 bits of the the 32bits signed integer, add or subtract 256 (or any power of 256) from any of the constants and the result should be the same, even when going to negative values. --[[User:TigroSpottystripes Katsu|TigroSpottystripes Katsu]] 13:00, 12 September 2009 (UTC)

:This doesn't surprise me. The underlying dataserver [[Message]] I'd bet uses a single byte. The number of frames supported by texture animations are similarly limited. I'll work this into the documentation later (caveat? notes?... notes definately). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:22, 12 September 2009 (UTC)

== Displaying Avatar Name information? ==

I'm not sure what the 3rd caveat intended. It just puts a clickable link in chat to open the avatar's profile. It's not useful to a script that wants to access the name. [[User:Omei Qunhua|Omei Qunhua]] 07:16, 12 January 2013 (PST)

:True, not useful for a script but might be useful for a human who just wants to a quick Key2Name... but then why not just type that string? Hmmm. Lets move that to notes or something. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:18, 12 January 2013 (PST)

== What happens with an invalid key? ==

In my limited experiments, dataserver() never gets called at all. Which seems sort of suboptimal! In that you can't tell "key was wrong" from "it's taking a really long time to fill the request". Is that correct? Should it be documented here? (Or is it and I just overlooked it?)

It would seem more useful to call dataserver back with "" or something, but at this point that would probably be a breaking change...

[[User:Dale Innis|Dale Innis]] 10:55, 4 October 2014 (PDT)

Talk:LlRequestAgentData

2014-10-04T17:55:46Z

Dale Innis: /* What happens with an invalid key? */ new section

Is this function reporting properly? Specifically, I seem to get more "2"s than I should. My status is on file and use and it returns a 2 for me. Yet, I do see threes returned for some people. In fact, I see 0 (No info), 2 (No Info but Used(Weird)) and 3 (Info and used), but never 1 (Info filed). Were the bits repurposed and the docs not updated? --[[User:Clang Bailey|Clang Bailey]] 16:34, 29 January 2008 (PST)
:It is possible to remove the payment information from the file after it has been used. -- [[User:Strife Onizuka|Strife Onizuka]] 20:24, 29 January 2008 (PST)

== taking a byte out of the integer ==

The integer parameter, seems to actually be just the first 8 bits of the the 32bits signed integer, add or subtract 256 (or any power of 256) from any of the constants and the result should be the same, even when going to negative values. --[[User:TigroSpottystripes Katsu|TigroSpottystripes Katsu]] 13:00, 12 September 2009 (UTC)

:This doesn't surprise me. The underlying dataserver [[Message]] I'd bet uses a single byte. The number of frames supported by texture animations are similarly limited. I'll work this into the documentation later (caveat? notes?... notes definately). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:22, 12 September 2009 (UTC)

== Displaying Avatar Name information? ==

I'm not sure what the 3rd caveat intended. It just puts a clickable link in chat to open the avatar's profile. It's not useful to a script that wants to access the name. [[User:Omei Qunhua|Omei Qunhua]] 07:16, 12 January 2013 (PST)

:True, not useful for a script but might be useful for a human who just wants to a quick Key2Name... but then why not just type that string? Hmmm. Lets move that to notes or something. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:18, 12 January 2013 (PST)

== What happens with an invalid key? ==

In my limited experiments, dataserver() never gets called at all. Which seems sort of suboptimal! In that you can't tell "key was wrong" from "it's taking a really long time to fill the request". Is that correct? Should it be documented here? (Or is it and I just overlooked it?) It would seem more useful to call dataserver back with "" or something, but at this point that would probably be a breaking change... [[User:Dale Innis|Dale Innis]] 10:55, 4 October 2014 (PDT)

Talk:LlSetPrimitiveParams

2014-06-23T02:09:40Z

Dale Innis: /* Three rogue "PRIM_SPECULAR"s */ new section

== Glow support in LSL ==
In Windlight there is support for a new parameter called "Glow." Is this in LSL yet? I want! ;D -- [[User:Cron Stardust|Cron Stardust]] 16:09, 1 January 2008 (PST)

== Weird Happenings ==
For some reason this doesnt work

llSetPrimitiveParams([
PRIM_TYPE,PRIM_TYPE_BOX,00,<0.0, 1.0, 0.0>, 0.0, <0.0, 0.0, 0.0>, <1.0, 1.0, 0.0>, <0.0, 0.0, 0.0>,PRIM_MATERIAL, PRIM_MATERIAL_STONE, PRIM_SIZE, <1.0,1.0,1.0>, PRIM_PHYSICS, TRUE]);

the prim doesnt change
Is this a bug, or did I miss something ?
Anylyn Hax 01:33, 8 August 2007 (PDT)

Was it a 1x1x1 box to start with? If so you might not notice the change and if it were a smaller shape sitting on the ground, making it larger would have it penetrate whats under it, and not be able to enable physics. Try changing PRIM_TYPE_BOX to PRIM_TYPE_CYLINDER. On style concerns, you could change 00 in the third position to PRIM_HOLE_DEFAULT but thats pure style and up to your conscience. -- [[User:Strife Onizuka|Strife Onizuka]] 12:41, 8 August 2007 (PDT)

no, it was a virgin prim 0.5,0.5,0.5 a BOX, ... just make a small script and drop the code in.
its wired, if I remove the PRIM_PHYSICS, TRUE, it works.
Anylyn Hax 04:58, 9 August 2007 (PDT)

== It changes prim properties - but the prim isn't affected ==

Running a script to change a prim to flexi whilst running, and then back again at the end fails:-

llSetPrimitiveParams([PRIM_FLEXIBLE,FALSE, etc])

Turns flexible off, but leaves it as phantom.

Adding:

llSetPrimitiveParams([PRIM_PHANTOM,FALSE])

Turns phantom off according to the object edit window, but I can still happily walk through it. Toggling flexible in the edit window restores a solid object, but that isn't much use.
{{Unsigned|Roken Price}}

:Please submit a bug report on [https://jira.secondlife.com/ Jira]. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 00:39, 15 October 2008 (PDT)

== Shadow parameter ==

Since there's a lot of work being done on the shadow code buried in the viewer (and turned off by default), is it likely that the PRIM_CAST_SHADOWS value might once more become useful? [[User:TaraLi Jie|TaraLi Jie]] 02:01, 28 July 2010 (UTC)

== Slang Can Be Hard to Translate ==

What is a 'sharp function'?

I see we say [[llSetPrimitiveParams]] is a 'sharp function'.

Could we improve the text by saying just 'powerful function' rather than 'powerful & sharp function'?

-- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 17:39, 24 December 2008 (UTC)

: It's a subtle warning. "sharp" in this context builds on the metaphor of a knife. It means that the function needs to be used carefully, that if you make a mistake it will not be forgiven (you will cut yourself). The user must be careful. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 17:55, 25 December 2008 (UTC)

:: Clear now, thank you, for me a completely new usage of the word 'sharp'. -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 03:51, 1 January 2009 (UTC)

:: The first time I read this it did strike me as awkward. Perhaps 'finicky' or 'nit-picky' would be a better adjective. Unless misuse of the function could cause serious damage, I don't think it deserves "sharp". --[[User:Christopher Omega|Christopher Omega]] 02:05, 30 March 2009 (UTC)

:: It is conceivable that if the user were to make a mistake, an integer value could be interpreted as a PRIM_* instruction. While unlikely it is possible that the malformed instructions could parse without an error message, resulting in something the user didn't and no warning. I've been thinking that a footnote or tooltip would be appropriate to describe what is meant by "sharp". I would opt for 'bites-the-hand-that-feeds-it'. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:22, 30 March 2009 (UTC)

Sharp can mean and basically '''does''' mean incisive. Take for example to "Have a sharp mind" or to be "sharp witted". Both are common terms that describe an instinctive or highly defined attention to detail that results in an accurate return. The function does exactly that and it does it very well too. I think sharp is a very appropriate word. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 07:18, 17 June 2009 (UTC)

== Whitespace? ==

I noted the comment about whitespace and the params listing shape is changed and wondered if it was for more than aesthetics? The simplification for the equation is great (lol(you should really see my scripts. I gotta feeling you would cringe)). Can you give a little explanation about the whitespace please Strife? Always eager to learn (sorry bout all the edits) -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 02:10, 16 June 2009 (UTC)

:The whitespace is so that people don't have to scroll horizontally; it's a real problem when using the client's built in browser. It's better to avoid long lines when possible. I used [[PRIM_SIZE]] because of the script delay. [[llSetScale]] and [[llSetPrimitiveParams]] both cause a 0.1 script delay; by combining them, we keep it down to 0.1 seconds instead of 0.2 seconds. Now, the LSL compiler is stupid, when it sees an integer constant being used where a float is expected, instead of doing the conversion at compile time, it inlines an implicit typecast instead; which costs more bytecode and is slower to execute. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 03:40, 17 June 2009 (UTC)

Wow, cool, wow and cool. I have adopted the method you showed me for the list of params (I didn't think of the delay (I stupid) but the list can cover a lot in one hit!!). So with the maths... even if it is plain maths inside brackets if there is an integer there the compiler gets upset? eek... I need to review all my scripts now :( I get you about the whitespace now. I try to keep them short where I can but didn't think about the inworld (rubbish) browser and forget that not everybody is widescreen etc. I will be more compact in future. Hi btw and thanx again. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 03:48, 17 June 2009 (UTC)

Zai told me off (lolz kinda) for editing comments. But I am hoping this time you don't mind Strife. I strikes me as ridiculous to ask you to do it. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 05:46, 17 June 2009 (UTC)

:Editing comments is tough. Writing comments is just as tough. You have to consider your audience... and I mean really consider it... and probably justify it in the edit summary. It's something we don't do often enough (consider the audience). Commenting code is a balance between explaining what the code does, and letting the code explain what it does. I think a good way to comment code is:
:# You make the code as expressive as you can, with good variable names, functions and breaks.
:# Then you have the comments explain what the code is having trouble expressing. Don't worry if there is overlap, but you really don't want to be writing your program twice (the second time as comments).
: -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:43, 17 June 2009 (UTC)

Ooops sry Strife. I was referring to the addition of the letter "a" in "llSetPrimitiveParams" in your comment above last. Typos happen (lots of 'em in my case) and the link was thus unfortunately broken. Zai is of course right to point out that editing talk page comments is bad behavior but I thought (correct me if I am wrong) that on this sort of occasion the fixing of a spelling would be ok. As for the orange comments I am on board with your instruction 100% (eagerly waiting to see what you make of my addition to [[llSubStringIndex]]). BTW... Other than something like ((5/100)*90) to get 90% how do I get the result more efficiently? Sorry for being a pain it just crossed my mind. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 06:54, 17 June 2009 (UTC)

: F*#$, I had this great response I was just about to post and my browser went berserk on me and ate it (<.< maybe using a Nightly build wasn't such a good idea). I shall try to recreate.
: I had just found the referenced comment from Zai and came back here to find your comment. Oops.
: I should have checked the link, I wasn't awake. Thanks for fixing it.
: As to efficiency...
: Imagine your audience could understand anything you wrote no matter how complicated the vocabulary or grammar as long as it was properly constructed. You would be free to write it any way you wanted. To describe the paths of logic to the finest detail or cover them with broad brush strokes. You would be empowered.
: Now imagine that same audience having having to slave away at dictionaries, taking notes to work out the meaning of your magna opus. You would try to make it easier for them, you wouldn't use the complicated vocabulary, you would shun the complex grammer. You would turn your back on the empowerment that set you free. You would be enslaved to their ignorance and mental limitations.
: It is for this reason LSL is a dead language, it doesn't empower. If you want to do anything remotely interesting you have to dive into it's guts and learn how it works. You have to waste your time and mental faculties to dodge it's limitations. You can learn how to write faster code, less wasteful code, but it won't set you free.
: As to your addition to [[llSubStringIndex]], it's a bit too complex. If you are going to make an interactive example, you need to supply some explanatory text about how to use it. When dealing with multi-line comments, they should be above the code they reference. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:34, 17 June 2009 (UTC)

:As to editing comments, on the wiki there isn't much in the way of personal space. Sure there are user pages but even they aren't entirely off limits. Comments are really the only personal space there is. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:44, 17 June 2009 (UTC)

Wow. I feel like a soldier being given that final pep talk..."once more into the breach dear friends"... If by "guts" you mean the code under the code, eek. I still dunno all the functions (http gives me chills) but where are the guts? I am fascinated by the logic of programing. "Take 8 switches and put them into groups ..." I mean somewhere inside all this there is a system supporting a system supporting a system. I can't help but lol at the idea that my example is '''too''' complex. That's ironic. I started out trying to figure a relevant way to describe the method I developed for searching the string from the end (going backwards) but realized that (not only could I not find a way to give it a use without including loads of extra scripting) it would be so complex that it would be the very sort of script example I was afraid of when I started out. I'll add some more oranges. I do like the basic idea cause it uses [[llSubStringIndex]] in a few different ways and describes a way to get around one of the limitations.

As for writing loads of words and browser crashing. That sucks. I feel for you there. I have experienced that myself and lost hours of work (in world scripts (painful) and typed out comments here in fact (but not through crashes, through network problems)). I hope that you realize how grateful I am for your advice and comments. '''Queue violins''' I haven't felt this driven and worthy for too long. Having a cause and a goal (in world and here) have turned my life around. Having a friend here watching and guiding is awesome. Thanx Strife. -- '''[[User:EddyFragment Robonaught|Eddy]]''' ([[User talk:EddyFragment_Robonaught|talk]]|[[Special:Contributions/EddyFragment_Robonaught|contribs]]) 16:56, 17 June 2009 (UTC)

== Set just color, or just alpha, using params ==

I know there's llSetColor and llSetAlpha, but it would be nice to also be able to set just the color, or just the alpha, using the params-style functions, without having to read the one you don't want to change in order to not change it. (PRIM_COLOR needs both color and alpha; maybe a PRIM_ALPHA and a PRIM_JUST_COLOR? :) ) [[User:Dale Innis|Dale Innis]] 20:12, 5 August 2011 (PDT)

== Reference to link parameter ==

llSetPrimitiveParams has no link parameter but this article has references to LINK_ROOT and LINK_THIS 
The references should be removed but I dare not do it. I fear to ruin the other PrimitiveParams articles if I try [[User:Dora Gustafson|Dora Gustafson]] 10:09, 7 August 2013 (PDT)

:llSetPrimitiveParams has no link parameter but [[PRIM_LINK_TARGET]] does. What you have picked up on is that the emphasis and layout is wrong. The link information should be wrapped in the context of [[PRIM_LINK_TARGET]] for this article. I'll see what I can hack together but I fear this may be impossible without the PrimitiveParams documentation redesign, which is still in the planning phase. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:46, 7 August 2013 (PDT)

:P.S. Why aren't you using [[llSetLinkPrimitiveParamsFast]]? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:50, 7 August 2013 (PDT)

:P.S.S. Maybe we should merge the llSet*PrimitiveParams* articles. There really is no different between them except the delay and the link parameter. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:50, 7 August 2013 (PDT)

Your last suggestion is very sensible, the three articles should be merged. [[User:Dora Gustafson|Dora Gustafson]] 14:28, 7 August 2013 (PDT) 
I use llSetPrimitiveParams when I can
* For nostalgic reasons
* It's simplicity when I need no link
* The delay is often convenient 
[[User:Dora Gustafson|Dora Gustafson]] 14:28, 7 August 2013 (PDT)

== Caveat in connection with llSetKeyframedMotion ==

Sometimes llSetLinkPrimitiveParamsFast is too fast for for the server
<lsl>
llSetLinkPrimitiveParamsFast( LINK_THIS, [PRIM_POSITION, basePos, PRIM_ROTATION, baseRot]);
llSetKeyframedMotion( KFMlist, []);
</lsl>
In this example the prim is not in place before the key framed motion starts, so the initial conditions are bad resulting in an unwanted motion
<lsl>
llSetPrimitiveParams([PRIM_POSITION, basePos, PRIM_ROTATION, baseRot]);
llSetKeyframedMotion( KFMlist, []);
</lsl>
This code with the included delay, works smoothly. [[User:Dora Gustafson|Dora Gustafson]] 10:29, 18 August 2013 (PDT)

:I've put in the llSetLinkPrimitiveParamsFast caveat and tried to explain why it happens. It's a great opportunity to introduce people to "asynchronous" and "synchronous" terminology (because they are a pain to learn and you have to start somewhere). If I had to guess, it's probably executing them between script timeslices. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:16, 20 August 2013 (PDT)

::I've done some playing around with this lately because I was having issues with llSetLinkPrimitiveParamsFast() being asynchronous as well, and I discovered that you can make it much more reliable by emulating a forced delay, using "llSleep(0.022);" between each function call. 0.022 is one server frame, if memory serves, so this may force the function to synchronize. I've tested it with 100 loops of subsequent colour changing, fullbright & glow changing on linksets with 100+ prims, using llSetLinkPrimitiveParamsFast() and so far I haven't experienced it desynchronizing. If anyone could help me confirm this, & it indeed makes the function more reliable, it will still be much faster in execution than the llSetLinkPrimitiveParams()'s forced delay. -- [[User:Tenaar Feiri|Tenaar Feiri]] 04:21, 17 September 2013 (PDT)

== TWIST ==
I can't see where to insert this:- The figures required by the vector TWIST differ from those shown in the client view. The conversion seems to be:- script twist value = client value divided by 360. e.g. client twist of 11 requires 0.03055 in llSPP. [[User:Omei Qunhua|Omei Qunhua]] 07:43, 5 January 2014 (PST)
: It's degrees. Used to be a decimal value though, afaik. Not sure when that changed. -- [[User:Kireji Haiku|Kireji Haiku]] 07:47, 5 January 2014 (PST)
:: Eh? The client value may be degrees, the script value is the proportion of a circle. (apparently). [[User:Omei Qunhua|Omei Qunhua]] 08:16, 5 January 2014 (PST)
:It is in the tooltips in the "Flag PArameters" column, and on the pages for each constant. Maybe the flag parameters header needs a subtitle to point out that there are important tooltips in there? --[[User:ObviousAltIsObvious Resident|ObviousAltIsObvious Resident]] 08:49, 5 January 2014 (PST)
:Well client range is now apparently <code>-180° ~ +180°</code> and script should still be <code>-1.0 ~ +1.0</code> as before. -- [[User:Kireji Haiku|Kireji Haiku]] 08:56, 5 January 2014 (PST)
:: Inworld testing is good. The client and LSL range depends on the prim type. +/-180 and +/-0.5 for box, cylinder, prism, but +/-180 and +/-1 for the rest of the twistable types. --[[User:ObviousAltIsObvious Resident|ObviousAltIsObvious Resident]] 09:04, 5 January 2014 (PST)

:Well it's got me stumped. I see nothing called "tooltips" on that page. And I've looked at every occurrence of "twist" and nowhere does it tell me the range of scriptable values. There is a caveat explaining the conversion required for 'top_size' (although that's buried somewhere in the intricacies of wiki-speak) but no caveat for twist. [[User:Omei Qunhua|Omei Qunhua]] 09:18, 5 January 2014 (PST)

:: OK, inworld testing done, actual LSL range is +/-1 for all prim types, while the +/-180 or 360 is still dependent on the prim type. The tooltips are the text that appears when the mouse hovers over the keywords with dotted underlining. I think it is too obscure, but the alternative that come to mind would make that wall of text even more intimidating. --[[User:ObviousAltIsObvious Resident|ObviousAltIsObvious Resident]] 09:27, 5 January 2014 (PST)

:Thanks. I investigated because a friend was trying to script twist, and only arrived at the desired effect by trial and error. She had studied the Wiki page, but like me was totally unaware of the existence of hover text. I've never 'hovered' - only gone to obvious links. :) [[User:Omei Qunhua|Omei Qunhua]] 09:51, 5 January 2014 (PST)

::You have been missing out. Any time you see the dotted underline indicates there is some extra information that is just a hover away. I have planned to use expandable sections to make the table better (eg give explanations etc for each param) but it hasn't happened yet (it's a huge project). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:37, 5 January 2014 (PST)

== for your own sake? ==

{{Quote|Although it might not seem obvious you actually can set [[link]] {{LSLP|rules}} using this function in combination with [[PRIM_LINK_TARGET]], however '''for your own sake''' please use [[#llSetLinkPrimitiveParams|llSetLinkPrimitiveParams]] or [[#llSetLinkPrimitiveParamsFast|llSetLinkPrimitiveParamsFast]] instead.}}
:I'd like the logic explained. A footnotes at the least but a note explaining this would be handy. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:43, 9 January 2014 (PST)

== calls to linknumber 0 in a set giving odd reaction ==

I accidentally ran into a bug calling linknumber 0 in a linkset.
Call it from a script in the root properly discards the call.
Call it from a script in a child prim though, and the call gets bounced to linknumber 1.
I would a note stating that effect (might be useful someday, for someone), but I can't seem to find out how to edit the notes; The edit page doesn't go that far for me.
[[User:Will Webb|Will Webb]] 15:11, 3 February 2014 (PST)

== Three rogue "PRIM_SPECULAR"s ==

Three different tags (besides PRIM_SPECULAR) show "PRIM_SPECULAR" in the right most column of the table, instead of the correct tag: PRIM_TEXTURE, PRIM_NORMAL, and PRIM_ALPHA_MODE. I would have fixed it myself, but it seems to be buried down in one or more layers of macros, and I couldn't find it... :) [[User:Dale Innis|Dale Innis]] 19:09, 22 June 2014 (PDT)

Talk:Land collision

2013-08-12T01:05:43Z

Dale Innis: Water collision?

== Water collision? ==

I don't suppose there's any way to get this? Outside of polling constantly to see if we've gone from above water-level to below? [[User:Dale Innis|Dale Innis]] 18:05, 11 August 2013 (PDT)

Talk:LlSetRegionPos

2013-07-20T03:14:53Z

Dale Innis: /* Going (just) off-sim? */

== Woot! ==

Woot! :) [[User:Dale Innis|Dale Innis]] 10:33, 8 February 2012 (PST)

Does the "success tolerance" of 0.1m hint that the function is for some reason prone to hitting with that wide an error, or is it just a very, very, very safe margin for a floating point roundoff of the requested location?
[[User:Tali Rosca|Tali Rosca]] 10:10, 3 March 2012 (PST)

The comment about warpPos is wrong
The error is <= 1e-6 .
( except of course if you try to go under the ground )
Tested on Linden Sandbox Magnum RC :
5000 llSetregionpos with random values ;
for z values < ground , we raise z;
Result : the 5000 llsetregionpos go to a correct position
<lsl>
default
{

touch_start(integer total_number)
{

integer numberTests = 5000 ;
integer n = 1;
vector d;
float h;
vector posTouched = llGetPos();
do
{
d = <llFrand(256.0), llFrand(256.0), llFrand(4096.0)>;
h = llGround(d-llGetPos());
if ( d.z <= h )
d.z = h + 1.0;
llSetRegionPos(d);
llOwnerSay(llList2CSV([ "test #", n, "error", llGetPos()-d, "pos",llGetPos(), "dest", d ]));
n++;
} while ( ((llGetPos()-d) == ZERO_VECTOR ) && ( n <= numberTests) ) ;
llSetRegionPos(posTouched);
}
}

</lsl> [[User:Miranda Umino|Miranda Umino]] 08:02, 6 March 2013 (PST)

In fact , i guess the function doeesn t try to move an object with 0.1 meters :
it moves an object EXACTLY to the position . But it can t move an object under the ground . And the function returns a value to inform succes or failure , it exists a test "if within 0.1 meters" to know if the object was high and has been capped by the ground , or if the object was already near the ground before the call of the function
[[User:Miranda Umino|Miranda Umino]] 08:30, 6 March 2013 (PST)

== Going (just) off-sim? ==

The writeup says that the target can be up to ten meters off-sim (basically), but when I try to do that terrible things happen, at least when it's an object I am sitting on. The usual terrible things associated with a failed sim-handoff: standing in mid-air, unable to move, unable to interact with visible objects if any, minimap and location-bar having different opinions about where you are, etc.

Has anyone been using the just-off-sim abilities of llSetRegionPos successfully at all?

(Where, just to be clear, I mean just-off-sim into another adjacent sim, not into a place where no sim exists.)

[[User:Dale Innis|Dale Innis]] 20:13, 19 July 2013 (PDT)

Talk:LlSetRegionPos

2013-07-20T03:13:06Z

Dale Innis: /* Going (just) off-sim? */

== Woot! ==

Woot! :) [[User:Dale Innis|Dale Innis]] 10:33, 8 February 2012 (PST)

Does the "success tolerance" of 0.1m hint that the function is for some reason prone to hitting with that wide an error, or is it just a very, very, very safe margin for a floating point roundoff of the requested location?
[[User:Tali Rosca|Tali Rosca]] 10:10, 3 March 2012 (PST)

The comment about warpPos is wrong
The error is <= 1e-6 .
( except of course if you try to go under the ground )
Tested on Linden Sandbox Magnum RC :
5000 llSetregionpos with random values ;
for z values < ground , we raise z;
Result : the 5000 llsetregionpos go to a correct position
<lsl>
default
{

touch_start(integer total_number)
{

integer numberTests = 5000 ;
integer n = 1;
vector d;
float h;
vector posTouched = llGetPos();
do
{
d = <llFrand(256.0), llFrand(256.0), llFrand(4096.0)>;
h = llGround(d-llGetPos());
if ( d.z <= h )
d.z = h + 1.0;
llSetRegionPos(d);
llOwnerSay(llList2CSV([ "test #", n, "error", llGetPos()-d, "pos",llGetPos(), "dest", d ]));
n++;
} while ( ((llGetPos()-d) == ZERO_VECTOR ) && ( n <= numberTests) ) ;
llSetRegionPos(posTouched);
}
}

</lsl> [[User:Miranda Umino|Miranda Umino]] 08:02, 6 March 2013 (PST)

In fact , i guess the function doeesn t try to move an object with 0.1 meters :
it moves an object EXACTLY to the position . But it can t move an object under the ground . And the function returns a value to inform succes or failure , it exists a test "if within 0.1 meters" to know if the object was high and has been capped by the ground , or if the object was already near the ground before the call of the function
[[User:Miranda Umino|Miranda Umino]] 08:30, 6 March 2013 (PST)

== Going (just) off-sim? ==

The writeup says that the target can be up to ten meters off-sim (basically), but when I try to do that terrible things happen, at least when it's an object I am sitting on. The usual terrible things associated with a failed sim-handoff: standing in mid-air, unable to move, unable to interact with visible objects if any, minimap and location-bar having different opinions about where you are, etc.

Has anyone been using the just-off-sim abilities of llSetRegionPos successfully at all?

[[User:Dale Innis|Dale Innis]] 20:13, 19 July 2013 (PDT)

Talk:LlSetRegionPos

2013-07-20T03:12:51Z

Dale Innis: /* Going (just) off-sim? */ new section

User:Dale Innis/AutomaticWalking

2012-11-18T17:28:07Z

Dale Innis:

{{LSL Header}}

= Intro =

So I have my [[AvatarFollower]] script, which lets you automatically follow someone without having to keep track of them and push arrow keys and stuff.

And one of the nice side-benefits of that is that while you're following someone, you don't have to hold down any arrow keys, so you can type in chatboxes and stuff (and for that matter like sort inventory) while you're walking along. Not to mention camming about so as to get good pictures of the two of you walking.

(Getting pictures of yourself walking is a hard thing to do in SL!)

So I thought it would also be good to have something similar where instead of following someone, you could just walk forward without having to hold down an arrow key, so you could also type and cam and take pictures and stuff while still walking.

= Code =

Here's the current draft, more or less:

<lsl>
// Tap fwd to walk forward, again or tap back to stop.
// Side-arrows still turn you while walking forward
// by Dale Innis

float RANGE = 2.0; // Meters away that we put the target
float TAU = 1.0; // Make smaller for more rushed walking

integer tid = 0;
integer walking = FALSE;

stopWalking() {
walking = FALSE;
llTargetRemove(tid);
llStopMoveToTarget();
llOwnerSay("No longer autowalking.");
}

startWalking() {
walking = TRUE;
keepWalking();
}

keepWalking() {
if (llGetAgentInfo(llGetOwner()) & AGENT_FLYING) {
stopWalking();
return;
}
llTargetRemove(tid);
llStopMoveToTarget();
vector offset = <2*RANGE,0,0>*llGetRootRotation();
vector targetPos = llGetPos() + offset;
targetPos.z += llGround(offset) - llGround(ZERO_VECTOR); // helps only on ground
llMoveToTarget(targetPos,TAU);
tid = llTarget(targetPos,RANGE/2.0);
}

default {

state_entry() {
if (llGetAttached()!=0)
llRequestPermissions(llGetOwner(),PERMISSION_TAKE_CONTROLS);
}

attach(key id) {
if (id==NULL_KEY) return;
}

run_time_permissions(integer perm) {
llTakeControls(CONTROL_FWD|CONTROL_BACK|CONTROL_ROT_LEFT|CONTROL_ROT_RIGHT|CONTROL_UP,TRUE,TRUE);
}

control(key id,integer level,integer edge) {
if (llGetAgentInfo(llGetOwner()) & AGENT_FLYING) {
stopWalking();
return;
}
integer tap = edge & level;
if (tap & CONTROL_FWD) {
if (walking) {
stopWalking();
} else {
startWalking();
}
}
if (tap & CONTROL_BACK) {
if (walking) stopWalking();
}
if (level & CONTROL_ROT_LEFT) {
if (walking) keepWalking();
}
if (level & CONTROL_ROT_RIGHT) {
if (walking) keepWalking();
}
}

on_rez(integer x) {
llResetScript(); // Why not?
}

at_target(integer tnum,vector tpos,vector ourpos) {
if (walking) keepWalking();
}

}
</lsl>

= Notes =

It's basically just like the avatar follower, except that what you are "following" is a spot a few meters in front of you, and every time you get too close to it, it pops out another few meters ahead.

This actually works! It's a little wonky, in that you turn rather slowly while autowalking (i.e. when you press left or right arrow, the camera moves at once, but your AV turns rather slowly, so you have a biggish turning radius), and it doesn't get along at all well with jumping (it basically prevents jumping, more or less).

The main problem is that it can't tell where the floor is, unless you're walking on the actual SL ground. If you are, say, walking on the deck of an airship or the floor of a skybox 2000m in the sky, the script will still see the official SL ground far beneath you, and (with the current code) try to make you follow the vertical contour of that ground as you walk.

The other way to approach this would be to ignore the vertical entirely, and have you always move toward a position that's in front of you and at the same z-height. The problem there is that when facing down a steepish hill (and sometimes up a shallowish one, for reasons I don't understand), you end up in a sort of flying-falling pose for a bit. And when facing up a too-steep hill (or toward an obstacle) sometimes you just stop.

I'm not sure what if anything can be done about those oddnesses. I may try using llApplyImpulse or llSetForce instead of llMoveToTarget; that might make a difference. And I may see if any of the new Pathfinding stuff would be useful here (in those places where it's active). If I don't get too lazy. :)

User:Dale Innis/AutomaticWalking

2012-11-18T17:20:29Z

Dale Innis: Created page with "So I have my AvatarFollower script, which lets you automatically follow someone without having to keep track of them and push arrow keys and stuff. And one of the nice side-…"

So I have my [[AvatarFollower]] script, which lets you automatically follow someone without having to keep track of them and push arrow keys and stuff.

And one of the nice side-benefits of that is that while you're following someone, you don't have to hold down any arrow keys, so you can type in chatboxes and stuff (and for that matter like sort inventory) while you're walking along. Not to mention camming about so as to get good pictures of the two of you walking.

(Getting pictures of yourself walking is a hard thing to do in SL!)

So I thought it would also be good to have something similar where instead of following someone, you could just walk forward without having to hold down an arrow key, so you could also type and cam and take pictures and stuff while still walking.

Here's the current draft, more or less:

<lsl>
// Tap fwd to walk forward, again or tap back to stop.
// Side-arrows still turn you while walking forward
// by Dale Innis

float RANGE = 2.0; // Meters away that we put the target
float TAU = 1.0; // Make smaller for more rushed walking

integer tid = 0;
integer walking = FALSE;

stopWalking() {
walking = FALSE;
llTargetRemove(tid);
llStopMoveToTarget();
llOwnerSay("No longer autowalking.");
}

startWalking() {
walking = TRUE;
keepWalking();
}

keepWalking() {
if (llGetAgentInfo(llGetOwner()) & AGENT_FLYING) {
stopWalking();
return;
}
llTargetRemove(tid);
llStopMoveToTarget();
vector offset = <2*RANGE,0,0>*llGetRootRotation();
vector targetPos = llGetPos() + offset;
targetPos.z += llGround(offset) - llGround(ZERO_VECTOR); // helps only on ground
llMoveToTarget(targetPos,TAU);
tid = llTarget(targetPos,RANGE/2.0);
}

default {

state_entry() {
if (llGetAttached()!=0)
llRequestPermissions(llGetOwner(),PERMISSION_TAKE_CONTROLS);
}

attach(key id) {
if (id==NULL_KEY) return;
}

run_time_permissions(integer perm) {
llTakeControls(CONTROL_FWD|CONTROL_BACK|CONTROL_ROT_LEFT|CONTROL_ROT_RIGHT|CONTROL_UP,TRUE,TRUE);
}

control(key id,integer level,integer edge) {
if (llGetAgentInfo(llGetOwner()) & AGENT_FLYING) {
stopWalking();
return;
}
integer tap = edge & level;
if (tap & CONTROL_FWD) {
if (walking) {
stopWalking();
} else {
startWalking();
}
}
if (tap & CONTROL_BACK) {
if (walking) stopWalking();
}
if (level & CONTROL_ROT_LEFT) {
if (walking) keepWalking();
}
if (level & CONTROL_ROT_RIGHT) {
if (walking) keepWalking();
}
}

on_rez(integer x) {
llResetScript(); // Why not?
}

at_target(integer tnum,vector tpos,vector ourpos) {
if (walking) keepWalking();
}

}
</lsl>

LlGetBoundingBox

2012-07-13T22:15:38Z

Dale Innis: fix example (need to add target position)

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

==== Server 1.36 and Beyond ====
* When an avatar sits on an object, the reported bounding box for the avatar is unchanged.

==== Before Server 1.36 ====
* The reported box for objects and avatars is too small by 0.1 meter in all three dimensions, missing the physics tolerance buffer. This error is retained for backward script compatibility. Subtract <0.05, 0.05, 0.05> from min_corner and add <0.05, 0.05, 0.05> to max_corner for a corrected box.
|constants
|examples=<lsl>default//An avatar bounding box ruler thingy
{
state_entry()
{
llSetStatus(STATUS_PHANTOM, TRUE);
}

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

|helpers
|also_functions={{LSL DefineRow||[[llGetAgentSize]]|}}
|also_events
|also_tests
|also_articles
|notes
|history=
===== Sitting in 1.36 =====
Avatars historically when they sit upon an object have been treated as part of the object, like a prim, even being assigned a link number (which can be used to detect and manipulate them to some extent). Unrelated to this, requesting the bounding box for a child prim of an object would return the bounding box for the entire object (unless it was an attachment, which point it would return the bounding box for the avatar). The first is something of a misfeature, the latter is an honest to goodness feature; the combination of these two lead to something interesting: Prior to 1.36 requesting the bounding box of an attachment while seated returned the bounding box for the object sat upon. It got reported as a bug {{JIRA|SVC-1174}}, and the behavior was changed in 1.36. The bounding box for the object sat upon is unchanged by 1.36, the avatar still counts. However when the bounding box for the seated avatar is requested it does not fall through to the object being sat upon.
|cat1=Physics
|cat2
|cat3
|cat4
}}

Category talk:LSL Types

2012-04-27T15:31:01Z

Dale Innis: /* Mutability */ oops, lists aren't mutable!

== Mutability ==

The section on mutability seems wrong, or at least needs more explanation if it isn't. Vectors and Rotations clearly appear to be mutable:

<pre>
vector v = <1,3,3>;

v.x = 0;
</pre>

Obviously, the following sequence has the same result:

<pre>
vector v = <1,2,3>;
v = <0,v.y,v.z>;
</pre>

These ''might'' be operationally equivalent. But it is less than clear that they are operationally the same (at least naively, one would expect the two versions to have a different machine implementation, with the first perhaps more efficient).

Yeah, even more obviously, lists are mutable. The person must have meant "basic types" or something... [[User:Dale Innis|Dale Innis]] 20:46, 26 April 2012 (PDT)

:You bring up a good point. The section is talking about a different type of mutability. What it is trying to say is that when a function is called the parameters are copies. You can manipulate and overwrite the parameters all you want and those changes will not be conveyed to the calling scope. So in that sense all variables are immutable. LSL may have pass by reference under the hood, but it does not enable mutability. In many languages you pass a list by reference to a sort function and that function sorts the list. The value of the list has changed as a result of calling the function. LSL does not have that capacity. In LSL anything you pass to a function will be unchanged by the function. Vectors & rotations are only sort of mutable (lists are not mutable at all), you can change their components. Coaching this in terms of mutability was a bad choice. Is there a better word for this? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:33, 26 April 2012 (PDT)

::Ah, okay! That's not really what "mutable" means in programming languages. :) The best way to say this is that all function parameters in LSL are passed by value rather than by reference. (To stress the fact that LSL has no pointer types, it would also be good to say that all parameters are passed by copy.) The fact that you can say for instance "myVector.z = 7" or "myList += [1,2,3]" means that vectors and lists are are mutable; but in some sense the fact that all function parameters are passed by copy makes that fact not matter nearly as much! [[User:Dale Innis|Dale Innis]] 07:21, 27 April 2012 (PDT)

::P.S. I've now convinced myself that, in this bizarre language of ours, lists are in fact *not* mutable. You can't say l[4] = 0, instead you have to say l = llListReplaceList(l,[0],4,4) or whatever it is. So you can't change an existing list, you can just calculate a new list and stick in in the existing variable. Craziness. :) But vectors and rotations are still mutable, since you can access the .x etc elements to change an existing one. [[User:Dale Innis|Dale Innis]] 08:31, 27 April 2012 (PDT)

== LSL Wiki links needed ==

[[Template:LSL Unhelpful]] should be added to the LSL data-type pages. — [[User:Albert Zerundi|Albert Zerundi]] 02:34, 21 May 2010 (UTC)
:Good idea. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:35, 26 April 2012 (PDT)

Category talk:LSL Types

2012-04-27T14:21:35Z

Dale Innis: /* Mutability */ pass-by-value (or by copy) is the right word I think

== Mutability ==

The section on mutability seems wrong, or at least needs more explanation if it isn't. Vectors and Rotations clearly appear to be mutable:

<pre>
vector v = <1,3,3>;

v.x = 0;
</pre>

Obviously, the following sequence has the same result:

<pre>
vector v = <1,2,3>;
v = <0,v.y,v.z>;
</pre>

These ''might'' be operationally equivalent. But it is less than clear that they are operationally the same (at least naively, one would expect the two versions to have a different machine implementation, with the first perhaps more efficient).

Yeah, even more obviously, lists are mutable. The person must have meant "basic types" or something... [[User:Dale Innis|Dale Innis]] 20:46, 26 April 2012 (PDT)

:You bring up a good point. The section is talking about a different type of mutability. What it is trying to say is that when a function is called the parameters are copies. You can manipulate and overwrite the parameters all you want and those changes will not be conveyed to the calling scope. So in that sense all variables are immutable. LSL may have pass by reference under the hood, but it does not enable mutability. In many languages you pass a list by reference to a sort function and that function sorts the list. The value of the list has changed as a result of calling the function. LSL does not have that capacity. In LSL anything you pass to a function will be unchanged by the function. Vectors & rotations are only sort of mutable (lists are not mutable at all), you can change their components. Coaching this in terms of mutability was a bad choice. Is there a better word for this? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:33, 26 April 2012 (PDT)

::Ah, okay! That's not really what "mutable" means in programming languages. :) The best way to say this is that all function parameters in LSL are passed by value rather than by reference. (To stress the fact that LSL has no pointer types, it would also be good to say that all parameters are passed by copy.) The fact that you can say for instance "myVector.z = 7" or "myList += [1,2,3]" means that vectors and lists are are mutable; but in some sense the fact that all function parameters are passed by copy makes that fact not matter nearly as much! [[User:Dale Innis|Dale Innis]] 07:21, 27 April 2012 (PDT)

== LSL Wiki links needed ==

[[Template:LSL Unhelpful]] should be added to the LSL data-type pages. — [[User:Albert Zerundi|Albert Zerundi]] 02:34, 21 May 2010 (UTC)
:Good idea. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:35, 26 April 2012 (PDT)

Category talk:LSL Types

2012-04-27T03:46:02Z

Dale Innis: /* Mutability */

Talk:Transaction result

2012-04-19T05:09:11Z

Dale Innis: /* LINDENDOLLAR_BADCLOCKSKEW? */ new section

Would it have been wiser to return negative integers as error tag constants in order to save a few bytes of precious LSL? [[User:NeoBokrug Elytis|NeoBokrug Elytis]] 12:55, 5 January 2012 (PST)

== LINDENDOLLAR_BADCLOCKSKEW? ==

Apparently this can also return "LINDENDOLLAR_BADCLOCKSKEW". Information about what that means would be valuable! I suspect it just means "transaction failed due to something messing up in the internal LL network, and it might work if you try again later", but it ought to be listed... [[User:Dale Innis|Dale Innis]] 22:09, 18 April 2012 (PDT)

Talk:LlSetRegionPos

2012-02-08T18:33:52Z

Dale Innis: Woot!

== Woot! ==

Woot! :) [[User:Dale Innis|Dale Innis]] 10:33, 8 February 2012 (PST)

Talk:LlRequestPermissions

2012-01-29T01:55:26Z

Dale Innis: /* Revoking permissions? */ new section

* There seems to be a formula regarding how many requests can be made from an object in a timeframe. I believe this to be 5 requests per 20 seconds (allows for bursts I think) from a small test, I need someone to get comfirmation on the real formula from more extensive testing or off a linden. --[[User:Nexii Malthus|Nexii Malthus]] 08:27, 6 April 2008 (PDT)
**This caveat: "The viewer limits permission requests from any agent to any other agent to 5 dialogs in 10 seconds" can't be correct. Permission requests are from objects, not agents. Is the limit actually on dialogs, or on permission requests? (That is, is the limit different for automatically granted requests?) [[User:Lear Cale|Lear Cale]] 18:58, 30 January 2009 (UTC)
*** The limit is based on dialogs. The throttle is keyed to the agent who owns the objects. This prevents someone from spamming dialogs with swarms of objects. In a later viewer (1.22? 1.23? I'm not sure if it's been merged yet), the throttle is keyed to objects if dealing with one's own objects. Others' objects are throttled against their owner. This helps with resetting masses of one's own tier boxes, etc. --[[User:Soft Linden|Soft Linden]] 19:11, 30 January 2009 (UTC)

* How do permission checks/grants work for group deeded objects? Which avatar ID do you send to since you can't llGetOwner()? Who should get the drop-down? [[User:Allen Kerensky|Allen Kerensky]] 16:39, 7 January 2011 (UTC)
:Only avatars can grant permissions. Permissions with owner only restrictions, like PERMISSION_DEBIT, are not available for deeded objects. --[[User:Cerise Resident|Cerise]] 20:49, 7 January 2011 (UTC)

== Revoking permissions? ==

Does anyone know under what circumstances permissions are revoked? llResetScript() or asking for different permissions in the script will do it. Does using "Stop Animating My Avatar" in the viewer also revoke whatever permissions are in place? What about logging out? There's at least one device in the Marketplace that claims you can "control" people "permanently" by basically tricking them into granting permission once, but I vaguely recall that some mechanism was added to make the grants less permanent, to prevent just that kind of griefing... [[User:Dale Innis|Dale Innis]] 17:55, 28 January 2012 (PST)

Talk:LlSetPrimitiveParams

2011-08-06T03:12:13Z

Dale Innis: /* Set just color, or just alpha, using params */ new section

Talk:Lighting and shadows

2011-06-15T14:00:14Z

Dale Innis: LSL support for projectors!

== LSL support for projectors! ==

We need scripting support for the neat projector light sources! Neeeeeeeeeed! :) [[User:Dale Innis|Dale Innis]] 07:00, 15 June 2011 (PDT)

Talk:LlRotLookAt

2011-03-22T02:00:40Z

Dale Innis: /* Description is wrong and/or unhelpful */ new section

An LSL example that shows how to look at some (vector) position would be nice. Every time I've looked at this call, it's been because I had an object that I wanted to look at (face) some other object or avatar. Usually, I hack at it until it works or run away and start drinking instead.

[[User:Meade Paravane|Meade Paravane]] 21:06, 18 August 2009 (UTC)

== Description is wrong and/or unhelpful ==

The description of the actual function is "Cause object to point its forward axis towards target". This makes no sense, since "target" is a rotation. What would it mean for an object to point its forward axis "towards" a rotation?

I would love to see a nice clear English description of what this function actually does. :) Every time I've started out trying to use it, I've ended up using something else (llLookAt(), or llSetRot(), or something else). Is this just the equivalent of llSetRot() for physical objects? (In which case it's odd that it works for nonphysical ones as well.) Or does it do something different / more complicated? Does the "forward" (i.e. increasing-x) axis actually play any sort of part in its function? Inquiring scripters want to know!

[[User:Dale Innis|Dale Innis]] 19:00, 21 March 2011 (PDT)

Talk:LlPlaySound

2011-03-18T00:20:00Z

Dale Innis: Subsequent Calls

== Subsequent Calls ==

The old wiki said "A script can only have one sound playing using llPlaySound; subsequent calls will be ignored until the first sound has stopped playing". But as far as I can tell that is just wrong; the second part, that is. Subsequent calls aren't ignored; they cause the existing sound to be replaced by the new one (or if the new call uses the same sound, they cause the existing sound to start over again from the start). Would it be a good idea to explicitly mention that in this article? [[User:Dale Innis|Dale Innis]] 17:20, 17 March 2011 (PDT)

ContinentDetector

2011-01-15T20:26:09Z

Dale Innis: /* The Code */ put in authorship and copyleft

{{LSL Header}}

= Introduction =

The Second Life grid, especially the mainland parts, is organized into interesting and aesthetically-pleasing continents, with a variety of landforms and connectivities and geographies. The continents have their own histories, their own interesting places. But because so many people just teleport everywhere (kids these days, I tell ya), all too many people aren't aware of which continent they're on, or where they are relative to the continents, much of the time. This script is a simple example of how one might determine this, and thereby become more Geographically Aware, and therefore more fun at parties.

= Usage =

To use this script, stick it into the root prim of pretty much any object, and wear that object somewhere on your person. Whenever you teleport, or touch the object, it will tell you your global coordinates, and also what continent or other area of the grid you are on.

= Limitations and Notes =

In fact this script is mostly just a demonstration of [[llGetRegionCorner]](). The division of the world into continents and other sections is strictly unofficial and approximate, the result of using the map to zip around the grid and see roughly where things seemed to start and stop. It's relatively easy to change what's there, or to add your own areas and divisions. (Is the old Teen Grid still around somewhere? If anyone knows the coordinates, it'd be fun to add them also.)

The reason the script should be put into the root prim of an object is that only root prims get the [[CHANGED_TELEPORT]] event.

= The Code =

You may do anything you like with this code, without limitation. Well, without limitation in the sense of me suing you, that is. If you do illegal things with it, you might get in trouble, for instance. And you can't do impossible things with it.

<lsl>
// Script by Dale Innis, January 2011. You may do whatever you like with this script, without limitation.

// Each set of five list elements represents a grid-aligned rectangle, in the form xmin,xmax,ymin,ymax,name.
// The code returns the FIRST one that it finds, so its okay if the rectangles overlap, as long as you put
// the right one first.

list map = [
257024.0,265984.0,229888.0,240384.0,"Jeogeot",
252928.0,254464.0,256000.0,257280.0,"Bay City",
254720.0,265728.0,250368.0,259072.0,"Sansara",
253696.0,259584.0,259328.0,265216.0,"Heterocera",
281600.0,290304.0,257280.0,268032.0,"Satori",
283136.0,291072.0,270848.0,276736.0,"Nautilus",
281600.0,296448.0,276992.0,281600.0,"Corsica",
290048.0,290816.0,268288.0,269824.0,"Western Blake Sea",
291072.0,294400.0,266496.0,272128.0,"Blake Sea",
291840.0,294144.0,284672.0,289280.0,"Gaeta I",
296960.0,304384.0,276736.0,281344.0,"Gaeta V",
460032.0,466176.0,301824.0,307200.0,"Zindra",
// and then for places outside the bounds of mainland continents, some random names...
0.0,250000.0, 0.0,999999.0,"the Western Ocean",
250000.0,265000.0, 0.0,999999.0,"the West",
265000.0,280000.0, 0.0,999999.0,"the Center Longitudes",
280000.0,310000.0, 0.0,999999.0,"the East",
310000.0,450000.0, 0.0,999999.0,"the Gap Longitudes",
450000.0,500000.0, 0.0,999999.0,"the Zindra Longitudes",
500000.0,999999.0, 0.0,999999.0,"the Far East"
];

string get_continent_name(vector gc) {
integer count = llGetListLength(map);
integer i;
for (i=0;i<count;i+=5) {
if ((gc.x>=llList2Float( map,i )) &&
(gc.x<=llList2Float( map,i+1 )) &&
(gc.y>=llList2Float( map,i+2 )) &&
(gc.y<=llList2Float( map,i+3 )) ) return llList2String( map,i+4 );
}
return "";
}

say_location() {
vector gc = llGetRegionCorner()+llGetPos();
llOwnerSay("Coordinates: "+(string)gc.x+","+(string)gc.y);
string s = get_continent_name(gc);
if (s!="") {
llOwnerSay("You are in "+s);
} else {
llOwnerSay("You are not in any known area.");
}
}

default
{

changed(integer change) {
if (change & CHANGED_TELEPORT) say_location();
}

touch_start(integer total_number) {
say_location();
}
}
</lsl>

= See Also =

'''Functions'''

[[llGetRegionCorner]] - to find out the global coordinates of the southwest corner of this sim

[[llOwnerSay]] - to tell you about it

'''Constants'''

[[CHANGED_TELEPORT]] - to see if we've teleported

'''General'''

[[Linden Department of Public Works Roads]] - shows the major continents and their Linden roads

[[History of Second Life]] - includes some discussion of the geography

[http://lalotelling.blogspot.com/p/sl-history.html Lalo Telling's history page] - has his very nice geohistory of the early grid

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

User:Dale Innis

2011-01-15T07:16:46Z

Dale Innis: add continent detector

=== About Me ===
* Rezdate 2006-11-22.
* Am bit of a shapeshifter: [http://www.flickr.com/photos/ceoln/2118487770/ What I might look like]
* Professional programmer in RL, casual scripter in SL, even more casual builder in SL, but with some modest skill
* Active member of [http://world.secondlife.com/group/65f9ba7a-fb47-c807-f495-ad446cc0bc45 Scripters of Second Life]
* Somewhat active member of [[AW Groupies]]
* Occasional [http://virtualartpedia.a.wiki-site.com/index.php/Dale_Innis SL artist]
* Devoted dance-clubber an' shopper an' sitter-about-talking
* [http://world.secondlife.com/resident/8a123731-b0cb-47e7-90c0-6ed49aeaff58 My Web Profile]
* [http://daleinnis.wordpress.com/ My SL weblog]
* [http://www.davidchess.com/words/log.html My RL weblog]
* [http://www.research.ibm.com/people/c/chess Work]
* [https://wiki.secondlife.com/wiki/Special:Contributions/Dale_Innis My contributions to the greater good, such as they are]
* [[User:Dale_Innis/SandBox/|My SandBox]]
* Collecting some thoughts on [[User:Dale_Innis/Asset_handling_in_OGP|Asset handling in the Open Grid Protocol]]
* And similarly some thoughts on [[User:Dale_Innis/Group_IM_in_OGP|Group IM in the Open Grid Protocol]]
* Some random little LSL Library scripts: [[AvatarFollower]], [[ExplodingObjects]], [[ContinentDetector]]

I do some architecture / design / scripting / building for work, but I also do casual scripting projects for random friends and acquaintances, if they're interesting an' not a conflict of interest. Generally work is free, tips are welcome. *8) I also fiddle casually about with the content of interesting Wikis, and hang out on the Scripters of Second Life group IM channel pretty much all the time I'm on, asking and answering questions and being sociable.

{{Jira Reporter}}
{{skills
|Builder=*
|Scripter=*
|Terraformer=
|Architect=*
|Scenographer=
|SLogistician=
|}}
[[Category:LSL Teachers]]
[[Category:AW Groupies]]

ContinentDetector

2011-01-15T07:01:01Z

Dale Innis: add llgetpos back in

{{LSL Header}}

= Introduction =

The Second Life grid, especially the mainland parts, is organized into interesting and aesthetically-pleasing continents, with a variety of landforms and connectivities and geographies. The continents have their own histories, their own interesting places. But because so many people just teleport everywhere (kids these days, I tell ya), all too many people aren't aware of which continent they're on, or where they are relative to the continents, much of the time. This script is a simple example of how one might determine this, and thereby become more Geographically Aware, and therefore more fun at parties.

= Usage =

To use this script, stick it into the root prim of pretty much any object, and wear that object somewhere on your person. Whenever you teleport, or touch the object, it will tell you your global coordinates, and also what continent or other area of the grid you are on.

= Limitations and Notes =

In fact this script is mostly just a demonstration of [[llGetRegionCorner]](). The division of the world into continents and other sections is strictly unofficial and approximate, the result of using the map to zip around the grid and see roughly where things seemed to start and stop. It's relatively easy to change what's there, or to add your own areas and divisions. (Is the old Teen Grid still around somewhere? If anyone knows the coordinates, it'd be fun to add them also.)

The reason the script should be put into the root prim of an object is that only root prims get the [[CHANGED_TELEPORT]] event.

= The Code =

You may do anything you like with this code, without limitation. Well, without limitation in the sense of me suing you, that is. If you do illegal things with it, you might get in trouble, for instance. And you can't do impossible things with it.

<lsl>
// Each set of five list elements represents a grid-aligned rectangle, in the form xmin,xmax,ymin,ymax,name.
// The code returns the FIRST one that it finds, so its okay if the rectangles overlap, as long as you put
// the right one first.

list map = [
257024.0,265984.0,229888.0,240384.0,"Jeogeot",
252928.0,254464.0,256000.0,257280.0,"Bay City",
254720.0,265728.0,250368.0,259072.0,"Sansara",
253696.0,259584.0,259328.0,265216.0,"Heterocera",
281600.0,290304.0,257280.0,268032.0,"Satori",
283136.0,291072.0,270848.0,276736.0,"Nautilus",
281600.0,296448.0,276992.0,281600.0,"Corsica",
290048.0,290816.0,268288.0,269824.0,"Western Blake Sea",
291072.0,294400.0,266496.0,272128.0,"Blake Sea",
291840.0,294144.0,284672.0,289280.0,"Gaeta I",
296960.0,304384.0,276736.0,281344.0,"Gaeta V",
460032.0,466176.0,301824.0,307200.0,"Zindra",
// and then for places outside the bounds of mainland continents, some random names...
0.0,250000.0, 0.0,999999.0,"the Western Ocean",
250000.0,265000.0, 0.0,999999.0,"the West",
265000.0,280000.0, 0.0,999999.0,"the Center Longitudes",
280000.0,310000.0, 0.0,999999.0,"the East",
310000.0,450000.0, 0.0,999999.0,"the Gap Longitudes",
450000.0,500000.0, 0.0,999999.0,"the Zindra Longitudes",
500000.0,999999.0, 0.0,999999.0,"the Far East"
];

string get_continent_name(vector gc) {
integer count = llGetListLength(map);
integer i;
for (i=0;i<count;i+=5) {
if ((gc.x>=llList2Float( map,i )) &&
(gc.x<=llList2Float( map,i+1 )) &&
(gc.y>=llList2Float( map,i+2 )) &&
(gc.y<=llList2Float( map,i+3 )) ) return llList2String( map,i+4 );
}
return "";
}

say_location() {
vector gc = llGetRegionCorner()+llGetPos();
llOwnerSay("Coordinates: "+(string)gc.x+","+(string)gc.y);
string s = get_continent_name(gc);
if (s!="") {
llOwnerSay("You are in "+s);
} else {
llOwnerSay("You are not in any known area.");
}
}

default
{

changed(integer change) {
if (change & CHANGED_TELEPORT) say_location();
}

touch_start(integer total_number) {
say_location();
}
}
</lsl>

= See Also =

'''Functions'''

[[llGetRegionCorner]] - to find out the global coordinates of the southwest corner of this sim

[[llOwnerSay]] - to tell you about it

'''Constants'''

[[CHANGED_TELEPORT]] - to see if we've teleported

'''General'''

[[Linden Department of Public Works Roads]] - shows the major continents and their Linden roads

[[History of Second Life]] - includes some discussion of the geography

[http://lalotelling.blogspot.com/p/sl-history.html Lalo Telling's history page] - has his very nice geohistory of the early grid

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

ContinentDetector

2011-01-15T06:59:30Z

Dale Innis: more general stuffs

{{LSL Header}}

= Introduction =

The Second Life grid, especially the mainland parts, is organized into interesting and aesthetically-pleasing continents, with a variety of landforms and connectivities and geographies. The continents have their own histories, their own interesting places. But because so many people just teleport everywhere (kids these days, I tell ya), all too many people aren't aware of which continent they're on, or where they are relative to the continents, much of the time. This script is a simple example of how one might determine this, and thereby become more Geographically Aware, and therefore more fun at parties.

= Usage =

To use this script, stick it into the root prim of pretty much any object, and wear that object somewhere on your person. Whenever you teleport, or touch the object, it will tell you your global coordinates, and also what continent or other area of the grid you are on.

= Limitations and Notes =

In fact this script is mostly just a demonstration of [[llGetRegionCorner]](). The division of the world into continents and other sections is strictly unofficial and approximate, the result of using the map to zip around the grid and see roughly where things seemed to start and stop. It's relatively easy to change what's there, or to add your own areas and divisions. (Is the old Teen Grid still around somewhere? If anyone knows the coordinates, it'd be fun to add them also.)

The reason the script should be put into the root prim of an object is that only root prims get the [[CHANGED_TELEPORT]] event.

= The Code =

You may do anything you like with this code, without limitation. Well, without limitation in the sense of me suing you, that is. If you do illegal things with it, you might get in trouble, for instance. And you can't do impossible things with it.

<lsl>
// Each set of five list elements represents a grid-aligned rectangle, in the form xmin,xmax,ymin,ymax,name.
// The code returns the FIRST one that it finds, so its okay if the rectangles overlap, as long as you put
// the right one first.

list map = [
257024.0,265984.0,229888.0,240384.0,"Jeogeot",
252928.0,254464.0,256000.0,257280.0,"Bay City",
254720.0,265728.0,250368.0,259072.0,"Sansara",
253696.0,259584.0,259328.0,265216.0,"Heterocera",
281600.0,290304.0,257280.0,268032.0,"Satori",
283136.0,291072.0,270848.0,276736.0,"Nautilus",
281600.0,296448.0,276992.0,281600.0,"Corsica",
290048.0,290816.0,268288.0,269824.0,"Western Blake Sea",
291072.0,294400.0,266496.0,272128.0,"Blake Sea",
291840.0,294144.0,284672.0,289280.0,"Gaeta I",
296960.0,304384.0,276736.0,281344.0,"Gaeta V",
460032.0,466176.0,301824.0,307200.0,"Zindra",
// and then for places outside the bounds of mainland continents, some random names...
0.0,250000.0, 0.0,999999.0,"the Western Ocean",
250000.0,265000.0, 0.0,999999.0,"the West",
265000.0,280000.0, 0.0,999999.0,"the Center Longitudes",
280000.0,310000.0, 0.0,999999.0,"the East",
310000.0,450000.0, 0.0,999999.0,"the Gap Longitudes",
450000.0,500000.0, 0.0,999999.0,"the Zindra Longitudes",
500000.0,999999.0, 0.0,999999.0,"the Far East"
];

string get_continent_name(vector gc) {
integer count = llGetListLength(map);
integer i;
for (i=0;i<count;i+=5) {
if ((gc.x>=llList2Float( map,i )) &&
(gc.x<=llList2Float( map,i+1 )) &&
(gc.y>=llList2Float( map,i+2 )) &&
(gc.y<=llList2Float( map,i+3 )) ) return llList2String( map,i+4 );
}
return "";
}

say_location() {
vector gc = llGetRegionCorner();
llOwnerSay("Coordinates: "+(string)gc.x+","+(string)gc.y);
string s = get_continent_name(gc);
if (s!="") {
llOwnerSay("You are in "+s);
} else {
llOwnerSay("You are not in any known area.");
}
}

default
{

changed(integer change) {
if (change & CHANGED_TELEPORT) say_location();
}

touch_start(integer total_number) {
say_location();
}
}
</lsl>

= See Also =

'''Functions'''

[[llGetRegionCorner]] - to find out the global coordinates of the southwest corner of this sim

[[llOwnerSay]] - to tell you about it

'''Constants'''

[[CHANGED_TELEPORT]] - to see if we've teleported

'''General'''

[[Linden Department of Public Works Roads]] - shows the major continents and their Linden roads

[[History of Second Life]] - includes some discussion of the geography

[http://lalotelling.blogspot.com/p/sl-history.html Lalo Telling's history page] - has his very nice geohistory of the early grid

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

ContinentDetector

2011-01-15T06:53:23Z

Dale Innis: some general links

{{LSL Header}}

= Introduction =

The Second Life grid, especially the mainland parts, is organized into interesting and aesthetically-pleasing continents, with a variety of landforms and connectivities and geographies. The continents have their own histories, their own interesting places. But because so many people just teleport everywhere (kids these days, I tell ya), all too many people aren't aware of which continent they're on, or where they are relative to the continents, much of the time. This script is a simple example of how one might determine this, and thereby become more Geographically Aware, and therefore more fun at parties.

= Usage =

To use this script, stick it into the root prim of pretty much any object, and wear that object somewhere on your person. Whenever you teleport, or touch the object, it will tell you your global coordinates, and also what continent or other area of the grid you are on.

= Limitations and Notes =

In fact this script is mostly just a demonstration of [[llGetRegionCorner]](). The division of the world into continents and other sections is strictly unofficial and approximate, the result of using the map to zip around the grid and see roughly where things seemed to start and stop. It's relatively easy to change what's there, or to add your own areas and divisions. (Is the old Teen Grid still around somewhere? If anyone knows the coordinates, it'd be fun to add them also.)

The reason the script should be put into the root prim of an object is that only root prims get the [[CHANGED_TELEPORT]] event.

= The Code =

You may do anything you like with this code, without limitation. Well, without limitation in the sense of me suing you, that is. If you do illegal things with it, you might get in trouble, for instance. And you can't do impossible things with it.

<lsl>
// Each set of five list elements represents a grid-aligned rectangle, in the form xmin,xmax,ymin,ymax,name.
// The code returns the FIRST one that it finds, so its okay if the rectangles overlap, as long as you put
// the right one first.

list map = [
257024.0,265984.0,229888.0,240384.0,"Jeogeot",
252928.0,254464.0,256000.0,257280.0,"Bay City",
254720.0,265728.0,250368.0,259072.0,"Sansara",
253696.0,259584.0,259328.0,265216.0,"Heterocera",
281600.0,290304.0,257280.0,268032.0,"Satori",
283136.0,291072.0,270848.0,276736.0,"Nautilus",
281600.0,296448.0,276992.0,281600.0,"Corsica",
290048.0,290816.0,268288.0,269824.0,"Western Blake Sea",
291072.0,294400.0,266496.0,272128.0,"Blake Sea",
291840.0,294144.0,284672.0,289280.0,"Gaeta I",
296960.0,304384.0,276736.0,281344.0,"Gaeta V",
460032.0,466176.0,301824.0,307200.0,"Zindra",
// and then for places outside the bounds of mainland continents, some random names...
0.0,250000.0, 0.0,999999.0,"the Western Ocean",
250000.0,265000.0, 0.0,999999.0,"the West",
265000.0,280000.0, 0.0,999999.0,"the Center Longitudes",
280000.0,310000.0, 0.0,999999.0,"the East",
310000.0,450000.0, 0.0,999999.0,"the Gap Longitudes",
450000.0,500000.0, 0.0,999999.0,"the Zindra Longitudes",
500000.0,999999.0, 0.0,999999.0,"the Far East"
];

string get_continent_name(vector gc) {
integer count = llGetListLength(map);
integer i;
for (i=0;i<count;i+=5) {
if ((gc.x>=llList2Float( map,i )) &&
(gc.x<=llList2Float( map,i+1 )) &&
(gc.y>=llList2Float( map,i+2 )) &&
(gc.y<=llList2Float( map,i+3 )) ) return llList2String( map,i+4 );
}
return "";
}

say_location() {
vector gc = llGetRegionCorner();
llOwnerSay("Coordinates: "+(string)gc.x+","+(string)gc.y);
string s = get_continent_name(gc);
if (s!="") {
llOwnerSay("You are in "+s);
} else {
llOwnerSay("You are not in any known area.");
}
}

default
{

changed(integer change) {
if (change & CHANGED_TELEPORT) say_location();
}

touch_start(integer total_number) {
say_location();
}
}
</lsl>

= See Also =

'''Functions'''

[[llGetRegionCorner]] - to find out the global coordinates of the southwest corner of this sim

[[llOwnerSay]] - to tell you about it

'''Constants'''

[[CHANGED_TELEPORT]] - to see if we've teleported

'''General'''

[[Linden Department of Public Works Roads]] - shows the major continents and their Linden roads

[[Physical]] - a page that should talk about physics stuff in general

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

ContinentDetector

2011-01-15T06:50:18Z

Dale Innis: first draft

{{LSL Header}}

= Introduction =

The Second Life grid, especially the mainland parts, is organized into interesting and aesthetically-pleasing continents, with a variety of landforms and connectivities and geographies. The continents have their own histories, their own interesting places. But because so many people just teleport everywhere (kids these days, I tell ya), all too many people aren't aware of which continent they're on, or where they are relative to the continents, much of the time. This script is a simple example of how one might determine this, and thereby become more Geographically Aware, and therefore more fun at parties.

= Usage =

To use this script, stick it into the root prim of pretty much any object, and wear that object somewhere on your person. Whenever you teleport, or touch the object, it will tell you your global coordinates, and also what continent or other area of the grid you are on.

= Limitations and Notes =

In fact this script is mostly just a demonstration of [[llGetRegionCorner]](). The division of the world into continents and other sections is strictly unofficial and approximate, the result of using the map to zip around the grid and see roughly where things seemed to start and stop. It's relatively easy to change what's there, or to add your own areas and divisions. (Is the old Teen Grid still around somewhere? If anyone knows the coordinates, it'd be fun to add them also.)

The reason the script should be put into the root prim of an object is that only root prims get the [[CHANGED_TELEPORT]] event.

= The Code =

You may do anything you like with this code, without limitation. Well, without limitation in the sense of me suing you, that is. If you do illegal things with it, you might get in trouble, for instance. And you can't do impossible things with it.

<lsl>
// Each set of five list elements represents a grid-aligned rectangle, in the form xmin,xmax,ymin,ymax,name.
// The code returns the FIRST one that it finds, so its okay if the rectangles overlap, as long as you put
// the right one first.

list map = [
257024.0,265984.0,229888.0,240384.0,"Jeogeot",
252928.0,254464.0,256000.0,257280.0,"Bay City",
254720.0,265728.0,250368.0,259072.0,"Sansara",
253696.0,259584.0,259328.0,265216.0,"Heterocera",
281600.0,290304.0,257280.0,268032.0,"Satori",
283136.0,291072.0,270848.0,276736.0,"Nautilus",
281600.0,296448.0,276992.0,281600.0,"Corsica",
290048.0,290816.0,268288.0,269824.0,"Western Blake Sea",
291072.0,294400.0,266496.0,272128.0,"Blake Sea",
291840.0,294144.0,284672.0,289280.0,"Gaeta I",
296960.0,304384.0,276736.0,281344.0,"Gaeta V",
460032.0,466176.0,301824.0,307200.0,"Zindra",
// and then for places outside the bounds of mainland continents, some random names...
0.0,250000.0, 0.0,999999.0,"the Western Ocean",
250000.0,265000.0, 0.0,999999.0,"the West",
265000.0,280000.0, 0.0,999999.0,"the Center Longitudes",
280000.0,310000.0, 0.0,999999.0,"the East",
310000.0,450000.0, 0.0,999999.0,"the Gap Longitudes",
450000.0,500000.0, 0.0,999999.0,"the Zindra Longitudes",
500000.0,999999.0, 0.0,999999.0,"the Far East"
];

string get_continent_name(vector gc) {
integer count = llGetListLength(map);
integer i;
for (i=0;i<count;i+=5) {
if ((gc.x>=llList2Float( map,i )) &&
(gc.x<=llList2Float( map,i+1 )) &&
(gc.y>=llList2Float( map,i+2 )) &&
(gc.y<=llList2Float( map,i+3 )) ) return llList2String( map,i+4 );
}
return "";
}

say_location() {
vector gc = llGetRegionCorner();
llOwnerSay("Coordinates: "+(string)gc.x+","+(string)gc.y);
string s = get_continent_name(gc);
if (s!="") {
llOwnerSay("You are in "+s);
} else {
llOwnerSay("You are not in any known area.");
}
}

default
{

changed(integer change) {
if (change & CHANGED_TELEPORT) say_location();
}

touch_start(integer total_number) {
say_location();
}
}
</lsl>

= See Also =

'''Functions'''

[[llGetRegionCorner]] - to find out the global coordinates of the southwest corner of this sim

[[llOwnerSay]] - to tell you about it

'''Constants'''

[[CHANGED_TELEPORT]] - to see if we've teleported

'''General'''

[[Havok4]] - the code that actually implements the physics that makes things blow up

[[Physical]] - a page that should talk about physics stuff in general

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

Talk:Channel and Version Requirements

2010-09-03T22:53:36Z

Dale Innis: /* Is this the thing that the --channel switch on most viewers changes for testing purposes? Or is that some other "channel"? */ new section

{{Talk}}

== Adding a fifth number to versions ==

I think this all makes sense except for this part:

Choose a version number
* The version number is in the form Major.Minor.Patch.Build
* The version number can be any four numbers
* We recommend using the Major, Minor, and Patch numbers from the most recently merged Linden Lab source code.
* We recommend using a Build number >= 100 to indicate a non Linden Lab version.

I think that the versions should be 5 numbers, since there have been occasions where multiple versions of Major.Minor.Patch have been released by Linden Lab. For example (from [[Source_downloads]]):

* ver 1.18.2.1
* ver 1.18.2.0

* ver 1.14.0.1
* ver 1.14.0.0

So, my proposal would be that the number be in the form Major.Minor.Patch.Build.3rdPartyNumber. [[User:Gibson Willis|Gibson Willis]] 12:12, 28 September 2007 (PDT)

''Steve Linden:'' That would be fine. The version is just a string so any convention would work and if you would like to be that specific we have no problem with that. Builds only represent bug fixes which is why we only think it is important to include the first three numbers since a build will not represent new features / functionality, but more information is not a bad thing.

== Add Snowglobe ==
We need to add references to Snowglobe throughout to be complete. Channel strings used for Snowglobe:
* Snowglobe Release : used for binaries built off release branches
* Snowglobe Test Build : used for binaries built of the live development trunk
* CommnityDeveloper : used for binaries you built on your own machine and use for testing.

Note: we ''should'' change that generic unclear '''CommunityDeveloper''' channel and use something like '''Snowglobe Community Developer'''

[[User:Merov Linden|Merov Linden]] 20:51, 12 February 2010 (UTC) Merov Linden

== Instructions for from-scratch viewers? ==

Should(n't) this page also contain (or link to, if it exists elsewhere) instructions for how to correctly transmit the viewer channel/version string in viewers that aren't based on the LL OS code? Telling those ppl to edit particular files in the OS tree doesn't help them much... :) [[User:Dale Innis|Dale Innis]] 16:38, 29 April 2010 (UTC)

== Other article about the topic ==

I just saw that there's already a page named [[Channel]]. Although it doesn't have a lot of content, yet, this page here should probably link to it.
--[[User:Boroondas Gupte|Boroondas Gupte]] 10:22, 8 August 2010 (UTC)

== Is this the thing that the --channel switch on most viewers changes for testing purposes? Or is that some other "channel"? ==

Is this the thing that the --channel switch on most viewers changes for testing purposes? Or is that some other "channel"? :) [[User:Dale Innis|Dale Innis]] 22:53, 3 September 2010 (UTC)

Talk:LlSetCameraEyeOffset

2010-08-30T04:14:37Z

Dale Innis: /* What are the vectors relative to, in child prims? */

== What are the vectors relative to, in child prims? ==

Are the vectors in this and llSetCameraAtOffset relative to the object (the root prim), or the prim that the script is in? Experiments suggest the latter (that it's relative to the prim), but I'm not entirely sure... [[User:Dale Innis|Dale Innis]] 02:45, 30 August 2010 (UTC)

Update: the situation seems to be very confusing! Both of these functions set the relevant feature in the co-ordinate system of, and relative to, the prim that they are called from (I think). But on the other hand the setting applies to every prim in the object! So if I do llSetCameraEyeOffset(v) in prim A, and someone sits on a different prim B, their camera eye goes to v relative to A (not to B). So it's like v is computed relative to A, and then the resulting absolute position applies for anyone who sits on any prim. Or something... [[User:Dale Innis|Dale Innis]] 04:14, 30 August 2010 (UTC)

Talk:LlSetCameraEyeOffset

2010-08-30T02:45:15Z

Dale Innis: What are the vectors relative to, in child prims?

Category:LSL Library

2010-08-25T22:24:31Z

Dale Innis: add Update distributor

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

<div id="box">
<div style="padding: 0.5em 0.5em 1.5em">
Come to this page to see complex examples that show how to combine parts of LSL.

Go to the [[:Category:LSL Examples|LSL Examples]] page to see brief examples of how to use parts of LSL

Why collect complex examples here? Well, ...

There are many [[script|scripts]] that have become buried in the [http://forums-archive.secondlife.com/15/1.html Scripting Library archive] or the newer [https://blogs.secondlife.com/community/forums/scripting_library?view=discussions Scripting Library forum], were lost with the death of the early scripting forums, or sit idle in [[inventory|inventories]] that could be useful and should be more accessible.

Other scripters may be in the same situation. This wiki is a well-suited medium for a script library. Feel free to add your scripts to the script library by creating new pages for them and linking to those pages here.

Note that there are many more scripts in the LSL Library here, but you can't get to them if you don't know they exist, because they are subpages now, instead of an automatically updated category. Good luck searching.
</div>
</div>

<div id="box">

== Rules for posting: ==
<div style="padding: 0.5em">
#Your script must be tested and working. If it's not, stick it in your user-space until it is. This is a list of working, usable scripts.
#Add a link to your script's page here. Link back to this page from your script's page. Start your page with <nowiki>{{LSL Header}}</nowiki>.
#Do not add scripts that duplicate the same functionality as an existing script or built in {{LSLGC|Functions|function}}. If yours does, explain why.
#Do not list simple scripts here. Include those among the [[:Category:LSL Examples|LSL Examples]] instead.
</div></div>

<div id="box">
==LSL Script Library==

{| class="sortable" {{Prettytable}}
|- {{Hl2}}
! '''Name'''
! '''Creator'''
! '''Description'''
|-
||[[1st necessity of SL]]
||[[User:Beer Dailey|Beer Dailey]]
||Monitors for avatars and (de)activates scripts states to control script performance/lag.
|-
||[[3D Radar]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Rezzes a ball for each avatar in range. Each ball tracks its own AV and displays distance.
|-
||[[Access (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||An easy to use script for permissions on who can use the script, Public/Group/Owner
|-
||[[Aim Detection]]
||[[User:Han Shuffle|Han Shuffle]]
||Monitors for avatars and reports back to owner about who is aiming at them.
|-
||[[AntiDelay Node]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Uses [[llMessageLinked]] to stop those pesky delays.
|-
||[[AO Overriding Pose Ball]]
||[[User:Jesse Barnett|Jesse Barnett]]
||No more turning your AO off and on when you sit down
|-
||[[ARCFOUR Strong Encryption Implementation]]
||[[User:Nekow42 Zarf|Nekow42 Zarf]]
||An LSL implementation of ARCFOUR, the most popular stream cipher still in use. It is licensed under a Creative Commons Attribution 3.0 license.
|-
||[[Assembly Programming Language|Assembly-Like Programming Language]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A compiler that runs assembly-like programs.
|-
||[[Associative Array Emulator|Associative Array (Dictionary) Emulator]]
||[[User:Alynna Vixen|Alynna Vixen]]
||This library provides a set of functions for using a list as an associative array where string based keys can refer to one or more variant elements.
|-
||[[AvatarFollower]]
||[[User:Dale Innis|Dale Innis]]
||Allows one avatar to automatically follow another.
|-
||[[Avatar Radar (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||Version 1.2; A nice new avatar radar script i just finish that you can place in your hud, Also features avatar locator
|-
||[[Base2Dec]]
||[[User:Siann Beck|Siann Beck]]
||Convert a number to decimal from any base.
|-
||[[BaseN]]
||[[User:Nexii Malthus|Nexii Malthus]]
||Variable base compression, dynamically maps to usable UTF code points.
|-
||[[Basic A-Star Pathfinder]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| My own interpretation of A Star into a highly efficient algorithmn
|-
||[[Basic Encryption Modules]]
||[[User:Beverly Larkin|Beverly Larkin]]
||Basic encryption scripts, allows you to encrypt a float and shout it to another prim on a randomly chosen channel.
|-
||[[Be happy]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Basic smile attachment script, makes your avatar smile.
|-
||[[Best Neighbor Ad Hiding Script|Best Neighbor]]
||[[User:Doran Zemlja|Doran Zemlja]]
||Reduce ad clutter by hiding ads when users are on their own land nearby.
|-
||[[BigNum|BigNum Library (RSA Encryption)]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A BigNum Library for dealing with big numbers! Specialized for modular multiplication, and RSA encryption.
|-
||[[Binary Clock v1.1|Binary Clock]]
||[[User:Fox Diller|Fox Diller]]
||A Binary Clock.
|-
||[[BinaryDecimalConverter]]
||[[User:Soundless Smalls|Soundless Smalls]]
||Converts a binary value to a decimal value and vice versa.
|-
||[[Blacklist and Remote Kill|Blacklist and Remote Kill]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Blacklist(denial of use) or a creator kill script(can delete someone's item by command on private channel)
|-
||[[User_talk:Rolig_Loon/Bookmark_URLs|Bookmark URLs]]
||[[User:Rolig Loon|Rolig Loon]]
||Dialog driven HUD reads bookmarked URLs from notecards and navigates directly to them with user's in-world browser.
|-
||[[Builders Buddy|Builder's Buddy Tool]]
||[[User:Newfie Pendragon|Newfie Pendragon]]
||Script to easily move/rotate large builds that exceed the linkable size limit (30 meters).
|-
||[[Button Click Detector]]
||{{User|Sendao Goodman}}
||Use [[llDetectedTouchUV]] to determine which button was pressed on a texture.
|-
||[[Camera following prim]]
||[[User:Dale Innis|Dale Innis]]
||Pair of scripts to make a prim follow your camera position around (for lights etc).
|-
||[[Camera Sync]]
||[[User:Meyermagic Salome|Meyermagic Salome]] and [[User:Nomad Padar|Nomad Padar]]
||A system to synchronize the cameras of two avatars.
|-
||[[Chatbot]]
||Anonymous
||Compile and run the LSL you type on a channel, faster than you can thru the 2007-08 SL GUI.
|-
||[[Chat Logger (GPL)]]
||[[User:Nobody Fugazi|Nobody Fugazi]]
||Chat logger which requests permission from participants before recording them.
|-
||[[Chat_Relay|Chat Relay]]
||[[User:grumble Loudon|grumble Loudon]]
||A Chat relay which can be routed using a path header and won't echo.
|-
||[[ClickAndDrag]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Click and Drag user interface elements using dynamic feedback
|-
||[[Code Racer]]
||Anonymous
||Race two versions of code forever, to see which runs faster.
|-
||[[Code Sizer]]
||Anonymous
||Count the bytes compiled from source code, to measure how to write small code.
|-
||[[User:Void_Singer/Programs#v7-D_Enh._Color_Picker|Color Changer]]
||[[User:Void_Singer|Void_Singer]]
||Dialog driven color changer. Supports 16million+ colors, web color codes, multiple targeted prims, with save and recall.
|-
||[[Color Changer|Color Changer Plus]]
||[[User:Neo Calcutt|Neo Calcutt]]
||A color changer with 14 colors, a random function, and a custom vector function.
|-
||[[Color conversion scripts|Color Conversion]]
||[[User:Sally LaSalle|Sally LaSalle]]
||Convert between Red Green Blue (RGB) and Hue Saturation Value (HSV).
|-
||[[ColorConvert]]
||[[User:Siann Beck|Siann Beck]]
||Convert color values to vector from RGB, hex or HTML color name.
|-
||[[Color script]]
||[[User:Masakazu Kojima|Masakazu Kojima]]
||Script for changing colors trough a listener with pre-defined colors.
|-
||[[Library Combined Library|Combined Library]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Library of mostly encoding and decoding functions, some more useful then others.
* String functions: Replace / Trim right / Trim left / Trim both
* Unicode conversion: UTF8 to Unicode / Unicode to UTF8
* List functions: Replace / Compare
|-
||[[Computer:jaycoonlanguage]]
||[[User:jayco121 Bing|jayco121 Bing]]
|| A language written in LSL that is meant for my computer (available at the shop).
|-
||[[Read Note Card Configuration|Configuration Notecard Reader]]
||{{User|Dedric Mauriac}}
||A script to read configuration information from a notecard. Parses notecard to extract key words and their assigned values. Allows for comment lines and many more useful features.
|-
||[[AdvancedNotecardReader|Configuration Notecard Reader (advanced)]]
||[[Lear Cale|Lear Cale]]
||Robust configuration notecard reader; supports multiple notecards with same suffix, handles reconfig on inventory change, and does not usurp the default state.
|-
||[[Library_Chat_Relay|Conversation Relay]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||Chat relay which requests permission from participants before relaying their messages. Also includes their attachments. (ToS compliant).
|-
||[[Curtain script]]
||[[User:Zilla Larsson|Zilla Larsson]]
||A simple script to retract/stretch curtains, blinds, bedcovers and more
|-
||[[Dataserver API]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dataserver Framework for Notecards.
|-
||[[Date Library]]
||[[User:Corto Maltese|Corto Maltese]]
|| Date library, based on number of day since march 3rd 1600, can be used to calculate weekday, date differences, and date offset, and date formating.
|-
||[[Day of the Week]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Function to get day of the week from [[llGetUnixTime]].
|-
||[[Days in Month]]
||[[User:IntLibber Brautigan begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting|IntLibber Brautigan]]
||Clicking on it returns the number of days in the present month. Useful for scripting calendars and tier systems that need to know the number of days in the month at hand or to calculate for any month. Even adjusts for leap years.
|-
||[[Deed Tools]]
||[[User:Falados Kapuskas|Falados Kapuskas]]
||Tools that allow the creator to modify Group-Owned (Deeded) Objects via chat.
|-
||[[Describe Chatter]]
||Anonymous
||Chat to see yourself as others do.
|-
||[[Dialog Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| A (not-so) simple dialog & menu control script. Call dialog and receive selected value via [[link_message]](), with built-in timer and [[link_message]]() notification on time out. Supports multi-pages dialog and numeric property dialog. Button text and dialog's returned value can differ.
Latest version also has [[Dialog Menus Control]] built-in; which allow multi-level menus through SL dialog system.
|-
||[[Dialog NumberPad|Dialog Number Pad]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Use a dialog to accept positive integer input from users.
|-
||[[Displayer Script]]
||[[User:Akinori Kimagawa|Akinori Kimagawa]]
||[[Display Words On Top Of An Object]]
|-
||[[Drink script]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Used mainly for food and drink in Second Life.
|-
||[[TOXDropBox|DropBox]]
||[[User:Dimentox Travanti|Dimentox Travanti]]
|| This is a Drop box which allows people to drop certain items in a object & has many config options.
|-
||[[Efficiency Tester]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Tests the speed of a function.
|-
||[[Email-to-IM|Email2IM]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Send IMs to SL friends via [[email]] (translate emails from friends into IMs).
|-
|-
||[[User:Kireji_Haiku/SIMchat_headset|Encrypted Region-wide chat]]
||'''[[User:Kireji Haiku|Kireji Haiku]]''' ([[User talk:Kireji Haiku|talk]]|[[Special:Contributions/Kireji Haiku|contribs]])
||Encrypted Region-wide chat
|-
||[[ExplodingObjects]]
||[[User:Dale Innis|Dale Innis]]
||Causes an object (of the appropriate type) to explode on command.
|-
||[[FadeEasy]]
||[[User:Nika Rugani|Nika Rugani]]
||The easy way of fading objects in or out (Using llSetLinkAlpha)
|-
||[[FastConeSpread]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Fast Algorithmn to achieve cone spread, main use in weaponry systems.
|-
||[[User:PixelProphet Lane/Scripts#Fast List Prim Contents|Fast List Prim Contents]]
||[[User:PixelProphet Lane|PixelProphet Lane]]
||Fast and efficient method to print Object Inventory (Name, Type and next Owner permissions)
|-
||[[Find Avatar Key|Find Avatar Key]]
||[[User:Huney Jewell|Huney Jewell]]
||Explores [[UUID]] of avatar whose name is said in local chat or who touches the prim.
|-
||[[First Name Letter Prize]]
||[[User:RaithSphere Whybrow|RaithSphere Whybrow]]
||Gives a prize if the person who sits on it's first letter of first name matches the random letter!
|-
||[[Fix Small Prims|Fix_Small_Prims]]
||[[User:Emma Nowhere|Emma Nowhere]]
||Finds and adjusts the smallest prims in a linkset so that it can be scaled down further.
|-
||[[Float2Hex]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Very useful for transporting [[float|floats]].
|-
||[[Float Box Contents]]
||[[User:Rolig Loon|Rolig Loon]]
||Displays object inventory in hover text, identified by type and updated marquee-style.
|-
||[[Follower (script)|Follower]]
||Unknown, uploaded by [[User:Slik Swindlehurst|Slik Swindlehurst]]
||Makes an object follow the nearest person. Do not use for [[grief|griefing]].
|-
||[[GA Event Notifier]]
||[[User:Victor Hua|Victor Hua]]
||Gathers seven days event data from a Google calendar and display it through a simple interface. The lsl script can access several calendars at once through seperate php files. One file per calendar. Host the included php on your own web server.
|-
||[[Geometric|Geometric Library]]
||Community Project
||A substantial amount of various geometric functions for intersection and other purposes of 3D maths.
|-
||[[Get Profile Picture]]
||[[User:Valentine Foxdale|Valentine Foxdale]]
||Sets the texture of the object to profile picture of the person that touches ot
|-
||[[GetTimestampOffset]]
||[[User:Siann_Beck|Siann Beck]]
||Returns [[llGetTimestamp]]() with an hour offset.
|-
||[[Give InvItem every n hours]]
||[[User:Criz Collins|Criz Collins]]
||Will give an inventory item on touch only every n hours, even if somebody touches the object more than once.
|-
||[[Give random object]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to receive a random object in the prim's inventory
|-
||[[Google Charts]]
||[[User:Dedric Mauriac|Dedric Mauriac]]
||Create links to display raw data as a chart image.
|-
||[[Google_Translator]]
||[[User:Ugleh Ulrik|Ugleh Ulrik]]
||Translates spanish to english, and its simple to make it any other way.
|-
||[[Go transparent when walking]]
||[[User:Emmas Seetan|Emmas Seetan]]
||An attachment that goes invisible when you walk and visible when you don't walk.
|-
||[[Group Authorization]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Checks to see if object is set to appropriate group (checks by [[Group key finder|group key]])
|-
||[[Group Information v1.0]]
||[[User:Tyrennic Rivera|Tyrennic Rivera]]
||When clicked the prim will show group information (set on the prim) from the official Second Life Search page.
|-
||[[Group key finder]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to find the key of the group
|-
||[[Group Privacy]]
||[[User:Chance Unknown|Chance Unknown]]
||Security device to insure members of a group can have a private area. Deactivates when nobody present.
|-
||[[Hello Avatar]]
||Linden Lab
||SL's default script.
|-
||[[Hello Avatar Companion]]
||[[Chase Quinnell]]
||Companion to the original [[Hello Avatar]] script
|-
||[[Hierarchics]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Advanced script to create an efficient self-aware hierarchic structure.
|-
||[[User:Rolig_Loon/High-Capacity_Greeter-Counter|High-Capacity Greeter-Counter]]
||[[User:Rolig Loon|Rolig Loon]]
||Uses a memory compression algorithm to store hashed visitor UUID's in a string instead of using a list.
|-
||[[Holodeck]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Home Rezzing System (Open Source).
|-
||[[Interpolation|Interpolation Library]]
||[[User:Nexii_Malthus|Nexii Malthus]]
||A small set of interpolation functions.
|-
||[[Intra-Region Update Server]]
||[[User:Emma_Nowhere|Emma Nowhere]]
||Centrally update objects such as Freeview screens or teleport pads within a region that are configured by notecards or contain modifiable objects or media assets.
|-
||[[Inventory_Based_Menu]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Inventory Based Menu System.
|-
||[[iTunes RPC Email|iTunes RPC]]
||[[User:Fox Diller|Fox Diller]]
||iTunes RPC via LSL [[llEmail]] and [[llRemoteDataReply]].
|-
||[[Kilt Editor|Kilt / Skirt Editor]]
||[[User:Brangus Weir|Brangus Weir]]
|| This changes all the parameters of all the flexis in the link set in one swell foop!
|-
||[[Key Pad Door|Keypad Door]]
||[[User:Tdub Dowler|Tdub Dowler]]
|| Door and keypad with changeable code. Follow instructions carefully!
|-
||[[Last Sound System]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL [http://Last.fm Last.fm] client.
|-
||[[LibraryDisplayLandScreenshot]]
||[[User:Jon Desmoulins|Jon Desmoulins]]
||A modified version of LibraryDisplayProfilePic using the new [[PARCEL_DETAILS_ID]] Implemented in Server v1.36
|-
||[[User:Daemonika_Nightfire/Scripts/LinkNumber-List_in_llSetLinkPrimitiveParamsFast|LinkNumber-List_in_llSetLinkPrimitiveParamsFast]]
||[[User:Daemonika Nightfire|Daemonika Nightfire]]
||Changed several prims in linkset with the same parameters, with a list. Without separate llSetLinkPrimitiveParams for each prim. (ideal for show/hide effects)
|-
||[[Linkset resizer]]
||[[User:Maestro Linden|Maestro Linden]]
||Systematically rescales a linkset by moving and resizing each prim (by using [[llGetLinkPrimitiveParams]] and [[llSetLinkPrimitiveParamsFast]])
|-
||[[Linkset resizer with menu]]
||[[User:Brilliant Scientist|Brilliant Scientist]]
||A menu-driven script that rescales a linkset by moving and resizing the prims using [[llGetLinkPrimitiveParams]] and [[llSetLinkPrimitiveParamsFast]] functions. Based on [[Linkset resizer]].
|-
||[[Linkset Resizer 2]]
||[[User:Emma Nowhere|Emma Nowhere]]
||A more user-friendly resizer script designed for either drop-in use by the end-user or builder or for use in products. Based on [[Fix Small Prims]].
|-
||[[List2CSV]]
||[[User:Kunnis Basiat|Kunnis Basiat]]
||List2CSV & CSV2List that include preserving type and escaping characters.
|-
||[[list_cast]]
||[[User:Fractured Crystal|Fractured Crystal]]
||Casts a list of strings into the type they appear to be. Designed for preprocessing user input for feeding into [[llSetPrimitiveParams]]
|-
||[[Listener Script]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Use to [[listen]] to other people's conversations (Like spying)
|-
||[[User:Void_Singer/Functions#List:_Find_Last_Index|List: Find Last Index]]
||[[User:Void Singer|Void Singer]]
||Returns the last index of searched item in a source list. (backwards version of [[llListFindList]])
|-
||[[User:Void_Singer/Functions#List:_Multi-Find_Index_.28First_or_Last.29|List: Multi Find]]
||[[User:Void Singer|Void Singer]]
||Returns the first found index of multiple search items in a list. (Multi-item version of [[llListFindList]]. Fwd and Rev versions included)
|-
||[[User:Void_Singer/Functions#List:_Get_Reverse_Order|List: Reverse]]
||[[User:Void Singer|Void Singer]]
||Returns an input List in reverse order
|-
||[[Load URL]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to get a dialog to visit the URL inside the script.
|-
||[[User:Kephra_Nurmi/lsDancemachine|lsDancemachine]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Low lag client server dancemachine.
|-
||[[User:Kephra_Nurmi/lsDeejay|lsDeejay Home Edition]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Client server media control for music, video, youtube, pictures, and texture animations.
|-
||[[User:Kephra_Nurmi/lsDialog|lsDialog]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Universal notecard driven menu dialog system.
|-
||[[User:Kephra_Nurmi/lsDisplay|lsDisplay]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Picture cycler with preloader.
|-
||[[User:Kephra_Nurmi/lsDistributor|lsDistributor]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Simple 'try' and 'buy' vendor system.
|-
||[[LSL_languageAPI]]
||[[User:Gypsy paz|Gypsy Paz]]
||Multi-lingual API from notecard based language files
|-
||[[Mandelbrot Explorer]]
||[[User:Babbage Linden|Babbage Linden]]
||An interactive fractal explorer.
|-
||[[Merge Sort]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Implements a Merge Sort in LSL, however this code is 300(ish) times slower than [[llListSort]]. Don't use this in a script!
|-
||[[Minesweeper]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A simple minesweeper game.
|-
||[[Morse Code]]
||{{User|Bobbyb30 Swashbuckler}}
||A script that allows for the conversion to and from morse code and can "play" morse code.
|-
||[[Multi Item Rezzer|Multi Item Rezzer]]
||[[User:Jesse Barnett|Jesse Barnett]]
||A rework of my old High Altitude Rezzer. Place the objects that you wish to choose from to be rezzed inside. Sit on the rezzer and pick the item and the height. It will go to target height and rez the object.
|-
||[[Multirezzer|Multirezzer (on collision)]]
||[[User:Beet Streeter|Beet Streeter]]
||Spawns up to 10 objects when the object containing the script collides with a user.
|-
||[[Name2Key in LSL]]
||[[User:Maeva Anatine|Maeva Anatine]]
||Get the Name2Key feature inside your scripts. Works even on lastly subscribed avatars.
|-
||[[No Auto-Return]]
||[[User:Bellla Clarity|Bella Clarity]]
||To stop your long and hard builds from getting returned in sandboxes (''only single prims, though!'').
|-
||[[No Auto-Return NR]]
||[[User:Jor3l Boa|Jor3l Boa]]
||This really works (29-05-09), needs a nearby region to do the trick and avoid auto return. (Tested on Blue and Rausch)
|-
||[[No Auto-Return (Multi)]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A revision of Bella's that works for multi-prim objects.
|-
||[[No Limit Teleporter]]
||[[User:Morgam Biedermann|Morgam Biedermann]]
||Teleport to infinite altitudes (up to 4096m)
|-
||[[Object Size]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Gets the dimensions and footprint of a linkset
|-
||[[Object to Data v1.3|Object to Data]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Turns an object into text (and back). Allows people to transfer objects through notecards (or otherwise).
|-
||[[Online Indicator|Online Indicator]]
||[[User:Kristy Fanshaw|Kristy Fanshaw]]
||Will show if the user is online or not. Displays users profile picture and allows to send IM's to user. Also gives a link to open the users profile
|-
||[[Open Group Join]]
||[[User:Alicia Stella|Alicia Stella]]
||User Touches Object to Join Group from Group Info window, (no bot.)
|-
||[[Open Zyngo Skin Installer]]
||[[User:Tmzasz Luminos|Tmzasz Luminos]]
||A Simple Script designed to install skins on the popular Skill machines.
|-
||[[One Script, many doors]]
||[[User:Kyrah Abattoir|Kyrah Abattoir]]
||Door script able to manage more than 50 linked doors from a single script instance.
|-
||[[ParseString2List]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Same as [[llParseString2List]] and [[llParseStringKeepNulls]], but not limited to 8 spacers or separators. Thus substitute a call to the [[llParseString2List]] and [[llParseStringKeepNulls]] functions by a call to [[Parse_String_To_List|ParseString2List]] whenever you have more than 8 separators or more than 8 spacers.
|-
||[[Password Generator]]
||[[User:Syntrax Canucci|Syntrax Canucci]]
||This is an over-complicated, semi-complex password generator, which goes through multiple steps.
|-
||[[Pathfinder]]
||[[User:Babbage Linden|Babbage Linden]]
||A potential field based pathfinding library.
|-
||[[Phantom Child]]
||[[User:Aeron Kohime|Aeron Kohime]]
||Causes a child in a link set to become phantom without the entire object becoming phantom.
|-
||[[PhysicsLib]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Interesting set of fun physics functions.
|-
||[[Play and Loop Sound]]
||[[User:Bellla Clarity|Bella Clarity]]
||Very short and simple script; plays and loops a sound in an object.
|-
||[[Posing stand|Posing Stand]]
||[[User:Bellla Clarity|Bella Clarity]]
||Just a pose script to edit [[attachments]] more easily.
|-
||[[PosJump]]
||[[User:Uchi Desmoulins|Uchi Desmoulins]]
||A much more efficient alternative to the popular [[warpPos]] function for bypassing 10m distance-moved limitations.
|-
||[[Prefix Calculator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
|| A calculator that evaluates expressions in prefix notation.
<code>+ 3 4 = 5. * + 1 2 + 3 4 = 14.</code>
|-
||[[Progress Bar]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Flexible and powerful little function for creating progress bars useful in hovertext.
|-
||[[Pseudo-random Number Generator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Generates a Pseudo-random number between -0x7FFFFFFF and 0x7FFFFFFF
|-
||[[User:Rolig_Loon/Quiz_From_Notecard|Quiz From Notecard]]
||[[User:Rolig Loon|Rolig Loon]]
||A multiple-choice testing script that reads questions and answer choices from a notecard and presents them in dialog boxes.
|-
||[[Rainbow_palette]]
||[[User:Rui Clary|Rui Clary]]
||Build a color picker, using only one prim, and a few lines of code.
|-
||[[Random AV Profile Projector]]
||[[User:Debbie Trilling|Debbie Trilling]]
||Randomly selects an AV from a crowd & then projects their profile picture as a 'holographic' image
|-
||[[Random Object Vendor]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Simple vendor that gives out random objects when paid the right amount
|-
||[[Random Password Generator]]
||[[User:Jor3l Boa|Jor3l Boa]]
||Generate Random passwords based on String Length.
|-
||[[RavText]]
||[[User:Ravenous Dingo|Ravenous Dingo]]
||An alternate to XyText. This is a lightweight, multiple font 10 character text display system. It only supports uppercase alphanumeric text and a few special characters, but it is very fast, renders quickly and supports multiple fonts. It is meant for specialized use when all that is desired is basic, fast text display and the extra "bells and whistles" are not needed.
|-
||[[User:PixelProphet Lane/Scripts#Real Object Inventory To Dialog|Real Object Inventory To Dialog]]
||[[User:PixelProphet Lane|PixelProphet Lane]]
||Display any amount of items contained in an Object in a Dialog, regardless of item name length.
|-
||[[RentalBoxv1|Rental Box, Simply]]
||[[User:Sendao Goodman|Sendao Goodman]]
||Simple explanation of how to make rental boxes.
|-
||[[Rental Cube]]
||[[User:Hank Ramos|Hank Ramos]]
||Simple cube for renting out a space.
|-
||[[Remote Texture Loader]]
||{{User|Bobbyb30 Swashbuckler}}
||A set of scripts for remotely loading textures within a sim. This means that a single "texture server" can manage multiple changing billboards within a sim.
|-
||[[Say Region Frames Per Second|Region Frames Per Second]]
||[[User:Heymeriou Mystakidou|Heymariou Mystakidou]]
|| Says the region name and frames per second out loud on command.
|-
||[[sbDialog]]
||[[User:Siann_Beck|Siann Beck]]
||A simple replacement function for [[llDialog]]. It re-orders the button list so that the button values, as passed to it, display left-to-right, top-to-bottom. It also opens a [[llListen|listen]] on the specified channel, and returns the handle.
|-
||[[Scheduler]]
||[[User:Haravikk Mistral|Haravikk Mistral]]
||Schedule multiple events using a single script timer
|-
||[[Scheme_Interpreter|Scheme Interpreter]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A scheme interpreter capable of handling most scheme expressions, including lambda and lists.
|-
||[[Script Override Functions]]
||[[User:Revolution Perenti|Revolution Perenti]]
||bypass default strings, integer etc in chat channel.
|-
||[[Scripted Attachment Detector.lsl|Scripted Attachment Detector]]
||{{User|Bobbyb30 Swashbuckler}}
||A script that will display avatars wearing scripted attatchments in hovertext. This may be worn as an hud or rezzed.
|-
||[[Self Upgrading Script Enhanced]]
||[[User:Cron Stardust|Cron Stardust]]
||Keeps only latest version of the script on prim (even with multiple adds of the same script!)
|-
||[[Sensor Visualizer]]
||[[User:Cerise Sorbet|Cerise Sorbet]]
||Shows the size and shape you get with [[llSensor]] range and arc parameters
|-
||[[Serverless Key Exchange]]
||[[User:Sendao Goodman|Sendao Goodman]]
||Maintains a network of object keys without using an external server.
|-
||[[SHA1|SHA1 Hash]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Preforms a SHA1 Hash on an input text. Similar to MD5 only (slightly) more secure.
|-
||[[Sim Map Particle Projector]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Displays a floating map of the sim the script is in.
|-
||[[Sim Restart Logger]]
||[[User:Kyrah Abattoir|Kyrah Abattoir]]
||Counts region restarts and displays log of last 9 restarts together with region FPS and dilation.
|-
||[[Simple Elevator in a Box]]
||[[User:Hank Ramos|Hank Ramos]]
||Simple elevator example.
|-
||[[Skillingo AntiHack Script]]
||[[User:Tmzasz Luminos|Tmzasz Luminos]]
||A simple Protection script for skillingo thats modifyable to work with other machines.
|-
||[[Skunk Money]]
||[[User:Hank Ramos|Hank Ramos]]
||Fun gambling machine of yesteryear, which only supports freeplay now due to SL regulations against gambling.
|-
||[[SLateIt]]
||[[User:Babbage Linden|Babbage Linden]]
||An augmented virtual reality HUD.
|-
||[[SLetanque]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL petanque game.
|-
||[[SLURL HUD]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Touch this HUD to get a SLURL through IM, email and floating text.
|-
||[[SL Mail V1.2]]
||[[User:Flennan Roffo|Flennan Roffo]]
||Second Life mail client V1.2 (released sept'07). Send and receive mail from within Second Life from and to any address. With Address Book function and many chat commands. V1.3 is upcoming soon!
|-
||[[SL_NTPoHTTP_v1.1_client|SL NTPoHTTP client]]
|[[User:SignpostMarv Martin|SignpostMarv Martin]]
||Second Life Needs Time Parsing over Hyper Text Transfer Protocol
Emulates the function of [[llGetWallclock]] for any timezone by using SLOpenID's SLNTPoHTTP service. Also supports ISO 8601 and RFC 2822 timestamps. Script is dependent upon an external service operated by the author!
|-
||[[Smooth Rotating Door]]
|[[User:Toy Wylie|Toy Wylie]]
||A script for doors that open and close smoothly using llTargetOmega
|-
||[[Smooth Sliding Door]]
|[[User:SimonT Quinnell|SimonT Quinnell]]
||A script for sliding doors that open and close smoothly using [[llMoveToTarget]]. Asjusts for prim orientation.
|-
||[[Speed Tester]]
||{{User|Bobbyb30 Swashbuckler}}
||Similar to the [[Efficiency Tester]], this script allows you to test the speed of a particular function or snippet with multiple trials giving min/max/avg/median and the standard deviation.
|-
||[[Spiral Staircase Generator]]
|[[User:Meyermagic Salome|Meyermagic Salome]]
||Generates nice looking spiral staircases without much hassle.
|-
||[[Static URL's for HTTP-In Service|Static_URLs]]
||[[User:Jor3l Boa|Jor3l Boa]]
||How to generate a static url for HTTP-In temporal limitations.
|-
||[[String Compare]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Compares two strings and reliably returns either 1, -1, or 0 if they are the same.
|-
||[[User:Void_Singer/Functions#String:_Find_Last_Index|String: Reverse]]
||[[User:Void Singer|Void Singer]]
||Returns an input string in reverse order
|-
||[[User:Void_Singer/Functions#String:_Get_Reverse_Order|String: Last Index]]
||[[User:Void Singer|Void Singer]]
||Returns the last index of search found in string (the backward equivalent of [[llSubStringIndex]])
|-
||[[Tail Messages (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||A super nice easy to use script for those non-scripters out there! NewAge coding has done it again where you no longer need to scroll up and down adding buttons and adding messages, Features a tag system (you'll see what i mean :P)
|-
||[[Teleport HUD]]
||[[User:Jesse Barnett|Jesse Barnett]]
||WORKS TO 4096 METERS!! Very user friendly teleport HUD. Add destinations by touching "Add" & naming destination in chat. Automatically gets sim name and coordinates. Will only display the destinations in the sim you are currently in. Demonstrates more advanced list manipulation and stride functions.
|-
||[[User:Void_Singer/Programs#v7-D_Enh._Landmark-2-Map|Teleporter (landmark based)]]
||[[User:Void_Singer|Void_Singer]]
||Uses Landmarks to offer map teleports. Works as Hud or inworld objects, just drop in landmarks and go.
|-
||[[Text_Scroller|Text Scroller]]
||[[User:Fred_Gandt|Fred Gandt]]
||A simple text display object that scrolls text (applied as a texture) from right to left (like ''those'' LED signs) in a continuous loop.
|-
||[[Bobbyb's texture changer|Texture Changers]]
||{{User|Bobbyb30 Swashbuckler}}
||A collection of texture changing scripts.
|-
||[[Texture Menu Management|Texture Management]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dialog Menu based Texture Selection.
|-
||[[Tic Tac Toe]]
||[[User:CG Linden|CG Linden]]
||Step by step demo on how to implement a larger scripting project
|-
||[[TightList]]
||[[User:Strife Onizuka|Revolution Perenti]]
||Tight List is a family of functions for encoding lists as strings and then decoding them back into lists.
There are two flavors: TightList and TightListType. TightListType preserves types and uses a 6 char header, while TightList uses a 1 char header that doesn't preserve type.
|-
||[[Timer Module]]
||[[User:Isabelle Aquitaine|Isabelle Aquitaine]]
||Manage multiple timers via linked messages.
|-
||[[User:Void_Singer/Functions#Unix_time_code_to_list_format|Timestamp: Unix time code to list format]]
||[[User:Void Singer|Void Singer]]
||converts Unix timestamps to their [Y, M, D, h, m, s] equivalents (ex: 1234567890 to [2009, 2, 13, 3, 31, 30])
|-
||[[User:Void_Singer/Functions#List_format_to_Unix_time_code.|Timestamp: List format to Unix time code]]
||[[User:Void Singer|Void Singer]]
||converts [Y, M, D, h, m, s] timestamps to their Unix equivalents (ex: [2009, 2, 13, 3, 31, 30] to 1234567890)
|-
||[[User:Void_Singer/Functions#Weekday_from_Unix_timestamp|Timestamp: Weekday from Unix timestamp]]
||[[User:Void Singer|Void Singer]]
||Gets weekday from Unix timestamps (ex: "Friday" from 1234567890)
|-
||[[User:Void_Singer/Functions#Weekday_from_.28_Y.2C_M.2C_D_.29_format|Timestamp: Weekday from (Y, M, D) format]]
||[[User:Void Singer|Void Singer]]
||Gets weekday from (Y, M, D) timestamps (ex: "Friday" from (2009, 2, 13))
|-
||[[Touch A Quote]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Touch an object to read quotes sequentially from a notecard
|-
||[[Touring Balloon]]
||[[User:Hank Ramos|Hank Ramos]]
||Automated touring balloon with many options from long ago. Always seems to work on one SL release, and not the other.
|-
||[[Under Age Boot]]
|[[User:Chance Unknown|Chance Unknown]]
||Security device example to teleport home accounts below a minimum age limit; can be useful in combating free griefer accounts.
|-
||[[User:Rolig_Loon/UNDO_PosRot|UNDO_PosRot]]
||[[User:Rolig Loon|Rolig Loon]]
||Allows user to undo position and rotation changes that have been made "manually" to any or all prims in a linkset.
|-
||[[Universal Translator]]
|[[User:Hank Ramos|Hank Ramos]]
||Chat listener that handles seamless translation of public chat between 50+ written languages without the need for configuration. Handles numerous avatars, auto-detects languages, and works together with multiple copies of translators to spread-workload using a sophisticated back-end communications sub-system.
|-
||[[Unix2DateTime]]
|[[User:Flennan Roffo|Flennan Roffo]]
||Conversion from Unix time ([[llGetUnixTime]]()) to date and time string and vice versa.
|-
||[[Unmutable Descript Nagger]]
|[[User:Bobbyb30 Zohari|Bobbyb30 Zohari]]
||To nag avatars to take off their scripted attatchments.
|-
||[[Unpacker On Rez (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||A very simple to use script for all you creators out there, This script will enable you to send out boxed items and make it easier for users to unpack, Also features auto die on completion. Very simple to configure!
|-
||[[Unpacker On Touch (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||Exactly like Unpacker On Rez, But changed some things about to make it Unpack On Touch
|-
||[[Update distributor]]
|[[User:Dale Innis|Dale Innis]]
||Distribute an object (like a project update) to a list of people named in a notecard.
|-
||[[UUID2Channel]]
||[[User:Project Neox|Project Neox]]
||Optimised version of the original key2channel generators.
|-
||[[UUID Song Generator]]
||{{User|Sendao Goodman}}
||Translates a UUID into a simple song and plays it.
|-
||[[VirtualID_URLMap|VirtualID URL Mapper for HTTP-in]]
|[[User:Cenji Neutra|Cenji Neutra]]
||A script showing how to setup a static URL of the form <your-alias>.obj.virtualid.info which maps to the dynamic HTTP-in URL LSL generates and keeps it up-to-date.
|-
||[[User:Void_Singer/Programs#v7-D_Advanced_Visitor_Greeter|Visitor Greeter]]
|[[User:Void_Singer|Void_Singer]]
||Reduced spam visitor greeter, highly configurable, easy to modify.
|-
||[[Visitor Logger (Web/Basic) ]]
|[[User:Buddy Sprocket|Buddy Sprocket]]
||A very basic visitor logger - log visitors in SL to a text file on your web-site.
|-
||[[Vote Simple]]
|[[User:JB_Kraft|JB Kraft]]
||Simple vote collector. One avi, one vote.
|-
||[[Walking Sound (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||Very powerful walking sound script, Featuring customer ability to add their own sounds with the API Sound Feature!
|-
||[[WarpPos]]
|[[User:Keknehv Psaltery|Keknehv Psaltery]]
||Non-physical movement without the 10m limit.
|-
||[[Wiki3DBuilder]] [[Wiki3DBuilder1.0]]
||[[User:Salahzar Stenvaag|Salahzar Stenvaag]]
||Allows a group of people to collectively build up complex 3D mindmaps with connected concepts. Uses particles for connections and low prim usage. Nodes can be textured, colored, changed form size moved collectively by everybody and can distribute notecards, landmarks, URL, objects, textures. I provide two version 0.1 and 1.0 and probably next version will communicate with moodle and sloodle external websites.
|-
||[[Window Control]]
||[[User:Emmas Seetan|Emmas Seetan]]
||For window opacity, helpful for buildings.
|-
||[[WHMcs SecondLife plugin]]
|[[User:Alicia Sautereau|Alicia Sautereau]]
||Linden Dollar payment plugin for the WHMcs hosting portal.
|-
||[[XTEA Strong Encryption Implementation]]
||[[User:Morse Dillon|Morse Dillon]]
||An LSL implementation of XTEA (eXtended Tiny Encryption Algorithm). This is the first known public release of a 'real' strong encryption implementation in LSL and is released under the GNU General Public License (GPL).
|-
||[[XyText 1.5|XyText]]
||[[User:Xylor Baysklef|Xylor Baysklef]]
|| Display text (up to 10 characters) on a prim. Use as many prims as desired.
|-
||[[XyyyyzText|XyyyyzText]]
||[[User:Criz Collins|Criz Collins]]
|| Display text (up to 10 characters) on a prim. Displays different text for each line instead of one single text, that will be broken into the next lines. Watch here for what that means: http://screencast.com/t/1wMLujLcEO
|-
||[[XyzzyText|XyzzyText]]
||[[User:Thraxis Epsilon|Thraxis Epsilon]] and [[User:Gigs Taggart|Gigs Taggart]]
|| Display text (up to 10 characters) on a prim. Way more efficient than XyText.
|-
||[[Youtube TV]]
||[[User:Morgam Biedermann|Morgam Biedermann]]
||Watch your favorite Youtube videos / auto set the texture to the parcel media texture.
|-
||[[Zero Lag Poseball]]
||[[User:Jippen Faddoul|Jippen Faddoul]] and [[User:Daemonika Nightfire|Daemonika Nightfire]]
||A simple poseball with no lag
|}

</div>
<div id="box">

==Support Script Library==
These are scripts in other languages, intended to be run on other systems that support scripts written in LSL

{| class="sortable" {{Prettytable}}
|- {{Hl2}}
! '''Name'''
! '''Creator'''
! '''Description'''
|-
|| [[User:Ina Centaur/UUID/calimg.api|Calendar Image UUID API]]
|| [[User:Ina Centaur|Ina Centaur]]
|| API that gives the UUID of an image of a calendar image give month and year arguments.
|-
||[[HTTP Post request to a PHP server]]
||[[User:Corto Maltese|Corto Maltese]]
|| This small library allows you to make simple POST requests to your website. The libraries allow you to get your request through the variable $_POST on the server. It also include a basic security mechanism aimed to stop hacking. Comprises of LSL client script and PHP server script.
|-
|| [[User:Ina Centaur/PHP/k2n.php|Key2Name.php]]
|| [[User:Ina Centaur|Ina Centaur]]
|| Get Avatar's Name using Second Life search service. (like in LSL Key2Name)
|-
|| [[Lame_Object_DNS_and_Cross_Sim_Messaging|Lame Object DNS and Cross Sim Messaging]]
|| [[User:Liandra Ceawlin|Liandra Ceawlin]]
|| Simple, cheeseball method of doing cross-sim communications with http-in and an external object DNS service.
|-
|| [[User:SignpostMarv Martin/PHP/llXorBase64StringsCorrect|llXorBase64StringsCorrect]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| An implementation of [[llXorBase64StringsCorrect]] in PHP- should be useful if you're using llXorBase64StringsCorrect to do cryptography work in LSL2 and posting it out to the web via [[llHTTPRequest]].
|-
|| [[User:SignpostMarv Martin/PHP/lsl fu.php|lsl_fu.php]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| A basic OOP'd PHP Class containing VeloxSeverine's $_POST fixer and Marv's own eccentric ideas for "fixing" things.
|-
|| [[User:Jor3l Boa/PHP/n2k.php|Name2Key.php]]
|| [[User:Jor3l Boa|Jor3l Boa]]
|| Get Avatar's UUID using Second Life search service. (like in LSL Name2Key)
|-
|| [[Public_Object_DNS|Public Object DNS]]
|| [[User:Liandra Ceawlin|Liandra Ceawlin]]
|| Public object DNS-like system running on GAE, for http-in. Hopefully scalable enough for wide-spread usage.
|-
|| Silo
|| [[User:Zero_Linden|Zero Linden]]
|| General purpose data store in PHP. Use this to persist arbitrary data from LSL via [[llHTTPRequest]]. See:
* [http://www.notabene-sl.com/misc/silo-README.txt README] file
* [http://www.notabene-sl.com/misc/silo.tgz silo.tgz] tarball
* forum post [http://forums-archive.secondlife.com/54/69/119570/1.html Announcement].
|-
||[[Silverday ObjectDNS]]
||[[User:Till Stirling|Till Stirling]]
||Dynamic Object-DNS-System to provide dynamic mapping of LSL-URLs to persistent domains. Features include redirect service, password protected domains, write protected domains, LSL-API for all necessary functions, optional web-interface.
|-
|| [http://aubretec.com/products/sldb SLDB]
|| [[User:Luc Aubret|Luc Aubret]]
|| Flexible web database storage using PHP/MySQL. Used to store per-user field/value pairs from in-world objects using [[llHTTPRequest]].
* [http://aubretec.com/support/manuals/sldbkit/ Implementation Guide]
* [http://aubretec.com/wp-content/uploads/2009/05/sldb.zip Download] (.zip, 12kb)
|}

== See Also ==
<div style="padding: 0.5em">
'''Articles'''
*[[:Category:LSL Examples| Examples]]

</div></div>

{{LSLC|}}

Update distributor

2010-08-25T22:20:28Z

Dale Innis: Create page

{{LSL Header}}

= Introduction =

A simple device for distributing an updated version of a product to a list of existing customers, or in general for sending a thing to a bunch of people whose names you know.

= Usage =

To use this script, put it into a prim, along with a notecard containing a list of names of residents (one per line), and the object to be distributed. Then touch the prim, and it will read the notecard, determine the key of each resident, and tell you that it is not actually sending the object to each of them in turn. Once you are satisfied that that's right, edit the script and change ACTUALLY_SEND to TRUE, save the script, and touch the object again. This time it will actually send the thing to the people! (Then edit it and change ACTUALLY_SEND back to FALSE, so you don't forget next time and send duplicates or something.)

= Limitations and Notes =

There should be exactly one notecard, and exactly one object, in the prim when you touch it. Otherwise it will complain and not do anything. To use it to send a texture or a script or a notecard or something, rather than an object, you'll have to modify the script.

The script uses the w-hat name2key server to get the keys of the people to send the thing to. If that server stops working, so will this script.

The script pauses for one second after each HTTP call to the name2key server; this makes it take awhile (over a minute for a 60-name list, for instance), but also avoids HTTP throttling. Another approach would be to explicitly check for HTTP throttling, and only slow down if it happens, but that would be more work.

= The Code =

You may do anything you like with this code, without limitation, subject only to the ToS, law, morality, etc.

<lsl>

// Send the thing to the people listed in the notecard!
// Script by Dale Innis
// Do with this what you will, no rights reserved
// See https://wiki.secondlife.com/wiki/Update_distributor for instructions and notes

integer ACTUALLY_SEND = FALSE; // Set to true to actually send the update to people

string URL = "http://w-hat.com/name2key";

string ncname;
integer nextline;
string name;

key dsqkey;
key httpqkey;

order_notecard_line() { // Request the next notecard line from the data server
dsqkey = llGetNotecardLine(ncname,nextline);
nextline++;
}

send_product(string name,key id) { // Send, or pretend to, the object to the given key
if (ACTUALLY_SEND) {
llOwnerSay("Sending "+llGetInventoryName(INVENTORY_OBJECT,0)+" to "+name+" ("+(string)id+")");
llGiveInventory( id, llGetInventoryName(INVENTORY_OBJECT,0) );
} else {
llOwnerSay("Not actually sending "+llGetInventoryName(INVENTORY_OBJECT,0)+" to "+name+" ("+(string)id+")");
}
}

default
{
state_entry()
{
// Not really anything to do here
}

touch_start(integer total_number)
{
if (llDetectedKey(0)!=llGetOwner()) return; // Ignore non-owner touches
if (llGetInventoryNumber(INVENTORY_NOTECARD)!=1) {
llOwnerSay("There needs to be exactly one notecard!");
return;
}
if (llGetInventoryNumber(INVENTORY_OBJECT)!=1) {
llOwnerSay("There needs to be exactly one object!");
return;
}
ncname = llGetInventoryName(INVENTORY_NOTECARD,0);
nextline = 0;
order_notecard_line(); // Request the first notecard line
}

dataserver(key id, string data) { // A notecard line has arrived
if (id != dsqkey) return;
if (data==EOF) {
llOwnerSay("Done!");
return;
}
name = llStringTrim(data,STRING_TRIM); // Strip blanks
integer sent = FALSE;
if (llStringLength(name)>2) { // Ignore blanks lines
if (llGetSubString(name,0,1)!="//") { // Ignore lines starting with //
httpqkey = llHTTPRequest( URL + "?terse=1&name=" + llEscapeURL(name), [], "" );
sent = TRUE;
llSleep(1.0); // Avoid HTTP throttling
}
}
if (sent==FALSE) {
order_notecard_line(); // If we didn't just send for a key, send for next name.
}
}

http_response(key id, integer status, list meta, string body) { // A key has arrived
if ( id != httpqkey )
return;
if ( status == 499 )
llOwnerSay("name2key request timed out for "+name);
else if ( status != 200 )
llOwnerSay("the internet exploded!! Blame "+name);
else if ( (key)body == NULL_KEY )
llOwnerSay("No key found for " + name);
else
send_product(name,(key)body); // Send, or not, the product to the key
order_notecard_line(); // Then order the next name to process
}

}
</lsl>

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

Category:LSL Library

2010-08-22T20:25:13Z

Dale Innis: /* LSL Script Library */ add camera following prim

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

<div id="box">
<div style="padding: 0.5em 0.5em 1.5em">
Come to this page to see complex examples that show how to combine parts of LSL.

Go to the [[:Category:LSL Examples|LSL Examples]] page to see brief examples of how to use parts of LSL

Why collect complex examples here? Well, ...

There are many [[script|scripts]] that have become buried in the [http://forums-archive.secondlife.com/15/1.html Scripting Library archive] or the newer [https://blogs.secondlife.com/community/forums/scripting_library?view=discussions Scripting Library forum], were lost with the death of the early scripting forums, or sit idle in [[inventory|inventories]] that could be useful and should be more accessible.

Other scripters may be in the same situation. This wiki is a well-suited medium for a script library. Feel free to add your scripts to the script library by creating new pages for them and linking to those pages here.

Note that there are many more scripts in the LSL Library here, but you can't get to them if you don't know they exist, because they are subpages now, instead of an automatically updated category. Good luck searching.
</div>
</div>

<div id="box">

== Rules for posting: ==
<div style="padding: 0.5em">
#Your script must be tested and working. If it's not, stick it in your user-space until it is. This is a list of working, usable scripts.
#Add a link to your script's page here. Link back to this page from your script's page. Start your page with <nowiki>{{LSL Header}}</nowiki>.
#Do not add scripts that duplicate the same functionality as an existing script or built in {{LSLGC|Functions|function}}. If yours does, explain why.
#Do not list simple scripts here. Include those among the [[:Category:LSL Examples|LSL Examples]] instead.
</div></div>

<div id="box">
==LSL Script Library==

{| class="sortable" {{Prettytable}}
|- {{Hl2}}
! '''Name'''
! '''Creator'''
! '''Description'''
|-
||[[1st necessity of SL]]
||[[User:Beer Dailey|Beer Dailey]]
||Monitors for avatars and (de)activates scripts states to control script performance/lag.
|-
||[[3D Radar]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Rezzes a ball for each avatar in range. Each ball tracks its own AV and displays distance.
|-
||[[Access (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||An easy to use script for permissions on who can use the script, Public/Group/Owner
|-
||[[Aim Detection]]
||[[User:Han Shuffle|Han Shuffle]]
||Monitors for avatars and reports back to owner about who is aiming at them.
|-
||[[AntiDelay Node]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Uses [[llMessageLinked]] to stop those pesky delays.
|-
||[[AO Overriding Pose Ball]]
||[[User:Jesse Barnett|Jesse Barnett]]
||No more turning your AO off and on when you sit down
|-
||[[ARCFOUR Strong Encryption Implementation]]
||[[User:Nekow42 Zarf|Nekow42 Zarf]]
||An LSL implementation of ARCFOUR, the most popular stream cipher still in use. It is licensed under a Creative Commons Attribution 3.0 license.
|-
||[[Assembly Programming Language|Assembly-Like Programming Language]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A compiler that runs assembly-like programs.
|-
||[[Associative Array Emulator|Associative Array (Dictionary) Emulator]]
||[[User:Alynna Vixen|Alynna Vixen]]
||This library provides a set of functions for using a list as an associative array where string based keys can refer to one or more variant elements.
|-
||[[AvatarFollower]]
||[[User:Dale Innis|Dale Innis]]
||Allows one avatar to automatically follow another.
|-
||[[Avatar Radar (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||Version 1.2; A nice new avatar radar script i just finish that you can place in your hud, Also features avatar locator
|-
||[[Base2Dec]]
||[[User:Siann Beck|Siann Beck]]
||Convert a number to decimal from any base.
|-
||[[BaseN]]
||[[User:Nexii Malthus|Nexii Malthus]]
||Variable base compression, dynamically maps to usable UTF code points.
|-
||[[Basic A-Star Pathfinder]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| My own interpretation of A Star into a highly efficient algorithmn
|-
||[[Basic Encryption Modules]]
||[[User:Beverly Larkin|Beverly Larkin]]
||Basic encryption scripts, allows you to encrypt a float and shout it to another prim on a randomly chosen channel.
|-
||[[Be happy]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Basic smile attachment script, makes your avatar smile.
|-
||[[Best Neighbor Ad Hiding Script|Best Neighbor]]
||[[User:Doran Zemlja|Doran Zemlja]]
||Reduce ad clutter by hiding ads when users are on their own land nearby.
|-
||[[BigNum|BigNum Library (RSA Encryption)]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A BigNum Library for dealing with big numbers! Specialized for modular multiplication, and RSA encryption.
|-
||[[Binary Clock v1.1|Binary Clock]]
||[[User:Fox Diller|Fox Diller]]
||A Binary Clock.
|-
||[[BinaryDecimalConverter]]
||[[User:Soundless Smalls|Soundless Smalls]]
||Converts a binary value to a decimal value and vice versa.
|-
||[[Blacklist and Remote Kill|Blacklist and Remote Kill]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Blacklist(denial of use) or a creator kill script(can delete someone's item by command on private channel)
|-
||[[User_talk:Rolig_Loon/Bookmark_URLs|Bookmark URLs]]
||[[User:Rolig Loon|Rolig Loon]]
||Dialog driven HUD reads bookmarked URLs from notecards and navigates directly to them with user's in-world browser.
|-
||[[Builders Buddy|Builder's Buddy Tool]]
||[[User:Newfie Pendragon|Newfie Pendragon]]
||Script to easily move/rotate large builds that exceed the linkable size limit (30 meters).
|-
||[[Button Click Detector]]
||{{User|Sendao Goodman}}
||Use [[llDetectedTouchUV]] to determine which button was pressed on a texture.
|-
||[[Camera following prim]]
||[[User:Dale Innis|Dale Innis]]
||Pair of scripts to make a prim follow your camera position around (for lights etc).
|-
||[[Camera Sync]]
||[[User:Meyermagic Salome|Meyermagic Salome]] and [[User:Nomad Padar|Nomad Padar]]
||A system to synchronize the cameras of two avatars.
|-
||[[Chatbot]]
||Anonymous
||Compile and run the LSL you type on a channel, faster than you can thru the 2007-08 SL GUI.
|-
||[[Chat Logger (GPL)]]
||[[User:Nobody Fugazi|Nobody Fugazi]]
||Chat logger which requests permission from participants before recording them.
|-
||[[Chat_Relay|Chat Relay]]
||[[User:grumble Loudon|grumble Loudon]]
||A Chat relay which can be routed using a path header and won't echo.
|-
||[[ClickAndDrag]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Click and Drag user interface elements using dynamic feedback
|-
||[[Code Racer]]
||Anonymous
||Race two versions of code forever, to see which runs faster.
|-
||[[Code Sizer]]
||Anonymous
||Count the bytes compiled from source code, to measure how to write small code.
|-
||[[User:Void_Singer/Programs#v7-D_Enh._Color_Picker|Color Changer]]
||[[User:Void_Singer|Void_Singer]]
||Dialog driven color changer. Supports 16million+ colors, web color codes, multiple targeted prims, with save and recall.
|-
||[[Color Changer|Color Changer Plus]]
||[[User:Neo Calcutt|Neo Calcutt]]
||A color changer with 14 colors, a random function, and a custom vector function.
|-
||[[Color conversion scripts|Color Conversion]]
||[[User:Sally LaSalle|Sally LaSalle]]
||Convert between Red Green Blue (RGB) and Hue Saturation Value (HSV).
|-
||[[ColorConvert]]
||[[User:Siann Beck|Siann Beck]]
||Convert color values to vector from RGB, hex or HTML color name.
|-
||[[Color script]]
||[[User:Masakazu Kojima|Masakazu Kojima]]
||Script for changing colors trough a listener with pre-defined colors.
|-
||[[Library Combined Library|Combined Library]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Library of mostly encoding and decoding functions, some more useful then others.
* String functions: Replace / Trim right / Trim left / Trim both
* Unicode conversion: UTF8 to Unicode / Unicode to UTF8
* List functions: Replace / Compare
|-
||[[Computer:jaycoonlanguage]]
||[[User:jayco121 Bing|jayco121 Bing]]
|| A language written in LSL that is meant for my computer (available at the shop).
|-
||[[Read Note Card Configuration|Configuration Notecard Reader]]
||{{User|Dedric Mauriac}}
||A script to read configuration information from a notecard. Parses notecard to extract key words and their assigned values. Allows for comment lines and many more useful features.
|-
||[[AdvancedNotecardReader|Configuration Notecard Reader (advanced)]]
||[[Lear Cale|Lear Cale]]
||Robust configuration notecard reader; supports multiple notecards with same suffix, handles reconfig on inventory change, and does not usurp the default state.
|-
||[[Library_Chat_Relay|Conversation Relay]]
||[[User:Jippen Faddoul|Jippen Faddoul]]
||Chat relay which requests permission from participants before relaying their messages. Also includes their attachments. (ToS compliant).
|-
||[[Curtain script]]
||[[User:Zilla Larsson|Zilla Larsson]]
||A simple script to retract/stretch curtains, blinds, bedcovers and more
|-
||[[Dataserver API]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dataserver Framework for Notecards.
|-
||[[Date Library]]
||[[User:Corto Maltese|Corto Maltese]]
|| Date library, based on number of day since march 3rd 1600, can be used to calculate weekday, date differences, and date offset, and date formating.
|-
||[[Day of the Week]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Function to get day of the week from [[llGetUnixTime]].
|-
||[[Days in Month]]
||[[User:IntLibber Brautigan begin_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting end_of_the_skype_highlighting|IntLibber Brautigan]]
||Clicking on it returns the number of days in the present month. Useful for scripting calendars and tier systems that need to know the number of days in the month at hand or to calculate for any month. Even adjusts for leap years.
|-
||[[Deed Tools]]
||[[User:Falados Kapuskas|Falados Kapuskas]]
||Tools that allow the creator to modify Group-Owned (Deeded) Objects via chat.
|-
||[[Describe Chatter]]
||Anonymous
||Chat to see yourself as others do.
|-
||[[Dialog Control]]
||[[User:Nargus Asturias|Nargus Asturias]]
|| A (not-so) simple dialog & menu control script. Call dialog and receive selected value via [[link_message]](), with built-in timer and [[link_message]]() notification on time out. Supports multi-pages dialog and numeric property dialog. Button text and dialog's returned value can differ.
Latest version also has [[Dialog Menus Control]] built-in; which allow multi-level menus through SL dialog system.
|-
||[[Dialog NumberPad|Dialog Number Pad]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Use a dialog to accept positive integer input from users.
|-
||[[Displayer Script]]
||[[User:Akinori Kimagawa|Akinori Kimagawa]]
||[[Display Words On Top Of An Object]]
|-
||[[Drink script]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Used mainly for food and drink in Second Life.
|-
||[[TOXDropBox|DropBox]]
||[[User:Dimentox Travanti|Dimentox Travanti]]
|| This is a Drop box which allows people to drop certain items in a object & has many config options.
|-
||[[Efficiency Tester]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Tests the speed of a function.
|-
||[[Email-to-IM|Email2IM]]
||[[User:DoteDote Edison|DoteDote Edison]]
||Send IMs to SL friends via [[email]] (translate emails from friends into IMs).
|-
|-
||[[User:Kireji_Haiku/SIMchat_headset|Encrypted Region-wide chat]]
||'''[[User:Kireji Haiku|Kireji Haiku]]''' ([[User talk:Kireji Haiku|talk]]|[[Special:Contributions/Kireji Haiku|contribs]])
||Encrypted Region-wide chat
|-
||[[ExplodingObjects]]
||[[User:Dale Innis|Dale Innis]]
||Causes an object (of the appropriate type) to explode on command.
|-
||[[FadeEasy]]
||[[User:Nika Rugani|Nika Rugani]]
||The easy way of fading objects in or out (Using llSetLinkAlpha)
|-
||[[FastConeSpread]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Fast Algorithmn to achieve cone spread, main use in weaponry systems.
|-
||[[User:PixelProphet Lane/Scripts#Fast List Prim Contents|Fast List Prim Contents]]
||[[User:PixelProphet Lane|PixelProphet Lane]]
||Fast and efficient method to print Object Inventory (Name, Type and next Owner permissions)
|-
||[[Find Avatar Key|Find Avatar Key]]
||[[User:Huney Jewell|Huney Jewell]]
||Explores [[UUID]] of avatar whose name is said in local chat or who touches the prim.
|-
||[[First Name Letter Prize]]
||[[User:RaithSphere Whybrow|RaithSphere Whybrow]]
||Gives a prize if the person who sits on it's first letter of first name matches the random letter!
|-
||[[Fix Small Prims|Fix_Small_Prims]]
||[[User:Emma Nowhere|Emma Nowhere]]
||Finds and adjusts the smallest prims in a linkset so that it can be scaled down further.
|-
||[[Float2Hex]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Very useful for transporting [[float|floats]].
|-
||[[Float Box Contents]]
||[[User:Rolig Loon|Rolig Loon]]
||Displays object inventory in hover text, identified by type and updated marquee-style.
|-
||[[Follower (script)|Follower]]
||Unknown, uploaded by [[User:Slik Swindlehurst|Slik Swindlehurst]]
||Makes an object follow the nearest person. Do not use for [[grief|griefing]].
|-
||[[GA Event Notifier]]
||[[User:Victor Hua|Victor Hua]]
||Gathers seven days event data from a Google calendar and display it through a simple interface. The lsl script can access several calendars at once through seperate php files. One file per calendar. Host the included php on your own web server.
|-
||[[Geometric|Geometric Library]]
||Community Project
||A substantial amount of various geometric functions for intersection and other purposes of 3D maths.
|-
||[[Get Profile Picture]]
||[[User:Valentine Foxdale|Valentine Foxdale]]
||Sets the texture of the object to profile picture of the person that touches ot
|-
||[[GetTimestampOffset]]
||[[User:Siann_Beck|Siann Beck]]
||Returns [[llGetTimestamp]]() with an hour offset.
|-
||[[Give InvItem every n hours]]
||[[User:Criz Collins|Criz Collins]]
||Will give an inventory item on touch only every n hours, even if somebody touches the object more than once.
|-
||[[Give random object]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to receive a random object in the prim's inventory
|-
||[[Google Charts]]
||[[User:Dedric Mauriac|Dedric Mauriac]]
||Create links to display raw data as a chart image.
|-
||[[Google_Translator]]
||[[User:Ugleh Ulrik|Ugleh Ulrik]]
||Translates spanish to english, and its simple to make it any other way.
|-
||[[Go transparent when walking]]
||[[User:Emmas Seetan|Emmas Seetan]]
||An attachment that goes invisible when you walk and visible when you don't walk.
|-
||[[Group Authorization]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Checks to see if object is set to appropriate group (checks by [[Group key finder|group key]])
|-
||[[Group Information v1.0]]
||[[User:Tyrennic Rivera|Tyrennic Rivera]]
||When clicked the prim will show group information (set on the prim) from the official Second Life Search page.
|-
||[[Group key finder]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to find the key of the group
|-
||[[Group Privacy]]
||[[User:Chance Unknown|Chance Unknown]]
||Security device to insure members of a group can have a private area. Deactivates when nobody present.
|-
||[[Hello Avatar]]
||Linden Lab
||SL's default script.
|-
||[[Hello Avatar Companion]]
||[[Chase Quinnell]]
||Companion to the original [[Hello Avatar]] script
|-
||[[Hierarchics]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Advanced script to create an efficient self-aware hierarchic structure.
|-
||[[User:Rolig_Loon/High-Capacity_Greeter-Counter|High-Capacity Greeter-Counter]]
||[[User:Rolig Loon|Rolig Loon]]
||Uses a memory compression algorithm to store hashed visitor UUID's in a string instead of using a list.
|-
||[[Holodeck]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Home Rezzing System (Open Source).
|-
||[[Interpolation|Interpolation Library]]
||[[User:Nexii_Malthus|Nexii Malthus]]
||A small set of interpolation functions.
|-
||[[Intra-Region Update Server]]
||[[User:Emma_Nowhere|Emma Nowhere]]
||Centrally update objects such as Freeview screens or teleport pads within a region that are configured by notecards or contain modifiable objects or media assets.
|-
||[[Inventory_Based_Menu]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Inventory Based Menu System.
|-
||[[iTunes RPC Email|iTunes RPC]]
||[[User:Fox Diller|Fox Diller]]
||iTunes RPC via LSL [[llEmail]] and [[llRemoteDataReply]].
|-
||[[Kilt Editor|Kilt / Skirt Editor]]
||[[User:Brangus Weir|Brangus Weir]]
|| This changes all the parameters of all the flexis in the link set in one swell foop!
|-
||[[Key Pad Door|Keypad Door]]
||[[User:Tdub Dowler|Tdub Dowler]]
|| Door and keypad with changeable code. Follow instructions carefully!
|-
||[[Last Sound System]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL [http://Last.fm Last.fm] client.
|-
||[[LibraryDisplayLandScreenshot]]
||[[User:Jon Desmoulins|Jon Desmoulins]]
||A modified version of LibraryDisplayProfilePic using the new [[PARCEL_DETAILS_ID]] Implemented in Server v1.36
|-
||[[User:Daemonika_Nightfire/Scripts/LinkNumber-List_in_llSetLinkPrimitiveParamsFast|LinkNumber-List_in_llSetLinkPrimitiveParamsFast]]
||[[User:Daemonika Nightfire|Daemonika Nightfire]]
||Changed several prims in linkset with the same parameters, with a list. Without separate llSetLinkPrimitiveParams for each prim. (ideal for show/hide effects)
|-
||[[Linkset resizer]]
||[[User:Maestro Linden|Maestro Linden]]
||Systematically rescales a linkset by moving and resizing each prim (by using [[llGetLinkPrimitiveParams]] and [[llSetLinkPrimitiveParamsFast]])
|-
||[[Linkset resizer with menu]]
||[[User:Brilliant Scientist|Brilliant Scientist]]
||A menu-driven script that rescales a linkset by moving and resizing the prims using [[llGetLinkPrimitiveParams]] and [[llSetLinkPrimitiveParamsFast]] functions. Based on [[Linkset resizer]].
|-
||[[Linkset Resizer 2]]
||[[User:Emma Nowhere|Emma Nowhere]]
||A more user-friendly resizer script designed for either drop-in use by the end-user or builder or for use in products. Based on [[Fix Small Prims]].
|-
||[[List2CSV]]
||[[User:Kunnis Basiat|Kunnis Basiat]]
||List2CSV & CSV2List that include preserving type and escaping characters.
|-
||[[list_cast]]
||[[User:Fractured Crystal|Fractured Crystal]]
||Casts a list of strings into the type they appear to be. Designed for preprocessing user input for feeding into [[llSetPrimitiveParams]]
|-
||[[Listener Script]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Use to [[listen]] to other people's conversations (Like spying)
|-
||[[User:Void_Singer/Functions#List:_Find_Last_Index|List: Find Last Index]]
||[[User:Void Singer|Void Singer]]
||Returns the last index of searched item in a source list. (backwards version of [[llListFindList]])
|-
||[[User:Void_Singer/Functions#List:_Multi-Find_Index_.28First_or_Last.29|List: Multi Find]]
||[[User:Void Singer|Void Singer]]
||Returns the first found index of multiple search items in a list. (Multi-item version of [[llListFindList]]. Fwd and Rev versions included)
|-
||[[User:Void_Singer/Functions#List:_Get_Reverse_Order|List: Reverse]]
||[[User:Void Singer|Void Singer]]
||Returns an input List in reverse order
|-
||[[Load URL]]
||[[User:Emmas Seetan|Emmas Seetan]]
||Touch to get a dialog to visit the URL inside the script.
|-
||[[User:Kephra_Nurmi/lsDancemachine|lsDancemachine]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Low lag client server dancemachine.
|-
||[[User:Kephra_Nurmi/lsDeejay|lsDeejay Home Edition]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Client server media control for music, video, youtube, pictures, and texture animations.
|-
||[[User:Kephra_Nurmi/lsDialog|lsDialog]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Universal notecard driven menu dialog system.
|-
||[[User:Kephra_Nurmi/lsDisplay|lsDisplay]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Picture cycler with preloader.
|-
||[[User:Kephra_Nurmi/lsDistributor|lsDistributor]]
||[[User:Kephra_Nurmi|Kephra Nurmi]]
|| Simple 'try' and 'buy' vendor system.
|-
||[[LSL_languageAPI]]
||[[User:Gypsy paz|Gypsy Paz]]
||Multi-lingual API from notecard based language files
|-
||[[Mandelbrot Explorer]]
||[[User:Babbage Linden|Babbage Linden]]
||An interactive fractal explorer.
|-
||[[Merge Sort]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Implements a Merge Sort in LSL, however this code is 300(ish) times slower than [[llListSort]]. Don't use this in a script!
|-
||[[Minesweeper]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A simple minesweeper game.
|-
||[[Morse Code]]
||{{User|Bobbyb30 Swashbuckler}}
||A script that allows for the conversion to and from morse code and can "play" morse code.
|-
||[[Multi Item Rezzer|Multi Item Rezzer]]
||[[User:Jesse Barnett|Jesse Barnett]]
||A rework of my old High Altitude Rezzer. Place the objects that you wish to choose from to be rezzed inside. Sit on the rezzer and pick the item and the height. It will go to target height and rez the object.
|-
||[[Multirezzer|Multirezzer (on collision)]]
||[[User:Beet Streeter|Beet Streeter]]
||Spawns up to 10 objects when the object containing the script collides with a user.
|-
||[[Name2Key in LSL]]
||[[User:Maeva Anatine|Maeva Anatine]]
||Get the Name2Key feature inside your scripts. Works even on lastly subscribed avatars.
|-
||[[No Auto-Return]]
||[[User:Bellla Clarity|Bella Clarity]]
||To stop your long and hard builds from getting returned in sandboxes (''only single prims, though!'').
|-
||[[No Auto-Return NR]]
||[[User:Jor3l Boa|Jor3l Boa]]
||This really works (29-05-09), needs a nearby region to do the trick and avoid auto return. (Tested on Blue and Rausch)
|-
||[[No Auto-Return (Multi)]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A revision of Bella's that works for multi-prim objects.
|-
||[[No Limit Teleporter]]
||[[User:Morgam Biedermann|Morgam Biedermann]]
||Teleport to infinite altitudes (up to 4096m)
|-
||[[Object Size]]
||[[User:Chase Quinnell|Chase Quinnell]]
||Gets the dimensions and footprint of a linkset
|-
||[[Object to Data v1.3|Object to Data]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Turns an object into text (and back). Allows people to transfer objects through notecards (or otherwise).
|-
||[[Online Indicator|Online Indicator]]
||[[User:Kristy Fanshaw|Kristy Fanshaw]]
||Will show if the user is online or not. Displays users profile picture and allows to send IM's to user. Also gives a link to open the users profile
|-
||[[Open Group Join]]
||[[User:Alicia Stella|Alicia Stella]]
||User Touches Object to Join Group from Group Info window, (no bot.)
|-
||[[Open Zyngo Skin Installer]]
||[[User:Tmzasz Luminos|Tmzasz Luminos]]
||A Simple Script designed to install skins on the popular Skill machines.
|-
||[[One Script, many doors]]
||[[User:Kyrah Abattoir|Kyrah Abattoir]]
||Door script able to manage more than 50 linked doors from a single script instance.
|-
||[[ParseString2List]]
||[[User:Strife Onizuka|Strife Onizuka]]
||Same as [[llParseString2List]] and [[llParseStringKeepNulls]], but not limited to 8 spacers or separators. Thus substitute a call to the [[llParseString2List]] and [[llParseStringKeepNulls]] functions by a call to [[Parse_String_To_List|ParseString2List]] whenever you have more than 8 separators or more than 8 spacers.
|-
||[[Password Generator]]
||[[User:Syntrax Canucci|Syntrax Canucci]]
||This is an over-complicated, semi-complex password generator, which goes through multiple steps.
|-
||[[Pathfinder]]
||[[User:Babbage Linden|Babbage Linden]]
||A potential field based pathfinding library.
|-
||[[Phantom Child]]
||[[User:Aeron Kohime|Aeron Kohime]]
||Causes a child in a link set to become phantom without the entire object becoming phantom.
|-
||[[PhysicsLib]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Interesting set of fun physics functions.
|-
||[[Play and Loop Sound]]
||[[User:Bellla Clarity|Bella Clarity]]
||Very short and simple script; plays and loops a sound in an object.
|-
||[[Posing stand|Posing Stand]]
||[[User:Bellla Clarity|Bella Clarity]]
||Just a pose script to edit [[attachments]] more easily.
|-
||[[PosJump]]
||[[User:Uchi Desmoulins|Uchi Desmoulins]]
||A much more efficient alternative to the popular [[warpPos]] function for bypassing 10m distance-moved limitations.
|-
||[[Prefix Calculator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
|| A calculator that evaluates expressions in prefix notation.
<code>+ 3 4 = 5. * + 1 2 + 3 4 = 14.</code>
|-
||[[Progress Bar]]
||[[User:Nexii Malthus|Nexii Malthus]]
|| Flexible and powerful little function for creating progress bars useful in hovertext.
|-
||[[Pseudo-random Number Generator]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Generates a Pseudo-random number between -0x7FFFFFFF and 0x7FFFFFFF
|-
||[[User:Rolig_Loon/Quiz_From_Notecard|Quiz From Notecard]]
||[[User:Rolig Loon|Rolig Loon]]
||A multiple-choice testing script that reads questions and answer choices from a notecard and presents them in dialog boxes.
|-
||[[Rainbow_palette]]
||[[User:Rui Clary|Rui Clary]]
||Build a color picker, using only one prim, and a few lines of code.
|-
||[[Random AV Profile Projector]]
||[[User:Debbie Trilling|Debbie Trilling]]
||Randomly selects an AV from a crowd & then projects their profile picture as a 'holographic' image
|-
||[[Random Object Vendor]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Simple vendor that gives out random objects when paid the right amount
|-
||[[Random Password Generator]]
||[[User:Jor3l Boa|Jor3l Boa]]
||Generate Random passwords based on String Length.
|-
||[[RavText]]
||[[User:Ravenous Dingo|Ravenous Dingo]]
||An alternate to XyText. This is a lightweight, multiple font 10 character text display system. It only supports uppercase alphanumeric text and a few special characters, but it is very fast, renders quickly and supports multiple fonts. It is meant for specialized use when all that is desired is basic, fast text display and the extra "bells and whistles" are not needed.
|-
||[[User:PixelProphet Lane/Scripts#Real Object Inventory To Dialog|Real Object Inventory To Dialog]]
||[[User:PixelProphet Lane|PixelProphet Lane]]
||Display any amount of items contained in an Object in a Dialog, regardless of item name length.
|-
||[[RentalBoxv1|Rental Box, Simply]]
||[[User:Sendao Goodman|Sendao Goodman]]
||Simple explanation of how to make rental boxes.
|-
||[[Rental Cube]]
||[[User:Hank Ramos|Hank Ramos]]
||Simple cube for renting out a space.
|-
||[[Remote Texture Loader]]
||{{User|Bobbyb30 Swashbuckler}}
||A set of scripts for remotely loading textures within a sim. This means that a single "texture server" can manage multiple changing billboards within a sim.
|-
||[[Say Region Frames Per Second|Region Frames Per Second]]
||[[User:Heymeriou Mystakidou|Heymariou Mystakidou]]
|| Says the region name and frames per second out loud on command.
|-
||[[sbDialog]]
||[[User:Siann_Beck|Siann Beck]]
||A simple replacement function for [[llDialog]]. It re-orders the button list so that the button values, as passed to it, display left-to-right, top-to-bottom. It also opens a [[llListen|listen]] on the specified channel, and returns the handle.
|-
||[[Scheduler]]
||[[User:Haravikk Mistral|Haravikk Mistral]]
||Schedule multiple events using a single script timer
|-
||[[Scheme_Interpreter|Scheme Interpreter]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||A scheme interpreter capable of handling most scheme expressions, including lambda and lists.
|-
||[[Script Override Functions]]
||[[User:Revolution Perenti|Revolution Perenti]]
||bypass default strings, integer etc in chat channel.
|-
||[[Scripted Attachment Detector.lsl|Scripted Attachment Detector]]
||{{User|Bobbyb30 Swashbuckler}}
||A script that will display avatars wearing scripted attatchments in hovertext. This may be worn as an hud or rezzed.
|-
||[[Self Upgrading Script Enhanced]]
||[[User:Cron Stardust|Cron Stardust]]
||Keeps only latest version of the script on prim (even with multiple adds of the same script!)
|-
||[[Sensor Visualizer]]
||[[User:Cerise Sorbet|Cerise Sorbet]]
||Shows the size and shape you get with [[llSensor]] range and arc parameters
|-
||[[Serverless Key Exchange]]
||[[User:Sendao Goodman|Sendao Goodman]]
||Maintains a network of object keys without using an external server.
|-
||[[SHA1|SHA1 Hash]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Preforms a SHA1 Hash on an input text. Similar to MD5 only (slightly) more secure.
|-
||[[Sim Map Particle Projector]]
||[[User:Jesse Barnett|Jesse Barnett]]
||Displays a floating map of the sim the script is in.
|-
||[[Sim Restart Logger]]
||[[User:Kyrah Abattoir|Kyrah Abattoir]]
||Counts region restarts and displays log of last 9 restarts together with region FPS and dilation.
|-
||[[Simple Elevator in a Box]]
||[[User:Hank Ramos|Hank Ramos]]
||Simple elevator example.
|-
||[[Skillingo AntiHack Script]]
||[[User:Tmzasz Luminos|Tmzasz Luminos]]
||A simple Protection script for skillingo thats modifyable to work with other machines.
|-
||[[Skunk Money]]
||[[User:Hank Ramos|Hank Ramos]]
||Fun gambling machine of yesteryear, which only supports freeplay now due to SL regulations against gambling.
|-
||[[SLateIt]]
||[[User:Babbage Linden|Babbage Linden]]
||An augmented virtual reality HUD.
|-
||[[SLetanque]]
||[[User:Babbage Linden|Babbage Linden]]
||An LSL petanque game.
|-
||[[SLURL HUD]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Touch this HUD to get a SLURL through IM, email and floating text.
|-
||[[SL Mail V1.2]]
||[[User:Flennan Roffo|Flennan Roffo]]
||Second Life mail client V1.2 (released sept'07). Send and receive mail from within Second Life from and to any address. With Address Book function and many chat commands. V1.3 is upcoming soon!
|-
||[[SL_NTPoHTTP_v1.1_client|SL NTPoHTTP client]]
|[[User:SignpostMarv Martin|SignpostMarv Martin]]
||Second Life Needs Time Parsing over Hyper Text Transfer Protocol
Emulates the function of [[llGetWallclock]] for any timezone by using SLOpenID's SLNTPoHTTP service. Also supports ISO 8601 and RFC 2822 timestamps. Script is dependent upon an external service operated by the author!
|-
||[[Smooth Rotating Door]]
|[[User:Toy Wylie|Toy Wylie]]
||A script for doors that open and close smoothly using llTargetOmega
|-
||[[Smooth Sliding Door]]
|[[User:SimonT Quinnell|SimonT Quinnell]]
||A script for sliding doors that open and close smoothly using [[llMoveToTarget]]. Asjusts for prim orientation.
|-
||[[Speed Tester]]
||{{User|Bobbyb30 Swashbuckler}}
||Similar to the [[Efficiency Tester]], this script allows you to test the speed of a particular function or snippet with multiple trials giving min/max/avg/median and the standard deviation.
|-
||[[Spiral Staircase Generator]]
|[[User:Meyermagic Salome|Meyermagic Salome]]
||Generates nice looking spiral staircases without much hassle.
|-
||[[Static URL's for HTTP-In Service|Static_URLs]]
||[[User:Jor3l Boa|Jor3l Boa]]
||How to generate a static url for HTTP-In temporal limitations.
|-
||[[String Compare]]
||[[User:Xaviar Czervik|Xaviar Czervik]]
||Compares two strings and reliably returns either 1, -1, or 0 if they are the same.
|-
||[[User:Void_Singer/Functions#String:_Find_Last_Index|String: Reverse]]
||[[User:Void Singer|Void Singer]]
||Returns an input string in reverse order
|-
||[[User:Void_Singer/Functions#String:_Get_Reverse_Order|String: Last Index]]
||[[User:Void Singer|Void Singer]]
||Returns the last index of search found in string (the backward equivalent of [[llSubStringIndex]])
|-
||[[Tail Messages (NewAge)]]
||[[User:Asia Snowfall|Asia Snowfall]]
||A super nice easy to use script for those non-scripters out there! NewAge coding has done it again where you no longer need to scroll up and down adding buttons and adding messages, Features a tag system (you'll see what i mean :P)
|-
||[[Teleport HUD]]
||[[User:Jesse Barnett|Jesse Barnett]]
||WORKS TO 4096 METERS!! Very user friendly teleport HUD. Add destinations by touching "Add" & naming destination in chat. Automatically gets sim name and coordinates. Will only display the destinations in the sim you are currently in. Demonstrates more advanced list manipulation and stride functions.
|-
||[[User:Void_Singer/Programs#v7-D_Enh._Landmark-2-Map|Teleporter (landmark based)]]
||[[User:Void_Singer|Void_Singer]]
||Uses Landmarks to offer map teleports. Works as Hud or inworld objects, just drop in landmarks and go.
|-
||[[Text_Scroller|Text Scroller]]
||[[User:Fred_Gandt|Fred Gandt]]
||A simple text display object that scrolls text (applied as a texture) from right to left (like ''those'' LED signs) in a continuous loop.
|-
||[[Bobbyb's texture changer|Texture Changers]]
||{{User|Bobbyb30 Swashbuckler}}
||A collection of texture changing scripts.
|-
||[[Texture Menu Management|Texture Management]]
||[[User:Revolution Perenti|Revolution Perenti]]
||Dialog Menu based Texture Selection.
|-
||[[Tic Tac Toe]]
||[[User:CG Linden|CG Linden]]
||Step by step demo on how to implement a larger scripting project
|-
||[[TightList]]
||[[User:Strife Onizuka|Revolution Perenti]]
||Tight List is a family of functions for encoding lists as strings and then decoding them back into lists.
There are two flavors: TightList and TightListType. TightListType preserves types and uses a 6 char header, while TightList uses a 1 char header that doesn't preserve type.
|-
||[[Timer Module]]
||[[User:Isabelle Aquitaine|Isabelle Aquitaine]]
||Manage multiple timers via linked messages.
|-
||[[User:Void_Singer/Functions#Unix_time_code_to_list_format|Timestamp: Unix time code to list format]]
||[[User:Void Singer|Void Singer]]
||converts Unix timestamps to their [Y, M, D, h, m, s] equivalents (ex: 1234567890 to [2009, 2, 13, 3, 31, 30])
|-
||[[User:Void_Singer/Functions#List_format_to_Unix_time_code.|Timestamp: List format to Unix time code]]
||[[User:Void Singer|Void Singer]]
||converts [Y, M, D, h, m, s] timestamps to their Unix equivalents (ex: [2009, 2, 13, 3, 31, 30] to 1234567890)
|-
||[[User:Void_Singer/Functions#Weekday_from_Unix_timestamp|Timestamp: Weekday from Unix timestamp]]
||[[User:Void Singer|Void Singer]]
||Gets weekday from Unix timestamps (ex: "Friday" from 1234567890)
|-
||[[User:Void_Singer/Functions#Weekday_from_.28_Y.2C_M.2C_D_.29_format|Timestamp: Weekday from (Y, M, D) format]]
||[[User:Void Singer|Void Singer]]
||Gets weekday from (Y, M, D) timestamps (ex: "Friday" from (2009, 2, 13))
|-
||[[Touch A Quote]]
||[[User:CodeBastard Redgrave|CodeBastard Redgrave]]
||Touch an object to read quotes sequentially from a notecard
|-
||[[Touring Balloon]]
||[[User:Hank Ramos|Hank Ramos]]
||Automated touring balloon with many options from long ago. Always seems to work on one SL release, and not the other.
|-
||[[Under Age Boot]]
|[[User:Chance Unknown|Chance Unknown]]
||Security device example to teleport home accounts below a minimum age limit; can be useful in combating free griefer accounts.
|-
||[[User:Rolig_Loon/UNDO_PosRot|UNDO_PosRot]]
||[[User:Rolig Loon|Rolig Loon]]
||Allows user to undo position and rotation changes that have been made "manually" to any or all prims in a linkset.
|-
||[[Universal Translator]]
|[[User:Hank Ramos|Hank Ramos]]
||Chat listener that handles seamless translation of public chat between 50+ written languages without the need for configuration. Handles numerous avatars, auto-detects languages, and works together with multiple copies of translators to spread-workload using a sophisticated back-end communications sub-system.
|-
||[[Unix2DateTime]]
|[[User:Flennan Roffo|Flennan Roffo]]
||Conversion from Unix time ([[llGetUnixTime]]()) to date and time string and vice versa.
|-
||[[Unmutable Descript Nagger]]
|[[User:Bobbyb30 Zohari|Bobbyb30 Zohari]]
||To nag avatars to take off their scripted attatchments.
|-
||[[Unpacker On Rez (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||A very simple to use script for all you creators out there, This script will enable you to send out boxed items and make it easier for users to unpack, Also features auto die on completion. Very simple to configure!
|-
||[[Unpacker On Touch (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||Exactly like Unpacker On Rez, But changed some things about to make it Unpack On Touch
|-
||[[UUID2Channel]]
||[[User:Project Neox|Project Neox]]
||Optimised version of the original key2channel generators.
|-
||[[UUID Song Generator]]
||{{User|Sendao Goodman}}
||Translates a UUID into a simple song and plays it.
|-
||[[VirtualID_URLMap|VirtualID URL Mapper for HTTP-in]]
|[[User:Cenji Neutra|Cenji Neutra]]
||A script showing how to setup a static URL of the form <your-alias>.obj.virtualid.info which maps to the dynamic HTTP-in URL LSL generates and keeps it up-to-date.
|-
||[[User:Void_Singer/Programs#v7-D_Advanced_Visitor_Greeter|Visitor Greeter]]
|[[User:Void_Singer|Void_Singer]]
||Reduced spam visitor greeter, highly configurable, easy to modify.
|-
||[[Visitor Logger (Web/Basic) ]]
|[[User:Buddy Sprocket|Buddy Sprocket]]
||A very basic visitor logger - log visitors in SL to a text file on your web-site.
|-
||[[Vote Simple]]
|[[User:JB_Kraft|JB Kraft]]
||Simple vote collector. One avi, one vote.
|-
||[[Walking Sound (NewAge)]]
|[[User:Asia Snowfall|Asia Snowfall]]
||Very powerful walking sound script, Featuring customer ability to add their own sounds with the API Sound Feature!
|-
||[[WarpPos]]
|[[User:Keknehv Psaltery|Keknehv Psaltery]]
||Non-physical movement without the 10m limit.
|-
||[[Wiki3DBuilder]] [[Wiki3DBuilder1.0]]
||[[User:Salahzar Stenvaag|Salahzar Stenvaag]]
||Allows a group of people to collectively build up complex 3D mindmaps with connected concepts. Uses particles for connections and low prim usage. Nodes can be textured, colored, changed form size moved collectively by everybody and can distribute notecards, landmarks, URL, objects, textures. I provide two version 0.1 and 1.0 and probably next version will communicate with moodle and sloodle external websites.
|-
||[[Window Control]]
||[[User:Emmas Seetan|Emmas Seetan]]
||For window opacity, helpful for buildings.
|-
||[[WHMcs SecondLife plugin]]
|[[User:Alicia Sautereau|Alicia Sautereau]]
||Linden Dollar payment plugin for the WHMcs hosting portal.
|-
||[[XTEA Strong Encryption Implementation]]
||[[User:Morse Dillon|Morse Dillon]]
||An LSL implementation of XTEA (eXtended Tiny Encryption Algorithm). This is the first known public release of a 'real' strong encryption implementation in LSL and is released under the GNU General Public License (GPL).
|-
||[[XyText 1.5|XyText]]
||[[User:Xylor Baysklef|Xylor Baysklef]]
|| Display text (up to 10 characters) on a prim. Use as many prims as desired.
|-
||[[XyyyyzText|XyyyyzText]]
||[[User:Criz Collins|Criz Collins]]
|| Display text (up to 10 characters) on a prim. Displays different text for each line instead of one single text, that will be broken into the next lines. Watch here for what that means: http://screencast.com/t/1wMLujLcEO
|-
||[[XyzzyText|XyzzyText]]
||[[User:Thraxis Epsilon|Thraxis Epsilon]] and [[User:Gigs Taggart|Gigs Taggart]]
|| Display text (up to 10 characters) on a prim. Way more efficient than XyText.
|-
||[[Youtube TV]]
||[[User:Morgam Biedermann|Morgam Biedermann]]
||Watch your favorite Youtube videos / auto set the texture to the parcel media texture.
|-
||[[Zero Lag Poseball]]
||[[User:Jippen Faddoul|Jippen Faddoul]] and [[User:Daemonika Nightfire|Daemonika Nightfire]]
||A simple poseball with no lag
|}

</div>
<div id="box">

==Support Script Library==
These are scripts in other languages, intended to be run on other systems that support scripts written in LSL

{| class="sortable" {{Prettytable}}
|- {{Hl2}}
! '''Name'''
! '''Creator'''
! '''Description'''
|-
|| [[User:Ina Centaur/UUID/calimg.api|Calendar Image UUID API]]
|| [[User:Ina Centaur|Ina Centaur]]
|| API that gives the UUID of an image of a calendar image give month and year arguments.
|-
||[[HTTP Post request to a PHP server]]
||[[User:Corto Maltese|Corto Maltese]]
|| This small library allows you to make simple POST requests to your website. The libraries allow you to get your request through the variable $_POST on the server. It also include a basic security mechanism aimed to stop hacking. Comprises of LSL client script and PHP server script.
|-
|| [[User:Ina Centaur/PHP/k2n.php|Key2Name.php]]
|| [[User:Ina Centaur|Ina Centaur]]
|| Get Avatar's Name using Second Life search service. (like in LSL Key2Name)
|-
|| [[Lame_Object_DNS_and_Cross_Sim_Messaging|Lame Object DNS and Cross Sim Messaging]]
|| [[User:Liandra Ceawlin|Liandra Ceawlin]]
|| Simple, cheeseball method of doing cross-sim communications with http-in and an external object DNS service.
|-
|| [[User:SignpostMarv Martin/PHP/llXorBase64StringsCorrect|llXorBase64StringsCorrect]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| An implementation of [[llXorBase64StringsCorrect]] in PHP- should be useful if you're using llXorBase64StringsCorrect to do cryptography work in LSL2 and posting it out to the web via [[llHTTPRequest]].
|-
|| [[User:SignpostMarv Martin/PHP/lsl fu.php|lsl_fu.php]]
|| [[User:SignpostMarv Martin|SignpostMarv Martin]]
|| A basic OOP'd PHP Class containing VeloxSeverine's $_POST fixer and Marv's own eccentric ideas for "fixing" things.
|-
|| [[User:Jor3l Boa/PHP/n2k.php|Name2Key.php]]
|| [[User:Jor3l Boa|Jor3l Boa]]
|| Get Avatar's UUID using Second Life search service. (like in LSL Name2Key)
|-
|| [[Public_Object_DNS|Public Object DNS]]
|| [[User:Liandra Ceawlin|Liandra Ceawlin]]
|| Public object DNS-like system running on GAE, for http-in. Hopefully scalable enough for wide-spread usage.
|-
|| Silo
|| [[User:Zero_Linden|Zero Linden]]
|| General purpose data store in PHP. Use this to persist arbitrary data from LSL via [[llHTTPRequest]]. See:
* [http://www.notabene-sl.com/misc/silo-README.txt README] file
* [http://www.notabene-sl.com/misc/silo.tgz silo.tgz] tarball
* forum post [http://forums-archive.secondlife.com/54/69/119570/1.html Announcement].
|-
||[[Silverday ObjectDNS]]
||[[User:Till Stirling|Till Stirling]]
||Dynamic Object-DNS-System to provide dynamic mapping of LSL-URLs to persistent domains. Features include redirect service, password protected domains, write protected domains, LSL-API for all necessary functions, optional web-interface.
|-
|| [http://aubretec.com/products/sldb SLDB]
|| [[User:Luc Aubret|Luc Aubret]]
|| Flexible web database storage using PHP/MySQL. Used to store per-user field/value pairs from in-world objects using [[llHTTPRequest]].
* [http://aubretec.com/support/manuals/sldbkit/ Implementation Guide]
* [http://aubretec.com/wp-content/uploads/2009/05/sldb.zip Download] (.zip, 12kb)
|}

== See Also ==
<div style="padding: 0.5em">
'''Articles'''
*[[:Category:LSL Examples| Examples]]

</div></div>

{{LSLC|}}

Camera following prim

2010-08-22T20:01:39Z

Dale Innis: Initial creation of page

{{LSL Header}}

= Introduction =

A reasonably simple demo of a prim that follows your camera around (as long as you are wearing the special attachment that makes it work). This was inspired by a request for a light that would follow the camera around, but can be used for all sorts of other things as well. Presumably.

= Usage =

To use these scripts, stick the CameraMaster script into the root prim of an object, and wear that object. (Anywhere on the body; wearing it as a HUD attachment hasn't been tested.) Then stick the CameraFollowerPrim script into the prim that you want to follow your camera around (it should be a non-physical prim; phantom is probably also a good idea). As you move your camera around (alt-click and so forth, you know), the prim will follow the camera-point around (which can, for obvious reasons, make it hard to see the prim!).

= Limitations and Notes =

The prim that moves will move rather jerkily, but very fast. Smoother (but generally slower) motion could be gotten by making the moving prim physical, and using llMoveToTarget rather than llSetPos. If you prefer smoother motion for some reason. I haven't tried that variation, but it ought to be relatively simple.

You can change the channel that the scripts use to communicate, and the frequency with which it updates the prim's position, by altering the obvious constants in the code. You can also make the moving prim go to some offset from the camera position, rather than right on the camera position itself (a meter above it, say) by changing OFFSET in the follower script (to, say, <0,0,1>).

To make the prim stop following your camera, detach the attachment.

= The Code =

You may do anything you like with this code, without limitation. As far as I'm concerned. As long as it's not anything mean. You shouldn't be mean.

The CameraMaster (for the attachment):

<lsl>
// Put this in an attachment and it will continuously broadcast your camera position

float DELAY = 0.5;
integer CHANNEL = -85847;

default
{
state_entry() {
// Nothing to do here really.
}

on_rez(integer n) {
// Nor here. I just put these in out of habit.
}

attach(key id) {
if (id != NULL_KEY) {
llRequestPermissions(id,PERMISSION_TRACK_CAMERA);
} else {
llSetTimerEvent(0.0);
}
}

run_time_permissions(integer p) {
llSetTimerEvent(DELAY);
}

timer() {
llShout(CHANNEL,(string)llGetCameraPos());
}

}
</lsl>

The follower, for the moving prim:

<lsl>
// Put this in a non-physical prim, and it will move to (an offset from) places that it hears about.

integer CHANNEL = -85847;
vector OFFSET = ZERO_VECTOR;

integer lh;

init() {
llListenRemove(lh);
lh = llListen(channel,"","","");
}

goto(vector dest) {
/// One could use WarpPos or whatever here as well
while ( llVecDist(llGetPos(),dest) > 0.1 ) {
llSetPos(dest);
}
}

default
{
state_entry() {
init();
}

on_rez(integer n) {
llResetScript();
}

changed(integer c) {
if (c & CHANGED_OWNER) {
llResetScript();
}
}

listen(integer c, string n, key id, string msg) {
if ( llGetOwner() != llGetOwnerKey(id) ) return;
vector v = OFFSET + (vector)msg;
goto(v);
}

}
</lsl>

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

Talk:Display names/FAQ

2010-08-18T19:20:09Z

Dale Innis: /* "Their scripts" */ new section

== The part about existing scripts can't be right... ==

This part can't be right:

"Will Display Names affect scripts I have created or bought?
No. Your username in Second Life will automatically change to your current Second Life name, lowercase, with a period between your first and last name (for example, "John Smith"'s username becomes "john.smith"). "

If every existing call that returned "firstname lastname" now returns "firstname.lastname", then thousands of scripts will break. For instance, any script that reads a list of authorized users from a notecard, and compares the result of llDetectedName() to see if it's on the list.

I assume that the actual story is that all of the existing LSL functions that deal with names will still deal with the "firstname lastname" form (even if, internally to the server, they're actually stored as "firstname.lastname").

This section should be revised accordingly.

*update*: Kelly Linden has clarified the plan in a few posts on the opensource and/or scripters lists: as well as the "whatever you want" display name and the "first.last" user name, there is also a "First Last" form, which is apparently called the full name. And existing LSL functions that deal with names will all deal with full names. So nothing should break.

[[User:Dale Innis|Dale Innis]] 01:16, 18 August 2010 (UTC)

I agree...I really hope what the FAQ actually says isn't what actually happens in regard to what existing avatar name calls will do.

* I'M GLAD YOU BROUGHT THIS UP. I've edited the section and linked to Kelly's post. THANK YOU. {{TorSig}} on 2010-08-18 @ 5:59 AM Pacific

== "Their scripts" ==

While we're on the subject :) , the phrase "Any of their scripts" can't be right either. It suggests that somehow the behavior differs based on who owns the script, and that's surely not the intent. [[User:Dale Innis|Dale Innis]] 19:20, 18 August 2010 (UTC)

Talk:Display names/FAQ

2010-08-18T04:03:16Z

Dale Innis: /* The part about existing scripts can't be right... */

Talk:Display names/FAQ

2010-08-18T01:16:20Z

Dale Innis: The part about existing scripts can't be right...

Talk:LlEmail

2010-08-04T18:41:15Z

Dale Innis: /* What if the target region is down? */ new section

I suggest removing the text at the end (starting with "Feature Design Document")

-- Catherine Pfeffer (2008-05-03)

It's note-worthy to add that the following line of code can be used in the email event to remove headers from the message.

message = llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1);

Example:

default
{
state_entry()
{
email(string time, string address, string subj, string message, integer num_left)
{
message = llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1);
llSay(0,message);
}
}
}

Originally added by [http://www.lslwiki.org/index.php?title=PrioSerpentine&action=edit Prio] @ http://www.lslwiki.org/index.php/LlEmail

--[[User:Lucius Obviate|Lucius Obviate]] 05:35, 20 May 2007 (PDT)

== What if the target region is down? ==

This page should probably say what happens if the target region is down.

If anyone knows, that is. :) [[User:Dale Innis|Dale Innis]] 18:41, 4 August 2010 (UTC)

Talk:LlRezObject

2010-05-03T15:33:36Z

Dale Innis: /* How far away can an object be rezzed? */ agreed agreed :)

can someone write some words about that integer param, the last parameter?
maybe the one who wrote the function!
:Yes, I'm adding more to the function description now. Including an example. [[User:Xaviar Czervik|Xaviar Czervik]] 18:58, 28 October 2007 (PDT)

== Delay? ==

Is the delay actually mass-based, or is it 0.1 seconds? The article currently says both... [[User:Dale Innis|Dale Innis]] 12:10, 1 November 2007 (PDT)

:Both, the function has a default delay of 0.1 seconds (it's part of how the function is plugged into the VM), but there is an additional mass based delay. -- [[User:Strife Onizuka|Strife Onizuka]] 13:42, 1 November 2007 (PDT)

== How far away can an object be rezzed? ==

I could spend some time testing it, but was hoping someone already did that. :) [[User:Lana Straulino|Lana Straulino]] 20:52, 29 April 2010 (UTC)

:This is just a guess plus a little experience with trying to rez at distance from the rezzer....I think the maximum distance '''may''' be variable and tied to the [[Linkability_Rules|linkability rules]]. It would make more sense than the maximum distance being (my memory fails me) ''about'' 18.5 meters, which was ''roughly'' the maximum I have managed in the past. Testing and posting the results would be of value if my guess doesn't help. -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 22:26, 29 April 2010 (UTC)

::Actually: See [[LlRezObject#Caveats|llRezObject Caveats]]. Apparently a maximum distance of 10 meters from the rezzer (center of the prim containing the script calling this function) is the limit. I'm sure I broke that though. I may end up testing it myself. -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 22:36, 29 April 2010 (UTC)

As I thought. The caveat is wrong. It also turns out my memory isn't so bad as I thought. Also...A difference in maximum distance is seen depending on the size of the object doing the rezzing.
*A 10 meter cube can rez up to 18.660279 meters away.
*A 0.01 cube can rez up to 10.008666 meters away.
Tested using a cube as the rezzer and rezzee. The rezzee size seemed to make no difference (this was a simple test).
<lsl>vector pos;

default
{
state_entry()
{
pos = llGetPos();
}
touch_start(integer nd)
{
llRezObject("Object", (pos + <0.0,0.0,10.008666>), <0.0,0.0,0.0>, <0.0,0.0,0.0,1.0>, 0);
}
}</lsl>
Any testing beyond this would bore me to tears so, good luck! Hope it helps. -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 23:18, 29 April 2010 (UTC)

:omg! Thanks you Fred! And believe it or not, that sort of work changes entire designs. [[User:Lana Straulino|Lana Straulino]] 03:22, 30 April 2010 (UTC)

I'm a little concerned by the idea of just casually replacing the original 10m-limit statement with the results of some experiments. My impression has been that what's officially supported is a 10m area, and anything beyond that that any particular version of the server software happens to support should be regarded with suspicion. That's one of the problems with a Wiki :) in that it's hard to distinguish the Official Contract of the function from stuff that people have discovered and posted on the page. Personally I wouldn't write any code (or at least no code that I was planning to support someone else's use of) that depended upon being able to rez an object more than 10m away; I can easily imagine the 10m limit becoming strict in some server update, and any bug reports against that being closed Working As Designed. Of course ymmv... [[User:Dale Innis|Dale Innis]] 14:07, 3 May 2010 (UTC)

:Agreed Dale. However, I first discovered the approx 18.5 meter range quite a few servers ago. 1.24? (I really can't say, about 18 months ago ish) The fact that I took the time to study the results on more than one occasion and on far removed server updates does lend my results some validity. You are of course right though. If 10.0 meters is what it ''should'' be, we should mention it. :-) -- '''[[User:Fred_Gandt|Fred Gandt]]''' ([[User talk:Fred_Gandt|talk]]|[[Special:Contributions/Fred_Gandt|contribs]]) 14:40, 3 May 2010 (UTC)

::Yeah would probably be good to confirm with a Linden as to what the actual supported use is, and write that down. I updated the text slightly to note 10m as the "official" limit, although I admit I can't point to specific proof of that! :) If you know which server versions your results apply to, that might be good to document as well, in case it ever becomes an issue... [[User:Dale Innis|Dale Innis]] 15:33, 3 May 2010 (UTC)

LlRezObject

2010-05-03T14:09:49Z

Dale Innis: Clarify official vs. observed distance limits

{{Issues/SVC-3145}}{{LSL_Function/inventory|inventory|uuid=false|type=object}}
{{LSL_Function
|func_id=104|func_sleep=0.1|func_energy=200.0
|func=llRezObject|sort=RezObject
|p1_type=string|p1_name=inventory
|p2_type=vector|p2_name=pos|p2_desc=position (in [[Viewer coordinate frames#Region|region coordinates]])|p2_hover=position (in region coordinates)
|p3_type=vector|p3_name=vel|p3_desc=velocity (max [[llVecMag|magnitude]] is 250)
|p4_type=rotation|p4_name=rot|p4_desc=rotation
|p5_type=integer|p5_name=param|p5_desc=[[on_rez]] event parameter and value returned by [[llGetStartParameter]] in the rezzed object (or by each of the items in a coalesced object).|p5_hover=on_rez event parameter and value returned by llGetStartParameter in the rezzed object.
|func_footnote=The root of '''inventory''' is not at '''pos''' but the [[llGetGeometricCenter|center]] of '''inventory''' is. To have the root prim at '''pos''' use [[llRezAtRoot]] instead.
|func_desc=Instantiate '''inventory''' object at '''pos''' with velocity '''vel''' and rotation '''rot''' with start parameter '''param'''
|return_text
|spec
|caveats=
*In addition to the normal function delay, there is an additional delay based on the mass and velocity of the object rezzed.
**<code>rez_delay = mass * llVecMag(velocity) / 10;</code> [http://forums.secondlife.com/showthread.php?t=82659]
*Silently fails to rez '''inventory''' if '''pos''' is too far from the prim trying to rez '''inventory'''.
**So if your script is mysteriously failing to rez things, make sure you haven't (say) written "<0.0,0.0,1.0>" for the '''pos''' parameter rather than (say) "llGetPos() + <0.0,0.0,1.0>".
**The documented limit is 10 meters; however in at least some server versions experimentation reveals a larger limit that seems to be related to the size of the object doing the rezzing:
**A 10 meter cube can rez up to approx 18.6 meters away.
**A 0.01 cube can rez up to approx 10.0 meters away.
***Even if the attempted rez succeeds, the rezzed object may not be exactly at the position you ordered. Accuracy of the final position reduces the closer your ordered '''pos''' is to the maximum that would succeed.
* When scripting attachments meant to rez objects, remember that attachments move. You will need to use <code>llGetPos()</code> and add it to '''pos''' to obtain a faithful position for your rezzed object. When used in the root of an (attached) attachment <code>llGetPos</code> doesn't return the position of the attachment but instead returns the position of the avatar's bounding box geometric center. Read [[llGetPos]] and [[llParticleSystem#Caveats]] for more information.
* If the owner of the object does not have copy permission on '''inventory''', the object will no longer be present in inventory after it is rezzed (so another attempt to rez it is likely to fail); if the owner does have copy permission, then a copy is rezzed, and the original '''inventory''' remains in inventory.
*Silently fails if you don't have offline building rights on the land.
**Which means that you need to either:
**#Own the land yourself.
**#Be in the group that owns it, the allow group to build parcel flag has to be enabled and the object has to be set to group.
**#Or everyone should be allowed to build.
**#You can also deed the object to the group that owns the land, this will always work.
**The group role "Always allow 'Create Objects'" will only work to override this when you are online. See [[#SVC-3145|SVC-3145]] in the Issues subsection of Deep Notes for more information.
|constants
|examples=<lsl>default
{
touch_start(integer param)
{
llRezObject("Object", llGetPos() + <0.0,0.0,1.0>, <0.0,0.0,0.0>, <0.0,0.0,0.0,1.0>, 0);
}
}</lsl>
<lsl>// Rez an object on touch, with relative position, rotation, and velocity all described in the rezzing prim's coordinate system.
string object = "Object"; // Name of object in inventory
vector relativePosOffset = <2.0, 0.0, 1.0>; // "Forward" and a little "above" this prim
vector relativeVel = <1.0, 0.0, 0.0>; // Traveling in this prim's "forward" direction at 1m/s
rotation relativeRot = <0.707107, 0.0, 0.0, 0.707107>; // Rotated 90 degrees on the x-axis compared to this prim
integer startParam = 10;

default
{
touch_start(integer a)
{
vector myPos = llGetPos();
rotation myRot = llGetRot();

vector rezPos = myPos+relativePosOffset*myRot;
vector rezVel = relativeVel*myRot;
rotation rezRot = relativeRot*myRot;

llRezObject(object, rezPos, rezVel, rezRot, startParam);
}
}</lsl>
|helpers
|also_constants=
{{LSL DefineRow||[[PRIM_TEMP_ON_REZ]]|}}
|also_functions=
{{LSL DefineRow||[[llRezAtRoot]]|Rezzes the object at the requested position}}
{{LSL DefineRow||[[llGetStartParameter]]|}}
{{LSL DefineRow||[[llGodLikeRezObject]]|}}
|also_tests
|also_events=
{{LSL DefineRow||[[object_rez]]|triggered when this object rezzes an object from inventory}}
|also_articles
|notes
|permission
|inventory
|negative_index
|cat1=Rez
|cat2=Object
|cat3=Inventory
|cat4
}}

Talk:LlRezObject

2010-05-03T14:07:16Z

Dale Innis: /* How far away can an object be rezzed? */ worries about > 10m

Talk:Channel and Version Requirements

2010-04-29T16:38:19Z

Dale Innis: /* Instructions for from-scratch viewers? */ new section

Talk:Landmarks and Navigation Project

2009-11-09T14:55:03Z

Dale Innis: /* Landmarks Certainly Aren't Perfect As They Stand */ True; maybe we need a suggestions page?

'''Del.icio.us for SL'''

Why start with a outdated bookmark model that doesn't scale properly after many years of use. Most people that I know have so many bookmarks in their browser that they stopped using them. Wouldn't it be better to just start with a tagging model at the heart of this, instead of shoving that of as some future feature?

Tags make searching for land/book marks much easier, specifically when you made them long ago and don't remember the exact name of the place, but do know it was a shop that sold red shoes and umbrellas. And lets remember bookmarks are used for storing place you wish to '''find''' on a later date, shouldn't you use the best system that helps people find things?

I don't know (yet) if there is any opensource bookmark tagging software, but I really think that should be looked into. That way most of the development can be offloaded to web devs, and api's could be created for people to create plugins for social networking sites, blogs, etc.

You could also opt to use del.icio.us as the place where landmarks are saved, but that would make us depended on their service, which doesn't have to be a bad thing. Or see if LL can buy a license of their software and neatly hook it up with Second Life. (Or any other bookmark tagging service can be used)

[[User:Frans Charming|Frans]] 10:50, 23 April 2008 (PDT)

1. Move landmarks out of inventory? No! Landmarks as inventory items that can be passed around is a powerful metaphor.

2. Deprecate picks? Picks are my "home page" (no, I'm not going to put a web home page in my profile ... or use anyone else's ... not until LL provides hosting for it).

3. Extend web search further into SL? Not to replace landmarks, see #1.

4. The #1 thing I want is to be able to limit what landmarks show up in the map landmarks pulldown to the ones in my Landmarks folder, so it doesn't get cluttered up with dozens of duplicate "hi, you bought something at my shop, now I get to spam your map" landmarks.

[[User:Argent Stonecutter|Argent Stonecutter]] 04:46, 20 May 2008 (PDT)

== Landmarks: "Tradeable assets" ==

If landmarks are moved out of the inventory altogether (I'm a bit undecided about it; in-world, I tend to pass SLURLs more frequently, since it's far easier to open the map, create a SLURL, and copy & paste it to someone who's waiting for it in IM — to do the same for landmarks would require me to drop everything I'm doing, teleport to the destination, create a landmark, and come back), can we have a ''simple'' way of passing them as assets somehow?

They might work like the del.icio.us suggestion above, of course: a way for residents to exchange SLURLs and have them stored "somewhere" (many of us use SL on different locations with different hardware and it's nice to know that landmarks are currently persistent — stored on the grid), and easily loaded back into the client when needed. Sort of like what .Mac does for Safari, Foxmarks for FireFox, or, well, del.icio.us for pretty much any browser.

[[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] 07:55, 30 May 2008 (PDT)

Gwyn your own personal use case is never a reason to bork the entire world. There are 1.5 million people here, many of whom don't even know what a SLURL is or can't make or use them but who can handle landmarks. In my experience, people have trouble with the Google-like search much much more than landmarks, and rely on landmarks as a very easy means of travel. You're talking about real-time communications and forgetting how to handle asynchronous communications that are at the heart of the SL experience given the diversity of time zones and countries, enabling people to view sites and interact with each other and trade experience outside of real-time contact.

The issue isn't the "how" of how they are passed as assets; it's assuring that they *will* remain discrete, concrete assets containable and sortable *in both prims and inventory and not just browser boxes*.

[[User:Prokofy Neva|Prokofy]] 6 November 2009

I agree that landmarks as a tradeble assests would be prefered, perhaps the inventory item could be a just a pointer to the landmark in the new landmark system.

[[User:Frans Charming|Frans]] 11:56, 31 May 2008 (PDT)

== Landmarks & Navigation Project suggestion: Mozilla Weave ==

Rather than duplicating the body of the message here, I'm merely pasting the link to the mailing list post: https://lists.secondlife.com/pipermail/sldev/2008-August/011304.html
 [[User:SignpostMarv Martin|SignpostMarv Martin]] 08:17, 10 August 2008 (PDT)

== Removing Landmarks as Shareable Objects Destroys Socialability and Commerce ==

This concept of removing landmarks as objects in the inventory -- and in fact removing them as objects in the world -- is all wrong.

Would you *please* stop trying to make this interactive 3-D virtual world "like a web page browser"? It's *not a web page*. It's a *world*.

You will really destroy commerce models already thriving inworld if you remove landmarks as an object that can be put in prims. Every single business in SL uses landmark giver objects onsite or in ads or gives people landmarks as part of their advertising. And that's all good.

The idea that you "can't find or use" the landmarks in inventory is false. Of course you can find them. You use "search inventory" with the name of the store or sim and the landmark is found in the search.

People constantly hand each other landmarks to interesting places precisely because there isn't enough space on the Picks. By putting these "bookmarking" functions into a browser, you remove the sharability. How will I share my landmarks if I can't push them as inventory to other people, individually?!

Again, SL is *not a web page*. It's a 3-D interactive social world that has objects in it that people share and move. Landmarks are one of them. They are sharable sortable objects and inventory access them just fine now.

It's noted in the design description that removing landmarks from the data base will be some kind of "save" for the dbase. Is that what this is all about? It doesn't seem warranted if it kills of interactivity and commerce, exchanging that robustness of socialibility and economic life for a static solo-user's experience of his own bookmarks.

--[[User:Prokofy Neva|Prokofy Neva]] 21:20, 29 September 2008 (PDT)

Uh-oh. The Lindens are back to removing landmarks again as inventoriable user-made shareable content. They want to have "the world like the web" and have instant browser-based transport with one-click travel, they appear to be getting rid of landmarks again. M Linden has indicated this in an interview today in massively.com and confirmed it with me when I asked him inworld, and said that browser-based travel would be happening but said there would still be tradeable links. How??? By cut and paste?! The landmark as an object for asynchronous travel outside of browsers but inworld in clickable objects are absolutely vital to commerce and socializing. There is absolutely no reason for this, and if they are fussing about database calls, the Lindens could police through the G-term more of the automatic spam landmark-givers all over now, that are causing clutter in inventories and accidental and excessive use of landmarks, if that is the issue.

A SLURL is not something that can be manipulated with scripts in the same way -- it would mean pasting manually into notecards and I'm not sure a randomizer or serialer script to deliver SLURLs exists or could be made. Currently such scripts have been made to deliver landmarks randomly or in serial fashion.

I have three such objects that all function with a combination of the portal script that pulls up the map with a landmark, and serializer and randomizer scripts. I'll leave aside the hundreds of hours I've spent for years creating and updating these links for travel and socializing in SL to help both newbies and oldbies, and the work that tens of thousands of merchants have done to put landmarks inside stores, rental offices, products, etc. etc. If all those landmarks in world are suddenly deprecated because of a browser solution, it leaves the world deaf, dumb, and blind utterly dependent only on closed friendship networks or groups to deliver links rather than open mechanisms of serendipity, free travel, asynchronous contacts at sites, etc.

--[[User Prokofy Neva|Prokofy Neva]] 6 November 2009

== Do Not Destroy User Generated Content ==

My mind absolutely boggles at the thought that you would want to get rid of User Picks.

This is *resident content*. *You do not get to destroy resident content*.

Deprecate picks? In favour of landmarks that will be shareable somehow? (when you're going to remove them out of the inventory? and have them shareable as...what exactly? how? off a browser? all of them at once?)

Why? People go to enormous trouble to make their Picks. It's the heart of their identity. I know as a landlord in SL that people record all kinds of special moments as well as places they like on their picks. The picks are *not just places*. The picks are a *story*. The picks have things like descriptions of your best friends. Or your business policies. Or information about using your product.

Could you people *look at how these things are actually used inworld* before you set about destroying them?!

There's no objective need to remove a page off the avatar, used to put his best selection of picks/story pages he wants to tell about his Second Life, in favour of some giant grab bug of landmarks, that does not tell that narrative.

Can you grasp that Picks are not just bookmarked spots, but *a story*? Can you please see this narrative on thousands of people and not tamper with it?!

I fail to see why your need to tinker with the viewer involves destroying what is already established *as user-generated content*. Try to remember that's what it is: *user-generated content*. Linden Lab should not be in the business of "deprecating" *user-generated content* under the guise of "new easier-to-use features".

--[[User:Prokofy Neva|Prokofy Neva]] 21:31, 29 September 2008 (PDT)

== Corrected some errors ==

I've corrected some errors in the (former) "Should we move Landmarks out of inventory?" section (including renaming it); it seems to have been originally written without an accurate knowledge of how landmarks currently work. In particular, Landmarks are not all in one huge list in inventory (this is true only of Landmarks that the user has made himself, and has not moved into other folders), although they are on the currently-useless Map "Landmarks" pulldown, and the names of Landmarks are not useless (they contain the region and parcel name, which is often exactly the right thing). The current inventory provides a powerful way (folders) to sort and organize landmarks, and this was not reflected in the existing "Food for Thought". This being a Wiki, I assume this sort of improvement is okay. :) -- [[User:Dale Innis|Dale Innis]] 06:54, 30 September 2008 (PDT)

== Restated idea about Picks ==

Residents love Picks; talking about "deprecating" them will just anger people (with good reason). What's really being talked about here is better linking Picks and Landmarks. So I've reworded (and renamed) that section to reflect that. -- [[User:Dale Innis|Dale Innis]] 07:27, 30 September 2008 (PDT)

== Fiddled with "Should we extend Web-type search further into SL? How, and how far?" some too ==

Just to correct more errors (Landmarks aren't rezzable) and to add a few more obvious thoughts. I'm somewhat concerned that the ideas represented here are some Web-Browser-derived preconceived notions, not very well informed by SL history and Resi expectations. I hope my edits have helped with this somewhat. -- [[User:Dale Innis|Dale Innis]] 07:27, 30 September 2008 (PDT)

== "To create a new navigation panel" should not be a project goal ==

New navigation panels, as fun as I'm sure they are to create, are not good in themselves. A new navigation panel should be created only if it actually makes the user experience better. -- [[User:Dale Innis|Dale Innis]] 07:34, 30 September 2008 (PDT)

== Relevant JIRA ==

There doesn't seem to be any linkage in this wiki discussion (or article) to the very relevant [http://jira.secondlife.com/browse/VWR-7900 VWR-7900] issue in the public SL jira. (This was formerly NAV-28.) This shows the outside developer's user interface, though there doesn't seem to be a lot of information about implementation under the covers. :: [[User:Latransa Pera|Latransa Pera]] 11:14, 30 September 2008 (PDT)

''I stuck in a link in the obvious place.'' -- [[User:Dale Innis|Dale Innis]] 11:46, 30 September 2008 (PDT)

== Regressed my change to "Food for Thought" ==

Since someone in a comment on Prokofy's weblog pointed out that there's a June mailinglist posting that obsoletes the entire "Food for Thought" section, this page is apparently not intended as a working document, so I've regressed it to how it used to look, and just added a note and pointers to that mailinglist posting. I think it would be great if someone on the Vectorform team or in LL, or some Resident who's following the relevant mailinglist(s), would keep this page up to date so those of us not as centrally involved could keep up, but I'm not signing up to do that myself! --[[User:Dale Innis|Dale Innis]] 07:24, 1 October 2008 (PDT)

== Landmarks, affinities, suggestions, and been there done that ==

A pointer to
[https://lists.secondlife.com/pipermail/sl-ux/2008-October/000127.html my post to SL-UX] that describes an idea for providing suggestions for places for residents to
visit similar to the "customers who bought this also bought..." systems
found on commercial web sites.

--[[User:Mm Alder|Mm Alder]] 16:35, 9 October 2008 (PDT)

== Landmarks Certainly Aren't Perfect As They Stand ==

Frankly, they're a pain in a lot of ways.

Redundant landmarks accumulate--I wouldn't mind at all if the client told me "You already have a landmark with coordinates within X meters of there--do you REALLY want to clutter your inventory?"

Landmarks become obsolete. You save a landmark because of what's there--if it moves, the landmark is useless. I'd like something that isn't a landmark but a pointer to a landmark. Vendors could hand out these new landmarks and then take the responsibility of updating the underlying landmark if the store/night club/etc. moves, rather than having untold numbers of landmarks suddenly become useless clutter. I wish I had L$1 for every time I looked at someone's picks, thought "gee, that sounds neat--I think I'll go there", clicked, and found myself falling into the sea, or at some store/building/etc. obviously _not_ the one described in the pick. (And if Picks are so darned important, why don't people update them?)

[[User:Melissa Yeuxdoux|Melissa Yeuxdoux]] 13:23, 9 November 2009 (UTC)

Those are true, and I think good suggestions for improvement. On the other hand I think it's important to avoid giving the impression that "Residents don't like landmarks", which someone who doesn't really understand the world (like the author of the original "food for thought" at the time it was written) could cite as a reason for replacing them with something even worse. 'cause that would be bad. :) Maybe someone could start (if there isn't one already) a "Improvement suggestions for landmarks" page in the Wiki. This "Landmarks and Navigation Project" page looks moribund to me; I suspect the "Project" doesn't actually exist anymore, given the lack of Lab activity on this page over the last year.

Just a thought... [[User:Dale Innis|Dale Innis]] 14:55, 9 November 2009 (UTC)

Protecting content in an open grid

2009-11-08T03:15:07Z

Dale Innis: /* Thought on DRM */ put my words back where they belong

[[Image:slarch.jpg]]

==Protecting content in an open grid==

Starting in September of 2007, there has been discussion on the
[https://wiki.secondlife.com/w/index.php?title=DRM%2C_IP_and_permissions#Discussion_on_the_mailing_list sldev mailing list] about how to protect content (objects, textures, scripts) in a future open grid (that is, a large grid that is an interconnection of grids operated by different companies, organizations, and individuals).

Basically we face the following challenges:

* content creators want the ability to specify rules about how the content they make available can be used; for example,
** "you can modify and transfer (give away or sell) what you got from me, but you can't make copies of it"
** "you can modify and copy but not transfer what you got from me (for money or for free)"
** "you can modify, copy, and transfer but not sell what you got from me"
** "you can do whatever you want with what you got from me"
** "you can take what you got from me with you to all grids that are trusted by Linden Labs"
** "you can modify this object but only to repair it to work in future simulator software, or to create a derivative work for sale to citizens of Portugal" (this example serves to illustrate how complex real licenses can be)
* content is basically just a series of bits; that is, a sequence of 0s and 1s. as such it is copyable. any SL client will by necessity have a copy of the visual part of content (including sound) as it has to render the content to the user
** with an open source viewer/client you can always copy the visual part of content (absent hardware features that aren't currently in place and seem unlikely, such as a shared secret between the server and the video card)
** scripts are (currently at least) running on the grid servers and can be protected that way (i.e., the server does not hand over the script to the client if the permissions do not allow this): in an open grid we will have grid servers that are not under the control of LL (that is the whole purpose of the open grid) and thus a grid server could very well provide copies of scripts to anyone in control of it.

So, basically the challenge is that content providers want to specify rules for the content they create and at the same time with an open grid and with open source SL clients we cannot ''guarantee'' those rules. This is not necessarily fatal; an economy can work even when theft is possible. But it is a fundamental limitation to what we can do with technical solutions.

==Linden Lab statement on content protection in interop==

On 8 July 2008, a [http://blog.secondlife.com/2008/07/08/ibm-linden-lab-interoperability-announcement/ posting in the Second Life weblog] entitled "IBM and Linden Lab Interoperability Announcement" included the following text:

Q: How will Linden Lab prevent property from being copied into other virtual worlds?

We’re paying extremely close attention to that question. We will be designing this with the Second Life community to ensure their needs are met. We want to stress that when it does become possible to move avatars between worlds, we will take the utmost care to protect the rights of Second Life property owners and creators. Linden Lab will not design a system that lets people openly violate the permissions of SL goods and take them to other worlds. We recognize that intellectual property is the engine that drives Second Life, and we are completely committed to preserving the qualities that make Second Life the unique, innovative and dynamic place that it is today.

==DRM?==

The challenge we face is the same as faced by digital content providers in the real world; for example, MP3 music outlets. The temptation is to try and go the same route that has been tried by those RL content providers: [http://en.wikipedia.org/wiki/Digital_rights_management DRM (digital rights management)]

There are a couple of problems with DRM systems:

* DRM systems in the past have almost always been cracked
* DRM systems tend to be rather complex and thus expensive to maintain
* in the end the content has to be displayed: couple that with an open source client and the DRM effort is nullified.

The consensus on the mailing (and also one voiced by LL) is that DRM is not going to work in an open source, open grid environment.

* I think we ought to be more specific about just what kind of DRM we're referring to here. To the extent that the SL mod/copy/transfer bits are "DRM", we have good evidence that they work well enough to support an economy, even with the client opensourced. There's no reason to think that this kind of DRM can't work just as well in an open grid, or at least that subset of an open grid in which there are mutual and enforceable agreements in place about obeying the bits. I assume this "is not going to work" refers to trying to make the system strong enough that even a skilled and determined attacker can't get around the protections? The talk in the list didn't really call this out clearly I don't think... -- [[User:Dale Innis|Dale Innis]] 08:33, 18 July 2008 (PDT)

==Do away with permissions?==

The current permission system works --- kind of. Objects and textures ''can'' be copied (by a modified SL client offering "right click->save as...", or by libsecondlife based "copybots"), while scripts are protected by the grid servers.

So, we could make the argument that in an open grid environment we cannot guarantee that an attached foreign grid or an attached client cannot by-pass the permission system nor that they cannot make use of content that contradicts the intentions of the content creator --- thus, we could argue that we can just forget about permissions and not bother.

But let's step back for a moment and look at the permission system from a different angle: we can also view the sets of permissions an object has as a ''license digest''. This license digest communicates what rights the content creator wants to give the content consumer. Instead of having a 100 page EULA to go along with that super-duper flying broomstick you have a fairly compact set of permissions that tell you...

* you can modify that super-duper broomstick
* you can make personal copies
* you can transfer copies
* you are not allowed to charge for it

or alternately

* you cannot modify that super-duper broomstick
* you can make personal copies
* you cannot transfer copies

So, yes, permissions are not perfectly enforceable by technical means --- but they make sense as a license digest. Technical means (code) can make it difficult or inconvenient to violate the license thus expressed, and can make it possible to detect violations so that other remedies can be employed when the technical protections fail.

==Extending the current permission system==

Two extensions have been suggested to the current permission system:

* ''transfer to trusted region'' --- that would allow the content creator either
** to allow transfer of the content to a list of trusted regions, or
** to allow transfer to all those regions that are trusted by a list of regions that she trusts
* ''sticky permissions'' --- permissions that cannot be changed down the food chain; for example,
** sticky transfer permission and sticky price tag: you can transfer the object, but you cannot take away the transfer permission, you should also not charge for the object.

[[User:Dr Scofield|Dr Scofield]] 04:29, 26 September 2007 (PDT)

* Other related extensions:
** allow transfer of the content to an indirectly-referenced list of trusted regions or domains (e.g. "the official list of Linden Lab Category A Partner Regions", or "Jared Hu's List of Regions Run by Friends", or whatever)
** allow transfer to some set of domains, but '''not''' some other set (exclusion as well as inclusion)

==Discussion on the mailing list==

Unfortunately the archive messed up and the permission thread is all over the place, but here are some link from which you might want to follow downwards the stream:
(probably also happens due to keyword juggling in the subject)

* https://lists.secondlife.com/pipermail/sldev/2007-September/004637.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/004652.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005065.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005086.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005104.html (a content creator's view)
* https://lists.secondlife.com/pipermail/sldev/2007-September/005128.html (cont'd)
* https://lists.secondlife.com/pipermail/sldev/2007-September/005144.html (cont'd)

Basically it's the [https://lists.secondlife.com/pipermail/sldev/2007-September/subject.html September archive].

== Summary ==

* I think all participants are more or less agreeing on the fact that a strong(er) DRM is not possible to be implemented. (We need to clarify this statement so it doesn't frighten people who read this without reading all the discussion. [[User:Dale Innis|Dale Innis]] 08:45, 18 July 2008 (PDT) )
* Permissions are here to stay, but these access constraints can hold ''only within the walls of specific managed grids''. One grid can only assume that another grid will respect the constraints if there is trust (backed where appropriate by enforceable agreements) between the grids.
* New permissions might be needed such as:
** allow an asset only to be used inside one region domain
** allow an asset only to be used inside one grid (= list of trusted region domains)
** allow an asset only to be used inside a set of region domains
*** For example, using signed certificates and revocation lists (possible implementation)
* It should also possible to create full-perm assets that stay full perm (such as a GPL-style license).
* It should be possible to make your intent more clear.
** Additional specific flags indicating certain permissions, even if they can't be enforced to serve as notice.
** An additional license field for license and copyright text, similar to land covenants (for e.g. CC licenses)

== Thought on DRM ==

This is a personal thought, but rooted in some fairly deep considerations. Given the real world nature of a distributed application and security, DRM becomes a perpetual arms race, and not one any standard is likely to win. We can, and should, however, try to make sure the system can aid in marking ''intent'' and in ''detecting '' theft and abuse, so that people can use other remedies when the theft hits levels where that matters.

A second, related thought, is that, we can, and should ensure that what we build permits marking content such that a sub cluster with a trusted set of services and trusted clients and keep content within that space, while allowing public hosted content to be used.

- [[user:Zha Ewry]] 9/25/2007

Those are good thoughts. I would add to them the suggestion that, as well as marking intent and detecting violations of intent, the system can make violation less convenient. This is reasonably important; there may well be cases where an economy will work if intent-violation (e.g. copying contrary to the license digest) is possible but inconvenient, whereas it would be on the other side of the viability curve if intent violation is trivial (i.e. press "copy"). We should not let the (impossible) perfect be the enemy of the (possible) good. :)

- [[User:Dale Innis|Dale Innis]] 08:49, 18 July 2008 (PDT)

== Arms Race Can Be Fought or Pretended to Be Fought ==

The doctrine of the "arms race" in software needs to be challenged vigorously. In RL, countries engage in arms races out of necessity because there are other factors outside the immediate realm of the arms they are racing with that can contribute to a favourable outcome. For example, Reagan believed that by ordering Star Wars anti-missile defense to be built, he could trump the Soviets' SS 20s threatening Europe's Pershing missiles, which were there in turn to counter conventional weapons. He could then bankrupt the Soviets and impoverish them as they struggled to build a system against Star Wars (note: I'm describing a historical event, not endorsing a policy). Online, there's no reason to consider that arms races are endless by their nature merely because they are technical, and that other factors of attrition cannot enter in.

In the SL setting, it is (still) a small world, and griefers' groups wanting to bother with SL a small and known quantity. Arms-racing against some of them is a trivial matter; they are kids. So the pool of hackers becomes reduced, and sure, more try the next time and the process *may* invite opportunistic players in the arms race game, but generally each new effort to obfuscate or create dodges or feints or decoys or poison apples or red dye jets or whatever the methods are wins some, and reduces the ranks. It also begins to establish the concept of "we mean business and we will keep stopping you". It doesn't even have to work every day. The DRM can, as indicated, merely mark intent; it can, as said here by Zha, merely mark the violation to trigger remedies. But it is good in its own right to stop casual thefts: the DRM of c/m/t works wonderfully in SL and should not be retired or dumped in the interoperability gambit. An arms race in cyberspace doesn't threaten the lives and property of real people; it impoverishes griefers only in time and ingenuity. It is worth fighting; it is worth *pretending* to fight. Digital rights management is not about digital; it's about rights and about management.

- [[user:Prokofy Neva]] 7 November 2009

== The fallacy of DRM ==

It's worth pointing out somewhere, just in case it hasn't come across, that the failure of DRM doesn't hinge on arms races or cleverness of crackers or anything like that. It stems from a failure to understand that encryption was designed to protect communications between Alice and Bob from the evil Eve, and not to handle the case where Bob and Eve are the same person. DRM proponents are trying to give Bob access to an item without giving him access to the item ... which isn't logical, Captain, and is always doomed to eventual failure. The Lindens do understand that, so all credit to them for not going down a path of self-delusion. --[[User:Morgaine Dinova|Morgaine Dinova]] 12:27, 2 October 2007 (PDT)

== Related Jira Entry ==

[https://jira.secondlife.com/browse/VWR-2571 VRW-2571 : Copyleft/share-alike permission for SL Items]
* The Jira discussion finally coalesced into some sort of general agreement that it would be A Good Thing for authors to be able to express their intentions with respect to downstream use of their work. This is true even under the inevitable "fallacy of DRM" ... in other words, it is worthwhile for an author to be able to express her intentions even in the absence of any guarantees. --[[User:Morgaine Dinova|Morgaine Dinova]] 11:55, 3 October 2007 (PDT)

== No, DRM is Not a Fallacy ==

DRM is not a fallacy. That is an opinion of one extreme school of thought, and not a fact. As noted, arms races can be fought; can be pretended to be fought; can have partial or full valid outcomes. While submitting typical coder opinion to the wiki seems valid enough, no opinion of this nature should be portrayed as "fact" and enabled to shut off further discussion.
[[User:Prokofy Neva|Prokofy Neva]] 7 November 2009

== Usecases ==

* [http://wiki.secondlife.com/wiki/Security_Usecases Security Related Usecases] (more needed!)

[[Category: AW Groupies]]

Protecting content in an open grid

2009-11-08T03:13:59Z

Dale Innis: /* Arms Race Can Be Fought or Pretended to Be Fought */ move misplaced words back to the previous section

[[Image:slarch.jpg]]

==Protecting content in an open grid==

Starting in September of 2007, there has been discussion on the
[https://wiki.secondlife.com/w/index.php?title=DRM%2C_IP_and_permissions#Discussion_on_the_mailing_list sldev mailing list] about how to protect content (objects, textures, scripts) in a future open grid (that is, a large grid that is an interconnection of grids operated by different companies, organizations, and individuals).

Basically we face the following challenges:

* content creators want the ability to specify rules about how the content they make available can be used; for example,
** "you can modify and transfer (give away or sell) what you got from me, but you can't make copies of it"
** "you can modify and copy but not transfer what you got from me (for money or for free)"
** "you can modify, copy, and transfer but not sell what you got from me"
** "you can do whatever you want with what you got from me"
** "you can take what you got from me with you to all grids that are trusted by Linden Labs"
** "you can modify this object but only to repair it to work in future simulator software, or to create a derivative work for sale to citizens of Portugal" (this example serves to illustrate how complex real licenses can be)
* content is basically just a series of bits; that is, a sequence of 0s and 1s. as such it is copyable. any SL client will by necessity have a copy of the visual part of content (including sound) as it has to render the content to the user
** with an open source viewer/client you can always copy the visual part of content (absent hardware features that aren't currently in place and seem unlikely, such as a shared secret between the server and the video card)
** scripts are (currently at least) running on the grid servers and can be protected that way (i.e., the server does not hand over the script to the client if the permissions do not allow this): in an open grid we will have grid servers that are not under the control of LL (that is the whole purpose of the open grid) and thus a grid server could very well provide copies of scripts to anyone in control of it.

So, basically the challenge is that content providers want to specify rules for the content they create and at the same time with an open grid and with open source SL clients we cannot ''guarantee'' those rules. This is not necessarily fatal; an economy can work even when theft is possible. But it is a fundamental limitation to what we can do with technical solutions.

==Linden Lab statement on content protection in interop==

On 8 July 2008, a [http://blog.secondlife.com/2008/07/08/ibm-linden-lab-interoperability-announcement/ posting in the Second Life weblog] entitled "IBM and Linden Lab Interoperability Announcement" included the following text:

Q: How will Linden Lab prevent property from being copied into other virtual worlds?

We’re paying extremely close attention to that question. We will be designing this with the Second Life community to ensure their needs are met. We want to stress that when it does become possible to move avatars between worlds, we will take the utmost care to protect the rights of Second Life property owners and creators. Linden Lab will not design a system that lets people openly violate the permissions of SL goods and take them to other worlds. We recognize that intellectual property is the engine that drives Second Life, and we are completely committed to preserving the qualities that make Second Life the unique, innovative and dynamic place that it is today.

==DRM?==

The challenge we face is the same as faced by digital content providers in the real world; for example, MP3 music outlets. The temptation is to try and go the same route that has been tried by those RL content providers: [http://en.wikipedia.org/wiki/Digital_rights_management DRM (digital rights management)]

There are a couple of problems with DRM systems:

* DRM systems in the past have almost always been cracked
* DRM systems tend to be rather complex and thus expensive to maintain
* in the end the content has to be displayed: couple that with an open source client and the DRM effort is nullified.

The consensus on the mailing (and also one voiced by LL) is that DRM is not going to work in an open source, open grid environment.

* I think we ought to be more specific about just what kind of DRM we're referring to here. To the extent that the SL mod/copy/transfer bits are "DRM", we have good evidence that they work well enough to support an economy, even with the client opensourced. There's no reason to think that this kind of DRM can't work just as well in an open grid, or at least that subset of an open grid in which there are mutual and enforceable agreements in place about obeying the bits. I assume this "is not going to work" refers to trying to make the system strong enough that even a skilled and determined attacker can't get around the protections? The talk in the list didn't really call this out clearly I don't think... -- [[User:Dale Innis|Dale Innis]] 08:33, 18 July 2008 (PDT)

==Do away with permissions?==

The current permission system works --- kind of. Objects and textures ''can'' be copied (by a modified SL client offering "right click->save as...", or by libsecondlife based "copybots"), while scripts are protected by the grid servers.

So, we could make the argument that in an open grid environment we cannot guarantee that an attached foreign grid or an attached client cannot by-pass the permission system nor that they cannot make use of content that contradicts the intentions of the content creator --- thus, we could argue that we can just forget about permissions and not bother.

But let's step back for a moment and look at the permission system from a different angle: we can also view the sets of permissions an object has as a ''license digest''. This license digest communicates what rights the content creator wants to give the content consumer. Instead of having a 100 page EULA to go along with that super-duper flying broomstick you have a fairly compact set of permissions that tell you...

* you can modify that super-duper broomstick
* you can make personal copies
* you can transfer copies
* you are not allowed to charge for it

or alternately

* you cannot modify that super-duper broomstick
* you can make personal copies
* you cannot transfer copies

So, yes, permissions are not perfectly enforceable by technical means --- but they make sense as a license digest. Technical means (code) can make it difficult or inconvenient to violate the license thus expressed, and can make it possible to detect violations so that other remedies can be employed when the technical protections fail.

==Extending the current permission system==

Two extensions have been suggested to the current permission system:

* ''transfer to trusted region'' --- that would allow the content creator either
** to allow transfer of the content to a list of trusted regions, or
** to allow transfer to all those regions that are trusted by a list of regions that she trusts
* ''sticky permissions'' --- permissions that cannot be changed down the food chain; for example,
** sticky transfer permission and sticky price tag: you can transfer the object, but you cannot take away the transfer permission, you should also not charge for the object.

[[User:Dr Scofield|Dr Scofield]] 04:29, 26 September 2007 (PDT)

* Other related extensions:
** allow transfer of the content to an indirectly-referenced list of trusted regions or domains (e.g. "the official list of Linden Lab Category A Partner Regions", or "Jared Hu's List of Regions Run by Friends", or whatever)
** allow transfer to some set of domains, but '''not''' some other set (exclusion as well as inclusion)

==Discussion on the mailing list==

Unfortunately the archive messed up and the permission thread is all over the place, but here are some link from which you might want to follow downwards the stream:
(probably also happens due to keyword juggling in the subject)

* https://lists.secondlife.com/pipermail/sldev/2007-September/004637.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/004652.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005065.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005086.html
* https://lists.secondlife.com/pipermail/sldev/2007-September/005104.html (a content creator's view)
* https://lists.secondlife.com/pipermail/sldev/2007-September/005128.html (cont'd)
* https://lists.secondlife.com/pipermail/sldev/2007-September/005144.html (cont'd)

Basically it's the [https://lists.secondlife.com/pipermail/sldev/2007-September/subject.html September archive].

== Summary ==

* I think all participants are more or less agreeing on the fact that a strong(er) DRM is not possible to be implemented. (We need to clarify this statement so it doesn't frighten people who read this without reading all the discussion. [[User:Dale Innis|Dale Innis]] 08:45, 18 July 2008 (PDT) )
* Permissions are here to stay, but these access constraints can hold ''only within the walls of specific managed grids''. One grid can only assume that another grid will respect the constraints if there is trust (backed where appropriate by enforceable agreements) between the grids.
* New permissions might be needed such as:
** allow an asset only to be used inside one region domain
** allow an asset only to be used inside one grid (= list of trusted region domains)
** allow an asset only to be used inside a set of region domains
*** For example, using signed certificates and revocation lists (possible implementation)
* It should also possible to create full-perm assets that stay full perm (such as a GPL-style license).
* It should be possible to make your intent more clear.
** Additional specific flags indicating certain permissions, even if they can't be enforced to serve as notice.
** An additional license field for license and copyright text, similar to land covenants (for e.g. CC licenses)

== Thought on DRM ==

This is a personal thought, but rooted in some fairly deep considerations. Given the real world nature of a distributed application and security, DRM becomes a perpetual arms race, and not one any standard is likely to win. We can, and should, however, try to make sure the system can aid in marking ''intent'' and in ''detecting '' theft and abuse, so that people can use other remedies when the theft hits levels where that matters.

A second, related thought, is that, we can, and should ensure that what we build permits marking content such that a sub cluster with a trusted set of services and trusted clients and keep content within that space, while allowing public hosted content to be used.

- [[user:Zha Ewry]] 9/25/2007

== Arms Race Can Be Fought or Pretended to Be Fought ==

The doctrine of the "arms race" in software needs to be challenged vigorously. In RL, countries engage in arms races out of necessity because there are other factors outside the immediate realm of the arms they are racing with that can contribute to a favourable outcome. For example, Reagan believed that by ordering Star Wars anti-missile defense to be built, he could trump the Soviets' SS 20s threatening Europe's Pershing missiles, which were there in turn to counter conventional weapons. He could then bankrupt the Soviets and impoverish them as they struggled to build a system against Star Wars (note: I'm describing a historical event, not endorsing a policy). Online, there's no reason to consider that arms races are endless by their nature merely because they are technical, and that other factors of attrition cannot enter in.

In the SL setting, it is (still) a small world, and griefers' groups wanting to bother with SL a small and known quantity. Arms-racing against some of them is a trivial matter; they are kids. So the pool of hackers becomes reduced, and sure, more try the next time and the process *may* invite opportunistic players in the arms race game, but generally each new effort to obfuscate or create dodges or feints or decoys or poison apples or red dye jets or whatever the methods are wins some, and reduces the ranks. It also begins to establish the concept of "we mean business and we will keep stopping you". It doesn't even have to work every day. The DRM can, as indicated, merely mark intent; it can, as said here by Zha, merely mark the violation to trigger remedies. But it is good in its own right to stop casual thefts: the DRM of c/m/t works wonderfully in SL and should not be retired or dumped in the interoperability gambit. An arms race in cyberspace doesn't threaten the lives and property of real people; it impoverishes griefers only in time and ingenuity. It is worth fighting; it is worth *pretending* to fight. Digital rights management is not about digital; it's about rights and about management.

- [[user:Prokofy Neva]] 7 November 2009

== The fallacy of DRM ==

It's worth pointing out somewhere, just in case it hasn't come across, that the failure of DRM doesn't hinge on arms races or cleverness of crackers or anything like that. It stems from a failure to understand that encryption was designed to protect communications between Alice and Bob from the evil Eve, and not to handle the case where Bob and Eve are the same person. DRM proponents are trying to give Bob access to an item without giving him access to the item ... which isn't logical, Captain, and is always doomed to eventual failure. The Lindens do understand that, so all credit to them for not going down a path of self-delusion. --[[User:Morgaine Dinova|Morgaine Dinova]] 12:27, 2 October 2007 (PDT)

== Related Jira Entry ==

[https://jira.secondlife.com/browse/VWR-2571 VRW-2571 : Copyleft/share-alike permission for SL Items]
* The Jira discussion finally coalesced into some sort of general agreement that it would be A Good Thing for authors to be able to express their intentions with respect to downstream use of their work. This is true even under the inevitable "fallacy of DRM" ... in other words, it is worthwhile for an author to be able to express her intentions even in the absence of any guarantees. --[[User:Morgaine Dinova|Morgaine Dinova]] 11:55, 3 October 2007 (PDT)

== No, DRM is Not a Fallacy ==

DRM is not a fallacy. That is an opinion of one extreme school of thought, and not a fact. As noted, arms races can be fought; can be pretended to be fought; can have partial or full valid outcomes. While submitting typical coder opinion to the wiki seems valid enough, no opinion of this nature should be portrayed as "fact" and enabled to shut off further discussion.
[[User:Prokofy Neva|Prokofy Neva]] 7 November 2009

== Usecases ==

* [http://wiki.secondlife.com/wiki/Security_Usecases Security Related Usecases] (more needed!)

[[Category: AW Groupies]]

Talk:LlRequestURL

2009-11-03T19:38:40Z

Dale Innis: /* Are URLs automatically released when the script is reset? */

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)