Second Life Wiki - User contributions [en]

User:Pedro Oval/Mono code memory usage/CIL

2015-03-30T00:56:42Z

Kizmut Smit: +cat :3

Here's the CIL code generated by the script below, which gives some insight of what's happening under the hood.

Compilation was done using the viewer's built-in compiler as suggested by [[User:Becky Pippen/LSL Performance]]. Assembly was done using <code>ilasm</code> from the Mono suite.

Script that gets compiled:

<source lang="lsl2">
integer i;
u(){}

default
{
state_entry()
{
integer x;
integer y = 0;
integer z;
float f;
float g;
vector v;
list a;

;;;;;;;;;{{{{{{{{}}}}}}}}
return;
x;
(x);
(integer)x;
(float)x;
f;
(float)f;
(integer)f;
v;
v.z;
-x;
~x;
!x;
--x;
++x;
x--;
x++;
x=y;
x==y;
x=y=z;
f=x;
f=(float)x;
x!=y;
x+y;
x-y;
x+-y;
x*y;
x/y;
x%y;
x&y;
x&&y;
x|y;
x||y;
x^y;
x<<y;
x>>y;
x<y;
x>y;
x<=y;
x>=y;
x+=y;
x-=y;
x+=-y;
x*=y;
x/=y;
x%=y;
if (x) ;
if (x) ; else ;
0;
x^x;
1;
-1;
0xffffffff;
ALL_SIDES;
x|~x;
x+1;
-~x;
x-1;
x+-1;
~-x;
x*y+y-1;
(x+1)*y-1;
~(~x*y)
while (x) ;
do ; while (x);
for (;x;) ;
@label; if (x) jump label;
0.0;
f=0.0;
f=0;
<0.0, 0.0, 0.0>;
ZERO_VECTOR;
<0, 0, 0>;
<-1.0, -1.0, 0.0>;
TOUCH_INVALID_TEXCOORD;
<-1, -1, 0>;
<0xffffffff, 0xffffffff, 0>;
v+v;
v-v;
v*v;
v%v;
[];
a=[];
a+[x];
a+x;
[x]+a;
x+a;
[x];
[]+x;
(list)x;
[x,y];
[]+x+y;
(string)a;
i;
u();
}
}
</source>

Compiled and annotated result:

<pre>
.assembly extern mscorlib {.ver 1:0:5000:0}
.assembly extern LslLibrary {.ver 0:1:0:0}
.assembly extern LslUserScript {.ver 0:1:0:0}
.assembly extern ScriptTypes {.ver 0:1:0:0}
.assembly 'LSL_y' {.ver 0:0:0:0}
.class public auto ansi serializable beforefieldinit LSL_y extends [LslUserScript]LindenLab.SecondLife.LslUserScript
{
.field public int32 'i'
.method public hidebysig specialname rtspecialname instance default void .ctor () cil managed
{
.maxstack 500

// Globals initialization

// integer i;
02 ldarg.0
16 ldc.i4.0
7D 01 00 00 04 stfld int32 LSL_y::'i'

02 ldarg.0
28 01 00 00 0A call instance void [LslUserScript]LindenLab.SecondLife.LslUserScript::.ctor()
2A ret
}
.method public hidebysig instance default void 'gu'() cil managed
{
.maxstack 500
2A ret
}

.method public hidebysig instance default void edefaultstate_entry() cil managed
{
.maxstack 500
.locals init (int32, int32, int32, float32, float32, class [ScriptTypes]LindenLab.SecondLife.Vector, class [mscorlib]System.Collections.ArrayList)
// integer x;
16 ldc.i4.0
13 00 stloc.s 0

// integer y = 0;
20 00 00 00 00 ldc.i4 0
13 01 stloc.s 1

// integer z;
16 ldc.i4.0
13 02 stloc.s 2

// float f;
23 00 00 00 00 ldc.r8 0
00 00 00 00
13 03 stloc.s 3

// float g;
23 00 00 00 00 ldc.r8 0
00 00 00 00
13 04 stloc.s 4

// vector v;
23 00 00 00 00 ldc.r8 0
00 00 00 00
23 00 00 00 00 ldc.r8 0
00 00 00 00
23 00 00 00 00 ldc.r8 0
00 00 00 00
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
13 05 stloc.s 5

// list a;
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
13 06 stloc.s 6

// ;;; {{{ }}} generate no code

// return;
2A ret

// x;
11 00 ldloc.s 0
26 pop

// (x);
11 00 ldloc.s 0
26 pop

// (integer)x;
11 00 ldloc.s 0
26 pop

// (float)x;
11 00 ldloc.s 0
6C conv.r8
26 pop

// f;
11 03 ldloc.s 3
26 pop

// (float)f;
11 03 ldloc.s 3
26 pop

// (integer)f;
11 03 ldloc.s 3
28 04 00 00 0A call int32 [LslLibrary]LindenLab.SecondLife.LslRunTime::ToInteger(float32)
26 pop

// v;
11 05 ldloc.s 5
26 pop

// v.z;
12 05 ldloca.s 5
78 05 00 00 0A ldfld float32 class [ScriptTypes]LindenLab.SecondLife.Vector::z
26 pop

// -x;
11 00 ldloc.s 0
65 neg
26 pop

// ~x;
11 00 ldloc.s 0
66 not
26 pop

// !x;
11 00 ldloc.s 0
16 ldc.i4.0
FE 01 ceq
26 pop

// --x;
11 00 ldloc.s 0
17 ldc.i4.1
59 sub
25 dup
13 00 stloc.s 0
26 pop

// ++x;
11 00 ldloc.s 0
17 ldc.i4.1
58 add
25 dup
13 00 stloc.s 0
26 pop

// x--;
11 00 ldloc.s 0
11 00 ldloc.s 0
17 ldc.i4.1
59 sub
25 dup
13 00 stloc.s 0
26 pop
26 pop

// x++;
11 00 ldloc.s 0
11 00 ldloc.s 0
17 ldc.i4.1
58 add
25 dup
13 00 stloc.s 0
26 pop
26 pop

// x = y;
11 01 ldloc.s 1
25 dup
13 00 stloc.s 0
26 pop

// x == y;
11 01 ldloc.s 1
11 00 ldloc.s 0
FE 01 ceq
26 pop

// x = y = z;
11 02 ldloc.s 2
25 dup
13 01 stloc.s 1
25 dup
13 00 stloc.s 0
26 pop

// f = x;
11 00 ldloc.s 0
6C conv.r8
25 dup
13 03 stloc.s 3
26 pop

// f = (float)x;
11 00 ldloc.s 0
6C conv.r8
25 dup
13 03 stloc.s 3
26 pop

// x != y; implemented as: !(x==y)
11 01 ldloc.s 1 // this part is x == y
11 00 ldloc.s 0
FE 01 ceq
16 ldc.i4.0 // this part is 'not'
FE 01 ceq
26 pop

// x + y;
11 01 ldloc.s 1
11 00 ldloc.s 0
58 add
26 pop

// x - y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 06 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Subtract(int32, int32)
26 pop

// x + -y;
11 01 ldloc.s 1
65 neg
11 00 ldloc.s 0
58 add
26 pop

// x * y;
11 01 ldloc.s 1
11 00 ldloc.s 0
5A mul
26 pop

// x / y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 07 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Divide(int32, int32)
26 pop

// x % y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 08 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Modulo(int32, int32)
26 pop

// x & y;
11 01 ldloc.s 1
11 00 ldloc.s 0
5F and
26 pop

// x && y; implemented as: !(!x | !y)
11 01 ldloc.s 1 // !x
16 ldc.i4.0
FE 01 ceq
11 00 ldloc.s 0 // !y
16 ldc.i4.0
FE 01 ceq
60 or // !x | !y
16 ldc.i4.0 // !(!x | !y)
FE 01 ceq
26 pop

// x | y;
11 01 ldloc.s 1
11 00 ldloc.s 0
60 or
26 pop

// x || y; implemented as: !!(x | y)
11 01 ldloc.s 1 // x | y
11 00 ldloc.s 0
60 or
16 ldc.i4.0 // !(x | y)
FE 01 ceq
16 ldc.i4.0 // !!(x | y)
FE 01 ceq
26 pop

// x ^ y;
11 01 ldloc.s 1
11 00 ldloc.s 0
61 xor
26 pop

// x << y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 09 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::ShiftLeft(int32, int32)
26 pop

// x >> y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 0A 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::ShiftRight(int32, int32)
26 pop

// x < y; implemented as: y > x
11 01 ldloc.s 1
11 00 ldloc.s 0
FE 02 cgt
26 pop

// x > y; implemented as: y < x;
11 01 ldloc.s 1
11 00 ldloc.s 0
FE 04 clt
26 pop

// x <= y; implemented as: !(y < x)
11 01 ldloc.s 1
11 00 ldloc.s 0
FE 04 clt
16 ldc.i4.0
FE 01 ceq
26 pop

// x >= y; implemented as: !(y > x)
11 01 ldloc.s 1
11 00 ldloc.s 0
FE 02 cgt
16 ldc.i4.0
FE 01 ceq
26 pop

// x += y;
11 01 ldloc.s 1
11 00 ldloc.s 0
58 add
25 dup
13 00 stloc.s 0
26 pop

// x -= y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 06 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Subtract(int32, int32)
25 dup
13 00 stloc.s 0
26 pop

// x += -y;
11 01 ldloc.s 1
65 neg
11 00 ldloc.s 0
58 add
25 dup
13 00 stloc.s 0
26 pop

// x *= y;
11 01 ldloc.s 1
11 00 ldloc.s 0
5A mul
25 dup
13 00 stloc.s 0
26 pop

// x /= y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 07 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Divide(int32, int32)
25 dup
13 00 stloc.s 0
26 pop

// x %= y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 08 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Modulo(int32, int32)
25 dup
13 00 stloc.s 0
26 pop

// if (x) ;
11 00 ldloc.s 0
39 00 00 00 00 brfalse LabelTempJump0
// THEN branch code goes here
LabelTempJump0:

// if (x) ; else ;
11 00 ldloc.s 0
39 05 00 00 00 brfalse LabelTempJump1
// THEN branch code would go here
38 00 00 00 00 br LabelTempJump2
// ELSE branch code would go here
LabelTempJump1:
LabelTempJump2:

// 0;
20 00 00 00 00 ldc.i4 0
26 pop

// x ^ x;
11 00 ldloc.s 0
11 00 ldloc.s 0
61 xor
26 pop

// 1;
20 01 00 00 00 ldc.i4 1
26 pop

// -1; note the negative sign takes code memory
20 01 00 00 00 ldc.i4 1
65 neg
26 pop

// 0xffffffff; note it equals -1 without the sign taking memory
20 FF FF FF FF ldc.i4 -1
26 pop

// ALL_SIDES; ditto
20 FF FF FF FF ldc.i4 -1
26 pop

// x | ~x;
11 00 ldloc.s 0
66 not
11 00 ldloc.s 0
60 or
26 pop

// x + 1;
20 01 00 00 00 ldc.i4 1
11 00 ldloc.s 0
58 add
26 pop

// -~x;
11 00 ldloc.s 0
66 not
65 neg
26 pop

// x - 1;
20 01 00 00 00 ldc.i4 1
11 00 ldloc.s 0
28 06 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Subtract(int32, int32)
26 pop

// x + -1;
20 01 00 00 00 ldc.i4 1
65 neg
11 00 ldloc.s 0
58 add
26 pop

// ~-x;
11 00 ldloc.s 0
65 neg
66 not
26 pop

// x*y + y - 1;
20 01 00 00 00 ldc.i4 1
11 01 ldloc.s 1
11 01 ldloc.s 1
11 00 ldloc.s 0
5A mul
58 add
28 06 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Subtract(int32, int32)
26 pop

// (x + 1)*y - 1;
20 01 00 00 00 ldc.i4 1
11 01 ldloc.s 1
20 01 00 00 00 ldc.i4 1
11 00 ldloc.s 0
58 add
5A mul
28 06 00 00 0A call int32 [LslUserScript]LindenLab.SecondLife.LslUserScript::Subtract(int32, int32)
26 pop

// ~(~x*y);
11 01 ldloc.s 1
11 00 ldloc.s 0
66 not
5A mul
66 not
26 pop

// while (x) ;
LabelTempJump3:
11 00 ldloc.s 0
39 05 00 00 00 brfalse LabelTempJump4
// Looped code would go here
38 F4 FF FF FF br LabelTempJump3
LabelTempJump4:

// do ; while (x);
LabelTempJump5:
// Looped code would go here
11 00 ldloc.s 0
3A F9 FF FF FF brtrue LabelTempJump5

// for (; x; ) ;
LabelTempJump6:
11 00 ldloc.s 0
39 05 00 00 00 brfalse LabelTempJump7
// Looped code would go here
38 F4 FF FF FF br LabelTempJump6
LabelTempJump7:

// @label; if (x) jump label;
'label':
// Looped code would go here
11 00 ldloc.s 0
39 05 00 00 00 brfalse LabelTempJump8
38 F4 FF FF FF br 'label'
LabelTempJump8:

// 0.0;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
26 pop

// f = 0.0;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
25 dup
13 03 stloc.s 3
26 pop

// f = 0;
20 00 00 00 00 ldc.i4 0
6C conv.r8
25 dup
13 03 stloc.s 3
26 pop

// <0.0, 0.0, 0.0>;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// ZERO_VECTOR;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// <0, 0, 0>;
20 00 00 00 00 ldc.i4 0
6C conv.r8
20 00 00 00 00 ldc.i4 0
6C conv.r8
20 00 00 00 00 ldc.i4 0
6C conv.r8
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// <-1.0, -1.0, 0.0>;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 f0 3f)
00 00 F0 3F
65 neg
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 f0 3f)
00 00 F0 3F
65 neg
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// TOUCH_INVALID_TEXCOORD;
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 f0 bf)
00 00 F0 BF
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 f0 bf)
00 00 F0 BF
23 00 00 00 00 ldc.r8 (00 00 00 00 00 00 00 00)
00 00 00 00
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// <-1, -1, 0>;
20 01 00 00 00 ldc.i4 1
65 neg
6C conv.r8
20 01 00 00 00 ldc.i4 1
65 neg
6C conv.r8
20 00 00 00 00 ldc.i4 0
6C conv.r8
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// <0xffffffff, 0xffffffff, 0>;
20 FF FF FF FF ldc.i4 -1
6C conv.r8
20 FF FF FF FF ldc.i4 -1
6C conv.r8
20 00 00 00 00 ldc.i4 0
6C conv.r8
28 02 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'CreateVector'(float32, float32, float32)
26 pop

// v + v;
11 05 ldloc.s 5
11 05 ldloc.s 5
28 0B 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'Add'(class [ScriptTypes]LindenLab.SecondLife.Vector, class [ScriptTypes]LindenLab.SecondLife.Vector)
26 pop

// v - v;
11 05 ldloc.s 5
11 05 ldloc.s 5
28 0C 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'Subtract'(class [ScriptTypes]LindenLab.SecondLife.Vector, class [ScriptTypes]LindenLab.SecondLife.Vector)
26 pop

// v * v;
11 05 ldloc.s 5
11 05 ldloc.s 5
28 0D 00 00 0A call float32 class [LslUserScript]LindenLab.SecondLife.LslUserScript::'Multiply'(class [ScriptTypes]LindenLab.SecondLife.Vector, class [ScriptTypes]LindenLab.SecondLife.Vector)
26 pop

// v % v;
11 05 ldloc.s 5
11 05 ldloc.s 5
28 0E 00 00 0A call class [ScriptTypes]LindenLab.SecondLife.Vector class [LslUserScript]LindenLab.SecondLife.LslUserScript::'Modulo'(class [ScriptTypes]LindenLab.SecondLife.Vector, class [ScriptTypes]LindenLab.SecondLife.Vector)
26 pop

// [];
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
26 pop

// a = [];
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
25 dup
13 06 stloc.s 6
26 pop

// a + [x];
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 0F 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(object, class [mscorlib]System.Collections.ArrayList)
11 06 ldloc.s 6
28 10 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(class [mscorlib]System.Collections.ArrayList, class [mscorlib]System.Collections.ArrayList)
26 pop

// a + x;
11 00 ldloc.s 0
11 06 ldloc.s 6
28 11 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(int32, class [mscorlib]System.Collections.ArrayList)
26 pop

// [x] + a;
11 06 ldloc.s 6
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 0F 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(object, class [mscorlib]System.Collections.ArrayList)
28 10 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(class [mscorlib]System.Collections.ArrayList, class [mscorlib]System.Collections.ArrayList)
26 pop

// x + a;
11 06 ldloc.s 6
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
28 12 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(class [mscorlib]System.Collections.ArrayList, object)
26 pop

// [x];
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 0F 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(object, class [mscorlib]System.Collections.ArrayList)
26 pop

// []+x;
11 00 ldloc.s 0
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 11 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(int32, class [mscorlib]System.Collections.ArrayList)
26 pop

// (list)x;
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
28 13 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList(object)
26 pop

// [x, y];
11 00 ldloc.s 0
8C 01 00 00 1B box [mscorlib]System.Int32
11 01 ldloc.s 1
8C 01 00 00 1B box [mscorlib]System.Int32
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 0F 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(object, class [mscorlib]System.Collections.ArrayList)
28 0F 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Prepend(object, class [mscorlib]System.Collections.ArrayList)
26 pop

// []+x+y;
11 01 ldloc.s 1
11 00 ldloc.s 0
28 03 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::CreateList()
28 11 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(int32, class [mscorlib]System.Collections.ArrayList)
28 11 00 00 0A call class [mscorlib]System.Collections.ArrayList class [LslUserScript]LindenLab.SecondLife.LslUserScript::Append(int32, class [mscorlib]System.Collections.ArrayList)
26 pop

// (string)a;
11 06 ldloc.s 6
28 14 00 00 0A call string [LslLibrary]LindenLab.SecondLife.LslRunTime::ListToString(class [mscorlib]System.Collections.ArrayList)
26 pop

// i;
02 ldarg.0
7B 01 00 00 04 ldfld int32 LSL_y::'i'
26 pop

// u();
02 ldarg.0
28 02 00 00 06 call instance void class LSL_y::'gu'()

// end of event
2A ret
}

}
</pre>

===== Important notes: =====

* <code>ldloc.s 0</code> (opcode 11, argument 00) is probably contracted to the abbreviation <code>ldloc.0</code> (opcode 06) at assembly time, resulting in the length of 2 obtained in the [[User:Pedro Oval/Mono code memory usage|memory usage tests]]. Or possibly the server-side compiler added an optimization of this case (!). Either way, the evidence for this is confirmed by the fact that <code>x;</code> takes 2 bytes if it's one of the first four local variables (there are 1-byte opcodes for ldloc.0 through ldloc.3), and 3 bytes otherwise. This applies to all appearances of this opcode and the similar <code>stloc.s</code>.
* Local variable definitions seem to take a variable and big number of bytes (averaging about 47 bytes for local integers) if there is a function call anywhere in the event in which they are defined. Reason unknown.
* Backward jumps seem to take many more bytes than what the CIL result above suggests. Forward jumps, however, seem predictable enough.
* As things are now, having more than 256 local variables in a single function or event causes wraparound, making the 257th be an alias to the 1st, and so on. If they aren't the same type, the script crashes at runtime with an uncaught exception. That's a consequence of using <code>ldloc.s</code> / <code>stloc.s</code> without switching to the long version (<code>ldloc</code> / <code>stloc</code>) when the argument is greater than 255.

===== Additional memory usage notes: =====
* Global variable, function, and function parameter names do take code memory from the script (as part of some symbol table). Fortunately they take 1 byte per character only, as opposed to Mono strings, which take at least 2 bytes per character (they are UTF-16). That extra code is only taken once per variable, regardless of how many times it is used.
* In addition to the state code and state change command code, the state names themselves take code memory from the script, as follows:
** The state name by itself takes no code memory, but internally, each event name includes the state name. The internal name for the event is e.g. <code>edefaultstate_entry</code> (for state <code>default</code>, event <code>state_entry</code>), <code>eblahtimer</code> (for state blah, event <code>timer</code>). These names take 1 byte per character.
** If a state switch statement appears in the code, the state name takes additionally 2 bytes per character. (But these strings are reused, so multiple state switch statements don't take additional space for the strings.)

Although not mentioned above, every single-byte string needs an additional terminating zero byte, and every UTF-16 string needs an additional length prefix byte (or more if longer than 127 bytes, i.e. 63 characters if in the ASCII range) plus an additional terminating zero byte.

{{Resource Conservation Portal Nav|cat=memory}}

Template:LSL Function/ParticleSystem

2014-06-01T05:07:48Z

Kizmut Smit: glBlendFunc URL update

{{#if:

{{LSL Signature/Add|
{{LSL Const/Signature|PSYS_PART_FLAGS|integer|0}}
{{LSL Const/Signature|PSYS_PART_BOUNCE_MASK|integer|hex=0x004|4}}
{{LSL Const/Signature|PSYS_PART_EMISSIVE_MASK|integer|hex=0x100|256}}
{{LSL Const/Signature|PSYS_PART_FOLLOW_SRC_MASK|integer|hex=0x010|16}}
{{LSL Const/Signature|PSYS_PART_FOLLOW_VELOCITY_MASK|integer|hex=0x020|32}}
{{LSL Const/Signature|PSYS_PART_INTERP_COLOR_MASK|integer|hex=0x001|1}}
{{LSL Const/Signature|PSYS_PART_INTERP_SCALE_MASK|integer|hex=0x002|2}}
{{LSL Const/Signature|PSYS_PART_RIBBON_MASK|integer|hex=0x400|1024}}
{{LSL Const/Signature|PSYS_PART_TARGET_LINEAR_MASK|integer|hex=0x080|128}}
{{LSL Const/Signature|PSYS_PART_TARGET_POS_MASK|integer|hex=0x040|64}}
{{LSL Const/Signature|PSYS_PART_WIND_MASK|integer|hex=0x008|8}}
{{LSL Const/Signature|PSYS_SRC_PATTERN|integer|9}}
{{LSL Const/Signature|PSYS_SRC_PATTERN_EXPLODE|integer|hex=0x02|2}}
{{LSL Const/Signature|PSYS_SRC_PATTERN_ANGLE_CONE|integer|hex=0x08|8}}
{{LSL Const/Signature|PSYS_SRC_PATTERN_ANGLE|integer|hex=0x04|4}}
{{LSL Const/Signature|PSYS_SRC_PATTERN_DROP|integer|hex=0x01|1}}
{{LSL Const/Signature|PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY|integer|hex=0x10|16}}
{{LSL Const/Signature|PSYS_SRC_BURST_RADIUS|integer|16}}
{{LSL Const/Signature|PSYS_SRC_ANGLE_BEGIN|integer|22}}
{{LSL Const/Signature|PSYS_SRC_ANGLE_END|integer|23}}
{{LSL Const/Signature|PSYS_SRC_INNERANGLE|integer|10|c=deprecated}}
{{LSL Const/Signature|PSYS_SRC_OUTERANGLE|integer|11|c=deprecated}}
{{LSL Const/Signature|PSYS_SRC_TARGET_KEY|integer|20}}
{{LSL Const/Signature|PSYS_PART_START_COLOR|integer|1}}
{{LSL Const/Signature|PSYS_PART_END_COLOR|integer|3}}
{{LSL Const/Signature|PSYS_PART_START_ALPHA|integer|2}}
{{LSL Const/Signature|PSYS_PART_END_ALPHA|integer|4}}
{{LSL Const/Signature|PSYS_PART_START_SCALE|integer|5}}
{{LSL Const/Signature|PSYS_PART_END_SCALE|integer|6}}
{{LSL Const/Signature|PSYS_SRC_TEXTURE|integer|12}}
{{LSL Const/Signature|PSYS_PART_START_GLOW|integer|26}}
{{LSL Const/Signature|PSYS_PART_END_GLOW|integer|27}}
{{LSL Const/Signature|PSYS_SRC_MAX_AGE|integer|19}}
{{LSL Const/Signature|PSYS_PART_MAX_AGE|integer|7}}
{{LSL Const/Signature|PSYS_SRC_BURST_RATE|integer|13}}
{{LSL Const/Signature|PSYS_SRC_BURST_PART_COUNT|integer|15}}
{{LSL Const/Signature|PSYS_SRC_ACCEL|integer|8}}
{{LSL Const/Signature|PSYS_SRC_OMEGA|integer|21}}
{{LSL Const/Signature|PSYS_SRC_BURST_SPEED_MIN|integer|17}}
{{LSL Const/Signature|PSYS_SRC_BURST_SPEED_MAX|integer|18}}
}}

<noinclude>
{{#vardefine:self|*}}
{{#vardefine:moded|stp}}
</noinclude>

<includeonly>
{{#vardefine:header|{{#var:header}}{{LSLC|Effects}}{{LSLC|Light}}{{LSLC|Particles}}{{LSLC|Prim}}{{LSLC|Stop}}}}
</includeonly>

{{LSL Function/color}}
{{LSL Function/alpha}}

}}<noinclude>
===constants_nb===
</noinclude>{{#if:
{{#vardefine:constants_nb|{{#var:constants_nb}}
{{{!}} {{prettytable|style=margin-top:0; margin-right:0;}}
{{!}}-{{Hl2}}
{{!!}}
{{!!}} Rule / Value Constant
{{!!}} Rule Parameter
{{!!}} Description
{{!!}} Value
{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:System Behavior}}"
{{!}} colspan="5" align="left"{{!}}'''System Behavior'''
{{!}}- id="PSYS_PART_FLAGS"
{{!}}colspan="2"{{!}}PSYS_PART_FLAGS
{{!!}}[[integer]] {{LSL Param|flags}}
{{!!}}Various flags controlling the behavior of the particle system. The value may be specified as an integer in decimal or [[hexadecimal|hex]] format, or by ORing together (using the <nowiki>|</nowiki> operator) one or more of the following flag constants:
{{!}}align="center"{{!}}0
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BOUNCE_MASK"
{{!}}rowspan="13" style="background-color:#c0c0c0;" align="center" valign="center"{{!}}'''V a l u e s'''
{{!}}colspan="2"{{!}}PSYS_PART_BOUNCE_MASK
{{!!}}When set, specifies particles will bounce off a plane at the [[Viewer coordinate frames#Region|region]] Z height of the emitter. On "bounce", each particle reverses velocity and angle. This only works for particles above the plane falling down on it.
{{!}}align="center"{{!}}{{LSL_Hex|0x004|4}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_EMISSIVE_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_EMISSIVE_MASK
{{!!}}When set, particles are full-bright and are unaffected by global lighting (sunlight). Otherwise, particles will be lit depending on the current global lighting conditions. Note that point lights '''do''' illuminate non-emissive particles.
{{!}}align="center"{{!}}{{LSL_Hex|0x100|256}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_FOLLOW_SRC_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_FOLLOW_SRC_MASK
{{!!}}When set, particles move relative to the position of the emitter. Otherwise, particle position and movement are unaffected by the position/movement of the emitter. This flag disables the PSYS_SRC_BURST_RADIUS rule.
{{!}}align="center"{{!}}{{LSL_Hex|0x010|16}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_FOLLOW_VELOCITY_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_FOLLOW_VELOCITY_MASK
{{!!}}When set, particles rotate to orient their "top" towards the direction of movement or emission. Otherwise, particles are oriented vertically as their textures would appear (top of texture at top, left at left).
{{!}}align="center"{{!}}{{LSL_Hex|0x020|32}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_INTERP_COLOR_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_INTERP_COLOR_MASK
{{!!}}When set, particle color and alpha transition from their START settings to their END settings during the particle's lifetime. The transition is a smooth interpolation.
{{!}}align="center"{{!}}{{LSL_Hex|0x001|1}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_INTERP_SCALE_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_INTERP_SCALE_MASK
{{!!}}When set, particle size/scale transitions from its START setting to its END setting during the particle's lifetime.
{{!}}align="center"{{!}}{{LSL_Hex|0x002|2}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_RIBBON_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_RIBBON_MASK
{{!!}}When set, particles are joined together into one continuous triangle strip
{{!}}align="center"{{!}}{{LSL_Hex|0x400|1024}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_TARGET_LINEAR_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_TARGET_LINEAR_MASK
{{!!}} When set, emitted particles move in a straight line towards the target specified by the PSYS_SRC_TARGET_KEY rule. In this mode, PSYS_SRC_ACCEL, PSYS_SRC_BURST_RADIUS, and possibly other rules are ignored.
{{!}}align="center"{{!}}{{LSL_Hex|0x080|128}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_TARGET_POS_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_TARGET_POS_MASK
{{!!}}When set, emitted particles change course during their lifetime, attempting to move towards the target specified by the PSYS_SRC_TARGET_KEY rule by the time they expire. Note that if no target is specified, the target moves out of range, or an invalid target is specified, the particles target the prim itself.
{{!}}align="center"{{!}}{{LSL_Hex|0x040|64}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_WIND_MASK"
{{!}} colspan="2"{{!}}PSYS_PART_WIND_MASK
{{!!}}When set, particle movement is affected by the [[llWind|wind]]. It is applied as a secondary force on the particles.
{{!}}align="center"{{!}}{{LSL_Hex|0x008|8}}
{{!}}-

{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BEAM_MASK"
{{!}} colspan="2"{{!}}<s>PSYS_PART_BEAM_MASK</s>
{{!!}}(''unimplemented'') mask but in the enum
{{!}}align="center"{{!}}{{LSL_Hex|0x200|}}
{{!}}-

{{!}}- style="background-color:#e0e0e0;" id="LL_PART_HUD"
{{!}} colspan="2"{{!}}<s>LL_PART_HUD</s>
{{!!}}Used by the viewer to keep HUD and World particle sources separate.
{{!}}align="center"{{!}}{{LSL_Hex|0x40000000|}}
{{!}}-

{{!}}- style="background-color:#e0e0e0;" id="LL_PART_DEAD_MASK"
{{!}} colspan="2"{{!}}<s>LL_PART_DEAD_MASK</s>
{{!!}}Removes particles, not compatible with any other PSYS_PART_*_MASK
{{!}}align="center"{{!}}{{LSL_Hex|0x80000000|}}
{{!}}-



{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:System Presentation}}"
{{!}} colspan="5" align="left"{{!}}'''System Presentation'''
{{!}}- id="PSYS_SRC_PATTERN"
{{!}} colspan="2"{{!}}PSYS_SRC_PATTERN
{{!!}}[[integer]] {{LSL Param|pattern}}
{{!!}}Specifies the general emission pattern.
{{!}}align="center"{{!}}9
{{!}}- style="background-color:#e0e0e0;" id="PSYS_SRC_PATTERN_EXPLODE"
{{!}}rowspan="5" style="background-color:#c0c0c0;" align="center" valign="center"{{!}}'''V a l u e s'''
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_EXPLODE
{{!!}}Sprays particles outwards in a spherical area. The Initial velocity of each particle is determined by PSYS_SRC_BURST_SPEED_MIN and PSYS_SRC_BURST_SPEED_MAX. The EXPLODE pattern ignores the ANGLE parameters.
{{!}}align="center"{{!}}{{LSL_Hex|0x02|2}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_SRC_PATTERN_ANGLE_CONE"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE_CONE
{{!!}}Sprays particles outwards in a spherical, sub-spherical, conical or ring shaped area, as defined by the ANGLE parameters PSYS_SRC_ANGLE_BEGIN and PSYS_SRC_ANGLE_END. The ANGLE_CONE pattern can be used to imitate the EXPLODE pattern by explicitly setting PSYS_SRC_ANGLE_BEGIN to 0.00000 and PSYS_SRC_ANGLE_END to 3.14159 (or PI) (or vice versa).
{{!}}align="center"{{!}}{{LSL_Hex|0x08|8}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_SRC_PATTERN_ANGLE"
{{!}} colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE
{{!!}}Sprays particles outward in a flat circular, semi-circular, arc or ray shaped areas, as defined by PSYS_SRC_ANGLE_BEGIN and PSYS_SRC_ANGLE_END. The circular pattern radiates outwards around the prim's local X axis line.
{{!}}align="center"{{!}}{{LSL_Hex|0x04|4}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_SRC_PATTERN_DROP"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_DROP
{{!!}}Creates particles with no initial velocity. The DROP pattern will override any values given for PSYS_SRC_BURST_RADIUS, PSYS_SRC_BURST_SPEED_MIN, and PSYS_SRC_BURST_SPEED_MAX, setting each to 0.00000. (All patterns will behave like the DROP pattern, if RADIUS, SPEED_MIN and SPEED_MAX are explicitly set to 0.0000.)
{{!}}align="center"{{!}}{{LSL_Hex|0x01|1}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY
{{!!}}(''incomplete implementation'') acts the same as the PSYS_SRC_PATTERN_DROP pattern, it is believed that the original intention for this pattern was to invert the effect of the ANGLE parameters, making them delineate an area where particles were NOT to be sprayed. (effectively the inverse or opposite of the behavior of the ANGLE_CONE pattern).
{{!}}align="center"{{!}}{{LSL_Hex|0x10|16}}
{{!}}- id="PSYS_SRC_BURST_RADIUS"
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_RADIUS
{{!!}}[[float]] {{LSL Param|radius}}
{{!!}}Specifies the distance from the emitter where particles will be created. This rule is ignored when the PSYS_PART_FOLLOW_SRC_MASK flag is set. A test in http://forums-archive.secondlife.com/327/f5/226722/1.html indicates that the maximum value is 50.00
{{!}}align="center"{{!}}16
{{!}}- id="PSYS_SRC_ANGLE_BEGIN"
{{!}}colspan="2"{{!}}PSYS_SRC_ANGLE_BEGIN
{{!!}}[[float]] {{LSL Param|angle_begin}}
{{!!}}Specifies a half angle, in radians, of a circular or spherical "dimple" or conic section (starting from the emitter facing) within which particles will NOT be emitted. Valid values are the same as for PSYS_SRC_ANGLE_END, though the effects are reversed accordingly. If the pattern is PSYS_SRC_PATTERN_ANGLE, the presentation is a 2D flat circular section. If PSYS_SRC_PATTERN_ANGLE_CONE or PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY is used, the presentation is a 3D spherical section. Note that the value of this parameter and PSYS_SRC_ANGLE_END are internally re-ordered such that this parameter gets the smaller of the two values.
{{!}}align="center"{{!}}22
{{!}}- id="PSYS_SRC_ANGLE_END"
{{!}}colspan="2"{{!}}PSYS_SRC_ANGLE_END
{{!!}}[[float]] {{LSL Param|angle_end}}
{{!!}}Specifies a half angle, in radians, of a circular or spherical "dimple" or conic section (starting from the emitter facing) within which particles WILL be emitted. Valid values are 0.0, which will result in particles being emitted in a straight line in the direction of the emitter facing, to [[PI]], which will result in particles being emitted in a full circular or spherical arc around the emitter, not including the "dimple" or conic section defined by PSYS_SRC_ANGLE_BEGIN. If the pattern is PSYS_SRC_PATTERN_ANGLE, the presentation is a 2D flat circular section. If PSYS_SRC_PATTERN_ANGLE_CONE or PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY is used, the presentation is a 3D spherical section. Note that the value of this parameter and PSYS_SRC_ANGLE_BEGIN are internally re-ordered such that this parameter gets the larger of the two values.
{{!}}align="center"{{!}}23
{{!}}- id="PSYS_SRC_INNERANGLE"
{{!}}colspan="2"{{!}}<del>PSYS_SRC_INNERANGLE</del>
{{!!}}[[float]] {{LSL Param|angle_inner}}
{{!!}}'''DEPRECATED: Use PSYS_SRC_ANGLE_BEGIN instead.''' Works similar to its replacement rule, except the edge of the section is aligned with the emitter facing, rather than its center.
{{!}}align="center"{{!}}10
{{!}}- id="PSYS_SRC_OUTERANGLE"
{{!}}colspan="2"{{!}}<del>PSYS_SRC_OUTERANGLE</del>
{{!!}}[[float]] {{LSL Param|angle_outer}}
{{!!}}'''DEPRECATED: Use PSYS_SRC_ANGLE_END instead.''' Works similar to its replacement rule, except the edge of the section is aligned with the emitter facing, rather than the section's center.
{{!}}align="center"{{!}}11
{{!}}- id="PSYS_SRC_TARGET_KEY"
{{!}}colspan="2"{{!}}PSYS_SRC_TARGET_KEY
{{!!}}[[key]] {{LSL Param|target}}
{{!!}}Specifies the key of a target object, prim, or agent towards which the particles will change course and move (if PSYS_PART_TARGET_POS_MASK is specified) or will move in a straight line (if PSYS_PART_TARGET_LINEAR_MASK is specified). They will attempt to end up at the geometric center of the target at the end of their lifetime. Requires the PSYS_PART_TARGET_POS_MASK or PSYS_PART_TARGET_LINEAR_MASK flag be set. [[#Caveats|caveat 4]]
{{!}}align="center"{{!}}20
{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:Particle Appearance}}"
{{!}}colspan="5" align="left"{{!}}'''Particle Appearance'''
{{!}}- id="PSYS_PART_START_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_START_COLOR
{{!!}}[[vector]] {{LSL Param|color_start}}
{{!!}}A vector specifying the [[color]] of the particles upon emission.
{{!}}align="center"{{!}}1
{{!}}- id="PSYS_PART_END_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_END_COLOR
{{!!}}[[vector]] {{LSL Param|color_end}}
{{!!}}A vector specifying the [[color]] the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_COLOR_MASK flag is set.
{{!}}align="center"{{!}}3
{{!}}- id="PSYS_PART_START_ALPHA"
{{!}}colspan="2"{{!}}PSYS_PART_START_ALPHA
{{!!}}[[float]] {{LSL Param|alpha_start}}
{{!!}}Specifies the [[alpha]] of the particles upon emission. Valid values are in the range 0.0 to 1.0. Lower values are more transparent; higher ones are more opaque.
{{!}}align="center"{{!}}2
{{!}}- id="PSYS_PART_END_ALPHA"
{{!}}colspan="2"{{!}}PSYS_PART_END_ALPHA
{{!!}}[[float]] {{LSL Param|alpha_end}}
{{!!}}Specifies the [[alpha]] the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_COLOR_MASK flag is set. Valid values are the same as PSYS_PART_START_ALPHA.
{{!}}align="center"{{!}}4
{{!}}- id="PSYS_PART_START_SCALE"
{{!}}colspan="2"{{!}}PSYS_PART_START_SCALE
{{!!}}[[vector]] {{LSL Param|scale_start}}
{{!!}}Specifies the [[scale]] or size of the particles upon emission. Valid values for each direction are 0.03125 to 4.0, in meters. The actual particle size is always a multiple of 0.03125. Smaller changes don't have any effect. Since particles are essentially 2D sprites, the Z component of the vector is ignored and can be set to 0.0.
{{!}}align="center"{{!}}5
{{!}}- id="PSYS_PART_END_SCALE"
{{!}}colspan="2"{{!}}PSYS_PART_END_SCALE
{{!!}}[[vector]] {{LSL Param|scale_end}}
{{!!}}Specifies the [[scale]] or size the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_SCALE_MASK flag is set. Valid values are the same as PSYS_PART_START_SCALE.
{{!}}align="center"{{!}}6
{{!}}- id="PSYS_SRC_TEXTURE"
{{!}}colspan="2"{{!}}PSYS_SRC_TEXTURE
{{!!}}[[string]] {{LSL Param|texture}}
{{!!}}Specifies the name of a texture in the emitter prim's inventory to use for each particle. Alternatively, you may specify an asset key [[UUID]] for a texture. If using [[llLinkParticleSystem]] and texture is not a UUID, texture must be in the emitter prim (not necessarily with the script).
{{!}}align="center"{{!}}12
{{!}}- id="PSYS_PART_START_GLOW"
{{!}}colspan="2"{{!}}PSYS_PART_START_GLOW
{{!!}}[[float]] {{LSL Param|glow_start}}
{{!!}}Specifies the glow of the particles upon emission. Valid values are in the range of 0.0 (no glow) to 1.0 (full glow).
{{!}}align="center"{{!}}26
{{!}}- id="PSYS_PART_END_GLOW"
{{!}}colspan="2"{{!}}PSYS_PART_END_GLOW
{{!!}}[[float]] {{LSL Param|glow_end}}
{{!!}}Specifies the glow that the particles transition to during their lifetime. Valid values are the same as PSYS_PART_START_GLOW.
{{!}}align="center"{{!}}27
{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:Particle Blending}}"
{{!}} colspan="5" align="left"{{!}}'''Particle Blending'''
{{!}}- style="background-color:#ffcccc;"
{{!}} colspan="5" align="left"{{!}}'''Note:''' The particle system blend parameters wrap directly to OpenGL's glBlendFunc. Detailed documentation for glBlendFunc, including formulas, can be found in the [http://www.opengl.org/sdk/docs/man/html/glBlendFunc.xhtml official glBlendFunc documentation]
{{!}}- id="PSYS_PART_BLEND_FUNC_SOURCE"
{{!}} colspan="2"{{!}}PSYS_PART_BLEND_FUNC_SOURCE
{{!!}}[[integer]] {{LSL Param|bf_source}}
{{!!}}Specifies how blending function uses the incoming particle's color and alpha information to produce the rendered result. Defaults to PSYS_PART_BF_SOURCE_ALPHA.
{{!}}align="center"{{!}}24
{{!}}- id="PSYS_PART_BLEND_FUNC_DEST"
{{!}} colspan="2"{{!}}PSYS_PART_BLEND_FUNC_DEST
{{!!}}[[integer]] {{LSL Param|bf_dest}}
{{!!}}Specifies how blending function uses the current framebuffer's color and alpha information to produce the rendered result. Defaults to PSYS_PART_BF_ONE_MINUS_SOURCE_ALPHA.
{{!}}align="center"{{!}}25
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_ONE"
{{!}}rowspan="8" style="background-color:#c0c0c0;" align="center" valign="center"{{!}}'''V a l u e s'''
{{!}}colspan="2"{{!}}PSYS_PART_BF_ONE
{{!!}}Do not scale the source or destination RGBA values.
{{!}}align="center"{{!}}{{LSL_Hex|0x0|0}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_ZERO"
{{!}}colspan="2"{{!}}PSYS_PART_BF_ZERO
{{!!}}Zero out the source or destination RGBA values.
{{!}}align="center"{{!}}{{LSL_Hex|0x1|1}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_DEST_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_BF_DEST_COLOR
{{!!}}Scale the RGBA values by the RGBA values of the destination.
{{!}}align="center"{{!}}{{LSL_Hex|0x2|2}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_SOURCE_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_BF_SOURCE_COLOR
{{!!}}Scale the RGBA values by the RGBA values of the particle source.
{{!}}align="center"{{!}}{{LSL_Hex|0x3|3}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_ONE_MINUS_DEST_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_BF_ONE_MINUS_DEST_COLOR
{{!!}}Scale the RGBA values by the inverted RGBA values of the destination.
{{!}}align="center"{{!}}{{LSL_Hex|0x4|4}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_ONE_MINUS_SOURCE_COLOR"
{{!}}colspan="2"{{!}}PSYS_PART_BF_ONE_MINUS_SOURCE_COLOR
{{!!}}Scale the RGBA values by the inverted RGBA values of the particle source.
{{!}}align="center"{{!}}{{LSL_Hex|0x5|5}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_SOURCE_ALPHA"
{{!}}colspan="2"{{!}}PSYS_PART_BF_SOURCE_ALPHA
{{!!}}Scale the RGBA values by the alpha values of the particle source.
{{!}}align="center"{{!}}{{LSL_Hex|0x7|7}}
{{!}}- style="background-color:#e0e0e0;" id="PSYS_PART_BF_ONE_MINUS_SOURCE_ALPHA"
{{!}}colspan="2"{{!}}PSYS_PART_BF_ONE_MINUS_SOURCE_ALPHA
{{!!}}Scale the RGBA values by the inverted alpha values of the particle source.
{{!}}align="center"{{!}}{{LSL_Hex|0x9|9}}
{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:Particle Flow}}"
{{!}}colspan="5" align="left"{{!}}'''Particle Flow'''
{{!}}- id="PSYS_SRC_MAX_AGE"
{{!}}colspan="2"{{!}}PSYS_SRC_MAX_AGE
{{!!}}[[float]] {{LSL Param|duration_system}}
{{!!}}Specifies the length of time, in seconds, that the emitter will operate upon coming into view range (if the particle system is already set) or upon execution of this function (if already in view range). Upon expiration, no more particles will be emitted, except as specified above. Zero will give the particle system an infinite duration. ([[#Caveats|caveat 1]])
{{!}}align="center"{{!}}19
{{!}}- id="PSYS_PART_MAX_AGE"
{{!}}colspan="2"{{!}}PSYS_PART_MAX_AGE
{{!!}}[[float]] {{LSL Param|duration_particle}}
{{!!}}Specifies the lifetime of each particle emitted, in seconds. Maximum is 30.0 seconds. During this time, the particle will appear, change appearance and move according to the parameters specified in the other sections, and then disappear.
{{!}}align="center"{{!}}7
{{!}}- id="PSYS_SRC_BURST_RATE"
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_RATE
{{!!}}[[float]] {{LSL Param|burst_sleep}}
{{!!}}Specifies the time interval, in seconds, between "bursts" of particles being emitted. Specifying a value of 0.0 will cause the emission of particles as fast as the viewer can do so.
{{!}}align="center"{{!}}13
{{!}}- id="PSYS_SRC_BURST_PART_COUNT"
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_PART_COUNT
{{!!}}[[integer]] {{LSL Param|burst_particle_count}}
{{!!}}Specifies the number of particles emitted in each "burst".
{{!}}align="center"{{!}}15
{{!}}- style="background-color:#ccffcc;" id="{{anchorencode:Particle Motion}}"
{{!}}colspan="5" align="left"{{!}}'''Particle Motion'''
{{!}}- id="PSYS_SRC_ACCEL"
{{!}}colspan="2"{{!}}PSYS_SRC_ACCEL
{{!!}}[[vector]] {{LSL Param|acceleration}}
{{!!}}Specifies a directional acceleration vector applied to each particle as it is emitted, in meters per second squared. Valid values are 0.0 to 100.0 for each direction both positive and negative, as [[Viewer coordinate frames#Region|region]] coordinates.
{{!}}align="center"{{!}}8
{{!}}- id="PSYS_SRC_OMEGA"
{{!}}colspan="2"{{!}}PSYS_SRC_OMEGA
{{!!}}[[vector]] {{LSL Param|omega}}
{{!!}}Specifies the rotational spin of the emitter in radians per second along each axis. This "unsticks" the emitter facing from the prim's positive Z axis and is noticeable in directional presentations. Prim spin (via [[llTargetOmega]]) has no effect on emitter spin. ([[#Caveats|caveat 2]] and [[#Caveats|caveat 3]])
{{!}}align="center"{{!}}21
{{!}}- id="PSYS_SRC_BURST_SPEED_MIN"
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_SPEED_MIN
{{!!}}[[float]] {{LSL Param|speed_min}}
{{!!}}Specifies the minimum value of a random range of values which is selected for each particle in a burst as its initial speed upon emission, in meters per second. Note that the value of this parameter and PSYS_SRC_BURST_SPEED_MAX are internally re-ordered such that this parameter gets the smaller of the two values.
{{!}}align="center"{{!}}17
{{!}}- id="PSYS_SRC_BURST_SPEED_MAX"
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_SPEED_MAX
{{!!}}[[float]] {{LSL Param|speed_max}}
{{!!}}Specifies the maximum value of a random range of values which is selected for each particle in a burst as its initial speed upon emission, in meters per second. Note that the value of this parameter and PSYS_SRC_BURST_SPEED_MIN are internally re-ordered such that this parameter gets the larger of the two values.
{{!}}align="center"{{!}}18
{{!}}-



{{!}}-
{{!}}} }}
}}<noinclude>
{{#var:constants_nb}}
</noinclude>{{#if:

}}<noinclude>

====Signature====
{{#tag:pre|{{#var:signature}}}}

</noinclude>{{#if:

}}

User:Toy Wylie/Misc/Script Memory

2014-03-31T22:51:25Z

Kizmut Smit: +cat :3

This is an example on why Script Memory Reporters are a bad thing and can't provide the information a land owner is looking for. Banning or kicking people because of the reported script memory size is not helping the case. What we really need is an accurate reporting tool that does not rely on scripts playing nice but reports the true facts regardless of how the script was made.

===Some Myths and Facts===
'''Myth:''' Mono scripts are much larger! They show as 64k on my reporter, while LSO scripts only need 16k

'''Fact:''' This is inaccurate. It is true that a Mono script needs more memory for the same source code size. However, an LSO script always allocates and uses the full 16k it gets, while a Mono script only uses what it needs, in 4k blocks. And since a lot of scripts are usually very small helper scripts, the memory consumption of Mono scripts is actually lower than LSO:

<lsl>// This standard door script takes up 4412 bytes in Mono
// and 16384 bytes in LSO. An outside script reporting tool
// would report it as 65536 bytes in Mono and 16384 in LSO.

rotation home;
integer isOpen=FALSE;

open()
{
if(isOpen)
llSetLocalRot(home);
else
{
home=llGetLocalRot();
llSetLocalRot(home*llEuler2Rot(<0.0,0.0,90.0>*DEG_TO_RAD));
}
isOpen=!isOpen;
}

default
{
touch_start(integer total_number)
{
llOwnerSay((string) llGetUsedMemory());
open();
}
}
</lsl>

Using the new [[llSetMemoryLimit]] function we can make the situation a little bit better:

<lsl>// This modified standard door script takes up 4924 bytes in Mono
// and 16384 bytes in LSO. An outside script reporting tool
// would report it as 5000 bytes in Mono and 16384 in LSO.

rotation home;
integer isOpen=FALSE;

open()
{
if(isOpen)
llSetLocalRot(home);
else
{
home=llGetLocalRot();
llSetLocalRot(home*llEuler2Rot(<0.0,0.0,90.0>*DEG_TO_RAD));
}
isOpen=!isOpen;
}

default
{
state_entry()
{
llSetMemoryLimit(5000);
}

touch_start(integer total_number)
{
llOwnerSay((string) llGetUsedMemory());
open();
}
}
</lsl>

But this is only good for static scripts like this one. If your script uses a lot of memory for a short period of time and most of the remaining time sits idle with little to no memory usage, this approach will not work at all. And having to manually re-set the memory limit for each part of the script adds more code and more ways for it to fail.

{{Resource Conservation Portal Nav|cat=memory}}

Category:Process-Time Conservation

2014-03-31T22:47:17Z

Kizmut Smit: +LSL cat

[[Category:LSL Resource Conservation]]
{{LSL Header|ml=*}}{{LSLC|}}

Category:LSL Resource Conservation

2014-03-31T22:46:59Z

Kizmut Smit: +LSL cat

[[Category:Simulator Resource Conservation]]
{{LSL Header|ml=*}}{{LSLC|}}

Category:Memory Conservation

2014-03-31T22:45:53Z

Kizmut Smit: -/+cat/cat templates

[[Category:LSL Resource Conservation]]
{{LSL Header|ml=*}}{{LSLC|}}

Category:LSL Script Profiler

2014-03-31T22:43:25Z

Kizmut Smit: +cat

User:Becky Pippen/Memory Efficiency

2014-03-31T22:39:30Z

Kizmut Smit: +cat :3

== Information Content and Memory Efficiency ==

For a refresher on relevant information theory, see [http://www.cs.cmu.edu/~dst/Tutorials/Info-Theory/ this tutorial].

It's useful to understand the "information content" of data so that you can calculate
the theoretical minimum number of bits needed to store the data. Typically it's the
logarithm base two of the total number of possible values the data can have. Here are
some examples:

* coin toss: log2(2) = 1 bit per toss
* 6-sided die toss: log2(6) = 2.585 bits per toss
* integers 0 through 100: log2(101) = 6.66 bits each
* 32-bit integers, non-negative values: log2(2147483648) = 31 bits each
* 32-bit integers, all possible values: log2(4294967296) = 32 bits each

The actual memory space used by various LSL data types can be found here:
* [http://lslwiki.net/lslwiki/wakka.php?wakka=MemoryUsage LSL Memory Usage in lswiki.net]
* [[LSL_Script_Memory|Script memory usage in wiki.secondlife.com]]

The memory efficiency is simply the information content divided by the actual memory used. Here are some examples:

==== Example #1 - 7-bit ASCII text ====

In classic LSO (the old LSL compiler), it takes one byte of memory (8 bits) to hold one 7-bit ASCII character
for an efficieny of 7/8 = 88%. In Mono, it takes two bytes (16 bits) to hold each ASCII character for an efficiency
of 7/16 = 44%.

==== Example #2 - Vectors in a global list ====

The information content of a vector is the equivalent of three floats, or 3 * 32 bits = 96 bits per vector.
A list in Mono consumes 224 bits for each vector element for an efficiency of 96 / 224 = 43%. Note that if you only
need to store a smaller range of values in each vector component, the information content will be smaller.
For example, suppose you need to store a color vector with two decimal digits of accuracy for each component.
In other words, instead of precision like <0.567876, 0.198273, 0.993656>, it's sufficient for your purposes if
the data gets rounded off to <0.57, 0.20, 0.99>. In that case, each of the three components can take
one of 101 possible values (0.00 through 1.00 with 0.01 resolution), and the information content is
then 3 * log2(101) = 20 bits. If regular vectors are stored in a list, the efficiency would drop to 20 / 224 = 9%. Ouch.

==== Example #3 - UUIDs in a global list ====

The information content of a UUID is 128 bits. In a global list in Mono, each key takes up to 106 bytes (848 bits)
for an efficiency of 128 / 848 = 15%. Suppose your script needs to store
up to 1000 avatar UUIDs in a global list. That's going to use up 1000*106 bytes = 106,000 bytes, more than
the memory available to a single Mono script. However, since each UUID contains only 16 bytes (128 bits)
of information, the theoretical minimum memory requirement would be 1000*16 = 16000 bytes, well within
the capacity of a Mono script.

===Now what?===

Now that you know the minimum amount of memory needed and the amount actually used, you can
make realistic goals for reducing memory usage. For some suggestions for specific scripting techniques,
see [[User:Becky_Pippen/Script_Memory_Limits| this checklist of things you can do]].

{{Resource Conservation Portal Nav|cat=memory}}

User:Becky Pippen/Script Memory Limits

2014-03-31T22:38:19Z

Kizmut Smit: +cat :3

== Script Memory Limits ==
Oh No! LSL script memory limits are coming! What to do?

Don't panic. [[User:Becky_Pippen/Memory_Limits_FAQ|'''See this FAQ''']], then see the strategy and checklist below and do what you need to do.

==Strategy==

To reduce script memory usage, start with the big items
first before tweaking individual lines of code. Sorry, I'm not impressed if you save
a dozen bytes through some clever rearrangement
of a formula here or a statement there. First see if you can eliminate entire scripts or whack off
''thousands'' of bytes all at once by using a different approach or algorithm,
or by removing that one memory-hungry feature, or by using a different
data storage format. Then review the checklist below for more ideas.

==Checklist==

# '''Measure''' - For help measuring the memory your script uses, see [[User:Becky_Pippen/Measure_Script_Memory_Usage|this page]].
# '''Requirements and goals''' - Do you know how efficiently your data currently uses memory? Do you know how much improvement is possible? For suggestions, see [[User:Becky_Pippen/Memory_Efficiency|this page about measuring information content and memory efficiency]].
# '''Scripts in child prims''' - If your object uses multiple scripts to detect changes in child prims, or for resizing or retexturing all the prims in a linkset (like some hair or shoes), see [[User:Becky_Pippen/New_LSL_Functions|the new LSL functions]] to reduce this to a single script.
# '''Hashing''' - Does your script need to remember lots of avatar names, keys, or other identifying information? If so, [[User:Becky_Pippen/Hashing|consider storing hashes of the data instead]].
# '''Strings/Text''' - If your script contain a large number of strings for error messages or help text, perhaps in multiple languages, see [[User:Becky_Pippen/Text_Storage| these suggestions for storing text data]].
# '''Numeric data''' - If your script needs to store long lists of numeric data, see [[User:Becky_Pippen/Numeric_Storage|these suggestions for storing numeric data]].

{{Resource Conservation Portal Nav|cat=memory}}

Code Racer

2014-03-13T01:31:42Z

Kizmut Smit: +cat

{{LSL Header}}

= Introduction =

'''Q: Want to see if one version of code usually runs faster than another?'''

'''A:''' Run your code inside a test harness such as the example code here to race two or more versions time and again. Along the way, declare the winners, measuring each win by the change in the [[llGetTime]] dilated script time.

= Sample Results =

<pre>

Click Running = No to stop this script after you've seen enough ...
2007-10-25T02:33:12.806088Z

~4.237066 ms elapsed in version 1 to place at 1 by 8 of 10 votes
~10.047700 ms elapsed in version 2 to place at 2 by 8 of 10 votes
2007-10-25T02:33:15.009855Z

~3.089838 ms elapsed in version 1 to place at 1 by 44 of 100 votes
~5.549734 ms elapsed in version 2 to place at 2 by 57 of 100 votes
2007-10-25T02:33:35.422763Z

~1.333064 ms elapsed in version 1 to place at 1 by 55 of 100 votes
~3.434490 ms elapsed in version 2 to place at 2 by 64 of 100 votes
2007-10-25T02:33:56.083810Z

~0.760552 ms elapsed in version 1 to place at 1 by 49 of 100 votes
~1.922230 ms elapsed in version 2 to place at 2 by 63 of 100 votes
2007-10-25T02:34:16.564139Z

~1.981575 ms elapsed in version 1 to place at 1 by 481 of 1000 votes
~5.013962 ms elapsed in version 2 to place at 2 by 597 of 1000 votes
2007-10-25T02:37:40.371221Z

~1.475276 ms elapsed in version 1 to place at 1 by 498 of 1000 votes
~3.177954 ms elapsed in version 2 to place at 2 by 596 of 1000 votes
2007-10-25T02:41:07.869815Z

~0.773118 ms elapsed in version 1 to place at 1 by 467 of 1000 votes
~1.858705 ms elapsed in version 2 to place at 2 by 597 of 1000 votes
2007-10-25T02:44:25.003959Z
</pre>

= Code =

<lsl>
// Race a few version of code in dilated script time as measured by llGetTime.
// http://wiki.secondlife.com/wiki/Code_Racer

// List every runnable version.

list theRunners = [0, 1, 2];

// Count runnable versions.

integer theRunnable;

// Count votes to place.

list theVotes;

// Sum the run times observed.

list theSums;

// Count the races that ran without time running backwards.

integer theAverageable;

// Race no code alongside the other code in order to measure overhead.

runner0()
{
}

// Race a few versions of code.

runner1()
{
integer spinning;
for (spinning = 0; spinning < 25; ++spinning)
;
}

runner2()
{
integer spinning;
for (spinning = 0; spinning < 50; ++spinning)
;
}

runner3()
{
}

runner4()
{
}

runner5()
{
}

// Run the chosen runner once.
// Run thru an equal time while choosing any runner.

run(integer runner)
{
if (runner == 0) { runner0(); }
if (runner == 1) { runner1(); }
if (runner == 2) { runner2(); }
if (runner == 3) { runner3(); }
if (runner == 4) { runner4(); }
if (runner == 5) { runner5(); }
}

// Start up.

startup()
{
llOwnerSay("");
llOwnerSay("Click Running = No to stop this script after you've seen enough ...");
llOwnerSay(llGetTimestamp());
}

// Measure the race in calendar time elapsed since the minute began,
// if called in place of llGetTime.
//
// Note: "YYYY-MM-DDThh:mm:ss.ff..fZ" = llGetTimestamp();
// Note: 17 = 0 + llStringLength("YYYY-MM-DDThh:mm:")
// Note: -2 = -1 - llStringLength("Z")

float getTime()
{
return (float) llGetSubString(llGetTimestamp(), 17, -2); // "ss.ff..f"
}

// Race the runners and return the times when each ran.
// Run in llGetTime dilated script time or in getTime calendar time.

list eachRunnerRun()
{
list befores = [];
integer runnablePlus = theRunnable + 1;
integer running;
for (running = 0; running < runnablePlus; ++running)
{
integer running = llList2Integer(theRunners, running);
befores += llGetTime(); // choose script llGetTime or calendar getTime here
run(running);
}
return befores;
}

// Return elapsed run time per runner,
// else return [] if time ran backwards.

list getRuntimesElseNone(list befores)
{
list runtimes = [];
float before = llList2Float(befores, 0);
integer timing;
for (timing = 0; timing < theRunnable; ++timing)
{
float after = llList2Float(befores, timing + 1);
float runtime = after - before;
if (runtime < 0.0) return [];
runtimes += runtime;
before = after;
}
return runtimes;
}

// Add to a listed float.

list addFloat(list sums, integer index, float addition)
{
list results = [];
integer summable = llGetListLength(sums);
integer summing;
for (summing = 0; summing < summable; ++summing)
{
float result = llList2Float(sums, summing);
if (index == summing)
{
result += addition;
}
results += result;
}
return results;
}

// Add to a listed integer.

list addInteger(list sums, integer index, integer addition)
{
list results = [];
integer summable = llGetListLength(sums);
integer summing;
for (summing = 0; summing < summable; ++summing)
{
integer result = llList2Integer(sums, summing);
if (index == summing)
{
result += addition;
}
results += result;
}
return results;
}

// Race the runners once, vote to place, and sum run time per runner.

runRace()
{

// Race the runners once.

list runtimes = getRuntimesElseNone(eachRunnerRun());
// llOwnerSay("[" + llDumpList2String(runtimes, ", ") + "] == runtimes");

// Sort the runtimes into places.

list places = llListSort(runtimes, 1, TRUE); // sort least to most
integer placeable = llGetListLength(places); // 0 or theRunnable

// Sum run time per runner.

integer adding;
for (adding = 0; adding < placeable; ++adding)
{
integer running = llList2Integer(theRunners, adding);
float runtime = llList2Float(runtimes, adding);
theSums = addFloat(theSums, running, runtime);
++theAverageable;

// Vote to place at each equal runtime.

integer placing;
for (placing = 0; placing < placeable; ++placing)
{
float placed = llList2Float(places, placing);
if (runtime == placed)
{
integer flat = (running * placeable) + placing;
theVotes = addInteger(theVotes, flat, 1);
}
}
}
}

// Start up a burst of races.

zeroBurst()
{
theSums = theVotes = [];
theRunnable = llGetListLength(theRunners);
integer placing;
for (placing = 0; placing < theRunnable; ++placing)
{
theSums += 0.0;
integer running;
for (running = 0; running < theRunnable; ++running)
{
theVotes += 0;
}
}
}

// Report a burst of races.

reportBurst(integer scaling)
{

// Consider each place.

integer placing;
for (placing = 0; placing < theRunnable; ++placing)
{
list votes = llList2ListStrided(llList2List(theVotes, placing, -1), 0, -1, theRunnable);
integer winner = llList2Integer(llListSort(votes, 1, TRUE), -1);

// Find the winner (or the winners) of that place.

integer running;
for (running = 1; running < theRunnable; ++running)
{
integer vote4place = llList2Integer(votes, running);
if (vote4place == winner)
{

// Describe a winner.

float summed = llList2Float(theSums, running) - llList2Float(theSums, 0);
float average = 1000.0 * (summed / theAverageable);

llOwnerSay("~" +
(string) average + " ms elapsed in version " + (string) running +
" to place at " + (string) placing +
" by " + (string) vote4place + " of " + (string) scaling + " votes"
);
}
}
}
}

// Run a few bursts of races at each scale, for indefinitely increasing scale.

runRaceRepeatedly()
{
integer scaleable = 10;
integer repeatable = 2; // decide how often to repeat the first burst
while (TRUE)
{
integer repeating;
for (repeating = 0; repeating < repeatable; ++repeating)
{
zeroBurst();

integer scaling;
for (scaling = 0; scaling < scaleable; ++scaling)
{
runRace();
theRunners = llList2List(theRunners, -1, -1) + llList2List(theRunners, 0, -2);
}

llOwnerSay("");
reportBurst(scaling);
llOwnerSay((string) llGetRegionTimeDilation() + " dilation @ " + llGetTimestamp());
}

scaleable *= 10;
repeatable = 3; // decide how often to repeat the other bursts
}
}

// Race to measure relative run-time cost of multiple versions of code.
// Produce unreasonable answers when the run-time cost measured equals or exceeds 60 seconds.

default
{
state_entry()
{
startup();
runRaceRepeatedly();
}
}
</lsl>

= Instructions =

This instrument quickly & accurately measures the run time difference between a number of fragments of code. For example, the code presented here measures the difference between the two fragments of code found inside the functions named runner1 and runner2. To measure other code, insert the code you want to compare into the runner1, runner2, runner3, etc. functions. See the source line that assigns [0, 1, 2] to theRunners? List all the runners you want to run there. Leave runner0 empty so that the harness correctly measures and subtracts out its own overhead.

= Alternatives & Caveats =

This instrument compares run times quickly, like 100X faster than the Efficiency Tester instrument. This instrument runs a number of fragments of code at a time, gives you immediate results and then progressively more accurate results over time, like when you slowly fetch a detailed image from the web. This instrument burns thru hugely much run time, so that it can provide immediate feedback to make work proceed when the work would otherwise be too hard & boring to attract enough volunteers.

The [[Efficiency Tester]] instrument serves a different purpose. That instrument adds accuracy to a measure of a range of observed run times in as little time as possible. By simple arithmetic, running thru 200ms for 1,000 times necessarily takes at least 200s, aka, more than 3 minutes. That instrument runs one fragment of code at a time, but then runs that fragment many many times to try and average out any distractions that may hit the server during the run. That instrument actually can measure 200ms in as little as 10 minutes, but that instrument gives you no answer at all until after 10,000 runs and no final answer until after 30,000 runs.

See the [[LSL Script Efficiency]] article for much discussion of the Efficiency Tester instrument, including recommendations on how to avoid distracting the server into spending run time running other code in parallel. Those same recommendation apply to any llGetTimestamp harness, including this instrument.

Please do try to find deserted places to run such benchmarks and remember to turn them off when you finish! Else naturally you'll be rudely lagging the sim for the other people sharing the sim with you, for however long you run the benchmark.

= See Also =

'''Functions'''

[[llGetTime]] - fetch the (often zeroed) dilated time in seconds and fractional seconds

[[llGetTimestamp]] - fetch the ISO 8601 "YYYY-MM-DDThh:mm:ss.ff..fZ" string that names the calendar date and time that is now

'''Scripts'''

[[Code Sizer]] - count bytes of code with perfect accuracy

[[Efficiency Tester]] - run as long as you please to count approximate milliseconds of run time with every more accuracy

{{Resource Conservation Portal Nav|cat=process}}
{{LSLC|Library}}{{LSLC|Examples}}

LSL Constants vs Globals

2014-03-13T01:20:16Z

Kizmut Smit: Replaced cat w nav

There are some advantages in using global variables over the string and key constants when programming in [[LSO]]; it's faster and uses less bytecode when it is longer than 3 characters and is used more than twice, but it uses more bytecode when it is shorter than 3 characters or is used once. This is easily demonstrated by running the scripts in Figure 1.

However, this is only true for [[LSO]] compiled programs. If [[Mono]] is used, then the opposite is true and it uses less memory to use constants. Mono uses only one copy of a constant in memory. In the scripts in Figure 1, using constants saves the memory used to initialize the variable null_key. This is true if LL constants (like NULL_KEY) are used or if user supplied strings (such as "this is a string") are used.

===Pros when using LSO===
* Faster
* Uses less bytecode when it is longer than 3 characters and it used more than twice.

===Cons===
* User can accidentally change the value.
* Uses more bytecode when it is shorter than 3 characters or it used once.

{| {{Prettytable|style=margin-top:0;}}
|+ Figure 1: Bytecode Cost
|- {{Hl2}}
! Constant
! Global
|- valign="top"
|
<lsl>

dead(){
key a = NULL_KEY;
key b = NULL_KEY;
key c = NULL_KEY;
key d = NULL_KEY;
}

default {
state_entry() {
llOwnerSay((string) llGetFreeMemory());
}
}</lsl>
|
<lsl>key null_key = NULL_KEY;

dead(){
key a = null_key;
key b = null_key;
key c = null_key;
key d = null_key;
}

default {
state_entry() {
llOwnerSay((string) llGetFreeMemory());
}
}</lsl>
|}

{{Resource Conservation Portal Nav|cat=memory}}
[[Category:LSL]]

Template:Resource Conservation Portal Nav/doc

2014-03-13T01:16:30Z

Kizmut Smit: making categories adaptable as pages are consolidated

Resource Conservation Portal Navigation box.

Usage:<nowiki>{{Resource Conservation Portal Nav|cat=memory}}</nowiki>
Result: {{Resource Conservation Portal Nav|cat=memory}}

Template:Resource Conservation Portal Nav

2014-03-13T01:16:21Z

Kizmut Smit: start:placeholder for resource nav

<onlyinclude>
{{#switch:{{{cat|}}}
|memory = [[Category:Memory Conservation]]
|process = [[Category:Process-Time Conservation]]
|client = [[Category:Client Resource Conservation]]
|[[Category:Performance and stability]]
}}</onlyinclude><noinclude>

{{{{PAGENAME}}/doc}} [[Category:KB Templates]]</noinclude>

Category:Script Resource Conservation

2014-03-12T23:33:34Z

Kizmut Smit: No LSL prefix

Category:Process-Time Conservation

2014-03-12T23:32:26Z

Kizmut Smit: LSL cat prefix

[[Category:LSL Resource Conservation]]

Category:LSL Resource Conservation

2014-03-12T23:31:41Z

Kizmut Smit: +cat cat

[[Category:Simulator Resource Conservation]]

Category:Memory Conservation

2014-03-12T23:27:16Z

Kizmut Smit: lsl prefix

[[Category:LSL Resource Conservation]]
[[Category:LSL Memory]]
[[Category:LSL]]

User:Kizmut Smit/ClientAssetKeys

2014-03-12T23:16:04Z

Kizmut Smit: start clientassetkeys

Textures
Environment, Avatar, General UI, Inventory, Map, Find, Movement Controls, Edit Mode, Misc
Animations
Sounds

==Textures==
===Environment===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|alpha_gradient.tga||e97cf410-8e61-7005-ec06-629eba4cd1fb||Used for generating the texture for the ground dynamically. Also used for creating the "invisiprim" that hides avatars, prims with alpha values less than 1.0 and particle effects
|-
|alpha_gradient_2d.tga||38b86f85-2575-52a9-a531-23108d8da837||Used for generating the texture for the ground dynamically. Also used for creating the "invisiprim" that hides avatars, prims with alpha values less than 1.0 and particle effects
|-
|collision texture||35f217a3-f618-49cf-bbca-c86d486551a9||Sprite used to generate collision visual effect.
|-
|grass_texture_1.tga||79504bf5-c3ec-0763-6563-d843de66d0a1
|-
|grass_texture_2.tga||6c4727b8-ac79-ba44-3b81-f9aa887b47eb
|-
|grass_texture_3.tga||99bd60a2-3250-efc9-2e39-2fbcadefbecc
|-
|grass_texture_4.tga||7a2b3a4a-53c2-53ac-5716-aac7d743c020
|-
|noentrylines.tga||5d3e196b-fd4d-ada7-e4c1-99f8e9f1cfbf||Red "No entry of property" lines.
|-
|noentrypasslines.tga||ac8f8627-6a30-8da8-d4bd-958668eea7a0||Green "No entry of property, except with pass" lines.
|-
|propertyline.tga||e3548c46-8d5e-03da-fcab-4fc36ad818bb||Semi-transparent texture overlayed on the ground along the borders of a property when View>Show Property Lines is active.
|-
|terrain_dirt.tga||b8d3965a-ad78-bf43-699b-bff8eca6c975||Ground texture.
|-
|terrain_dirt_detail.tga||0bc58228-74a0-7e83-89bc-5c23464bcec5||Hi-res ground texture.
|-
|terrain_grass.tga||abb783e6-3e93-26c0-248a-247666855da3||Ground texture.
|-
|terrain_grass_detail.tga||63338ede-0037-c4fd-855b-015d77112fc8||Hi-res ground texture.
|-
|terrain_mountain.tga||179cdabd-398a-9b6b-1391-4dc333ba321f||Ground texture.
|-
|terrain_mountain_detail.tga||303cd381-8560-7579-23f1-f0a880799740||Hi-res ground texture.
|-
|terrain_rock.tga||beb169c7-11ea-fff2-efe5-0f24dc881df2||Ground texture.
|-
|terrain_rock_detail.tga||53a2f406-4895-1d13-d541-d2e3b86bc19c||Hi-res ground texture.
|-
|tree_beach_grass_1.tga||18fb888b-e8f1-dce7-7da7-321d651ea6b0
|-
|tree_cypress_1.tga||fb2ae204-3fd1-df33-594f-c9f882830e66
|-
|tree_cypress_2.tga||30047cec-269d-408e-0c30-b2603b887268
|-
|tree_dogwood.tga||64367bd1-697e-b3e6-0b65-3f862a577366
|-
|tree_eelgrass.tga||96b4de31-f4fa-337d-ec78-451e3609769e
|-
|tree_eucalyptus.tga||a6162133-724b-54df-a12f-51cd070ad6f3
|-
|tree_fern.tga||8872f2b8-31db-42d8-580a-b3e4a91262de
|-
|tree_kelp_1.tga||2caf1179-7861-6ff3-4b7d-46e17780bdfa
|-
|tree_kelp_2.tga||2a4880b6-b7a3-690a-2049-bfbe38eafb9f
|-
|tree_oak.tga||8a515889-eac9-fb55-8eba-d2dc09eb32c8
|-
|tree_palm_1.tga||ca4e8c27-473c-eb1c-2f5d-50ee3f07d85c
|-
|tree_palm_2.tga||2d784476-d0db-9979-0cff-9408745a7cf3
|-
|tree_pine_1.tga||0187babf-6c0d-5891-ebed-4ecab1426683
|-
|tree_pine_2.tga||d691a01c-13b7-578d-57c0-5caef0b4e7e1
|-
|tree_plumeria.tga||6de37e4e-7029-61f5-54b8-f5e63f983f58
|-
|tree_sea_sword.tga||5894e2e7-ab8d-edfa-e61c-18cf16854ba3
|-
|tree_tropical_1.tga||5bc11cd6-2f40-071e-a8da-0903394204f9
|-
|tree_tropical_2.tga||cdd9a9fc-6d0b-f90d-8416-c72b6019bca8
|-
|undergrowth_1.tga||8f458549-173b-23ff-d4ff-bfaa5ea2371b
|-
|water||2bfd3884-7e27-69b9-ba3a-3e673f680004||Semi-transparent blue texture shown on the surface of water.
|-
|winter_tree_aspen.tga||7c0cf89b-44b1-1ce2-dd74-07102a98ac2a
|-
|winter_tree_pine_1.tga||10d2a01a-0818-84b9-4b96-c2eb63256519
|-
|winter_tree_pine_2.tga||67931331-0c02-4876-1255-28770896c6a2
|}

===Avatar===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|silhouette.tga||da5d4079-7819-6b53-d2a4-dc9929381d7d||The constant shadow cast by the avatar's feet?
|-
|avatar_thumb_bkgrnd.tga||3a7f4f0d-be14-ee78-29e3-fc8b0b2a68d3
|-
|eyes.tga||6522e74d-1660-4e7f-b601-6f48c1659a77
|-
|hair.tga||7ca39b4c-bd19-4699-aff7-f93fd03d3e7b
|-
|pixiesmall.tga||168e6813-096e-07ea-97ae-fd416826f627||The particle texture used as both the default texture for particles and for avatar editing beams.
|}

===General UI===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|button_disabled_32x128.tga||f8124d60-2875-c358-7847-2acb63e5400c
|-
|button_enabled_32x128.tga||d8faf8cb-ee6e-b0b5-abd9-bde873ad3461
|-
|button_enabled_selected_32x128.tga||1eddba75-b682-110a-104e-6cdcce616a25
|-
|cam_rotate_in.tga||70bf2262-3eed-4996-88ac-076907e8921d
|-
|cam_rotate_out.tga||88745b46-da05-11d5-8ac0-0003477c4611
|-
|cam_tracking_in.tga||fe2fc73b-5a64-4a8e-aacc-46fa81faf96a
|-
|cam_tracking_out.tga||95c4ea0e-e3c2-4904-b847-7d7676139ebb
|-
|cam_zoom_minus_in.tga||deed3f4b-93e9-4183-a3b0-a5a98a6de1bb
|-
|cam_zoom_out.tga||bb02e941-cb3b-4dd3-892a-6841b5de6e45
|-
|cam_zoom_plus_in.tga||c7aefd32-ce13-4242-82cc-2631d44ff9d3
|-
|checkbox_disabled_false.tga||7d94cb59-32a2-49bf-a516-9e5a2045f9d9
|-
|checkbox_disabled_true.tga||c817c642-9abd-4236-9287-ae0513fe7d2b
|-
|checkbox_enabled_false.tga||05bb64ee-96fd-4243-b74e-f40a41bc53ba
|-
|checkbox_enabled_true.tga||cf4a2ed7-1533-4686-9dde-df9a37ddca55
|-
|closebox.tga||47a8c844-cd2a-4b1a-be01-df8b1612fe5d
|-
|close_in_blue.tga||e5821134-23c0-4bd0-af06-7fa95b9fb01a
|-
|close_inactive_blue.tga||779e4fa3-9b13-f74a-fba9-3886fe9c86ba
|-
|combobox_arrow.tga||b31c1335-0e9c-4927-bc90-53277777d9c1
|-
|crosshairs.tga||6e1a3980-bf2d-4274-8970-91e60d85fb52||Texture for the mouselook crosshairs.
|-
|minimize.tga||34c9398d-bb78-4643-9633-46a2fa3e9637
|-
|minimize_inactive.tga||6e72abba-1378-437f-bf7a-f0c15f3e99a3
|-
|minimize_pressed.tga||39801651-26cb-4926-af57-7af9352c273c
|-
|notify_box_icon.tga||b2ef2d31-9714-a07b-6ca7-31638166364b
|-
|notify_next.tga||07d0ea4c-af0c-aad1-dbbf-c24020ff2b80
|-
|notify_tip_icon.tga||74ba3584-58ea-9984-5b76-62d37942ab77
|-
|radio_active_false.tga||7a1ba9b8-1047-4d1e-9cfc-bc478c80b63f
|-
|radio_active_true.tga||52f09e07-5816-4052-953c-94c6c10479b7
|-
|radio_inactive_false.tga||90688481-67ff-4af0-be69-4aa084bcad1e
|-
|radio_inactive_true.tga||1975db39-aa29-4251-aea0-409ac09d414d
|-
|resize_handle_bottom_right_blue.tga||e3690e25-9690-4f6c-a745-e7dcd885285a
|-
|restore.tga||111b39de-8928-4690-b7b2-e17d5c960277
|-
|restore_inactive.tga||0eafa471-70af-4882-b8c1-40a310929744
|-
|restore_pressed.tga||90a0ed5c-2e7b-4845-9958-a64a1b30f312
|-
|scrollbutton_down_in_blue.tga||d2421bab-2eaf-4863-b8f6-5e4c52519247
|-
|scrollbutton_down_out_blue.tga||b4ecdecf-5c8d-44e7-b882-17a77e88ed55
|-
|scrollbutton_left_in_blue.tga||ea137a32-6718-4d05-9c22-7d570d27b2cd
|-
|scrollbutton_left_out_blue.tga||43773e8d-49aa-48e0-80f3-a04715f4677a
|-
|scrollbutton_right_in_blue.tga||b749de64-e903-4c3c-ac0b-25fb6fa39cb5
|-
|scrollbutton_right_out_blue.tga||3d700d19-e708-465d-87f2-46c8c0ee7938
|-
|scrollbutton_up_in_blue.tga||a93abdf3-27b5-4e22-a8fa-c48216cd2e3a
|-
|scrollbutton_up_out_blue.tga||dad084d7-9a46-452a-b0ff-4b9f1cefdde9
|-
|spin_down_in_blue.tga||a985ac71-052f-48e6-9c33-d931c813ac92
|-
|spin_down_out_blue.tga||b6d240dd-5602-426f-b606-bbb49a30726d
|-
|spin_up_in_blue.tga||c8450082-96a0-4319-8090-d3ff900b4954
|-
|spin_up_out_blue.tga||56576e6e-6710-4e66-89f9-471b59122794
|-
|square_btn_32x128.tga||b28df901-6b8d-d31c-7903-4eb9676d4bfc
|-
|square_btn_selected_32x128.tga||c48c9e95-191b-96d3-08b2-6e8ada58b651
|-
|startup_logo.tga||66864f3c-e095-d9c8-058d-d6575e6ed1b8
|-
|status_build.tga||175a6b75-45c9-c2c2-4765-bf37a3909b53||No-build land status symbol.
|-
|status_busy.tga||beb0d821-6725-abdf-032d-1f70cdabde82||Busy mode symbol.
|-
|status_fly.tga||0e058115-5b8f-c3d7-dcaa-9623d92885d1||No-fly land status symbol.
|-
|status_health.tga||4330e8ce-b39b-1eb8-c2ec-a97c0b3947b5||Health-enabled area symbol.
|-
|status_money.tga||5863eb7a-1546-6501-533a-6061f73a36b7||L$ symbol.
|-
|status_scripts.tga||4cc1afcd-04dd-178f-e074-0f9dc730ab45||No-scripts land status symbol.
|-
|tab_bottom_blue.tga||bf0a8779-689b-48c3-bb9a-6af546366ef4
|-
|tab_bottom_selected_blue.tga||c001d8fd-a869-4b6f-86a1-fdcb106df9c7
|-
|tab_left.tga||1097dcb3-aef9-8152-f471-431d840ea89e
|-
|tab_left_selected.tga||bea77041-5835-1661-f298-47e2d32b7a70
|-
|tab_top_blue.tga||1ed83f57-41cf-4052-a3b4-2e8bb78d8191
|-
|tab_top_selected_blue.tga||16d032e8-817b-4368-8a4e-b7b947ae3889
|}

===Inventory===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!Filename
!UUID
!Description
|-
|button_anim_pause.tga||db2d9c2d-0bbd-21e2-e83a-103ea2def7a8
|-
|button_anim_pause_selected.tga||ad65d67a-777b-fbfa-693d-4bdcfca2acca
|-
|button_anim_play.tga||2a7f6738-5d82-2ff3-d419-30ed09cbb72b
|-
|button_anim_play_selected.tga||119c37bb-24af-45fe-ae11-3a6bc3c85138
|-
|button_anim_stop.tga||e10c9e36-d9f6-c8b4-de96-557dccce9205
|-
|button_anim_stop_selected.tga||b8c0e0aa-2771-439e-c919-d2f5dad69a1c
|-
|container_animation.tga||c4e657a1-4c86-0159-2da0-32ff948484e6
|-
|container_bodypart.tga||770cb2df-758d-34d5-36c7-e3de06db5b5d
|-
|container_clothing.tga||dd90406f-4c8f-a3f9-41df-d562f94f09e0
|-
|container_gesture.tga||59cd31c0-2791-3c48-f740-f0a36c68653e||If a gesture is dragged out of inventory onto the ground, it appears contained in a cube with this texture applied to it.
|-
|container_landmark.tga||24c63386-04f7-ce6f-4ff2-dfb215d2e21f||If a landmark is dragged out of inventory onto the ground, it appears contained in a cube with this texture applied to it.
|-
|container_many_things.tga||849d3292-d9fa-7186-5465-dd7b5fc1ec48||If multiple inventory items (or a folder is) are selected, and dragged on to the ground, they appear in the contents of a cube with this texture applied to it.
|-
|container_object.tga||ad887ae1-2bee-f2c9-6786-5599de3c95c4
|-
|container_script.tga||b93bd494-c4bd-bcdf-4a59-35a9497d03f3||If a script is dragged out of inventory onto the ground, it appears contained in a cube with this texture applied to it.
|-
|container_sound.tga||5ddea031-cfa3-2776-43e3-c7146c1b4cd6||If a sound is dragged out of inventory onto the ground, it appears contained in a cube with this texture applied to it.
|-
|container_texture.tga||b3f95caf-bd62-bef3-0ded-dea752920629||If a texture is dragged out of inventory onto the ground, it appears contained in a cube with this texture applied to it.
|-
|inv_folder_animation.tga||4d59b3ee-f29d-b912-2bcc-9bb1f8a07ec6||Icon used for the "Animations" inventory folder.
|-
|inv_folder_bodypart.tga||1fe05580-1d2f-0345-b28b-52b6e3a20e5d||Icon used for the "Bodyparts" inventory folder.
|-
|inv_folder_callingcard.tga||a3735971-e2b2-d78a-580d-d265cd8f2484||Icon used for the "Calling Cards" inventory folder.
|-
|inv_folder_clothing.tga||f1427d3d-b2e8-97c4-69ab-1f36d4c0e8f0||Icon used for the "Clothing" inventory folder.
|-
|inv_folder_gesture.tga||4de9129a-9fc1-d759-d739-364293906ba2||Icon used for the "Gestures" inventory folder.
|-
|inv_folder_landmark.tga||9f921155-7c8c-e276-d5ec-03ac9340584d||Icon used for the "Landmarks" inventory folder.
|-
|inv_folder_lostandfound.tga||9a371a04-297d-bacf-0d16-5f49753efe1d||Icon used for the "Lost and Found" inventory folder.
|-
|inv_folder_notecard.tga||a9e75d84-5073-9cb7-10a9-1ca68ef5c7ba||Icon used for the "Notecards" inventory folder.
|-
|inv_folder_object.tga||113e5133-fd0d-ee51-4a59-9d67ca10e8a7||Icon used for the "Objects" inventory folder.
|-
|inv_folder_plain_closed.tga||86f00960-c3e9-9680-145d-3beffd743e9c||Icon used for closed inventory folders.
|-
|inv_folder_plain_open.tga||d15dc243-2d0b-47af-0ce1-ec376464bdc8||Icon used for open inventory folders.
|-
|inv_folder_script.tga||baa5c310-6a6d-cc48-51eb-65196ba31d77||Icon used for the "Scripts" inventory folder.
|-
|inv_folder_snapshot.tga||6efe85e7-800f-1843-296c-a5b7adffe091||Icon used for the "Snapshots" inventory folder.
|-
|inv_folder_sound.tga||e10cb910-1e71-da47-bd12-8c53f7793714||Icon used for the "Sounds" inventory folder.
|-
|inv_folder_texture.tga||743f035b-a049-43f4-16c7-7ec8daa2c481||Icon used for the "Textures" inventory folder.
|-
|inv_folder_trash.tga||88ad072e-ea0b-aabd-5ac0-b37862a6eb66||Icon used for the "Trash" inventory folder.
|-
|inv_item_animation.tga||b5cda0d6-d196-ce48-63db-d04323ef8931||Icon used to represent a texture inventory item.
|-
|inv_item_attach.tga||5bcae41e-aa5d-02f8-edf1-605ebdd875ab||Icon used to represent a texture inventory item.
|-
|inv_item_bodypart.tga||d2a5362d-5c55-57dd-a9e9-5c814d1ddc16||Icon used to represent a texture inventory item.
|-
|inv_item_callingcard_offline.tga||d0afe86b-2489-7600-55b7-6abb0a63d9f9||Icon used to represent an offline calling card.
|-
|inv_item_callingcard_online.tga||672cc53e-8dc0-ba91-2a4e-574104cf071c||Icon used to represent an online calling card.
|-
|inv_item_clothing.tga||34dfe476-8e26-0e3a-11cf-76cc4a7126ce||Icon used to represent a clothing inventory item.
|-
|inv_item_eyes.tga||eaa5fd96-5c25-06ef-2280-7ef20203e167||Icon used to represent eye settings.
|-
|inv_item_gesture.tga||5579245d-d5bf-5f13-46b0-8624490de24c||Icon used to represent a gesture inventory item.
|-
|inv_item_gloves.tga||117b11cb-c04e-5081-13da-1a8846070fd0||Icon used to represent a texture inventory item.
|-
|inv_item_hair.tga||6bca3bf4-ed6d-d438-63a0-2a7066d03a0b||Icon used to represent hair settings.
|-
|inv_item_jacket.tga||8df59386-56e0-c811-0443-840da3acb3a5||Icon used to represent a jacket inventory item.
|-
|inv_item_landmark.tga||bf25a2a0-85da-7fa0-0993-e461768d0221||Icon used to represent an unvisited landmark.
|-
|inv_item_landmark_visited.tga||229fac85-5428-4ab7-adeb-eb8389e91092||Icon used to represent a visited landmark.
|-
|inv_item_notecard.tga||23ce8a2c-9ea2-d863-6572-806f0645b0c7||Icon used to represent a notecard inventory item.
|-
|inv_item_object.tga||0f0780a0-89c4-742a-ef28-26405a41cf85||Icon used to represent a object inventory item.
|-
|inv_item_pants.tga||a87a58ca-f857-63b1-0acf-072711ed1bdb||Icon used to represent a pants inventory item.
|-
|inv_item_script.tga||59a3df81-ed76-06c9-7264-6dada535e7a3||Icon used to represent a script inventory item.
|-
|inv_item_shape.tga||4463e433-4db5-79ef-c1b0-4821b03ddb07||Icon used to represent a shape inventory item.
|-
|inv_item_shirt.tga||e2ffb62b-6abc-22d6-952d-764759b4d636||Icon used to represent a shirt inventory item.
|-
|inv_item_shoes.tga||cf384fa5-1edd-c37c-2134-283dd4fe3396||Icon used to represent a shoes inventory item.
|-
|inv_item_skirt.tga||0b43f826-2abc-2944-7d72-10777a51d19b||Icon used to represent a skirt inventory item.
|-
|inv_item_snapshot.tga||3810d584-b092-7caa-57e0-010f192b9659||Icon used to represent a snapshot inventory item.
|-
|inv_item_socks.tga||22137c6d-6ec5-6eee-9a2e-2d7a9e6cbcd4||Icon used to represent a socks inventory item.
|-
|inv_item_sound.tga||eb414d69-c77d-d4e7-66e6-6c2e6f6c1976||Icon used to represent a sound inventory item.
|-
|inv_item_texture.tga||19f452d7-4eee-9f46-76cc-5497d17f1dd9||Icon used to represent a texture inventory item.
|-
|inv_item_underpants.tga||2f15dc09-4385-526c-aa5d-d9d516ec7d99||Icon used to represent a underpants inventory item.
|-
|inv_item_undershirt.tga||f72ab629-a3ab-de0c-35c0-5285e27478ce||Icon used to represent a undershirt inventory item.
|}

===Map===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|compass markers||79156764-de98-4815-9d50-b10a7646bcf4
|-
|direction_arrow.tga||586383e8-4d9b-4fba-9196-2b5938e79c2c
|-
|map_avatar_16.tga||db0dadd5-026a-88cf-f5c1-523a0a2daa3e
|-
|map_avatar_8.tga||0be58a91-8065-c02b-7a12-2cc14dddbc37
|-
|map_avatar_you_8.tga||02fbdc40-5e07-a6e1-228b-58e10f8335b7
|-
|map_event.tga||6008be5e-9267-2a3a-9798-e81b076c22ca||Map event icon
|-
|map_event_mature.tga||f9cdba28-a227-d613-2f16-ce06209314ae||Map mature event icon
|-
|map_home.tga||ae9b8f5f-03a1-2e71-db77-6eb27a1ba181||Map telehub icon
|-
|map_telehub.tga||bf1b2bb0-13b1-40ae-3354-b1b93761bdb4||Map telehub icon
|-
|map_track_16.tga||a3878395-ef00-a0e6-ee9a-f45ed6b9ce59
|-
|map_track_8.tga||bfdc7bf6-e2ee-1754-f4df-cc25887714ad
|}

===Find===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|icon_auction.tga||96abf5b1-335c-6b76-61e3-74ada07f3cb8
|-
|icon_avatar_offline.tga||34648c67-5bfb-5790-e05e-8bd6600fd087
|-
|icon_avatar_online.tga||529ed15b-3d41-dcc1-79de-90bf21770b5b
|-
|icon_day_cycle.tga||5b30a285-f1e3-92b1-dcd3-0d07366ced3e
|-
|icon_event.tga||be235ae0-53cf-1d68-b3ae-cf375ed1fb58
|-
|icon_event_mature.tga||cc090999-1b3e-2e97-7a38-c9f4afd10297
|-
|icon_for_sale.tga||f20728fd-1670-3771-2293-e0dd3f0bcaab
|-
|icon_group.tga||04237108-a879-5a95-9b0c-b18fd09bc447
|-
|icon_land_for_landless.tga||c421ddf2-b9d7-b373-503c-f4c423f37f1c
|-
|icon_place.tga||ba0bac4e-815e-14e1-2895-5065b8c703b3
|-
|icon_popular.tga||bdd47da5-5b5b-c906-37ad-16aaa64f096f
|-
|icon_top_pick.tga||77ca91a2-4431-aeaf-6249-3dd99c7dd86d
|}

===Movement Controls===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|move_backward_in.tga||db11d956-5e7d-4aa5-b39d-7774d339fc5c
|-
|move_backward_out.tga||3ae8bb18-ed97-4cd3-ae5c-d54bc8479fe7
|-
|move_down_in.tga||b92a70b9-c841-4c94-b4b3-cee9eb460d48
|-
|move_down_out.tga||b5abc9fa-9e62-4e03-bc33-82c4c1b6b689
|-
|move_forward_in.tga||54197a61-f5d1-4c29-95d2-c071d08849cb
|-
|move_forward_out.tga||a0eb4021-1b20-4a53-892d-8faa9265a6f5
|-
|move_left_in.tga||724996f5-b956-46f6-9844-4fcfce1d5e83
|-
|move_left_out.tga||82476321-0374-4c26-9567-521535ab4cd7
|-
|move_right_in.tga||7eeb57d2-3f37-454d-a729-8b217b8be443
|-
|move_right_out.tga||1fbe4e60-0607-44d1-a50a-032eff56ae75
|-
|move_turn_left_in.tga||95463c78-aaa6-464d-892d-3a805b6bb7bf
|-
|move_turn_left_out.tga||13a93910-6b44-45eb-ad3a-4d1324c59bac
|-
|move_turn_right_in.tga||5e616d0d-4335-476f-9977-560bccd009da
|-
|move_turn_right_out.tga||5a44fd04-f52b-4c30-8b00-4a31e27614bd
|-
|move_up_in.tga||49b4b357-e430-4b56-b9e0-05b8759c3c82
|-
|move_up_out.tga||f887146d-829f-4e39-9211-cf872b78f97c
|}

===Edit Mode===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|bump_bark.tga||6c9fa78a-1c69-2168-325b-3e03ffa348ce||Bumpieness
|-
|bump_bricks.tga||b8eed5f0-64b7-6e12-b67f-43fa8e773440||Bumpieness
|-
|bump_checker.tga||9deab416-9c63-78d6-d558-9a156f12044c||Bumpieness
|-
|bump_concrete.tga||db9d39ec-a896-c287-1ced-64566217021e||Bumpieness
|-
|bump_crustytile.tga||f2d7b6f6-4200-1e9a-fd5b-96459e950f94||Bumpieness
|-
|bump_cutstone.tga||d9258671-868f-7511-c321-7baef9e948a4||Bumpieness
|-
|bump_discs.tga||d21e44ca-ff1c-a96e-b2ef-c0753426b7d9||Bumpieness
|-
|bump_gravel.tga||4726f13e-bd07-f2fb-feb0-bfa2ac58ab61||Bumpieness
|-
|bump_petridish.tga||e569711a-27c2-aad4-9246-0c910239a179||Bumpieness
|-
|bump_siding.tga||073c9723-540c-5449-cdd4-0e87fdc159e3||Bumpieness
|-
|bump_stonetile.tga||ae874d1a-93ef-54fb-5fd3-eb0cb156afc0||Bumpieness
|-
|bump_stucco.tga||92e66e00-f56f-598a-7997-048aa64cde18||Bumpieness
|-
|bump_suction.tga||83b77fc6-10b4-63ec-4de7-f40629f238c5||Bumpieness
|-
|bump_weave.tga||735198cf-6ea0-2550-e222-21d3c6a341ae||Bumpieness
|-
|bump_woodgrain.tga||058c75c0-a0d5-f2f8-43f3-e9699a89c2fc||Bumpieness
|-
|missing_asset.tga||32dfd1c8-7ff6-5909-d983-6d4adfb4255d||MISSING IMAGE
|-
|object_cone.tga||c2b8c90a-7dca-26e3-1a63-7aa4a0389cf9||Build tools Cone object type icon
|-
|object_cone_active.tga||cf69c64b-f19e-e1f3-a586-42fef31a23be||Build tools Cone object selected icon
|-
|object_cube.tga||70c747ac-1de3-a8b9-514d-101753ca6ccb||Build tools Cube object type icon
|-
|object_cube_active.tga||f9c5e213-1076-7a7d-7889-52388aad2c1a||Build tools Cube object selected icon
|-
|object_cylinder.tga||13e35d95-5f6c-9a91-1766-49dedf9b1267||Build tools Cylinder object type icon
|-
|object_cylinder_active.tga||3f3e4932-8412-e2a7-cfe9-92caf5978b1b||Build tools Cylinder object selected icon
|-
|object_grass.tga||7ca8e672-920b-4653-3970-1abc91abef58||Build tools Grass object type icon
|-
|object_grass_active.tga||d0fc7cc9-646a-6860-cf7c-1d9e58cd6dab||Build tools Grass object selected icon
|-
|object_hemi_cone.tga||69d5e60c-739a-40b1-b526-84072121e394||Build tools half-cone object type icon
|-
|object_hemi_cone_active.tga||2e0c5435-95bb-1c0d-5da1-42336fb1cfc0||Build tools half-cone object selected icon
|-
|object_hemi_cylinder.tga||f4be3e06-24a8-f86e-acc7-7daefc0572b7||Build tools half-cylinder object type icon
|-
|object_hemi_cylinder_active.tga||67279486-cfc1-3633-de42-85db65db373c||Build tools half-cylinder object selected icon
|-
|object_hemi_sphere.tga||b67251ab-1716-b9fb-f911-967ba3fe027b||Build tools half-sphere object type icon
|-
|object_hemi_sphere_active.tga||6c489466-3058-6475-6b1b-e5fc1d49f1f3||Build tools half-sphere object selected icon
|-
|object_prism.tga||02935f3a-dcda-3b42-1874-da89d4c12870||Build tools Prism object type icon
|-
|object_prism_active.tga||223aac97-bd2f-ec2e-ad45-5641b77c78f9||Build tools Prism object selected icon
|-
|object_pyramid.tga||9dde8b56-2cc4-a932-b63a-38c3a83221ad||Build tools Pyramid object type icon
|-
|object_pyramid_active.tga||e7217b1a-e3d8-e339-d28a-d7714d0b5bee||Build tools Pyramid object selected icon
|-
|object_ring.tga||a7610e41-4647-16d8-0e0e-85a1211c1596||Build tools Ring object type icon
|-
|object_ring_active.tga||2c955a73-fa31-237b-a4a1-5c8ede3bae50||Build tools Ring object selected icon
|-
|object_sphere.tga||7fa122c0-b994-460e-8636-cdc451d67268||Build tools Sphere object type icon
|-
|object_sphere_active.tga||f2c3bcbc-2904-41a5-1c22-688f176fd1ee||Build tools Sphere object selected icon
|-
|object_tetrahedron.tga||e17db404-9fc5-9534-1038-777c82b2771f||Build tools Tetrahedron object type icon
|-
|object_tetrahedron_active.tga||2792ea3b-c052-85fe-d168-a62b2f4e9d7c||Build tools Tetrahedron object selected icon
|-
|object_torus.tga||19e1f4c9-6aa6-4414-981d-59a1343a6472||Build tools Torus object type icon
|-
|object_torus_active.tga||ef2bca77-5004-4547-b00a-3b96e463f89f||Build tools Torus object selected icon
|-
|object_tree.tga||710d1bec-fb33-28f1-e77e-ddbb5b51f5ed||Build tools Tree object type icon
|-
|object_tree_active.tga||da4835c7-b12a-41dd-11db-dae452f040c2||Build tools Tree object selected icon
|-
|object_tube.tga||7ce81316-a478-480f-961c-435fcbdecaf0||Build tools Tube object type icon
|-
|object_tube_active.tga||55c3e4d1-cfdc-48a8-af32-a34844b91832||Build tools Tube object selected icon
|-
|plywood (default object texture)||89556747-24cb-43ed-920b-47caed15465f||The default texture prims are set to upon creation.
|-
|selected texture||a85ac674-cb75-4af6-9499-df7c5aaf7a28||Texture of crosshairs that is overlayed onto the selected texture in "Select Texture" mode.
|-
|tool_dozer.tga||d2a0d4d4-54eb-4d16-be4b-4eae43845c74
|-
|tool_dozer_active.tga||d4afdbbe-1550-4b7d-91de-95731f47e8e3
|-
|tool_land.tga||86fe4df4-0ecb-4382-b9ae-475925a92388
|-
|tool_land_active.tga||34e60587-0791-4a07-8918-f5995fcc22a3
|-
|tool_orbit.tga||06964fe4-033f-448a-95c9-30dc41d1be8b
|-
|tool_orbit_active.tga||ee4e07db-3f72-4098-bd4c-aef34515a7bc
|-
|tool_pan.tga||a32aa302-0a15-48d2-b2b1-4d69f1161173
|-
|tool_pan_active.tga||24d9ad33-0b42-4eb5-99a3-659d838bc5c0
|-
|tool_zoom.tga||27eb8829-fe65-45ed-a49a-73aac42f4b38
|-
|tool_zoom_active.tga||69445f58-5c8e-44e0-9d2e-47408bb43b39
|-
|white.tga||5748decc-f629-461c-9a36-a35a221fe21f||The "blank" texture.
|}

===Misc===
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|alpha_noise.tga||b9e1cf8a-9660-c020-0c69-18f1ea27268a
|-
|alpha_sizzle.tga||e121e2fc-7573-740f-edfd-0d45a9ba486e||Possibly a texture used to generate clouds? Also the texture used for unloaded textures in the texture picker
|-
|black.tga||e2244626-f22f-4839-8123-1e7baddeb659
|-
|darkgray.tga||267e26d3-e0e1-41b8-91b1-3b337102928d
|-
|legend.tga||ca7609c6-6ec6-32d9-332e-0d8f437ef644
|-
|lightning||f8e2c2f0-7d5e-bb9a-68d0-7a3e87984784
|-
|lightning (flipped horizontally)||eef34d99-4f5b-efa1-4586-b4853c430dd3
|-
|lightgray.tga||c520bf46-cc5d-412b-a60b-9f1bd245189f
|-
|rounded_square.tga||38ce8b3c-fb30-5c59-9926-bd643613f606
|-
|rounded_square_soft.tga||4c95e6bc-fe77-9cb4-b58a-909848042c1e
|}

==Animations==
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!File
!UUID
!Description
|-
|avatar_aim_l_bow.bvh||46bb4359-de38-4ed8-6a22-f1f52fe8f506
|-
|avatar_aim_r_bazooka.bvh||b5b4a67d-0aee-30d2-72cd-77b333e932ef
|-
|avatar_aim_r_handgun.bvh||3147d815-6338-b932-f011-16b56d9ac18b
|-
|avatar_aim_r_rifle.bvh||ea633413-8006-180a-c3ba-96dd1d756720
|-
|avatar_angry_fingerwag.bvh||c1bc7f36-3ba0-d844-f93c-93be945d644f
|-
|avatar_angry_tantrum.bvh||11000694-3f41-adc2-606b-eee1d66f3724
|-
|avatar_away.bvh||fd037134-85d4-f241-72c6-4f42164fedee
|-
|avatar_backflip.bvh||c4ca6188-9127-4f31-0158-23c4e2f93304
|-
|avatar_blowkiss.bvh||db84829b-462c-ee83-1e27-9bbee66bd624
|-
|avatar_bow.bvh||82e99230-c906-1403-4d9c-3889dd98daba
|-
|avatar_brush.bvh||349a3801-54f9-bf2c-3bd0-1ac89772af01
|-
|avatar_busy.bvh||efcf670c-2d18-8128-973a-034ebc806b67
|-
|avatar_clap.bvh||9b0c1c4e-8ac7-7969-1494-28c874c4f668
|-
|avatar_courtbow.bvh||9ba1c942-08be-e43a-fb29-16ad440efc50
|-
|avatar_crouch.bvh||201f3fdf-cb1f-dbec-201f-7333e328ae7c
|-
|avatar_crouchwalk.bvh||47f5f6fb-22e5-ae44-f871-73aaaf4a6022
|-
|avatar_dance1.bvh||b68a3d7c-de9e-fc87-eec8-543d787e5b0d
|-
|avatar_dance2.bvh||928cae18-e31d-76fd-9cc9-2f55160ff818
|-
|avatar_dance3.bvh||30047778-10ea-1af7-6881-4db7a3a5a114
|-
|avatar_dance4.bvh||951469f4-c7b2-c818-9dee-ad7eea8c30b7
|-
|avatar_dance5.bvh||4bd69a1d-1114-a0b4-625f-84e0a5237155
|-
|avatar_dance6.bvh||cd28b69b-9c95-bb78-3f94-8d605ff1bb12
|-
|avatar_dance7.bvh||a54d8ee2-28bb-80a9-7f0c-7afbbe24a5d6
|-
|avatar_dance8.bvh||b0dc417c-1f11-af36-2e80-7e7489fa7cdc
|-
|avatar_dead.bvh||57abaae6-1d17-7b1b-5f98-6d11a6411276
|-
|avatar_drink.bvh||0f86e355-dd31-a61c-fdb0-3a96b9aad05f
|-
|avatar_express_afraid.bvh||6b61c8e8-4747-0d75-12d7-e49ff207a4ca
|-
|avatar_express_afraid_emote.bvh||aa2df84d-cf8f-7218-527b-424a52de766e
|-
|avatar_express_anger.bvh||5747a48e-073e-c331-f6f3-7c2149613d3e
|-
|avatar_express_anger_emote.bvh||1a03b575-9634-b62a-5767-3a679e81f4de
|-
|avatar_express_bored.bvh||b906c4ba-703b-1940-32a3-0c7f7d791510
|-
|avatar_express_bored_emote.bvh||214aa6c1-ba6a-4578-f27c-ce7688f61d0d
|-
|avatar_express_cry.bvh||92624d3e-1068-f1aa-a5ec-8244585193ed
|-
|avatar_express_cry_emote.bvh||d535471b-85bf-3b4d-a542-93bea4f59d33
|-
|avatar_express_disdain.bvh||d4416ff1-09d3-300f-4183-1b68a19b9fc1
|-
|avatar_express_embarrassed_emote.bvh||0b8c8211-d78c-33e8-fa28-c51a9594e424
|-
|avatar_express_frown.bvh||fee3df48-fa3d-1015-1e26-a205810e3001
|-
|avatar_express_kiss.bvh||1e8d90cc-a84e-e135-884c-7c82c8b03a14
|-
|avatar_express_laugh.bvh||18b3a4b5-b463-bd48-e4b6-71eaac76c515
|-
|avatar_express_laugh_emote.bvh||62570842-0950-96f8-341c-809e65110823
|-
|avatar_express_open_mouth.bvh||d63bc1f9-fc81-9625-a0c6-007176d82eb7
|-
|avatar_express_repulsed.bvh||36f81a92-f076-5893-dc4b-7c3795e487cf
|-
|avatar_express_repulsed_emote.bvh||f76cda94-41d4-a229-2872-e0296e58afe1
|-
|avatar_express_sad.bvh||0eb702e2-cc5a-9a88-56a5-661a55c0676a
|-
|avatar_express_sad_emote.bvh||eb6ebfb2-a4b3-a19c-d388-4dd5c03823f7
|-
|avatar_express_shrug.bvh||70ea714f-3a97-d742-1b01-590a8fcd1db5
|-
|avatar_express_shrug_emote.bvh||a351b1bc-cc94-aac2-7bea-a7e6ebad15ef
|-
|avatar_express_smile.bvh||b7c7c833-e3d3-c4e3-9fc0-131237446312
|-
|avatar_express_surprise.bvh||313b9881-4302-73c0-c7d0-0e7a36b6c224
|-
|avatar_express_surprise_emote.bvh||728646d9-cc79-08b2-32d6-937f0a835c24
|-
|avatar_express_tongue_out.bvh||835965c6-7f2f-bda2-5deb-2478737f91bf
|-
|avatar_express_toothsmile.bvh||b92ec1a5-e7ce-a76b-2b05-bcdb9311417e
|-
|avatar_express_wink.bvh||869ecdad-a44b-671e-3266-56aef2e3ac2e
|-
|avatar_express_wink_emote.bvh||da020525-4d94-59d6-23d7-81fdebf33148
|-
|avatar_express_worry.bvh||9f496bd2-589a-709f-16cc-69bf7df1d36c
|-
|avatar_express_worry_emote.bvh||9c05e5c7-6f07-6ca4-ed5a-b230390c3950
|-
|avatar_falldown.bvh||666307d9-a860-572d-6fd4-c3ab8865c094
|-
|avatar_female_walk.bvh||f5fc7433-043d-e819-8298-f519a119b688
|-
|avatar_fist_pump.bvh||7db00ccd-f380-f3ee-439d-61968ec69c8a
|-
|avatar_fly.bvh||aec4610c-757f-bc4e-c092-c6e9caf18daf
|-
|avatar_flyslow.bvh||2b5a38b2-5e00-3a97-a495-4c826bc443e6
|-
|avatar_hello.bvh||9b29cd61-c45b-5689-ded2-91756b8d76a9
|-
|avatar_hold_l_bow.bvh||8b102617-bcba-037b-86c1-b76219f90c88
|-
|avatar_hold_r_bazooka.bvh||ef62d355-c815-4816-2474-b1acc21094a6
|-
|avatar_hold_r_handgun.bvh||efdc1727-8b8a-c800-4077-975fc27ee2f2
|-
|avatar_hold_r_rifle.bvh||3d94bad0-c55b-7dcc-8763-033c59405d33
|-
|avatar_hold_throw_r.bvh||7570c7b5-1f22-56dd-56ef-a9168241bbb6
|-
|avatar_hover.bvh||4ae8016b-31b9-03bb-c401-b1ea941db41d
|-
|avatar_hover_down.bvh||20f063ea-8306-2562-0b07-5c853b37b31e
|-
|avatar_hover_up.bvh||62c5de58-cb33-5743-3d07-9e4cd4352864
|-
|avatar_impatient.bvh||5ea3991f-c293-392e-6860-91dfa01278a3
|-
|avatar_jump.bvh||2305bd75-1ca9-b03b-1faa-b176b8a8c49e
|-
|avatar_jumpforjoy.bvh||709ea28e-1573-c023-8bf8-520c8bc637fa
|-
|avatar_kick_roundhouse_r.bvh||49aea43b-5ac3-8a44-b595-96100af0beda
|-
|avatar_kissmybutt.bvh||19999406-3a3a-d58c-a2ac-d72e555dcf51
|-
|avatar_land.bvh||7a17b059-12b2-41b1-570a-186368b6aa6f
|-
|avatar_laugh_short.bvh||ca5b3f14-3194-7a2b-c894-aa699b718d1f
|-
|avatar_motorcycle_sit.bvh||08464f78-3a8e-2944-cba5-0c94aff3af29
|-
|avatar_musclebeach.bvh||315c3a41-a5f3-0ba4-27da-f893f769e69b
|-
|avatar_no_head.bvh||5a977ed9-7f72-44e9-4c4c-6e913df8ae74
|-
|avatar_no_unhappy.bvh||d83fa0e5-97ed-7eb2-e798-7bd006215cb4
|-
|avatar_nyanya.bvh||f061723d-0a18-754f-66ee-29a44795a32f
|-
|avatar_peace.bvh||b312b10e-65ab-a0a4-8b3c-1326ea8e3ed9
|-
|avatar_point_me.bvh||17c024cc-eef2-f6a0-3527-9869876d7752
|-
|avatar_point_you.bvh||ec952cca-61ef-aa3b-2789-4d1344f016de
|-
|avatar_prejump.bvh||7a4e87fe-de39-6fcb-6223-024b00893244
|-
|avatar_punch_l.bvh||f3300ad9-3462-1d07-2044-0fef80062da0
|-
|avatar_punch_onetwo.bvh||eefc79be-daae-a239-8c04-890f5d23654a
|-
|avatar_punch_r.bvh||c8e42d32-7310-6906-c903-cab5d4a34656
|-
|avatar_rps_countdown.bvh||35db4f7e-28c2-6679-cea9-3ee108f7fc7f
|-
|avatar_rps_paper.bvh||0836b67f-7f7b-f37b-c00a-460dc1521f5a
|-
|avatar_rps_rock.bvh||42dd95d5-0bc6-6392-f650-777304946c0f
|-
|avatar_rps_scissors.bvh||16803a9f-5140-e042-4d7b-d28ba247c325
|-
|avatar_run.bvh||05ddbff8-aaa9-92a1-2b74-8fe77a29b445
|-
|avatar_salute.bvh||cd7668a6-7011-d7e2-ead8-fc69eff1a104
|-
|avatar_shoot_l_bow.bvh||e04d450d-fdb5-0432-fd68-818aaf5935f8
|-
|avatar_shout.bvh||6bd01860-4ebd-127a-bb3d-d1427e8e0c42
|-
|avatar_sit.bvh||1a5fe8ac-a804-8a5d-7cbd-56bd83184568
|-
|avatar_sit_female.bvh||b1709c8d-ecd3-54a1-4f28-d55ac0840782
|-
|avatar_sit_generic.bvh||245f3c54-f1c0-bf2e-811f-46d8eeb386e7
|-
|avatar_sit_ground.bvh||1c7600d6-661f-b87b-efe2-d7421eb93c86
|-
|avatar_sit_to_stand.bvh||a8dee56f-2eae-9e7a-05a2-6fb92b97e21e
|-
|avatar_sleep.bvh||f2bed5f9-9d44-39af-b0cd-257b2a17fe40
|-
|avatar_smoke_idle.bvh||d2f2ee58-8ad1-06c9-d8d3-3827ba31567a
|-
|avatar_smoke_inhale.bvh||6802d553-49da-0778-9f85-1599a2266526
|-
|avatar_smoke_throw_down.bvh||0a9fb970-8b44-9114-d3a9-bf69cfe804d6
|-
|avatar_snapshot.bvh||eae8905b-271a-99e2-4c0e-31106afd100c
|-
|avatar_soft_land.bvh||f4f00d6e-b9fe-9292-f4cb-0ae06ea58d57
|-
|avatar_stand.bvh||2408fe9e-df1d-1d7d-f4ff-1384fa7b350f
|-
|avatar_stand_1.bvh||15468e00-3400-bb66-cecc-646d7c14458e
|-
|avatar_stand_2.bvh||370f3a20-6ca6-9971-848c-9a01bc42ae3c
|-
|avatar_stand_3.bvh||42b46214-4b44-79ae-deb8-0df61424ff4b
|-
|avatar_stand_4.bvh||f22fed8b-a5ed-2c93-64d5-bdd8b93c889f
|-
|avatar_standup.bvh||3da1d753-028a-5446-24f3-9c9b856d9422
|-
|avatar_stretch.bvh||80700431-74ec-a008-14f8-77575e73693f
|-
|avatar_stride.bvh||1cb562b0-ba21-2202-efb3-30f82cdf9595
|-
|avatar_surf.bvh||41426836-7437-7e89-025d-0aa4d10f1d69
|-
|avatar_sword_strike_r.bvh||85428680-6bf9-3e64-b489-6f81087c24bd
|-
|avatar_talk.bvh||5c682a95-6da4-a463-0bf6-0f5b7be129d1
|-
|avatar_throw_r.bvh||aa134404-7dac-7aca-2cba-435f9db875ca
|-
|avatar_tryon_shirt.bvh||83ff59fe-2346-f236-9009-4e3608af64c1
|-
|avatar_turn_180.bvh||038fcec9-5ebd-8a8e-0e2e-6e71a0a1ac53
|-
|avatar_turnback_180.bvh||6883a61a-b27b-5914-a61e-dda118a9ee2c
|-
|avatar_turnleft.bvh||56e0ba0d-4a9f-7f27-6117-32f2ebbf6135
|-
|avatar_turnright.bvh||2d6daa51-3192-6794-8e2e-a15f8338ec30
|-
|avatar_type.bvh||c541c47f-e0c0-058b-ad1a-d6ae3a4584d9
|-
|avatar_walk.bvh||6ed24bd8-91aa-4b12-ccc7-c97c857ab4e0
|-
|avatar_whisper.bvh||7693f268-06c7-ea71-fa21-2b30d6533f8f
|-
|avatar_whistle.bvh||b1ed7982-c68e-a982-7561-52a88a5298c0
|-
|avatar_wink_hollywood.bvh||c0c4030f-c02b-49de-24ba-2331f43fe41c
|-
|avatar_yes_happy.bvh||b8c8b2a3-9008-1771-3bfc-90924955ab2d
|-
|avatar_yes_head.bvh||15dd911d-be82-2856-26db-27659b142875
|-
|avatar_yoga_float.bvh||42ecd00b-9947-a97c-400a-bbc9174c7aeb
|}

==Sounds==
{|border="1" style="width: 100%; border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0;"
|- style="background-color: #dfd;"
!Sound
!UUID
|-
|bell ting||ed124764-705d-d497-167a-182cd9fa2e6c
|-
|click||4c8c3c77-de8d-bde2-b9b8-32635e0fd4a6
|-
|health reduction (female)||219c5d93-6c09-31c5-fb3f-c5fe7495c115
|-
|health reduction (male)||e057c244-5768-1056-c37e-1537454eeb62
|-
|IM session, new incoming (2 bells)||67cc2844-00f3-2b3c-b991-6418d01e1bb7
|-
|IM start||c825dfbc-9827-7e02-6507-3713d18916c1
|-
|instant message notification||67cc2844-00f3-2b3c-b991-6418d01e1bb7
|-
|invalid operation||4174f859-0d3d-c517-c424-72923dc21f65
|-
|keyboard loop||5e191c7b-8996-9ced-a177-b2ac32bfea06
|-
|money change, down (coins)||77a018af-098e-c037-51a6-178f05877c6f
|-
|money change, up (cash register bell)||104974e3-dfda-428b-99ee-b0d4e748d3a3
|-
|null keystroke||2ca849ba-2885-4bc3-90ef-d4987a5b983a
|-
|object collision||be582e5d-b123-41a2-a150-454c39e961c8
|-
|object collision (rubber)||212b6d1e-8d9c-4986-b3aa-f3c6df8d987d
|-
|object collision (plastic)||d55c7f3c-e1c3-4ddc-9eff-9ef805d9190e
|-
|object collision (flesh)||2d8c6f51-149e-4e23-8413-93a379b42b67
|-
|object collision (wood splintering?)||6f00669f-15e0-4793-a63e-c03f62fee43a
|-
|object collision (glass break)||85cda060-b393-48e6-81c8-2cfdfb275351
|-
|object collision (metal clunk)||d1375446-1c4d-470b-9135-30132433b678
|-
|object create (whoosh)||f4a0660f-5446-dea2-80b7-6482a082803c
|-
|object delete||0cb7b00a-4c10-6948-84de-a93c09af2ba9
|-
|object rez (shake)||3c8fc726-1fd6-862d-fa01-16c5b2568db6
|-
|pie menu appear (ding)||8eaed61f-92ff-6485-de83-4dcc938a478e
|-
|pie menu slice highlight||d9f73cf8-17b4-6f7a-1565-7951226c305d
|-
|pie menu slice highlight1||f6ba9816-dcaf-f755-7b67-51b31b6233e5
|-
|pie menu slice highlight2||7aff2265-d05b-8b72-63c7-dbf96dc2f21f
|-
|pie menu slice highlight3||09b2184e-8601-44e2-afbb-ce37434b8ba1
|-
|pie menu slice highlight4||bbe4c7fc-7044-b05e-7b89-36924a67593c
|-
|pie menu slice highlight5||d166039b-b4f5-c2ec-4911-c85c727b016c
|-
|pie menu slice highlight6||242af82b-43c2-9a3b-e108-3b0c7e384981
|-
|pie menu slice highlight7||c1f334fb-a5be-8fe7-22b3-29631c21cf0b
|-
|snapshot||3d09f582-3851-c0e0-f5ba-277ac5c73fb4
|-
|teleport/texture apply||d7a9a565-a013-2a69-797d-5332baa1a947
|-
|thunder||e95c96a5-293c-bb7a-57ad-ce2e785ad85f
|-
|window close||2c346eda-b60c-ab33-1119-b8941916a499
|-
|window open||c80260ba-41fd-8a46-768a-6bf236360e3a
|-
|zipper/squeek||6cf2be26-90cb-2669-a599-f5ab7698225f
|}

Category:Simulator Resource Conservation

2014-03-06T00:57:22Z

Kizmut Smit: +catcat

[[Category:Categories]]
[[Category:Performance_and_stability]]

LSL Constants vs Globals

2014-03-06T00:56:20Z

Kizmut Smit: +cats

Category:Simulator Resource Conservation

2014-03-06T00:55:46Z

Kizmut Smit: +catcat

[[Category:Categories]]

Category:Script resource Conservation

2014-03-06T00:54:50Z

Kizmut Smit: +blanking typo

Category:Script Resource Conservation

2014-03-06T00:53:15Z

Kizmut Smit: +catcat

[[Category:Simulator Resource Conservation]]

Category:Memory Conservation

2014-03-06T00:52:24Z

Kizmut Smit: +capitalize Resource!

[[Category:Script Resource Conservation]]
[[Category:LSL Memory]]
[[Category:LSL]]

Category:Process-Time Conservation

2014-03-06T00:51:32Z

Kizmut Smit: +catcat

[[Category:Script Resource Conservation]]

Category:Script resource Conservation

2014-03-06T00:49:01Z

Kizmut Smit: +catcat

[[Category:Simulator Resource Conservation]]

Category:Memory Conservation

2014-03-06T00:48:26Z

Kizmut Smit: +catcat

[[Category:Script resource Conservation]]
[[Category:LSL Memory]]
[[Category:LSL]]

User:Kizmut Smit/kizmuTECH/Paint Can

2013-12-20T00:55:11Z

Kizmut Smit: Paint Can usage

=Paint Can=
__TOC__
==Objective==
Alleviate tedium for builders and modders attempting to adjust matching colours in a linkset on many faces at a time.

==Usage==
#Insert script into root of object.
#Specify the new colour by changing the face of one prim in the linkset and then click on it.
#Press Select in the dialogue menu. This will be the colour used to replace the rest.
#Specify the colour to be replaced by clicking on one of the remaining faces to be changed.
#Press Change in the dialogue menu. This will change the remaining prim faces matching the old colour in the linkset to the new colour specified in the beginning.

 

{{User:Kizmut Smit/Templates/Scripts}}

User:Kizmut Smit/Templates/Scripts

2013-12-20T00:54:34Z

Kizmut Smit: *nudge*

<onlyinclude><center><table style="border: 1px solid #0000ff; background: #ccddff; color: black; width: {{{width|85%}}}; min-width: 400px; margin-left: 20px; margin-right: 20px;">
<tr>
<td width="32" valign="top">[[Image:KBtip.png|32px|link=]]</td>

<td>At this time scripts mentioned here are available upon request. Contact [[User:Kizmut Smit|kizmut Smit]] for more info.</td>
</tr>
</table></center></onlyinclude><noinclude>

Availability note for kizmuTECH scripts pages.

</noinclude>

User:Kizmut Smit/Templates/Scripts

2013-12-20T00:54:06Z

Kizmut Smit: *nudge*

<onlyinclude><center><table style="border: 1px solid #0000ff; background: #ccddff; color: black; width: {{{width|85%}}}; min-width: 400px; margin-left: 20px; margin-right: 20px;"></center>
<tr>
<td width="32" valign="top">[[Image:KBtip.png|32px|link=]]</td>

<td>At this time scripts mentioned here are available upon request. Contact [[User:Kizmut Smit|kizmut Smit]] for more info.</td>
</tr>
</table></onlyinclude><noinclude>

Availability note for kizmuTECH scripts pages.

</noinclude>

User:Kizmut Smit/Templates/Scripts

2013-12-20T00:52:32Z

Kizmut Smit: template for availability note

<onlyinclude><table style="border: 1px solid #0000ff; background: #ccddff; color: black; width: {{{width|85%}}}; min-width: 400px; margin-left: 20px; margin-right: 20px;">
<tr>
<td width="32" valign="top">[[Image:KBtip.png|32px|link=]]</td>

<td>At this time scripts mentioned here are available upon request. Contact [[User:Kizmut Smit|kizmut Smit]] for more info.</td>
</tr>
</table></onlyinclude><noinclude>

Availability note for kizmuTECH scripts pages.

</noinclude>

User:Kizmut Smit/kizmuTECH

2013-12-20T00:28:20Z

Kizmut Smit: projects

=kizmuTECH=
Catalogue of projects developed under the kizmuTECH umbrella.
==Scripts==
===Build Tools===
*[[User:Kizmut Smit/kizmuTECH/Paint Can|Paint Can]]
*[[User:Kizmut Smit/kizmuTECH/Scripts#Touch Face/Link Report|Touch Face/Link Report]]
*[[User:Kizmut Smit/kizmuTECH/Scripts#Rotation Report|Rotation Report]]
*[[User:Kizmut Smit/kizmuTECH/Scripts#Animation Check|Animation Check]]
*[[User:Kizmut Smit/kizmuTECH/Scripts#Texture Anim on Touch|Texture Anim on Touch]]

==Builds==
===Structures===
*[[User:Kizmut Smit/kizmuTECH/Structures#Unicorn Mayo|Unicorn Mayo]]
===Entertainment===
*[[User:Kizmut Smit/kizmuTECH/Entertainment#Memory Game|Memory Game]]
===Accessories===
*[[User:Kizmut Smit/kizmuTECH/Accessories#Rainbow Text|Rainbow Text]]

==Services==
*kizmuTECH Radio

User:Kizmut Smit/kizmuTECH/Scripts

2013-12-20T00:27:45Z

Kizmut Smit: kizmuTECH Scripts Available

=Scripts=
__TOC__
==Tools==
===Touch Face/Link Report===
Indicates link number and face where touched on object linkset.

 

===Rotation Report===
Reports rotation in rotation format for scripting.

 

===Animation Check===
Reports current animation.

 

===Texture Anim on Touch===
Animates texture on face touched.

LSL Script Memory

2013-01-16T18:26:55Z

Kizmut Smit: +cat

{{Multi-lang|category=LSL}}{{LSL Header}}{{LSLC|}}{{RightToc}}

=Script Memory=
All scripts in LSL pre-MONO start out with 16 kilobytes of memory. Mono scripts start with 64 kilobytes, this may be reduced with [[llSetMemoryLimit]](). Additionally, Mono scripts only use the amount of real memory that they currently need, not the amount allocated to them (64kB, or whatever was set by [[llSetMemoryLimit]](). Mono scripts also share the memory needed for their bytecode with all other instances in the same region of the same script copied after compilation. Below is a list of code and the memory usage.

All of the following data was collected through [[llGetFreeMemory]](). As the LSL compiler is not a simple program, the data below may not be 100% accurate, in fact, much of it is wrong and could use corrections.

There are still many bits that could be improved upon, and many more that could use more detail. If anyone has any free time, play around with the memory usage for different functions. A list of needed updates is at the end of the page.

=Variables=
See the end of this page.
==Declaring variables as global==
===Variable Memory Usage===
<pre>
integer 10
float 10
string 18 + 1 per character
key 18 + 1 per character
vector 18
rotation 22
list 21 + list memory usage
</pre>
===List Memory Usage===
<pre>
integer 15
float 15
string 12 + 1 per character
key 12 + 1 per character
vector 23
rotation 27
list Lists Can Not Contain Lists
</pre>
=== List Memory Usage (MONO) ===
<pre>
integer 20
float 20
string 22 + 2 per character
key 34 + 2 per character
vector 28
rotation 32
list Lists Can Not Contain Lists
</pre>

String entries have a constant 8 for pre-compile text.
<pre>
myList = ["testing", "1", "asdhdgkjajlgsdfdsw"]
(8, 8, 8)
myList = [llGetSubString("testing", 0, -1), (string)1, llToUpper("asdhdgkjajlgsdfdsw")]
(22 + 14, 22 + 2, 22 + 36)
</pre>

==Declaring variables inside default state==
===Variable Memory Usage===
<pre>
integer 15
float 15
string 12 + 1 per character
key 12 + 1 per character
vector 31
rotation 39
list 15 + list memory usage
</pre>
===List Memory Usage===
<pre>
integer 7
float 7
string 4 + 1 per character
key 4 + 1 per character
vector 23
rotation 30
list Lists Can Not Contain Lists
</pre>
==Simply stating values==
===Putting a Value onto the Stack===
<pre>
Integers 1 + 4 bytes for the value
Float 1 + 4 bytes for the value
String 1 + bytes for characters + 1 byte for null
Key 1 + bytes for characters + 1 byte for null
Vector 1 + 3 * float cost
Rotation 1 + 4 * float cost
List 1 + 4 for list length + list memory usage
</pre>
To remove a value from the stack costs 1 byte.

===List Memory Usage===
<pre>
Integers 7
Float 7
String 4 + 1 per character
Key 4 + 1 per character
Vector 23
Rotation 30
list Lists Can Not Contain Lists
</pre>
==Constants==
All integer constants use 6 bytes of memory.
===Other Constants===
<pre>
ZERO_VECTOR 16
ZERO_ROTATION 21
NULL_KEY 39
</pre>
==Extras==
6 bytes to reference variables
==Examples==
<lsl>
integer i; //10 bytes

default {
state_entry() {
list l = ["Testing", "This"] //15 (list) + 15 (string) + 8 (string)
}
}
</lsl>

=Functions=
==Declaring functions==
Functions require 16 bytes to be created, with 3 bytes per parameter, plus bytes commensurate with the return type.

In Mono, however, functions and event handlers take up memory in '''512-byte chunks'''. Even an empty function requires at least 512 bytes. (Empty event handlers, however, apparently do not.) The code within the function takes up whatever bytes are not required by the declaration. Once the code + declaration fills a 512-byte chunk, another whole chunk is allocated to it.

===Return Types===
<pre>
integer 4
float 4
string 4
key 4
vector 20
rotation 27
list 4
</pre>

==Declaring variables in functions==
===Variable Memory Usage===
<pre>
integer 11
float 11
string 8 + 1 per character
key 8 + 1 per character
vector 19
rotation 23
list 11 + list memory usage
</pre>
===List Memory Usage===
<pre>
integer 7
float 7
string 4 + 1 per character
key 4 + 1 per character
vector 23
rotation 30
list Lists Can Not Contain Lists
</pre>
==Calling functions==
21 bytes to call a function with no return 
21 bytes to call a function with any return + type of return 
Subtract number of parameters entered
===Return Types===
<pre>
integer 2
float 2
string 10 + 1 per character returned
key 10 + 1 per character returned
vector 2
rotation 2
list 18 + list memory usage
</pre>

==Examples==
<lsl>
list f() { //16 (function) + 4 (return)
list ret = [0]; //11 (list) + 7 (integer)
return ret; 6 (list)
}
</lsl>
<lsl>
string f() {
return "";
}

default {
state_entry() {
f(); //21 (call to f) + 10 (returns string)
}
}
</lsl>

=Operators=
==List of Operators==
<pre>
+ 1
- 1
* 1
/ 1
% 1
& 0
| 0
^ 0
! 0
>> 0
<< 0
~ 1
== 1
<= 1
< 1
>= 1
> 1
!= 1
</pre>
==Assignment==
Assigning values to variables takes as many bytes as used minus one.
===Examples===
<lsl>
string s; //12 bytes
s; //6 bytes
""; //3 bytes (see below)
s = ""; //8 (6 (string) + 3 (null string) - 1) bytes
</lsl>
However...
<lsl>
string s = ""; //12 bytes
</lsl>
<lsl>
integer i; //15 bytes
i = i + 1 // 6 bytes (integer) + 6 bytes (integer) + 6 bytes (1) + 1 byte (addition) - 1 byte (assignment)
</lsl>

==Statements==
<pre>
if 6
while 11
for 11
do 6
jump 5
@ 0
state 5
</pre>
===Examples===
<lsl>
if (5 < 10) { // 6 (if) + 6 (integer) + 6 (integer) + 1 (compare)
//Do something here
}
</lsl>
<lsl>
while (1 < 2 & 3 < 4) { // 11 (while) + 4*6 (4 integers) + 2 (2 compares)
//Do something here
}
</lsl>

==Typecasting==
<pre>
integer 10
float 10
string 10
key 10
vector 10
rotation 10
list 25
</pre>
==States==
14 bytes for any event in a state + 1 for each parameter
17 bytes to create a new state
=Needed Updates=
Several updates are needed for this page, the most needed are listed below:
* Verification of all data
* Clarification of explanations
* Investigations into how the functions work
** Calling of functions
** How return types effect the return
* In the following code, the call to llGetFreeMemory() returns a different value. How is it affected? Why?
<lsl>
default {
state_entry() {
llOwnerSay((string)llGetFreeMemory());
list l = ["", "", "", ""];
llOwnerSay((string)llGetFreeMemory());
}
}
</lsl>

=Update pending=
<lsl>
////////////////////////////////////////////////////////////////////////////////
//
// Script memory - work in progress
//
// (c) 1012
// llDeleteSubString( "yepey Resident", llSubstringIndex( "yepey Resident", " " ), -1 );
//
// The script won't compile due to previously decalerd variables.
// This script will, when finished, replace all of the above.
//
// Regards,
// yepey
//
//
// GLOBAL VARIABLES
// --------------------------------------------------------------------
integer int = 0; // 8
float fl = 0.0; // 8
string str = ""; // 22
string str = "a"; // 22 + 2
string str = "\n"; // 22 + 2
key id = ""; // 8
key id = NULL_KEY; // 8
key id = "a822ff2b-ff02-461d-b45d-dcd10a2de0c2"; // 8
vector v = ZERO_VECTOR; // 16
vector v = < 0, 0, 0 >; // 16
rotation r = ZERO_ROTATION; // 16
rotation r = < 0, 0, 0, 1 >; // 16
list l = []; // 44
list l = [ // 44 + o.O
0, // 28
1.0, // 28
"", // 30
"a", // 32
"\n", // 32
NULL_KEY, // 102
ZERO_VECTOR, // 36
ZERO_ROTATION // 40
];

default
{

state_entry()
{

// LOCAL VARIABLES
// ------------------------------------------------------------------------
integer int = 0; // 4
float fl = 0.0; // 4
string str = ""; // 18 +
string str = "a"; // 2
string str = "\n"; // 2
key id = ""; // 4
key id = NULL_KEY; // 4
key id = "a822ff2b-ff02-461d-b45d-dcd10a2de0c2"; // 4
vector v = ZERO_VECTOR; // 12
vector v = < 0, 0, 0 >; // 12
rotation r = ZERO_ROTATION; // 16
rotation r = < 0, 0, 0, 1 >; // 16
list l = []; // 40
list l = [ // 40 + o.O
0, // 16
1.0, // 16
"", // 18 +
"a", // 2
"\n", // 2
NULL_KEY, // 90
ZERO_VECTOR, // 24
ZERO_ROTATION // 28
];

}

}

state examples
{

state_entry()
{

/* IMPLEMENTATION NEEDED */

}

}
</lsl>

[[Category:LSL Memory]]

External script memory

2013-01-16T18:22:37Z

Kizmut Smit: +cat

{{LSL Header|ml=3}}{{LSLC|}}
{{hint
|mode=note
|title_desc=Under Construction
|desc=More examples need to be added.
}}
There is a few ways in LSL to store external memory for using later on in case of resetting the script or any of many possibilities of just variable storage just wont cut it, and this page is to show whats the possible ways in storing data.

One way of storing data for later use is [[llGetObjectDesc]] and [[llSetObjectDesc]].

<lsl>
string data;
string username;
default
{
state_entry()
{
data = llGetObjectDesc();
if(llGetObjectDesc()){
llSay(0,"Last Toucher was saved as "+llGetObjectDesc());
}else{
llSay(0,"No Data found");
}
}

touch_start(integer total_number)
{
username = llDetectedName(0);
llSetObjectDesc(username);
llResetScript();
}
}
</lsl>

To create a Boolean constant you can use a method like so.

<lsl>
//These functions should only be used if your script is not going to be using llSetText
SetConstant(integer tof){
if(tof == TRUE)
llSetPrimitiveParams([ PRIM_TEXT, " ",<1,0,0>, 1.0 ]);
if(tof == FALSE)
llSetPrimitiveParams([ PRIM_TEXT, "",<1,0,0>, 1.0 ]);
}
integer GetConstant(){
list params = llGetPrimitiveParams([PRIM_TEXT]);
if (llList2String(params,0))
return TRUE;
return FALSE;
}

default
{
state_entry()
{
llSay(0,(string)GetConstant()); //First time should output 0, then once you click and it restarts, it will output 1
}

touch_start(integer total_number)
{
SetConstant(TRUE);
llResetScript();
}
}

</lsl>
[[Category:LSL Memory]]

Talk:LSL Portal

2012-06-14T19:18:26Z

Kizmut Smit: +dynamic /* Categories */

{{LSL Header}}{{Talk}}
= Please do not copy content from LSLwiki =

From [http://forums.secondlife.com/showpost.php?p=1392697&postcount=44 Rob Linden's post to the forum]:
:Hi folks, sorry for dropping into this conversation late. I haven't read through everything here, but I'd like to present an alternative.

:There have been several requests that Linden Lab take on the hosting of the LSL wiki. There are several problems with us doing this work. The primary problem is the question of ownership of the material. Since, to the best of our knowledge, there was never an explicit, consistent notice of ownership of this material throughout its creation, nor a clear assignment/license associated with contributing more material, it would seem the only safe way to license this content would be to contact every single contributor throughout the life of the wiki and get an explicit license or copyright assignment from them. Note that I said "safe", not "practical".

:We're not in a position to go down that road. However, we do have wiki.secondlife.com, which has had, since day one, a very clear notice about the license under which contributions are made and distributed. We would be very happy to see the community collaborate on newly created content on wiki.secondlife.com. As long as you author the content (not cut and paste from sources you are not the sole author of), we welcome your contribution. -- [[User:Rob Linden|Rob Linden]] 14:30, 24 January 2007 (PST)

----

OK, so let's talk about formatting rules for entries.

(Moved to [[LSL Portal Guidelines]], so that this talk doesn't get too cluttered.) -- [[User:Talarus Luan|Talarus Luan]] 16:32, 24 January 2007 (PST)

[[User:Talarus Luan|Talarus Luan]] 14:28, 24 January 2007 (PST)

----

=Other Discussion=

== LSL Guide lost ==

http://svn.secondlife.com/trac/linden/changeset/1392
linked from the page history
says new residents downloading the client won't be getting a copy of the LSL_Guide.html any more ...

Q1. Where on the web do new residents go to get the LSL_Guide now? -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:17, 3 January 2009 (UTC)

Q2. How should this [[LSL Portal]] page tell new residents to be sure to read the LSL_Guide first to correctly understand what else we say here? -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:17, 3 January 2009 (UTC)

== Untitled Chat ==

Should we make this the front page to the LSL reference, or put that one more level down? I kinda lean toward the former. [[User:Gigs Taggart|Gigs Taggart]] 14:09, 24 January 2007 (PST)

----

Yeah i think so... (Unsigned by Dimentox Travanti}
:Remember to sign your post with four tildes. [[User:Gigs Taggart|Gigs Taggart]] 14:26, 24 January 2007 (PST)

I used a modified version of the [http://meta.wikimedia.org/wiki/User:Ajqnic:GeSHiHighlight GeSHiHighlight] plugin for MediaWiki. With an LSL syntax file. The license for the plugin and for [http://qbnz.com/highlighter/ GeSHi] is GPL, it also requires another plugin [http://meta.wikimedia.org/wiki/User:Ajqnic:purgePage purgePage].
--[[User:Thraxis Epsilon|Thraxis Epsilon]] 15:00, 24 January 2007 (PST)

== Regarding copying content from the existing Wiki ==

This isn't clear from Rob's post, but it should be made clear: we CAN copy our OWN content from the existing wiki. IE, I plan to copy/paste my XML-RPC notes from the existing one. Does that present an issue? If so, why?
[[User:Talarus Luan|Talarus Luan]] 16:03, 24 January 2007 (PST)
:If you are the sole author, it wouldn't. Just be careful and check the page history. [[User:Gigs Taggart|Gigs Taggart]] 16:10, 24 January 2007 (PST)

== Syntax Highlighting ==

Updated info on the syntax highlighting is available here [[http://rpgstats.com/wiki/index.php?title=GeSHiHiLight.php GeSHiHiLight]]
--[[User:Thraxis Epsilon|Thraxis Epsilon]] 16:10, 24 January 2007 (PST)

:Lets hope they include it soon ^^ [[User:Strife Onizuka|Strife Onizuka]] 21:21, 24 January 2007 (PST)
:Is there anyone we can ask? [[User:Dimentox Travanti|Dimentox Travanti]] 10:50, 25 January 2007 (PST)
:any news or update on this? [[User:Blueman Steele|Blueman Steele]] 6:12, 10 February 2007 (PST)

::We tried to use start using this on Thursday, but ran into some problems. Thraxis, it'll help if you can contact me privately to discuss some of the issues. -- [[User:Rob Linden|Rob Linden]] 00:37, 11 February 2007 (PST)

:What's the status of syntax highlighting? --[[User:Mokelembembe Mokeev|Mokelembembe Mokeev]] 15:11, 24 April 2007 (PDT)

::No one has made any efforts recently to get the highlighter included in the wiki. If you are going to post highlighted code, it would be good to have it output in such a way that keywords link to their appropriate pages. -- [[User:Strife Onizuka|Strife Onizuka]] 16:53, 24 April 2007 (PDT)

:Talked with Rob Liden - The concern with the script is about security and the possiblity of injecting PHP code into the script hilighting. Since its a possible security issue he would like somebody at Linden to look into and fix it. I'm going to look into the script and tell Rob what I found also. --[[User:Mokelembembe Mokeev|Mokelembembe Mokeev]] 15:29, 4 May 2007 (PDT)

== Let's refer to this simply as the "LSL portal" ==

Since there's already something out there called the "LSLwiki", let's refer to this as the LSL Portal to distinguish it. If there's no objection, I'll move the pages with "LSL Wiki" in the title to some other appropriate name -- [[User:Rob Linden|Rob Linden]] 17:09, 24 January 2007 (PST)
:No objections here. :) I just updated [[LSL Wiki To-do]] with some assignment tables. I went ahead and moved it to [[LSL Portal To-do]] [[User:Talarus Luan|Talarus Luan]] 18:12, 24 January 2007 (PST)
:: Simple, consistent messaging: I've gotten into the habit of using "LSL Portal" regularly myself.
:: --[[User:Torley Linden|Torley Linden]] 10:40, 31 January 2007 (PST)

== A way back... ==

Every page should have a header that goes back to the portal index not the wiki index.
if we could even geta link in the left hand would be great.

[[User:Dimentox Travanti|Dimentox Travanti]] 10:47, 25 January 2007 (PST)

: I second the idea of a link in the main Navigation list. It makes it a lot easier to access the LSL Portal.
: [[User:Cron Stardust|Cron Stardust]] 11:25, 5 March 2007 (PST)

== Transitions ==
Encouraging to see this happening — and to see [http://www.lslwiki.org/ a second mirror] for the [http://www.lslwiki.com LSL wiki] too; hopefully I haven't come too late, because these developments look like they've transpired over the last few days.

Just wanted to let you know I've added a link to our LSL Portal from our blog's Notices; it'll be up for some time. I'm also going to add a simple article to the [http://secondlife.com/knowledgebase/ Knowledge Base] directing to this LSL Portal, since it's important to get more contributors aware, interested, and involved.

I'd like to personally be more active in this wiki... great things are afoot. I've been spread across too many [http://secondlife.com/knowledgebase/article.php?id=357 communication channels] lately, so I've been rotating between focuses (foci?); hopefully next week I'll have more hands-on energy here.

Thanx to each and all of you building up this resource so far!

--[[User:Torley Linden|Torley Linden]] 10:21, 26 January 2007 (PST)

== LSL Header/Footer ==
Below is the header/footer template: <nowiki>{{LSL Header}}</nowiki>
{{LSL Header}}
Also, since <nowiki><lsl></lsl></nowiki> tags don't seem to work yet, I used <nowiki><pre></pre></nowiki>... hope that's alright, I know nothing about wikis except what I've taught myself tonight. --[[User:DoteDote Edison|DoteDote Edison]] 20:45, 27 January 2007 (EST)
:Actually, go ahead and use the <nowiki><lsl></lsl></nowiki> tags. Even though it may look like crap right this minute, as soon as the module is installed, it will instantly be perfect. :) [[User:Talarus Luan|Talarus Luan]] 14:59, 29 January 2007 (PST)

== LSL wiki-namespace ==

All the LSL pages are prefixed with "LSL ", like "LSL Portal", "LSL LLRand", etc. It would seem more justly to use the wiki-namespace "LSL:". Change the names from "LSL LLRand" to "LSL:LLRand". My 2 lindens. [[User:Dzonatas Sol|Dzonatas Sol]] 00:28, 2 February 2007 (PST)
:Just thought about this little more. We could use subpages instead of namespaces, then the talk pages will fully work. "LSL/LLRand" for example [[User:Dzonatas Sol|Dzonatas Sol]] 00:41, 2 February 2007 (PST)
::I'm not going to make a big fuss about it, but I'd prefer if, per the [[Editing Guidelines]], that the page just be called "LLRand". -- [[User:Rob Linden|Rob Linden]] 01:06, 2 February 2007 (PST)
:As this wiki has grown a great deal in other aspects the need for a namespace for LSL: has become even greater. This would allow the search functions to isolate LSL results from the more general content unrelated to LSL. This would also start a shift from many listings being sorted entirely under '''L'''. — [[User:Kizmut Smit|kizmut]][[User Talk:Kizmut Smit|T]]/[[Special:Contributions/Kizmut Smit|C]] 12:02, 14 June 2012 (PDT)

== LSL conformance test ==

Hi folks, we're planning to consolidate a lot of our scattered LSL conformance tests on this wiki. I created two rather crude templates: [[Template:LSL conformance test]] and [[Template:LSL conformance script]], which were created for adding our conformance suite. See [[LSL llGetUnixTime test]] for an example. I'd like to get a sense from people if this is a sensible way to do this. The idea is to get these templates stabilized, and that will provide us a mechanism for those of us at LL to consolidate our tests. Of course, if the community wants to chip in, that's great too...having items in our standard LSL conformance suite makes it less likely that we'll break an LSL feature that's important to you. -- [[User:Rob Linden|Rob Linden]] 22:53, 7 February 2007 (PST)

== LSL Categories List ==
What about a vertical list of categories down the right side of the LSL Portal front page? The right-side list on the original wiki was my primary source of navigation, but maybe I'm odd. I could add it myself, but I'm not sure how to make it automatically update the list as new categories are added. --[[User:DoteDote Edison|DoteDote Edison]] 20:20, 9 February 2007 (EST)
:Oops... right after I posted this, I noticed that it's item #4 on the "To-Do" list. I went ahead and modified the front page to add a cetagories list. If you don't like it, feel free to revert. --[[User:DoteDote Edison|DoteDote Edison]] 20:55, 9 February 2007 (EST)
:The names all start with "LSL" and the names are not optimal for listing... The names could be changed though. I'll dig though the MediaWiki commands later and see if I can find any that would work well in this case. I don't have high hopes in this case. [[User:Strife Onizuka|Strife Onizuka]] 18:59, 9 February 2007 (PST)
Is the 200 articles per category page a mediawiki limit, or can we change it to 400 per page in a configuration somewhere? [[User:DoteDote Edison|DoteDote Edison]] 21:50, 22 February 2007 (EST)

:If there's an issue with seeing all the pages, I can add the alphabetical navigation template later.
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 06:16, 23 February 2007 (PST)

== Internationalizing ==

How do we want to go about internationalizing the LSL wiki. It should probably be tied into the global wiki effort. [[User:Strife Onizuka|Strife Onizuka]] 07:20, 11 February 2007 (PST)

:With modular templates (e.g. the way I do them) vs monolithic templates (e.g. the way you do them), the templates won't need to be changed, only the content going into them. Regarding [[User talk:SignpostMarv Martin/Sandbox/Project:Internationalisation#multi-lingual articles|Project:Internationalisation#multi-lingual articles]], I have some freaky ideas to make maintenance of the LSL-specific multi-lingual articles a little easier to maintain. p.s. I'm not sure whether Internationalisation of the LSL articles should be discussed here or [[User talk:SignpostMarv Martin/Sandbox/Project:Internationalisation#multi-lingual articles|there]]. [[User:SignpostMarv Martin|SignpostMarv Martin]] 08:05, 11 February 2007 (PST) [[Talk:LSL_Function_Style|Moved from Talk:LSL_Function_Style]]

::But your idea on templates don't provide structure, it requires the user to provide the structure and if we want to change the layout of the pages we need to go through and change ever single page. I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables. We wouldn't be using the template-template directly for rendering but use [http://meta.wikimedia.org/wiki/Help:Substitution substitution]. Changing a dozen monolithic templates is better then changing a dozen * 328 pages. Also means that you get the same translation ever single time. I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist. No special modifications to the links needed.[[User:Strife Onizuka|Strife Onizuka]] 06:43, 13 February 2007 (PST)
:::''But your idea on templates don't provide structure, it requires the user to provide the structure''
:::* That's kinda the point. Look at what information will need to be reused over and over again, and put it into a small template. Then those templates can be used directly, or as part of a wrapper template.
:::''I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables.''
:::* The templates don't need translating, just the content.
:::''I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist.''
:::* That would be bad.
:::* Better idea to follow.
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 13:13, 13 February 2007 (PST)
:::[[Template:Multi-lang]] I've given up fixing the bugs in that, but you get the idea behind it's intent. Include [[Help:Getting_started_in_Second_Life/langs]] in your test page and <nowiki>{{#vardefine:article-lang}}</nowiki> to either '''spa'' or '''eng'''.
:::Please fork the code into your own userspace if you're going to work on it (unless you know of an instant fix) to prevent edit collisions.
:::I've also started work on [[Template:ISO_639-3/native]] to save a bit of time with entering languages that one browser might not be configured for (e.g. the higher-end UTF-8 characters)
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 22:08, 19 February 2007 (PST)

:[[User:CatherinePfeffer|Catherine Pfeffer]] Starting translation of the LSL Portal to French with the group "Constructeurs et scripteurs"

: Please refer to a related discussion on [[Project:Languages]]. -- [[User:Alissa Sabre|Alissa Sabre]] 07:58, 4 November 2007 (PST)

== phasing out of [[Template:LSLG]] ==

Since the need to prefix almost everything with LSL_ is now being removed, all articles that are calling [[Template:LSLG]] should be edited to use a Wiki link, as the template is now rather redundant.

The list of articles calling [[Template:LSLG|LSLG]] can be viewed via [https://wiki.secondlife.com/w/index.php?title=Special:Whatlinkshere&target=Template%3ALSLG Special:Whatlinkshere].
 [[User:SignpostMarv Martin|SignpostMarv Martin]] 22:08, 19 February 2007 (PST)

:I think the pages in the {{LSLGC|FixMe}} category should be of a higher priority. Phasing out usage is reasonable, going through every page that uses it on the other hand just to remove it would be a waste of resources. I'm a bit nervous about stopping using it at present, the metaphoric paint hasn't even dried on the move yet. Considering it doesn't effect the rendering, phasing it's usage out is appropriate. [[User:Strife Onizuka|Strife Onizuka]] 23:20, 20 February 2007 (PST)
::Waste of resources ?
::Isn't it a waste of resources to use a template that in most cases is entirely redundant ?
::[[User:SignpostMarv Martin|SignpostMarv Martin]] 02:23, 21 February 2007 (PST)
:::We haven't even finihed moving the function pages to the new names and template yet. You could help with that instead of worrying about templates, you know. [[User:Gigs Taggart|Gigs Taggart]] 07:35, 21 February 2007 (PST)

== The original LSL Wiki is back! ==
Catherine Omega's [http://www.lslwiki.net original LSL Wiki] is back. She mentioned:

: ''"This is DEFINITELY back. And it's definitely permanent. It's all editable. And it's the 'official', Catherine-Omega-approved one."''

[http://www.catherineomega.com/2007/37/the-lsl-wiki-finds-a-new-home Further context can be found @ her blog.] --[[User:Torley Linden|Torley Linden]] 13:41, 28 February 2007 (PST)

== Table ==

I've been playing with the table (again). I've tried to get it so it looks decent in both IE and Firefox. I've been trying to get it to put all the extra space into the last section, which I managed in Firefox but haven't figured out the correct permutation of parameters for IE. I'm content at this moment to leave it be (I use Firefox). [[User:Strife Onizuka|Strife Onizuka]] 08:49, 17 March 2007 (PDT)

== Warning notice? ==

Might it be an idea to include a short warning on the top of this page that the LSL Portal is as yet incomplete?

I just spent a while trying to find a list function I knew existed, but couldn't remember the exact name of, which hasn't made it here yet before realising that not all functions are listed yet.
--[[User:Nick Shatner|Nick Shatner]], 02:56, 2 May 2007 (PDT)

:The vast majority of functions have been catagorized so if you had started from the {{LSLGC|List|list category page}} you probably would have found it. There are a small handful of functions that haven't been catagorized beyond the {{LSLGC|Functions}} category. I'm not sure if a warning is warranted but I do recognize there are gaps in the LSL information. -- [[User:Strife Onizuka|Strife Onizuka]] 13:31, 2 May 2007 (PDT)

llSetText page
which is here
http://wiki.secondlife.com/wiki/LlSetText
is missing from page listing all the functions. Can't quite figure out how that page gets its info, so not going to touch it.
-- (anonymous and undated) (because not signed with dash dash tilde tilde tilde tilde)

:http://wiki.secondlife.com/w/index.php?title=Category:LSL_Functions&from=PlaySound
:includes [[llSetText]] nowadays
:maybe because "LSL Functions" appears in the Categories list at the end nowadays.
:-- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 05:57, 2 December 2007 (PST)

== Conspiracy? ==

I whould like to know if 
a) this is a public wiki, where everybody can contribute so the LSL gets better known, or if it is a private viki with conspirativ charakter 
b) why it is kept so spartanik with information 
c) why no lindens who wrote LSL document their work 
d) why some private persons are called administrators, what rights do they have, and if they have ever signed a paper that makes them not abuse theyr position 
e) why linden lab employees never fisicaly work and only give "precios advises" 
dont dare to delete this. 
{{User|Anylyn Hax}} 04:09, 8 August 2007 (PDT)

:I shall try to answer:
:a) It is a public wiki but not everyone can contribute, you must have an SL account to contribute.
:b) No one has added more information.
:c) They did, it's in the LSL manual that ships with the client (it's common knowledge that it sucks).
:d) I don't know of any non-linden administrators on the wiki.
:e) The design of LSL is stable and there are very few LSL bugs that haven't been vetted; it would surprise me if there were any full time LSL devs. Just because we don't see them working doesn't mean they aren't working; the SL code base is huge.
:-- [[User:Strife Onizuka|Strife Onizuka]] 12:56, 8 August 2007 (PDT)

== Vehicle Tutorial ==

Could we get the original vehicle tutorial added to this wiki. I realize it's not in the correct format, but it's a place to start. There was a wikified version too in the old wiki someone did, but they'd have to contribute it themselves I'd think. I can't find the original tutorial outside the old wiki.

:The tutorial was part of the LSL manual that ships with the client. LL has given permission to post it on the wiki. -- [[User:Strife Onizuka|Strife Onizuka]] 16:37, 8 September 2007 (PDT)

::I found an old copy I had and wikified it. This is pretty much the original version, so it's probably a bit whacked, please fix any problems you're aware of [[User:Ralph Doctorow|Ralph Doctorow]]

== color ==

It would be very helpful if I could use different colored text when writing my articles. Could buttons be added for black text, red text, green text, and one other color of text? Or could someone list the codes that can be used to change text color?

Just as an example of what I intend to use color for:

''black''rotation ''red''variable''black''=<''red''%,%,%,''green''#.#''black''>;

-- Anonymous, Undated

: The LSL /LSL tags give colour to LSL code, ''e.g.'':

<lsl>vector up = < 0, 0, 1 >;</lsl> -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:20, 3 January 2009 (UTC)

== LSL tags and automatic linking: some errors noticed ==

I'm not aware of a specific template to edit/update, but I've noticed some of auto-linked functions and constants from <nowiki><lsl></lsl></nowiki> tags point to incorrect or 'bad' (not found) pages. case in point, llSay points to Lsl_LLSay (which will redirect), and PUBLIC_CHANNEL points to a non-existant search page (there is an actual page available, but it doesn't go there). I'm sure there are other examples of this, but I'm not aware of a way to update it....

also curious to know if there is any hope of having localized pages (like french) redirect to their language equivalents through these tags at some point (I know it's not really feasible at the moment)
-- [[User:Void Singer|Void Singer]] 13:42, 19 February 2008 (PST)

== Hacks? ==

Could we please create a hacks page to be linked on the main LSL portal. Similiar to the old LSL wiki of compiling a growing list of well known tricks and tips for scripting.

For example a well known trick, which I use frequently is the use of (List!=[]) instead of llGetListLength. --[[User:Nexii Malthus|Nexii Malthus]] 07:38, 19 May 2008 (PDT)

:I've slapped a page together: [[LSL Hacks]]. I'd like comments on the style and layout. Please in the future don't stand on ceremony, if a niche needs filling, then please fill it with content. I have found that if you wait for people to weigh in before you start then nothing will get done. Better to do your best and make adjustments when there is a stink. -- [[User:Strife Onizuka|Strife Onizuka]] 09:37, 19 May 2008 (PDT)

== LSLwiki.net ==
(moved from [{{fullurl:Template talk:LSL Function|oldid=110833}} Template talk:LSL Function])

I had a discussion with [[User:Gally Young|Gally]] today and we came to the following conclusion: Since we're not able to copy content from [http://www.lslwiki.net lslwiki.net] and vice versa - because of licensing problems - we might benefit from linking related articles of both wikis. So users can easily switch from one Wiki to the other and find the information most helpful for them. There shouldn't be a rivalry between these two documentation projects. They should benefit from each other. Therefor, we're adding a link to the related LSLwiki.net article to this template. I hope it's ok. 
Something else on the same topic: It seems to be(come) quite popular in Wiki culture to double-license the own contributions, in order to make them easier to share. Wikis of interest for us:
* The Second Life Wiki (of course): [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]
* The [http://www.lslwiki.net LSLwiki.net]: an [http://lslwiki.net/lslwiki/wakka.php?wakka=LSLwikicopyright implicit copyright model]
* The [http://secondlife.wikia.com/wiki/Main_Page SecondLife Wikia]: [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License]
Please consider to double-license your contributions to this (or other) Wikis in order to make them easier to share, by writing a statemanet about double licensing on your userpage. You can also use one of [[User:SignpostMarv Martin|Marv]]'s templates: [[Template:Re-license contributions]] as well as [[Template:License]]. 
This is just a ''suggestion'' of course. Just do it, in case you want to do it. 
Greetz, [[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 20:14, 9 September 2008 (PDT)

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

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

* I take it you haven't see the [[Template:LSL Header|Header]] at the top of every article in the [[LSL Portal]]. It has all those links you call for. (Those articles didn't get popular because people used "Search").
* The [[LSL Portal Guidelines]] contains not just the rules but the mission statement for the LSL Portal. It is fundamental to the this portals continued existence. Without it we would lack direction, and defined social guidelines. Without defined guidelines we would eventual descend into chaos (I've seen it happen; the writing of the guidelines has mostly been in reaction to specific incidents). It needs to be in a prominent position so that editors will find it and read it (or can't make excuses as to why they haven't read it).
* Like the [[LSL Portal Guidelines]], the [[LSL Portal To-do]] link is in a section dedicated to the [[LSL Portal]] as a whole, not to LSL scripting. The rest of the page is dedicated to scripting. It's a small section.
-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:14, 23 April 2010 (UTC)

== Proposal About "LSL Categories" Section ==

I find current view is too messing and difficult to find what I need. The users end up looking in huge list of {{LSLGC|Functions}}, clicking much. I am thinking about organizing the list to easily look up the LSL articles.

Here is the proposal of categorizing.
<pre>
Avatar
- Animation
- Attachment
- Behavior
- Camera
- Properties
Land
- Parcel
- Region
Object
- Detection
- Existence
- Face
- Inventory
- Link
- Media
- Physic
- Properties
- Text
Script
- Control
　- Convert
- List
- Math
- Network
- String
- Time
</pre>

I tried to sort all existing 339 functions (except God, not active one).
Here is the list ---> [[User:Mako_Nozaki/Category_Function]]

My thought is, current categories will remain as is and will be used as "tags". Missing categories will be added and be linked from each functions. Adding these categories to LSL Header using Javascript (pulldown menu) might be cool. --[[User:Mako Nozaki|Mako]] 12:56, 1 May 2010 (UTC)

== User-Defined Functions ==

I'm personally adverse to linking to the template description rather than the category (which already back links to the template) in the "language reference" section, as per the [[https://wiki.secondlife.com/w/index.php?title=LSL_Portal&diff=0&oldid=1158048|most recent edit]]. but since it's obvious someone else is not I thought I'd solicit thoughts before reverting it. I'm thinking it could be more clear on the category page though. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 22:49, 10 May 2012 (PDT)

:I agree with you. In addition to that, I think the two articles should be merged. We gain nothing of value by having them separate. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:37, 11 May 2012 (PDT)

::Pointed the link back at the category, folded the article into the category page, and marked the original article page for deletion. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 10:45, 1 June 2012 (PDT)

== Categories ==

It's probably time to update the category list and tree again. It's been a while and I'm sure I've added more since the last time we update them. Also I should remember to update the LSL News box. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:42, 11 May 2012 (PDT)
:There are extensions that can update the category list automagically like [https://www.mediawiki.org/wiki/Extension:DynamicPageList_(Wikimedia) Extension:DynamicPageList]. I am not sure one is installed here. Would we have to wait for a Linden to set something up like this? — [[User:Kizmut Smit|kizmut]][[User Talk:Kizmut Smit|T]]/[[Special:Contributions/Kizmut Smit|C]] 12:18, 14 June 2012 (PDT)

Talk:LSL Portal

2012-06-14T19:05:45Z

Kizmut Smit: +L /* LSL wiki-namespace */

Talk:LSL Portal

2012-06-14T19:02:18Z

Kizmut Smit: !/* LSL wiki-namespace */ !

{{LSL Header}}{{Talk}}
= Please do not copy content from LSLwiki =

From [http://forums.secondlife.com/showpost.php?p=1392697&postcount=44 Rob Linden's post to the forum]:
:Hi folks, sorry for dropping into this conversation late. I haven't read through everything here, but I'd like to present an alternative.

:There have been several requests that Linden Lab take on the hosting of the LSL wiki. There are several problems with us doing this work. The primary problem is the question of ownership of the material. Since, to the best of our knowledge, there was never an explicit, consistent notice of ownership of this material throughout its creation, nor a clear assignment/license associated with contributing more material, it would seem the only safe way to license this content would be to contact every single contributor throughout the life of the wiki and get an explicit license or copyright assignment from them. Note that I said "safe", not "practical".

:We're not in a position to go down that road. However, we do have wiki.secondlife.com, which has had, since day one, a very clear notice about the license under which contributions are made and distributed. We would be very happy to see the community collaborate on newly created content on wiki.secondlife.com. As long as you author the content (not cut and paste from sources you are not the sole author of), we welcome your contribution. -- [[User:Rob Linden|Rob Linden]] 14:30, 24 January 2007 (PST)

----

OK, so let's talk about formatting rules for entries.

(Moved to [[LSL Portal Guidelines]], so that this talk doesn't get too cluttered.) -- [[User:Talarus Luan|Talarus Luan]] 16:32, 24 January 2007 (PST)

[[User:Talarus Luan|Talarus Luan]] 14:28, 24 January 2007 (PST)

----

=Other Discussion=

== LSL Guide lost ==

http://svn.secondlife.com/trac/linden/changeset/1392
linked from the page history
says new residents downloading the client won't be getting a copy of the LSL_Guide.html any more ...

Q1. Where on the web do new residents go to get the LSL_Guide now? -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:17, 3 January 2009 (UTC)

Q2. How should this [[LSL Portal]] page tell new residents to be sure to read the LSL_Guide first to correctly understand what else we say here? -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:17, 3 January 2009 (UTC)

== Untitled Chat ==

Should we make this the front page to the LSL reference, or put that one more level down? I kinda lean toward the former. [[User:Gigs Taggart|Gigs Taggart]] 14:09, 24 January 2007 (PST)

----

Yeah i think so... (Unsigned by Dimentox Travanti}
:Remember to sign your post with four tildes. [[User:Gigs Taggart|Gigs Taggart]] 14:26, 24 January 2007 (PST)

I used a modified version of the [http://meta.wikimedia.org/wiki/User:Ajqnic:GeSHiHighlight GeSHiHighlight] plugin for MediaWiki. With an LSL syntax file. The license for the plugin and for [http://qbnz.com/highlighter/ GeSHi] is GPL, it also requires another plugin [http://meta.wikimedia.org/wiki/User:Ajqnic:purgePage purgePage].
--[[User:Thraxis Epsilon|Thraxis Epsilon]] 15:00, 24 January 2007 (PST)

== Regarding copying content from the existing Wiki ==

This isn't clear from Rob's post, but it should be made clear: we CAN copy our OWN content from the existing wiki. IE, I plan to copy/paste my XML-RPC notes from the existing one. Does that present an issue? If so, why?
[[User:Talarus Luan|Talarus Luan]] 16:03, 24 January 2007 (PST)
:If you are the sole author, it wouldn't. Just be careful and check the page history. [[User:Gigs Taggart|Gigs Taggart]] 16:10, 24 January 2007 (PST)

== Syntax Highlighting ==

Updated info on the syntax highlighting is available here [[http://rpgstats.com/wiki/index.php?title=GeSHiHiLight.php GeSHiHiLight]]
--[[User:Thraxis Epsilon|Thraxis Epsilon]] 16:10, 24 January 2007 (PST)

:Lets hope they include it soon ^^ [[User:Strife Onizuka|Strife Onizuka]] 21:21, 24 January 2007 (PST)
:Is there anyone we can ask? [[User:Dimentox Travanti|Dimentox Travanti]] 10:50, 25 January 2007 (PST)
:any news or update on this? [[User:Blueman Steele|Blueman Steele]] 6:12, 10 February 2007 (PST)

::We tried to use start using this on Thursday, but ran into some problems. Thraxis, it'll help if you can contact me privately to discuss some of the issues. -- [[User:Rob Linden|Rob Linden]] 00:37, 11 February 2007 (PST)

:What's the status of syntax highlighting? --[[User:Mokelembembe Mokeev|Mokelembembe Mokeev]] 15:11, 24 April 2007 (PDT)

::No one has made any efforts recently to get the highlighter included in the wiki. If you are going to post highlighted code, it would be good to have it output in such a way that keywords link to their appropriate pages. -- [[User:Strife Onizuka|Strife Onizuka]] 16:53, 24 April 2007 (PDT)

:Talked with Rob Liden - The concern with the script is about security and the possiblity of injecting PHP code into the script hilighting. Since its a possible security issue he would like somebody at Linden to look into and fix it. I'm going to look into the script and tell Rob what I found also. --[[User:Mokelembembe Mokeev|Mokelembembe Mokeev]] 15:29, 4 May 2007 (PDT)

== Let's refer to this simply as the "LSL portal" ==

Since there's already something out there called the "LSLwiki", let's refer to this as the LSL Portal to distinguish it. If there's no objection, I'll move the pages with "LSL Wiki" in the title to some other appropriate name -- [[User:Rob Linden|Rob Linden]] 17:09, 24 January 2007 (PST)
:No objections here. :) I just updated [[LSL Wiki To-do]] with some assignment tables. I went ahead and moved it to [[LSL Portal To-do]] [[User:Talarus Luan|Talarus Luan]] 18:12, 24 January 2007 (PST)
:: Simple, consistent messaging: I've gotten into the habit of using "LSL Portal" regularly myself.
:: --[[User:Torley Linden|Torley Linden]] 10:40, 31 January 2007 (PST)

== A way back... ==

Every page should have a header that goes back to the portal index not the wiki index.
if we could even geta link in the left hand would be great.

[[User:Dimentox Travanti|Dimentox Travanti]] 10:47, 25 January 2007 (PST)

: I second the idea of a link in the main Navigation list. It makes it a lot easier to access the LSL Portal.
: [[User:Cron Stardust|Cron Stardust]] 11:25, 5 March 2007 (PST)

== Transitions ==
Encouraging to see this happening — and to see [http://www.lslwiki.org/ a second mirror] for the [http://www.lslwiki.com LSL wiki] too; hopefully I haven't come too late, because these developments look like they've transpired over the last few days.

Just wanted to let you know I've added a link to our LSL Portal from our blog's Notices; it'll be up for some time. I'm also going to add a simple article to the [http://secondlife.com/knowledgebase/ Knowledge Base] directing to this LSL Portal, since it's important to get more contributors aware, interested, and involved.

I'd like to personally be more active in this wiki... great things are afoot. I've been spread across too many [http://secondlife.com/knowledgebase/article.php?id=357 communication channels] lately, so I've been rotating between focuses (foci?); hopefully next week I'll have more hands-on energy here.

Thanx to each and all of you building up this resource so far!

--[[User:Torley Linden|Torley Linden]] 10:21, 26 January 2007 (PST)

== LSL Header/Footer ==
Below is the header/footer template: <nowiki>{{LSL Header}}</nowiki>
{{LSL Header}}
Also, since <nowiki><lsl></lsl></nowiki> tags don't seem to work yet, I used <nowiki><pre></pre></nowiki>... hope that's alright, I know nothing about wikis except what I've taught myself tonight. --[[User:DoteDote Edison|DoteDote Edison]] 20:45, 27 January 2007 (EST)
:Actually, go ahead and use the <nowiki><lsl></lsl></nowiki> tags. Even though it may look like crap right this minute, as soon as the module is installed, it will instantly be perfect. :) [[User:Talarus Luan|Talarus Luan]] 14:59, 29 January 2007 (PST)

== LSL wiki-namespace ==

All the LSL pages are prefixed with "LSL ", like "LSL Portal", "LSL LLRand", etc. It would seem more justly to use the wiki-namespace "LSL:". Change the names from "LSL LLRand" to "LSL:LLRand". My 2 lindens. [[User:Dzonatas Sol|Dzonatas Sol]] 00:28, 2 February 2007 (PST)
:Just thought about this little more. We could use subpages instead of namespaces, then the talk pages will fully work. "LSL/LLRand" for example [[User:Dzonatas Sol|Dzonatas Sol]] 00:41, 2 February 2007 (PST)
::I'm not going to make a big fuss about it, but I'd prefer if, per the [[Editing Guidelines]], that the page just be called "LLRand". -- [[User:Rob Linden|Rob Linden]] 01:06, 2 February 2007 (PST)
:As this wiki has grown a great deal in other aspects the need for a namespace for LSL: has become even greater. This would allow the search functions to isolate LSL results from the more general content unrelated to LSL. — [[User:Kizmut Smit|kizmut]][[User Talk:Kizmut Smit|T]]/[[Special:Contributions/Kizmut Smit|C]] 12:02, 14 June 2012 (PDT)

== LSL conformance test ==

Hi folks, we're planning to consolidate a lot of our scattered LSL conformance tests on this wiki. I created two rather crude templates: [[Template:LSL conformance test]] and [[Template:LSL conformance script]], which were created for adding our conformance suite. See [[LSL llGetUnixTime test]] for an example. I'd like to get a sense from people if this is a sensible way to do this. The idea is to get these templates stabilized, and that will provide us a mechanism for those of us at LL to consolidate our tests. Of course, if the community wants to chip in, that's great too...having items in our standard LSL conformance suite makes it less likely that we'll break an LSL feature that's important to you. -- [[User:Rob Linden|Rob Linden]] 22:53, 7 February 2007 (PST)

== LSL Categories List ==
What about a vertical list of categories down the right side of the LSL Portal front page? The right-side list on the original wiki was my primary source of navigation, but maybe I'm odd. I could add it myself, but I'm not sure how to make it automatically update the list as new categories are added. --[[User:DoteDote Edison|DoteDote Edison]] 20:20, 9 February 2007 (EST)
:Oops... right after I posted this, I noticed that it's item #4 on the "To-Do" list. I went ahead and modified the front page to add a cetagories list. If you don't like it, feel free to revert. --[[User:DoteDote Edison|DoteDote Edison]] 20:55, 9 February 2007 (EST)
:The names all start with "LSL" and the names are not optimal for listing... The names could be changed though. I'll dig though the MediaWiki commands later and see if I can find any that would work well in this case. I don't have high hopes in this case. [[User:Strife Onizuka|Strife Onizuka]] 18:59, 9 February 2007 (PST)
Is the 200 articles per category page a mediawiki limit, or can we change it to 400 per page in a configuration somewhere? [[User:DoteDote Edison|DoteDote Edison]] 21:50, 22 February 2007 (EST)

:If there's an issue with seeing all the pages, I can add the alphabetical navigation template later.
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 06:16, 23 February 2007 (PST)

== Internationalizing ==

How do we want to go about internationalizing the LSL wiki. It should probably be tied into the global wiki effort. [[User:Strife Onizuka|Strife Onizuka]] 07:20, 11 February 2007 (PST)

:With modular templates (e.g. the way I do them) vs monolithic templates (e.g. the way you do them), the templates won't need to be changed, only the content going into them. Regarding [[User talk:SignpostMarv Martin/Sandbox/Project:Internationalisation#multi-lingual articles|Project:Internationalisation#multi-lingual articles]], I have some freaky ideas to make maintenance of the LSL-specific multi-lingual articles a little easier to maintain. p.s. I'm not sure whether Internationalisation of the LSL articles should be discussed here or [[User talk:SignpostMarv Martin/Sandbox/Project:Internationalisation#multi-lingual articles|there]]. [[User:SignpostMarv Martin|SignpostMarv Martin]] 08:05, 11 February 2007 (PST) [[Talk:LSL_Function_Style|Moved from Talk:LSL_Function_Style]]

::But your idea on templates don't provide structure, it requires the user to provide the structure and if we want to change the layout of the pages we need to go through and change ever single page. I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables. We wouldn't be using the template-template directly for rendering but use [http://meta.wikimedia.org/wiki/Help:Substitution substitution]. Changing a dozen monolithic templates is better then changing a dozen * 328 pages. Also means that you get the same translation ever single time. I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist. No special modifications to the links needed.[[User:Strife Onizuka|Strife Onizuka]] 06:43, 13 February 2007 (PST)
:::''But your idea on templates don't provide structure, it requires the user to provide the structure''
:::* That's kinda the point. Look at what information will need to be reused over and over again, and put it into a small template. Then those templates can be used directly, or as part of a wrapper template.
:::''I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables.''
:::* The templates don't need translating, just the content.
:::''I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist.''
:::* That would be bad.
:::* Better idea to follow.
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 13:13, 13 February 2007 (PST)
:::[[Template:Multi-lang]] I've given up fixing the bugs in that, but you get the idea behind it's intent. Include [[Help:Getting_started_in_Second_Life/langs]] in your test page and <nowiki>{{#vardefine:article-lang}}</nowiki> to either '''spa'' or '''eng'''.
:::Please fork the code into your own userspace if you're going to work on it (unless you know of an instant fix) to prevent edit collisions.
:::I've also started work on [[Template:ISO_639-3/native]] to save a bit of time with entering languages that one browser might not be configured for (e.g. the higher-end UTF-8 characters)
:::[[User:SignpostMarv Martin|SignpostMarv Martin]] 22:08, 19 February 2007 (PST)

:[[User:CatherinePfeffer|Catherine Pfeffer]] Starting translation of the LSL Portal to French with the group "Constructeurs et scripteurs"

: Please refer to a related discussion on [[Project:Languages]]. -- [[User:Alissa Sabre|Alissa Sabre]] 07:58, 4 November 2007 (PST)

== phasing out of [[Template:LSLG]] ==

Since the need to prefix almost everything with LSL_ is now being removed, all articles that are calling [[Template:LSLG]] should be edited to use a Wiki link, as the template is now rather redundant.

The list of articles calling [[Template:LSLG|LSLG]] can be viewed via [https://wiki.secondlife.com/w/index.php?title=Special:Whatlinkshere&target=Template%3ALSLG Special:Whatlinkshere].
 [[User:SignpostMarv Martin|SignpostMarv Martin]] 22:08, 19 February 2007 (PST)

:I think the pages in the {{LSLGC|FixMe}} category should be of a higher priority. Phasing out usage is reasonable, going through every page that uses it on the other hand just to remove it would be a waste of resources. I'm a bit nervous about stopping using it at present, the metaphoric paint hasn't even dried on the move yet. Considering it doesn't effect the rendering, phasing it's usage out is appropriate. [[User:Strife Onizuka|Strife Onizuka]] 23:20, 20 February 2007 (PST)
::Waste of resources ?
::Isn't it a waste of resources to use a template that in most cases is entirely redundant ?
::[[User:SignpostMarv Martin|SignpostMarv Martin]] 02:23, 21 February 2007 (PST)
:::We haven't even finihed moving the function pages to the new names and template yet. You could help with that instead of worrying about templates, you know. [[User:Gigs Taggart|Gigs Taggart]] 07:35, 21 February 2007 (PST)

== The original LSL Wiki is back! ==
Catherine Omega's [http://www.lslwiki.net original LSL Wiki] is back. She mentioned:

: ''"This is DEFINITELY back. And it's definitely permanent. It's all editable. And it's the 'official', Catherine-Omega-approved one."''

[http://www.catherineomega.com/2007/37/the-lsl-wiki-finds-a-new-home Further context can be found @ her blog.] --[[User:Torley Linden|Torley Linden]] 13:41, 28 February 2007 (PST)

== Table ==

I've been playing with the table (again). I've tried to get it so it looks decent in both IE and Firefox. I've been trying to get it to put all the extra space into the last section, which I managed in Firefox but haven't figured out the correct permutation of parameters for IE. I'm content at this moment to leave it be (I use Firefox). [[User:Strife Onizuka|Strife Onizuka]] 08:49, 17 March 2007 (PDT)

== Warning notice? ==

Might it be an idea to include a short warning on the top of this page that the LSL Portal is as yet incomplete?

I just spent a while trying to find a list function I knew existed, but couldn't remember the exact name of, which hasn't made it here yet before realising that not all functions are listed yet.
--[[User:Nick Shatner|Nick Shatner]], 02:56, 2 May 2007 (PDT)

:The vast majority of functions have been catagorized so if you had started from the {{LSLGC|List|list category page}} you probably would have found it. There are a small handful of functions that haven't been catagorized beyond the {{LSLGC|Functions}} category. I'm not sure if a warning is warranted but I do recognize there are gaps in the LSL information. -- [[User:Strife Onizuka|Strife Onizuka]] 13:31, 2 May 2007 (PDT)

llSetText page
which is here
http://wiki.secondlife.com/wiki/LlSetText
is missing from page listing all the functions. Can't quite figure out how that page gets its info, so not going to touch it.
-- (anonymous and undated) (because not signed with dash dash tilde tilde tilde tilde)

:http://wiki.secondlife.com/w/index.php?title=Category:LSL_Functions&from=PlaySound
:includes [[llSetText]] nowadays
:maybe because "LSL Functions" appears in the Categories list at the end nowadays.
:-- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 05:57, 2 December 2007 (PST)

== Conspiracy? ==

I whould like to know if 
a) this is a public wiki, where everybody can contribute so the LSL gets better known, or if it is a private viki with conspirativ charakter 
b) why it is kept so spartanik with information 
c) why no lindens who wrote LSL document their work 
d) why some private persons are called administrators, what rights do they have, and if they have ever signed a paper that makes them not abuse theyr position 
e) why linden lab employees never fisicaly work and only give "precios advises" 
dont dare to delete this. 
{{User|Anylyn Hax}} 04:09, 8 August 2007 (PDT)

:I shall try to answer:
:a) It is a public wiki but not everyone can contribute, you must have an SL account to contribute.
:b) No one has added more information.
:c) They did, it's in the LSL manual that ships with the client (it's common knowledge that it sucks).
:d) I don't know of any non-linden administrators on the wiki.
:e) The design of LSL is stable and there are very few LSL bugs that haven't been vetted; it would surprise me if there were any full time LSL devs. Just because we don't see them working doesn't mean they aren't working; the SL code base is huge.
:-- [[User:Strife Onizuka|Strife Onizuka]] 12:56, 8 August 2007 (PDT)

== Vehicle Tutorial ==

Could we get the original vehicle tutorial added to this wiki. I realize it's not in the correct format, but it's a place to start. There was a wikified version too in the old wiki someone did, but they'd have to contribute it themselves I'd think. I can't find the original tutorial outside the old wiki.

:The tutorial was part of the LSL manual that ships with the client. LL has given permission to post it on the wiki. -- [[User:Strife Onizuka|Strife Onizuka]] 16:37, 8 September 2007 (PDT)

::I found an old copy I had and wikified it. This is pretty much the original version, so it's probably a bit whacked, please fix any problems you're aware of [[User:Ralph Doctorow|Ralph Doctorow]]

== color ==

It would be very helpful if I could use different colored text when writing my articles. Could buttons be added for black text, red text, green text, and one other color of text? Or could someone list the codes that can be used to change text color?

Just as an example of what I intend to use color for:

''black''rotation ''red''variable''black''=<''red''%,%,%,''green''#.#''black''>;

-- Anonymous, Undated

: The LSL /LSL tags give colour to LSL code, ''e.g.'':

<lsl>vector up = < 0, 0, 1 >;</lsl> -- [[User:Ppaatt Lynagh|Ppaatt Lynagh]] 16:20, 3 January 2009 (UTC)

== LSL tags and automatic linking: some errors noticed ==

I'm not aware of a specific template to edit/update, but I've noticed some of auto-linked functions and constants from <nowiki><lsl></lsl></nowiki> tags point to incorrect or 'bad' (not found) pages. case in point, llSay points to Lsl_LLSay (which will redirect), and PUBLIC_CHANNEL points to a non-existant search page (there is an actual page available, but it doesn't go there). I'm sure there are other examples of this, but I'm not aware of a way to update it....

also curious to know if there is any hope of having localized pages (like french) redirect to their language equivalents through these tags at some point (I know it's not really feasible at the moment)
-- [[User:Void Singer|Void Singer]] 13:42, 19 February 2008 (PST)

== Hacks? ==

Could we please create a hacks page to be linked on the main LSL portal. Similiar to the old LSL wiki of compiling a growing list of well known tricks and tips for scripting.

For example a well known trick, which I use frequently is the use of (List!=[]) instead of llGetListLength. --[[User:Nexii Malthus|Nexii Malthus]] 07:38, 19 May 2008 (PDT)

:I've slapped a page together: [[LSL Hacks]]. I'd like comments on the style and layout. Please in the future don't stand on ceremony, if a niche needs filling, then please fill it with content. I have found that if you wait for people to weigh in before you start then nothing will get done. Better to do your best and make adjustments when there is a stink. -- [[User:Strife Onizuka|Strife Onizuka]] 09:37, 19 May 2008 (PDT)

== LSLwiki.net ==
(moved from [{{fullurl:Template talk:LSL Function|oldid=110833}} Template talk:LSL Function])

I had a discussion with [[User:Gally Young|Gally]] today and we came to the following conclusion: Since we're not able to copy content from [http://www.lslwiki.net lslwiki.net] and vice versa - because of licensing problems - we might benefit from linking related articles of both wikis. So users can easily switch from one Wiki to the other and find the information most helpful for them. There shouldn't be a rivalry between these two documentation projects. They should benefit from each other. Therefor, we're adding a link to the related LSLwiki.net article to this template. I hope it's ok. 
Something else on the same topic: It seems to be(come) quite popular in Wiki culture to double-license the own contributions, in order to make them easier to share. Wikis of interest for us:
* The Second Life Wiki (of course): [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]
* The [http://www.lslwiki.net LSLwiki.net]: an [http://lslwiki.net/lslwiki/wakka.php?wakka=LSLwikicopyright implicit copyright model]
* The [http://secondlife.wikia.com/wiki/Main_Page SecondLife Wikia]: [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License]
Please consider to double-license your contributions to this (or other) Wikis in order to make them easier to share, by writing a statemanet about double licensing on your userpage. You can also use one of [[User:SignpostMarv Martin|Marv]]'s templates: [[Template:Re-license contributions]] as well as [[Template:License]]. 
This is just a ''suggestion'' of course. Just do it, in case you want to do it. 
Greetz, [[Image:Zai_signature.png|45px]] '''[[User:Zai Lynch|Lynch]]''' ([[User talk:Zai Lynch|talk]]|[[Special:Contributions/Zai Lynch|contribs]]) 20:14, 9 September 2008 (PDT)

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

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

* I take it you haven't see the [[Template:LSL Header|Header]] at the top of every article in the [[LSL Portal]]. It has all those links you call for. (Those articles didn't get popular because people used "Search").
* The [[LSL Portal Guidelines]] contains not just the rules but the mission statement for the LSL Portal. It is fundamental to the this portals continued existence. Without it we would lack direction, and defined social guidelines. Without defined guidelines we would eventual descend into chaos (I've seen it happen; the writing of the guidelines has mostly been in reaction to specific incidents). It needs to be in a prominent position so that editors will find it and read it (or can't make excuses as to why they haven't read it).
* Like the [[LSL Portal Guidelines]], the [[LSL Portal To-do]] link is in a section dedicated to the [[LSL Portal]] as a whole, not to LSL scripting. The rest of the page is dedicated to scripting. It's a small section.
-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:14, 23 April 2010 (UTC)

== Proposal About "LSL Categories" Section ==

I find current view is too messing and difficult to find what I need. The users end up looking in huge list of {{LSLGC|Functions}}, clicking much. I am thinking about organizing the list to easily look up the LSL articles.

Here is the proposal of categorizing.
<pre>
Avatar
- Animation
- Attachment
- Behavior
- Camera
- Properties
Land
- Parcel
- Region
Object
- Detection
- Existence
- Face
- Inventory
- Link
- Media
- Physic
- Properties
- Text
Script
- Control
　- Convert
- List
- Math
- Network
- String
- Time
</pre>

I tried to sort all existing 339 functions (except God, not active one).
Here is the list ---> [[User:Mako_Nozaki/Category_Function]]

My thought is, current categories will remain as is and will be used as "tags". Missing categories will be added and be linked from each functions. Adding these categories to LSL Header using Javascript (pulldown menu) might be cool. --[[User:Mako Nozaki|Mako]] 12:56, 1 May 2010 (UTC)

== User-Defined Functions ==

I'm personally adverse to linking to the template description rather than the category (which already back links to the template) in the "language reference" section, as per the [[https://wiki.secondlife.com/w/index.php?title=LSL_Portal&diff=0&oldid=1158048|most recent edit]]. but since it's obvious someone else is not I thought I'd solicit thoughts before reverting it. I'm thinking it could be more clear on the category page though. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 22:49, 10 May 2012 (PDT)

:I agree with you. In addition to that, I think the two articles should be merged. We gain nothing of value by having them separate. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:37, 11 May 2012 (PDT)

::Pointed the link back at the category, folded the article into the category page, and marked the original article page for deletion. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 10:45, 1 June 2012 (PDT)

== Categories ==

It's probably time to update the category list and tree again. It's been a while and I'm sure I've added more since the last time we update them. Also I should remember to update the LSL News box. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:42, 11 May 2012 (PDT)

LlGetRegionAgentCount

2012-06-07T08:14:07Z

Kizmut Smit: +related

{{LSL_Function
|func_id=334|func_sleep=0.0|func_energy=10.0
|func=llGetRegionAgentCount
|return_type=integer
|return_text=that is the number of avatars in the region.
|caveats
|examples=<lsl>//Tell the owner how many avatars are in the region on touch
default
{
touch_start(integer count)
{
llOwnerSay((string)llGetRegionAgentCount());
}
}</lsl>
|spec
|caveats=
* The value returned by this function is technically the average number of agents who were in the region for the past second, rounded to the nearest integer. This means that there is a slight (<1 second) delay in agent count when an agent enters or exits a region.
|constants
|helpers
|also_functions=
{{LSL DefineRow||[[llGetAgentList]]}}
{{LSL DefineRow||[[llGetRegionFPS]]}}
{{LSL DefineRow||[[llGetRegionTimeDilation]]}}
|also_tests
|also_events
|also_articles
|notes
|history=Introduced in {{SVN|568|rev=88085|branch=Release|anchor=file33|date=Wednesday, 21 May 2008}}
|cat1=Region
|cat2
|cat3
|cat4
}}

LlSetPos

2012-05-23T18:52:31Z

Kizmut Smit: +also regionpos

{{LSL Function
|inject-2={{Issues/SVC-1945}}{{LSL Function/position|pos|region=*|local=*}}
|func_id=58|func_sleep=0.2|func_energy=10.0
|func=llSetPos
|p1_type=vector|p1_name=pos|p1_desc= (see ''[[#Specification]]'').|p1_hover=.
|func_desc=Moves the object or primitive towards '''pos''' without using physics.
|func_footnote=Movement is capped to 10m per call for unattached root prims.{{Footnote|Unless you exploit the undocumented [[warpPos]] bug.}}
|spec=This function is available for nonphysical root prims and all child prims. It has no effect on the root prim if the object is physical.
=====Coordinate Frame=====
*Root prims (or single prim objects)
**Attached
***'''pos''' is a [[Viewer coordinate frames#Local|local coordinate]] relative to the attach point.
**Not attached
***'''pos''' is a [[Viewer coordinate frames#Region|region coordinate]].
*Child prims (non root prims)
**'''pos''' is a [[Viewer coordinate frames#Local|local coordinate]] relative to the root prim.
|caveats=
*Because of the intermixing of local and regional coordinates with this function, when a prims position is wanted it is best to use [[llGetLocalPos]].
*This function does not work in the root prim of physical objects. Use a physical function like [[llMoveToTarget]] instead.
|constants
|examples=
<lsl>
//Move the object up 1m when someone touches it.
default {
touch_start(integer i) {
llSetPos(llGetPos() + <0,0,1>);
}
}
// to bypass the small movement bug use this
// - created by Madpeter Zond
// notes: it does not check if the movement would go out of limit range for linked prims
llSetLocalPos(vector offset)
{
vector save = offset;
if(offset.x < 0.0) offset.x -= 1;
else offset.x += 1;
if(offset.y < 0.0) offset.y -= 1;
else offset.y += 1;
if(offset.z < 0.0) offset.z -= 1;
else offset.z += 1;
llSetPos(offset);
llSetPos(save);
}
</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llSetRegionPos]]|Sets position of object to any position within the region.}}
{{LSL DefineRow||[[llGetLocalPos]]|Returns the prim's local position if it is attached or non-root (otherwise it returns the global position)}}
{{LSL DefineRow||[[llGetRootPosition]]|Gets the root prims position}}
{{LSL DefineRow||[[llGetPos]]|Returns the prim's global position, even if it is attached or non-root}}
|also_tests
|also_events
|also_articles
|notes=Multiple movement commands can be chained together with [[llSetPrimitiveParams]] and [[PRIM_POSITION]]. The advantage of doing this is that the script only sleeps once per function call instead of once per movement.
|cat1=Movement
|cat2=Prim
|cat3
|cat4
}}

LlRegionSay

2012-01-07T09:40:56Z

Kizmut Smit: +llRegionSayTo

{{LSL_Function/chat|channel|msg|np=*}}{{LSL_Function
|func_id=331
|func_sleep=0.0
|func_energy=10.0
|func=llRegionSay
|p1_type=integer|p1_name=channel|p1_desc
|p2_type=string|p2_name=msg|p2_desc
|func_desc=Says the string '''msg''' on channel number '''channel''' that can be heard anywhere in the [[region]] by a script [[listen|listening]] on '''channel'''.
|func_footnote=Regardless of where the prim is, the message will not travel over region borders.
|return_text
|spec
|constants
|caveats=*This function cannot transmit on the {{#var:PUBLIC_CHANNEL}}, this is a design feature and not a bug.
*If '''msg''' is longer than 1023 bytes it is truncated to 1023 bytes.
*A prim can '''not''' hear itself, to prevent problems with recursion.
|examples=<lsl>default
{
state_entry()
{
llRegionSay(25,"This is an incredibly useless program." );
}
}</lsl>
To avoid making your object spam its neighborhood, use [[llOwnerSay]] or [[llInstantMessage]].
|helpers
|also_events=
{{LSL DefineRow||[[listen]]|}}
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llRegionSayTo]]|Sends chat directly to specified target within region}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|}}
{{LSL DefineRow||[[llDialog]]|}}
{{LSL DefineRow||[[llTextBox]]|}}
|also_tests
|also_articles
|notes=If one object 'says' something to another object (e.g., a button that, when touched,
turns on a lamp), it is a good idea to use a very negative channel, e.g.,
<lsl> llRegionSay(-5243212,"turn on");</lsl>
Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to [[llTextBox]] was to use [[llDialog]] which was limited to 24 bytes.

If {{#var:DEBUG_CHANNEL}} is used as '''channel''', the script will say '''msg''' to the Script Warning/Error window.

* As of 1.18.3, using llRegionSay on the {{#var:DEBUG_CHANNEL}} will wrap around and display on channel 0, with a range of 100m.
|history=
*Introduced with SL 1.16.0
|cat1=Communications
|cat2=Chat
|cat3
|cat4
}}

User:Kizmut Smit

2010-10-01T19:53:13Z

Kizmut Smit:

{{Template:Kizmut Smit/imgbox|image=KSmit02 001.png|caption=kizmut Smit}}
'''Resident since:''' 2007-08-11

'''Main objective:''' Assist others in making fun objects do fun stuff.

'''Abilities:'''
* Advanced building
* Extensive lsl
* poses
* Streaming media
* Land/Region/Estate Management
* html/php

'''Languages:''' English and lsl.

'''Species:''' Noob ringtail lemur.

'''Personal description:''' I like pudding.

'''Second Life profile:''' [http://world.secondlife.com/resident/5a9f5114-65dd-4d55-9383-9516c418111d kizmut Smit]

User:Kizmut Smit/EmeraldStuff

2010-10-01T19:52:29Z

Kizmut Smit: Replaced content with '[]'

[]

Talk:Viewer URI Name Space

2010-08-23T18:47:50Z

Kizmut Smit: /* URL Escaped? */

Does this mean that no region can be named 'app'? [[User:Phoenix|Phoenix]] 17:27, 23 July 2007 (PDT)
:Yes, no region can be named "app". I had to pick some prefix, this one seemed reasonable. Unfortunately, also any string starting with secondlife:// can be legally parsed as a region name. [[User:James|James]] 08:54, 24 July 2007 (PDT)
::I think this is a really bad direction to start down -- it artificially limits our usable space. I think we should instead make a new protocol for local resources, or make a more general url syntax. For example:

slclient://locally/available/resource

or

secondlifegrid://localhost/locally/available/resource

[[User:Phoenix|Phoenix]] 09:39, 24 July 2007 (PDT)

I agree with Phoenix here. Extending the secondlife: scheme is a mistake, since it's already well defined what it means:

"Via the Second Life protocol I am access Region Foo at x,y,z"

Mozilla uses the uri scheme chrome for "locally accessable resources that are accessed without knowing their precise filesystem location".

secondlife:// as a region name is actually okay. In URI form, it would be secondlife://secondlife%3A%2F%2F/1/2/3

From what I can tell, something like slchrome:// or slui:// would be better.

[[User:Mark|Mark]] 10:07, 24 July 2007 (PDT)

Yes, I see your point and agree. I initially chose secondlife:// for expedience, as the installer already registered it on all platforms, the embedded mozilla already had callbacks for the links, etc. But we need a different protocol for this type of command.

I'm going to use slclient:// because the word "client" is probably more understandable to an end user (who might see the raw link in a browser warning dialog) than "chrome" or "ui".

[[User:James|James]] 10:30, 24 July 2007 (PDT)

----

Well, while it is ugly, and unfortunate, I don't think a "one-time" fix of inserting "/app" at the top level is that bad. I think there are plenty of downsides to creating another scheme identifier. A way to make this more palatable is to fix the top level of the path, so whereas before you had:
secondlife://Obscure/123/98
you'd now have:
secondlife://location/Obscure/123/98
The old one would be deprecated, and yes, regions with the name "app" or "location" or whatever else we put a the top level wouldn't work with the old style.

The primary reason for having a scheme is that it is the way to get an operating system to open up another application with a class of URIs. Hence, everything in such a URI namespace is really the name for something the running viewer can do. We shouldn't use the secondlife: scheme to address elements of our network at all. Hence, I don't think the need for a top level '/localhost' in the examples above.

Since the scheme is entirely for the purpose of directing the viewer, it is reasonable to think of all those resources named as actions or concepts in the viewer. In otherwords, the URI
secondlife://event/<uuid>
should be though of as the viewer's concept of that event in our system. And this should conceptually distinct from, say:
http://services.agni.lindenlab.com/event/<uuid>
which would be a reference to the event resource back at the grid.

As such, such URIs really should only imply viewer actions on those objects: I could see secondlife: URIs that open an event in the viewer (but one wonders why?), but not one that creates an event that way. For the most part, I think we should be steering such functionality to the web services.

Lastly, a big problem with the URI tree proposed is that it puts all content into global name spaces by type. In particular:
secondlife://app/parcel/<uuid>
implies that one can reach ANY parcel that way. This is bad as it forces us to think in terms of a single global list. Much better would be
secondlife://app/grid/agni/region-by-name/Obscure/parcels/<uuid>/view
Though, admittadly, the "/grid/agni" part may be overkilll.... but perhaps not...

[[User:ZeroLinden|ZeroLinden]] 10:38, 24 July 2007 (PDT)

----

The primary motivation for this is to make clicking on links in a Find All search results page (output by Google Search Appliance) show SL UI with details on that data. Even if we move that data display to HTML, we'll still need a way to have links/buttons that offer teleports, open the IM window, etc. So we need a commmand format.

At the time the parcel links in the HTML pages for search are made, I do not have access to the region name or other information other than the UUID of the parcel. For example, top picks only store the parcel UUIDs. I could thrash the database during the static HTML page generation for search to look up the region names for each parcel UUID I encountered, but that seems a waste of effort to me.

I could imagine having special links that opened, say, the event UI as a useful way to share references to information in our system, on outside web pages, in our own IM, and in tutorials. Since I have to do some internal link management for search, it seems reasonable to me to expose those URLs to the outside world.

I would prefer to reserve the words "event", "classified", "place", "parcel", "agent", "resident", "person" and "group" as being invalid region names. secondlife://agent/<agent_id> looks cleaner to me than secondlife://app/...

Without slclient://, all these links are working now. Do we really want slclient://? Also, our entire system for places/events/top picks currently stores only parcel ids. I'm not thrilled about embarking on a huge refactoring of this system just to get search to work.

[[User:James|James]] 10:56, 24 July 2007 (PDT)

== Non-Standard ==

Bah! I can't believe I didn't notice this before: Our syntax doesn't follow the recommended syntax for path based URI schemes! It should start with three slashes, not two, like file: does. This is because the thing after the double slash is the authority section, containing a hostname and port (and other stuff optionally as well...).

It might be worse - depending on one's reading of section 3 of RFC 3986, our use of double slashes without an authority section could be seen as illegal. Of course, we could claim that the region name or "app" was the authority (and hence host).... but I bet w don't follow all the proper conventions for host names. Fie!

See http://tools.ietf.org/html/rfc3986

[[User:ZeroLinden|ZeroLinden]] 15:33, 6 September 2007 (PDT)

----

James writes:

Looks like <code>secondlife:///</code> is what we want. My only concern would be
that crappy IRC clients and other programs that attempt to automatically
identify URLs in text would choke. Colloquy does it correctly. I will
try other clients in the office tomorrow.

Changing to <code>secondlife:///</code> is trivial in my code. Any reason I
shouldn't just do it?

----

Well, we have to continue to handle the existant URLs. So perhaps we take this moment to "fix" the whole scheme:

secondlife://<region name>/<x>/<y>/<z>
-- old style, still accepted

secondlife:///viewer/go/<region name/<x>/<y>/<z>
-- new style, with well defined rules about encoding region names

secondlife:///viewer/agent/<agent_id>
secondlife:///viewer/group/<group_id>
-- etc., the controls being added for search
-- (that these are an implicit "open a floater on this item" verb is a little odd,
what's the URL for "IM this line of text to this agent"?)

secondlife:///viewer/login/...
-- the login work for web site auth.

[[User:ZeroLinden|ZeroLinden]] 08:57, 7 September 2007 (PDT)

----

I will of course support legacy URLs. I see no strong reason to switch from "app" to "viewer". Likewise, my initial syntax for agents/groups/etc. is of the form:

secondlife:///app/agent/<agent_id>/about

Where "about" is the verb. Thus we can add "im", "offer-teleport", etc.

Any reason I should not just implement secondlife:///app/agent/<agent_id>/about ?

[[User:James|James]] 09:57, 7 September 2007 (PDT)

== Question About secondlife:///app/chat/channel/text ==

I tried "secondlife:///app/chat/0/Text" And That Worked But How Do You Get More Than One Word? I Would Like To Use It In A Hud For Staff At A Club When The Hud Will Fill In The First Name Of The Person Into Some Standard Greetings And Information. But Escaping The Text And My Character Will Of Course Say It With It Still Escaped.
Ive Tried A Few Ways Hoping Something Would Work But Get Only The Forst Word Or Nothing At All, Its A Rainy Day Project
llOwnerSay("Click To Speak: secondlife:///app/chat/0/Testing, Testing 123");//Says Testing
llOwnerSay("Click To Speak: secondlife:///app/chat/0/" + llEscapeURL("Testing, Testing 123"));//Says Testing%2C%20Testing%20123
llLoadURL(llGetOwner(), "Click To Speak", "secondlife:///app/chat/0/" + llEscapeURL("Testing, Testing 123"));//Nothing Happens
llLoadURL(llGetOwner(), "Click To Speak", "secondlife:///app/chat/0/Testing, Testing 123");//Nothing Happens

[[User:Adicted Waco|Adi]] 07:12, 8 August 2010 (UTC)

== URL Escaped? ==

Someone tell me if I am testing this wrong, since this article says it is URL escaped.

If I click: secondlife:///app/chat/0/foo%20bar

The result is as follows:

[11:46:03] kizmut Smit: foo%20bar

[[User:Kizmut Smit|Kizmut Smit]] 18:47, 23 August 2010 (UTC)
----

Talk:Viewer URI Name Space

2010-08-23T18:47:09Z

Kizmut Smit: /* URL Escaped? */ new section

Does this mean that no region can be named 'app'? [[User:Phoenix|Phoenix]] 17:27, 23 July 2007 (PDT)
:Yes, no region can be named "app". I had to pick some prefix, this one seemed reasonable. Unfortunately, also any string starting with secondlife:// can be legally parsed as a region name. [[User:James|James]] 08:54, 24 July 2007 (PDT)
::I think this is a really bad direction to start down -- it artificially limits our usable space. I think we should instead make a new protocol for local resources, or make a more general url syntax. For example:

slclient://locally/available/resource

or

secondlifegrid://localhost/locally/available/resource

[[User:Phoenix|Phoenix]] 09:39, 24 July 2007 (PDT)

I agree with Phoenix here. Extending the secondlife: scheme is a mistake, since it's already well defined what it means:

"Via the Second Life protocol I am access Region Foo at x,y,z"

Mozilla uses the uri scheme chrome for "locally accessable resources that are accessed without knowing their precise filesystem location".

secondlife:// as a region name is actually okay. In URI form, it would be secondlife://secondlife%3A%2F%2F/1/2/3

From what I can tell, something like slchrome:// or slui:// would be better.

[[User:Mark|Mark]] 10:07, 24 July 2007 (PDT)

Yes, I see your point and agree. I initially chose secondlife:// for expedience, as the installer already registered it on all platforms, the embedded mozilla already had callbacks for the links, etc. But we need a different protocol for this type of command.

I'm going to use slclient:// because the word "client" is probably more understandable to an end user (who might see the raw link in a browser warning dialog) than "chrome" or "ui".

[[User:James|James]] 10:30, 24 July 2007 (PDT)

----

Well, while it is ugly, and unfortunate, I don't think a "one-time" fix of inserting "/app" at the top level is that bad. I think there are plenty of downsides to creating another scheme identifier. A way to make this more palatable is to fix the top level of the path, so whereas before you had:
secondlife://Obscure/123/98
you'd now have:
secondlife://location/Obscure/123/98
The old one would be deprecated, and yes, regions with the name "app" or "location" or whatever else we put a the top level wouldn't work with the old style.

The primary reason for having a scheme is that it is the way to get an operating system to open up another application with a class of URIs. Hence, everything in such a URI namespace is really the name for something the running viewer can do. We shouldn't use the secondlife: scheme to address elements of our network at all. Hence, I don't think the need for a top level '/localhost' in the examples above.

Since the scheme is entirely for the purpose of directing the viewer, it is reasonable to think of all those resources named as actions or concepts in the viewer. In otherwords, the URI
secondlife://event/<uuid>
should be though of as the viewer's concept of that event in our system. And this should conceptually distinct from, say:
http://services.agni.lindenlab.com/event/<uuid>
which would be a reference to the event resource back at the grid.

As such, such URIs really should only imply viewer actions on those objects: I could see secondlife: URIs that open an event in the viewer (but one wonders why?), but not one that creates an event that way. For the most part, I think we should be steering such functionality to the web services.

Lastly, a big problem with the URI tree proposed is that it puts all content into global name spaces by type. In particular:
secondlife://app/parcel/<uuid>
implies that one can reach ANY parcel that way. This is bad as it forces us to think in terms of a single global list. Much better would be
secondlife://app/grid/agni/region-by-name/Obscure/parcels/<uuid>/view
Though, admittadly, the "/grid/agni" part may be overkilll.... but perhaps not...

[[User:ZeroLinden|ZeroLinden]] 10:38, 24 July 2007 (PDT)

----

The primary motivation for this is to make clicking on links in a Find All search results page (output by Google Search Appliance) show SL UI with details on that data. Even if we move that data display to HTML, we'll still need a way to have links/buttons that offer teleports, open the IM window, etc. So we need a commmand format.

At the time the parcel links in the HTML pages for search are made, I do not have access to the region name or other information other than the UUID of the parcel. For example, top picks only store the parcel UUIDs. I could thrash the database during the static HTML page generation for search to look up the region names for each parcel UUID I encountered, but that seems a waste of effort to me.

I could imagine having special links that opened, say, the event UI as a useful way to share references to information in our system, on outside web pages, in our own IM, and in tutorials. Since I have to do some internal link management for search, it seems reasonable to me to expose those URLs to the outside world.

I would prefer to reserve the words "event", "classified", "place", "parcel", "agent", "resident", "person" and "group" as being invalid region names. secondlife://agent/<agent_id> looks cleaner to me than secondlife://app/...

Without slclient://, all these links are working now. Do we really want slclient://? Also, our entire system for places/events/top picks currently stores only parcel ids. I'm not thrilled about embarking on a huge refactoring of this system just to get search to work.

[[User:James|James]] 10:56, 24 July 2007 (PDT)

== Non-Standard ==

Bah! I can't believe I didn't notice this before: Our syntax doesn't follow the recommended syntax for path based URI schemes! It should start with three slashes, not two, like file: does. This is because the thing after the double slash is the authority section, containing a hostname and port (and other stuff optionally as well...).

It might be worse - depending on one's reading of section 3 of RFC 3986, our use of double slashes without an authority section could be seen as illegal. Of course, we could claim that the region name or "app" was the authority (and hence host).... but I bet w don't follow all the proper conventions for host names. Fie!

See http://tools.ietf.org/html/rfc3986

[[User:ZeroLinden|ZeroLinden]] 15:33, 6 September 2007 (PDT)

----

James writes:

Looks like <code>secondlife:///</code> is what we want. My only concern would be
that crappy IRC clients and other programs that attempt to automatically
identify URLs in text would choke. Colloquy does it correctly. I will
try other clients in the office tomorrow.

Changing to <code>secondlife:///</code> is trivial in my code. Any reason I
shouldn't just do it?

----

Well, we have to continue to handle the existant URLs. So perhaps we take this moment to "fix" the whole scheme:

secondlife://<region name>/<x>/<y>/<z>
-- old style, still accepted

secondlife:///viewer/go/<region name/<x>/<y>/<z>
-- new style, with well defined rules about encoding region names

secondlife:///viewer/agent/<agent_id>
secondlife:///viewer/group/<group_id>
-- etc., the controls being added for search
-- (that these are an implicit "open a floater on this item" verb is a little odd,
what's the URL for "IM this line of text to this agent"?)

secondlife:///viewer/login/...
-- the login work for web site auth.

[[User:ZeroLinden|ZeroLinden]] 08:57, 7 September 2007 (PDT)

----

I will of course support legacy URLs. I see no strong reason to switch from "app" to "viewer". Likewise, my initial syntax for agents/groups/etc. is of the form:

secondlife:///app/agent/<agent_id>/about

Where "about" is the verb. Thus we can add "im", "offer-teleport", etc.

Any reason I should not just implement secondlife:///app/agent/<agent_id>/about ?

[[User:James|James]] 09:57, 7 September 2007 (PDT)

== Question About secondlife:///app/chat/channel/text ==

I tried "secondlife:///app/chat/0/Text" And That Worked But How Do You Get More Than One Word? I Would Like To Use It In A Hud For Staff At A Club When The Hud Will Fill In The First Name Of The Person Into Some Standard Greetings And Information. But Escaping The Text And My Character Will Of Course Say It With It Still Escaped.
Ive Tried A Few Ways Hoping Something Would Work But Get Only The Forst Word Or Nothing At All, Its A Rainy Day Project
llOwnerSay("Click To Speak: secondlife:///app/chat/0/Testing, Testing 123");//Says Testing
llOwnerSay("Click To Speak: secondlife:///app/chat/0/" + llEscapeURL("Testing, Testing 123"));//Says Testing%2C%20Testing%20123
llLoadURL(llGetOwner(), "Click To Speak", "secondlife:///app/chat/0/" + llEscapeURL("Testing, Testing 123"));//Nothing Happens
llLoadURL(llGetOwner(), "Click To Speak", "secondlife:///app/chat/0/Testing, Testing 123");//Nothing Happens

[[User:Adicted Waco|Adi]] 07:12, 8 August 2010 (UTC)

== URL Escaped? ==

Someone tell me if I am testing this wrong, since this article says it is URL escaped.

If I click: secondlife:///app/chat/0/foo%20bar
The result is as follows:
[11:46:03] kizmut Smit: foo%20bar

[[User:Kizmut Smit|Kizmut Smit]] 18:47, 23 August 2010 (UTC)
----

Web Textures

2010-07-31T03:52:51Z

Kizmut Smit: +cat

{{hint|mode=note|desc=This has been superseded by [[HTTP Texture]].}}

==Summary==
This page is about dynamic web textures, a feature to allow an LSL script to assign an image URL to a face and cause it to dynamically update from the script. This is not HTML-on-a-prim, though it shares some of the same complications regarding anonymity.

This raises a potential issue regarding [[Expected Privacy]]. The only practical way to accomplish dynamic web textures is to let the client download the image directly. This will expose user's IP addresses. This issue is also there for HTML on a prim, though the limitations several Lindens have mentioned to reduce the processing overhead of HTML on a prim - similar to the current limitations for media textures - make it less likely to be easily abused.

<blockquote>We are looking toward making it possible for prims to reference external websites for texture information, which is where PNG textures would start to come into play. -Phoenix Linden</blockquote>

== Benefits of this feature ==

#Negates the need for scripts like XyText that are very laggy when dynamic displays are large.
#Allows for things like streaming news service [[HUD]]s.
#Interactive games can present large amounts of off-world data.
#Corporations that already have many dynamic web assets can reuse them in-world.
#The L$10 upload fee can be avoided if the user hosts the content by him/herself.

== Possible benefits ==

#Live porn. ''Did we really have to mention this?''
#Web Cams.

The previous 2 are already possible via quicktime streaming which is more efficient.

== Potential LSL implementation ==
<lsl>
llSetTextureURL(integer face, string url);
llRefreshTextureURL(integer face);
</lsl>
Example with text generation script:

<lsl>
llSetTextureURL(1, llUrlEncode("http://example.com/getpng.php?text= " + text + "&font=futura&rez=512x512");
llRefreshTextureURL(integer face);
</lsl>

== Privacy problems ==
The agent IP is already exposed if the avatar is listening to streamed media, but this is limited to agents that (a) have streaming media enabled, and (b) visit the specific parcel that the 'media bug' is associated with. Attempting to use streaming media to build up a database associating avatars with IP addresses would be enormously expensive.

Despite the small exposure, there are a number of people who do not use streaming media because of privacy concerns.

Textures, unlike streaming media, are ubiquitous and require no significant expenditure to distribute around the grid. The potential for large scale data mining to associate characters in SL with each other and with real-life identities is significantly higher.

*The relative severity of this should be pondered.

== Suggested Privacy Protections ==
There are a number of mechanisms that could be used to mitigate this effect:

=== Do nothing, just implement it ===
* Pro: Feature itself is somewhat easy to implement, if images are powers of 2
* Pro: Most other protocols on the internet expose IP to the server, this isn't unprecedented.
* Con: Unannounced loss of anonymity.
** Mitigation: Announce it first.
* Con: Sets precedent for other features that may expose IP association information.
** Note: this might be seen as a "Pro".
* Con: Trivial to associate IP with agent using textures. Much easier than it is with a parcel media stream.
* Con: Could become a public relations nightmare if users react badly.

=== Global on/off, with one time dialog opt-in ===
The client could prompt the first time you encounter a web texture, and ask you if you want to enable it, warning you that it will expose your IP address to third parties. This would be similar to the way parcel streaming media prompts the first time you encounter a parcel with it set.
*Con: The user is asked to make technical decisions they might not understand.
*Con: The user must sacrifice all dynamic web content to get privacy for their IP.
*Pro: No annoyance for those who don't care about exposing IP associations.

For HUD attachments this could be handled as a special case (see below).

=== Proxy Options ===

''External Proxy''

Update (7/7/2007): [[SLSquid Proxy]] addresses this issue.

The client would provide a place to enter a HTTP proxy address for web textures. This would allow the user to enter an anonymizing proxy service if they want to.
*Pro: Easy to implement
*Pro: Proxy support will be needed anyway for the general move to HTTP texture transfers for regular asset textures.
*Con: Configuring proxy settings for anonymizing proxies can be extremely difficult even for professionals.
** Mitigation: this work can be hidden by the browser or browser extensions, so SL or a plugin for SL could do the work.
*** But there isn't such a plugin mechanism yet.
*Con: Anonymizing proxies are slow and unreliable.
** Only individuals that care about exposing their IP need to suffer this delay.
*Con: Proxy support is not even implemented yet for the help browser
*Con: Default settings (no proxy) expose users to privacy violations.
** Which means this is likely to be a PR disaster.

''Built-In''

Linden Lab could create their own anonymizing proxy server.
*Pro: No setup on the user's part is required.
*Con: Cost / Support / Implementation on Linden Lab's plate.

=== Attachments ===
Using web textures in an attachment (particularly a [[HUD]]) provides an attacker the greatest opportunity to ensure that they have a correct match to an IP address, so while this is not that useful for bulk data gathering it's particularly problematic for targeted attacks. It would probably be best not to make web textures on attachments an exception to any wider restrictions. Web textures on HUDs, though, are particularly useful, so there should be some mechanism to allow a user to grant their own attachments the right to load web textures even if they are otherwise disabled.

*Pro: Allows cautious users to use web-enabled HUDs.
*Pro: Promotes effective low-lag tools.

=== Server side (SIM) ===
Much like {{LSLG|llHTTPRequest}} the SIM could download the texture and be subjected to the same restrictions (no more than 20 requests per 100 seconds). This would ensure peoples privacy is protected. Another permutation of this would be to provide both a client side and server side implementation of web textures.

*Pro: Privacy is protected
*Pro: No user intervention required.
*Con: More pressure on the sim.
**Mitigation: Limits per sim. Freedom for sim owners to decide.
*Con: Not suitable for highly dynamic applications, such as web cams or games.
**Mitigation: SIM should be able to cache Web-acquired content, the total cache can be limited similar to prim-limitations. This forces creative management. Cams should stream anyway, and game mediums usually require memory management.
*Con: Vulnerability of LL servers for image-load attacks
**Mitigation: Limitation similar to llHTTPRequest,llEmail, etc.
*Note: This is effectively equivalent to LL providing a proxy.
*Con: May run into DMCA issues retaining copyrighted material on sim.

=== Dialog Boxes for HUD attachments ===
For the subset of targeted exploits using HUDs, a dialog box similar to the ones used for other permissions could be used when attaching a HUD with web textures, asking if you want to allow the HUD to use them.

*Pro: Easy on the scripter.
*Pro: Implemented entirely in the client.
*Con: This only protects against targeted attacks though HUDs, it provides no protection against data mining. A more general mechanism might still be required.
*Con: The user is asked to make technical decisions they might not understand.
*Con: It's a unique mechanism.
*Con: Dialog boxes are annoying.
*Con: UI studies show that users automatically click yes in many dialog boxes without thinking.
*Pro: Establishes precedent for other useful client-side security and privacy tools
**Or is that a con? :)

==== The Permissions system ====

Alternatively, this could be done through the normal LSL permission system with a permission request, and something like PERMISSION_TEXTURE_URL.

*Pro: Already well-understood interface.
*Con: Relatively inflexible, especially if required for non-HUD objects that might want to reach a wide audience (like a billboard).
**Compromise: Perhaps non-attached objects could default to having the permission. But, attached or especially HUDs could not. As stated in this sub-proposal.

==== Whitelists ====

This could simply be handled the same way as third-party textures in the proposal below. The same pros and cons apply.

*Pro: No need for separate mechanisms for HUD textures and non-HUD textures.
*Con: HUDs do not detach after leaving a SIM. This could allow for pop-up like exploits. Especially, for the novice who believes what they read.

=== White/Black List ===
Similar to Firefox/IE popup blocking, the client could manage white/black lists.
*Pro: Flexible and complete control
*Pro: users not concerned about privacy could select "Accept everything"
*Con: If poorly implementd, this would cause a lot of user input: (for example, thousands of prompts per second for someone flying over the mainland).
*Con: The user is asked to make technical decisions they might not understand (the user might be tricked, they might not know who to trust).
*Con: Very complex to implement, UI elements hard to design effectively.
**Mitigation: Using existing controls (texture cues, pie menu) would simplify the implementation and make the interface more familiar.
*Con: Reinstalling could lose settings.
**Mitigation: Selecting a "safe default" would protect naive users. If it's easy to update the whitelist or disable the protections again this shouldn't cause any major inconvenience for anyone.

==== Suggested implementation: ====

===== Safe but convenient default behavior. =====
*Textures on prims set to the land group are automatically loaded by default.
*Optionally - Textures set by scripts created by you, or owned by and readable by you are automatically loaded by default.
*All other textures are left unloaded.

===== No popups. =====
*Unloaded HTML textures have a distinct appearance.
*Optionally - Left-clicking on the object will load the unloaded texture(s).
*Right-clicking on an unloaded HTML texture will bring up the pie menu, and a pie menu option will allow you to load the textures on the object or whitelist it.
**Load the textures on this object.
**Always load textures on this object
**Always load textures from objects owned by this person
**Always load textures from objects in this group
*You can also remove these permissions if they are set.

===== Simple preferences =====
* Privacy setting: only three levels of privacy:
** Low - load all HTTP textures and HTML-on-a-prim automatically.
** Normal - default behavior described above.
** High - No HTTP textures are loaded.
* Button to clear textures.

===== What is required of the Sim =====

When an HTTP texture is sent to the client, it's bundled with some UUIDs:
*The owner of the object. (Already available)
*Optionally - The creator (and owner if the script was full perm when the texture was set) of the script that set the texture, to implement the "my scripts" option.
*Optionally - A flag indicating the user has granted permission to display this texture through the permission system as suggested under '''Attachments''', above.
*The group of the object. (Already available)

=== Change Users Privacy Expectation ===
Make it clear to the users that their IP address association with their avatar name is not private information and can't be protected while still providing dynamic and seamless integration with the rest of the Internet.
*Pro: No technical implementation necessary.
*Con: Not easy.
*Assumes 'dynamic and seamless integration with the rest of the Internet' is necessarily desirable. The results of Microsoft attempting this with Active Desktop has been less than optimal to say the least.

=== Trusted hosting partners ===
Have one or more trusted hosting partners that would provide scriptable webspace on standard Linux servers. The key difference is that the partners could not allow the IP address of clients to pass through to the scripting language.
*Pro: Fully fixes privacy problem, with no effort required from the end user.
*Con: Hard to monitor trusted partners for compliance if more than one.
*Con: If only one, then developers have no choice.
*Con: Business risk from close external relationship with other company if only one provider.
*Con: Not in the spirit of SL.

=== Linden Lab Webhosting ===
Linden Lab would could offer their own webhosting that withholds end user IP similar to above.
*Pro: Fully fixes the privacy problem
*Pro: Could also be used as a super low latency way to do HTTPRequest calls to a web server. HTTPRequest limits could be raised for requests to these servers.
*Con: LL is not a web hosting company.
**But they sort of are... it's just a "3d web".

== See also ==
* {{Jira|VWR-217}} - New Feature -> LSL -> Dynamic Web Textures
* [[SLSquid Proxy]]

[[Category:Feature Requests]]
[[Category:LSL_HTTP]]

User:Kizmut Smit

2010-05-15T13:48:46Z

Kizmut Smit: profile update

LINK SET

2010-05-15T13:38:38Z

Kizmut Smit: +primparamsFAST

{{Issues/SVC-3510}}{{LSL Constant
|name=LINK_SET
|type=integer
|value=-1
|desc
|examples
|constants=
{{LSL DefineRow||[[LINK_ALL_CHILDREN]]|}}
{{LSL DefineRow||[[LINK_ALL_OTHERS]]|}}
{{LSL DefineRow||[[LINK_ROOT]]|}}
{{LSL DefineRow||[[LINK_THIS]]|}}
|functions=
{{LSL DefineRow||[[llBreakLink]]|}}
{{LSL DefineRow||[[llGetLinkKey]]|}}
{{LSL DefineRow||[[llGetLinkName]]|}}
{{LSL DefineRow||[[llMessageLinked]]|}}
{{LSL DefineRow||[[llSetLinkAlpha]]|}}
{{LSL DefineRow||[[llSetLinkColor]]|}}
{{LSL DefineRow||[[llSetLinkTexture]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParamsFast]]|}}
|events=
|cat1=Link
|cat2=Link Message
|cat3
|cat4
}}

LINK ROOT

2010-05-15T13:38:02Z

Kizmut Smit: +primparams

{{LSL Constant
|name=LINK_ROOT
|type=integer
|value=1
|desc
|caveats=
*In a single prim object LINK_ROOT will not refer to the root prim!
**If your script needs to work in single and multiprim objects, instead of <code>[[LINK_ROOT]]</code>, use either <code>([[llGetLinkNumber]]() != 0)</code> or <code>(!![[llGetLinkNumber]]())</code>
|examples
|constants=
{{LSL DefineRow||[[LINK_ALL_CHILDREN]]|}}
{{LSL DefineRow||[[LINK_ALL_OTHERS]]|}}
{{LSL DefineRow||[[LINK_SET]]|}}
{{LSL DefineRow||[[LINK_THIS]]|}}
|functions=
{{LSL DefineRow||[[llBreakLink]]|}}
{{LSL DefineRow||[[llGetLinkKey]]|}}
{{LSL DefineRow||[[llGetLinkName]]|}}
{{LSL DefineRow||[[llMessageLinked]]|}}
{{LSL DefineRow||[[llSetLinkAlpha]]|}}
{{LSL DefineRow||[[llSetLinkColor]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParamsFast]]|}}
|events=
{{LSL DefineRow||[[link_message]]|}}
|cat1=Link
|cat2=Link Message
|cat3
|cat4
}}

LINK THIS

2010-05-15T13:37:40Z

Kizmut Smit: +primparams

{{Issues/SVC-600}}{{Issues/SVC-3510}}{{Issues/SVC-3199}}{{LSL Constant
|name=LINK_THIS
|type=integer
|value=-4
|desc
|examples
|constants=
{{LSL DefineRow||[[LINK_ALL_CHILDREN]]|}}
{{LSL DefineRow||[[LINK_ALL_OTHERS]]|}}
{{LSL DefineRow||[[LINK_ROOT]]|}}
{{LSL DefineRow||[[LINK_SET]]|}}
|functions=
{{LSL DefineRow||[[llBreakLink]]|}}
{{LSL DefineRow||[[llGetLinkKey]]|}}
{{LSL DefineRow||[[llGetLinkName]]|}}
{{LSL DefineRow||[[llMessageLinked]]|}}
{{LSL DefineRow||[[llSetLinkAlpha]]|}}
{{LSL DefineRow||[[llSetLinkColor]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParamsFast]]|}}
|events=
|issues
|cat1=Link
|cat2=Link Message
|cat3
|cat4
}}