Second Life Wiki - User contributions [en]

LlInstantMessage/de

2015-12-22T20:52:08Z

Vulcan Viper: Just to see if everything that should be shown as LSL can be made to appear within the border.

{{LSL_Function/de
|func_id=118|func_sleep=2.0|func_energy=10.0
|func=llInstantMessage
|p1_type=key|p1_name=user|p1_desc
|p2_type=string|p2_name=message|p2_desc
|func_desc=Sendet eine durch den string '''message''' spezifizierte Sofortnachricht zu einem durch '''key''' spezifizierten user.
|return_text
|spec
|caveats=**Für anwendungen wo dies problematisch ist, ist es möglich, den Aufruf von llInstantMessage in einem Child Script zu platzieren und die Infomationen via [[llMessageLinked/de|llMessageLinked]] an das Script weiterzuleiten.
*Die gesendete Nachricht kann nicht länger als 1024 bytes sein.
*Die Nachricht erscheint im Chat Fenster. Die Nachricht wird nicht als Teil des InstantMessage Systems geloggt.
|examples=Sag dem Besitzer, dass jemand das Objekt berührt hat:

<lsl>
key owner;

default
{
on_rez(integer start_param)
{
owner=llGetOwner(); // holt sich den key des Objektbesitzers.
}
touch_start(integer total_num)
{
llInstantMessage(owner,llKey2Name(owner)+", " + (string)total_num +" Avatar(s) touched me!");
}
}
</lsl>
Sendet eine Benachrichtung zu dem Avatar der das Objekt berührt hat, ohne andere Avatare zu spammen:
<lsl>
default
{
touch_start(integer total_num)
{
llInstantMessage(llDetectedKey(0),"Sie wurden registriert!");
}
}</lsl>
|helpers
|also_functions=
{{Template:LSL_Chatfunction_Links/de}}
|also_tests
|also_articles
|also_events
|notes=Sofortnachrichten (Instant Messages) haben den Vorteil, dass sie es einem Objekt erlauben, eine Nachricht an einen Avatar irgendwo auf dem Grid zu senden. Ein Objekt hingegen kann keine Sofortnachricht an ein Objekt senden. Die Kommunikation kann nur in eine Richtung stattfinden. Ebenfalls die Zwei-Sekunden Verzögerung kann in manchen Anwendungen als Negativaspekt gesehen werden.
|cat1=Communications
|cat2=Instant Message
|cat3
|cat4
}}

A Basic LSL Tutorial

2012-08-15T16:38:27Z

Vulcan Viper:

Basic Tutorial on LSL.
By [[User:James Benedek|James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

'''Errors and how to fix them?'''
---------------------------
If you get an error while scripting at any time, it will usually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a syntax error). Sometimes this may not be the case though.

'''Basic understanding of terms''':
-----------------------------
A function shown in red

An event is shown in light blue

A string is characters and should be in "", like "hello bill!".

A integer is a whole number like 1

A float is a decimal number like 1.0, usually used in alpha and calculation.

A vector is three floats enclosed in < pointy brackets > like so <0.0,0.0,0.0>, it can represent
colours and positions.

A key is a random generated UUID on the Linden Labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

'''TASK 1''':
-------
Let's begin by doing an easy task first off, let's make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit in-between the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

'''TASK 2''':
-------
Let's just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when someone touches it
}
}
</lsl>

'''TASK 3''':
-------
Let's now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}
</lsl>

'''TASK 4''':
-------
Let's now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldn't be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}
</lsl>

'''TASK 5''':
-------
Now that you understand alpha we shall make our object disappear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}
</lsl>

'''Task 6''':
-------
Let's try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}
</lsl>

'''Task 7''':
-------
Now let's move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}
</lsl>

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}
</lsl>

'''Task 8''':
-------
Now let's try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will firstly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}
</lsl>

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggy in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}
</lsl>

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}
</lsl>

To learn more about llListen take a look at:

https://wiki.secondlife.com/wiki/llListen

'''TASK 9''':
-------
Now let's experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}
</lsl>

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

https://wiki.secondlife.com/wiki/llSetPos

'''TASK 10''':
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}
</lsl>

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

http://wiki.secondlife.com/wiki/LSL_Portal

http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage

http://rpgstats.com/wiki/index.php?title=Main_Page

---------------------------------------------------------------------------------------------------
{{LSLC|Tutorials}}

A Basic LSL Tutorial

2012-08-15T15:59:55Z

Vulcan Viper:

Basic Tutorial on LSL.
By [[User:James Benedek|James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

'''Errors and how to fix them?'''
---------------------------
If you get an error while scripting at any time, it will usually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a syntax error). Sometimes this may not be the case though.

'''Basic understanding of terms''':
-----------------------------
A function shown in red

An event is shown in light blue

A string is characters and should be in "", like "hello bill!".

A integer is a whole number like 1

A float is a decimal number like 1.0, usually used in alpha and calculation.

A vector is three floats enclosed in < pointy brackets > like so <0.0,0.0,0.0>, it can represent
colours and positions.

A key is a random generated UUID on the Linden Labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

'''TASK 1''':
-------
Let's begin by doing an easy task first off, let's make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit in-between the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

'''TASK 2''':
-------
Let's just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when someone touches it
}
}
</lsl>

'''TASK 3''':
-------
Lets now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}
</lsl>

'''TASK 4''':
-------
Lets now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldn't be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}
</lsl>

'''TASK 5''':
-------
Now that you understand alpha we shall make our object disappear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}
</lsl>

'''Task 6''':
-------
Lets try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}
</lsl>

'''Task 7''':
-------
Now lets move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}
</lsl>

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}
</lsl>

'''Task 8''':
-------
Now lets try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will firstly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}
</lsl>

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggy in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}
</lsl>

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}
</lsl>

To learn more about llListen take a look at:

https://wiki.secondlife.com/wiki/llListen

'''TASK 9''':
-------
Now lets experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}
</lsl>

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

https://wiki.secondlife.com/wiki/llSetPos

'''TASK 10''':
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}
</lsl>

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

http://wiki.secondlife.com/wiki/LSL_Portal

http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage

http://rpgstats.com/wiki/index.php?title=Main_Page

---------------------------------------------------------------------------------------------------
{{LSLC|Tutorials}}

A Basic LSL Tutorial

2012-08-15T14:15:58Z

Vulcan Viper:

Basic Tutorial on LSL.
By [[User:James Benedek|James Benedek]]
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------

When you create a new script, it will always start out like this:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>

This script will basically say "Hello, Avatar!" on the public channel which is 0,
and will then say "Touched." on the public channel when a user touches or clicks it.

'''Errors and how to fix them?'''
---------------------------
If you get an error while scripting at any time, it will usually be that you have missed
out a ; at the end of a function or a { or a } after or before an event. This is the most
common error (a syntax error). Sometimes this may not be the case though.

'''Basic understanding of terms''':
-----------------------------
A function shown in red

An event is shown in light blue

A string is characters and should be in "", like "hello bill!".

A integer is a whole number like 1

A float is a decimal number like 1.0, usually used in alpha and calculation.

A vector is three floats enclosed in < pointy brackets > like so <0.0,0.0,0.0>, it can represent
colours and positions.

A key is a random generated UUID on the Linden Labs database mine is
d77442ea-5acc-4ed3-bbb4-1f2bf2c31bb6.

TRUE and FALSE, FALSE is equal to the integer 0, and TRUE is equal to the integer 1.

'''TASK 1''':
-------
Lets begin by doing a easy task first off, lets make the box say something else
when you touch/click it, you can do this by editing the "llSay(0, "Touched.");".
Just edit in-between the "". llSay's layout is like this llSay(Channel, "SAY STUFF");

llSay is not the only function where the object can communicate you can also try out:

llShout(Channel, "SHOUT STUFF");
llWhisper(Channel, "WHISPER STUFF");
llOwnerSay("SAY STUFF TO YOU ONLY");
llRegionSay(Channel, "REGION SAY STUFF");

'''TASK 2''':
-------
Let's just add some information after this explaining what it each thing does,
you can do this by adding // and anything after it will appear orange, this is a comment.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); // says hello at start
}

touch_start(integer total_number)
{
llSay(0, "Touched."); // says touched when someone touches it
}
}
</lsl>

'''TASK 3''':
-------
Lets now try make it change its color when we click it, the function we will need is
llSetColor, its layout is like this llSetColor(vector color, integer face); this basically
means if i wanted the cube to be red i would use the vector <1,0,0>, green <0,1,0>, blue <0,0,1>.
For a full color chart see the link below:

http://www.lslwiki.net/lslwiki/wakka.php?wakka=color

If it was a linked object you could use llSetLinkColor, which its layout is
llSetLinkColor(integer linknumber, vector color, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetColor(<1,0,0>, ALL_SIDES);
}
}
</lsl>

'''TASK 4''':
-------
Lets now make it have text appear over it, you can do this by using the function
llSetText, its layout is llSetText(string text, vector color, float alpha).
Basically if you do this llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
will appear as HELLO CAN YOU READ THIS in the colour red. Alpha is the transparency,
if you did llSetText("HELLO CAN YOU READ THIS",<1,0,0>,0); you wouldn't be able to see it.
0 = high transparency, 0.5 = in the middle, 1 = no transparency.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetText("HELLO CAN YOU READ THIS",<1,0,0>,1);
}
}
</lsl>

'''TASK 5''':
-------
Now that you understand alpha we shall make our object disappear!
To do this we will use the function llSetAlpha, its layout is llSetAlpha(float alpha, integer face).
llSetAlpha(0, ALL_SIDES); would make all the faces of the object transparent.
If it was a linked object you could use llSetLinkAlpha, which its layout is
llSetLinkAlpha(integer linknumber, float alpha, integer face).
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetAlpha(0, ALL_SIDES);
}
}
</lsl>

'''Task 6''':
-------
Lets try make our object texture itself, to do this we will use the function llSetTexture, its
layout is llSetTexture(string texture, integer face).You can do this two ways, you can place a
texture inside the object or use a UUID. To make it change to a texture you have placed inside
the object, do it like this llSetTexture("NAME OF TEXTURE", ALL_SIDES);
If you want to use a UUID, find a texture in your inventory, right click it > copy asset UUID,
then paste the UUID in the "" so it looks like this
llSetTexture("j4m3s000-0000-0000-0000-b3n3d3k00000", ALL_SIDES);
If it was a linked object you could use llSetLinkTexture, which its layout is
llSetLinkTexture(integer linknumber, string texture, integer face);
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetTexture("NAME OF TEXTURE", ALL_SIDES);
}
}
</lsl>

'''Task 7''':
-------
Now lets move onto something more tricky, as you understand a bit about keys we will make out object
only respond when the owner clicks the object, this is called a if statement.
To do this we will need to use the functions llGetOwner() and llDetectedKey(0);, llGetOwner will
return your key UUID and llDetectedKey(0) when put under the touch event will return the key of who is
clicking/touching your object. So firstly lay it out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}

}
}
</lsl>

If you want it to do something when someone else other than the owner touches it, use a else statement.
You can do this by, laying out your script like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
if (llDetectedKey(0) == llGetOwner())
{
llSay(0, "Owner Touched.");
}
else
{
llSay(0, "Someone Else Touched.");
}
}
}
</lsl>

'''Task 8''':
-------
Now lets try make a object do something when you say something, to do this
we will have to use a llListen function, its layout is this
llListen(integer channel, string name, key id, string msg);
We will firstly place this under the state_entry() event.
In this task we will just make it use the public channel, which is 0, and we will make it
listen to only you, which requires the llGetOwner() function we used previously.
We will then need to use a listen event, its layout is like this
listen(integer channel, string name, key id, string message) {, replace the touch event with this.
we will then make the object annoy you by it saying "Really?" whenever you type something XD
This will involve using a llSay like we used in task 1.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(0,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llSay(0,"Really?");
}
}
</lsl>

To make it only listen for commands not on the public channel, which will be more secret and
which is less laggy in complex scripts, you can do this by changing the integer 0 to something
like 99, this time use a llOwnerSay instead of a llSay, which should make it secret.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{

llOwnerSay("Really?");
}
}
</lsl>

To chat in another channel, just type in the chat bar /channel before you type something,
in this case it will be "/99 hello" for example.To make it do only certain stuff when you say
certain commands we will have to use a if statement, like before but this time we will have
to check if the message equals the command, if (message == "Your Command Here").
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llListen(99,"",llGetOwner(),"");
}

listen(integer channel, string name, key id, string message)
{
if (message == "hello")
{
llOwnerSay("Hello to you too!");
}
else
{
llOwnerSay("INVALID COMMAND");
}
}
}
</lsl>

To learn more about llListen take a look at:

https://wiki.secondlife.com/wiki/llListen

'''TASK 9''':
-------
Now lets experiment with vectors, and make your object move non physically,
to do this we will need to use the function llSetPos, its layout is llSetPos(vector pos);
We will also use llGetPos() so we can make it move +1 of its current position.
Place the llSetPos function under a touch event with a vector <0,0,1> + llGetPos();.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}

touch_start(integer total_number)
{
llSetPos(llGetPos() + <0,0,1>);
}
}
</lsl>

A position vector layout is in the format x,y,z, so <0,0,1> will make it go up 1m.
to learn more take a look at:

https://wiki.secondlife.com/wiki/llSetPos

'''TASK 10''':
--------
Like when editing a object you can make it Phantom, Physical...
You can also do this with scripting, the function you have to use to do this is
llSetStatus, its layout is llSetStatus(integer status, integer value);, so if i wanted
to make my object go physical the integer status would be STATUS_PHYSICS or 1, if i wanted
to make my object go phantom i would use STATUS_PHANTOM or 16.
Your script should look something like this:

<lsl>
default
{
state_entry()
{
llSetStatus(STATUS_PHYSICS, TRUE);
}
}
</lsl>

---------------------------------------------------------------------------------------------------

You now know pretty much the basics of scripting,
but there are still many more functions to use and experiment with yet!!!!!!
To know more functions and what they do, take a look at these links below:

http://wiki.secondlife.com/wiki/LSL_Portal

http://www.lslwiki.net/lslwiki/wakka.php?wakka=HomePage

http://rpgstats.com/wiki/index.php?title=Main_Page

---------------------------------------------------------------------------------------------------
{{LSLC|Tutorials}}

UUID

2012-01-14T19:51:45Z

Vulcan Viper: /* The UUID and Secondlife */

{{Help |Glossary=*}}{{LSL Header}}

UUID is an abbreviation for '''Universally Unique Identifier'''. It is a 128-bit (16 byte) value which is generated in such a way as to make collisions very unlikely. They are often represented as a string of 32 hex characters with four dashes interspersed. See [http://en.wikipedia.org/wiki/UUID Wikipedia on UUIDs] for more information.

In LSL they are stored in the [[key]] variable type (which is a specialized form of a string).

== The UUID and Secondlife ==
In Second Life every object and every avatar has an UUID and they can be split up into four groups: Asset, Instance, Account and Land UUID's.

SL uses Version 4 UUIDs as defined in {{RFC|4122|target=section-4.1.3}}, though there are some that are not V4.

=== Inventory ===
Inventory as it is thought of is really only a permissions layer. The inventory item, is really just a wrapper around an [[asset]]. The wrapper contains the permissions, creator & owner of the asset and a link to the asset. The link is the asset UUID.

=== Asset UUIDs ===
Asset UUIDs are used as the handle for all types that can be inventory items. The asset UUID is what is returned by [[llGetInventoryKey]] and by the "Copy UUID" feature in the client. Full (asset) permissions are required to get the UUID. Assets are immutable (they cannot be modified); when the user is editing an asset, they are in fact creating new assets. The appearance is that modified inventory items are assigned new UUIDs.

* Animation
* Gestures
* Objects
* Notecards
* Scripts
* Sounds
* Textures (including sculpty textures)
----
*When an Object is modified in-world, it is not assigned a new asset UUID until it is derezzed, copied back to inventory or during sim-state save. Modifying an instance of an asset will not update other instances or inventory copies.
*Brand new notecards are just asset wrappers without an asset. That is to say, new notecards have an asset UUID of [[NULL_KEY]]. The asset isn't created until the notecard is edited and then saved.
*Assets that are no longer inventory and are not referenced by any script are eventually deleted. Before they are deleted they are place in a database where they await deletion but can still be revived.

=== Instance UUIDs ===
Every time an object is [[rez]]zed, all of the prims (including the root prim) are assigned instance UUIDs. An avatar's attachments keeps it's instance UUIDs when the user teleports or moves from one region to another (they are not kept when an avatar logs off). The instance UUID is what is returned by [[llGetKey]] and other functions.

=== Account UUIDs ===
Account UUIDs are assigned during the creation process and never change. They are generally public information.
* Avatar - Public
* Group - Public or private depending on setup.
The avatar UUID is returned by [[llGetOwner]] and other functions.

=== Land UUIDs ===
* Parcel
* Region
----
* This information is technically available to the public but there is no interface to get at it directly (the UUIDs are sent to the client but consumed internally and never exposed to the user).
* Only one instance of these can exist in-world at any time.
** When copied, new UUIDs are assigned.
* Modification does not cause a new UUID to be assign.

How do I make it brighter? It's so dark I can't see anything.

2010-03-08T15:03:57Z

Vulcan Viper: Updated the text of the last two menu options, to be in accordance with the latest SL viewer.

{{KBmaster}}
This is how you do it!

* Select '''World > Environment Settings > Midday'''. The sun will come out and shine for you.
[[Category:Moving Around]]
[[Category:Controls and Getting Around]]
[[Category:Menus and Controls]]

[[Category:Knowledge Base]]

Talk:What does "SLT" stand for?

2009-11-09T19:44:41Z

Vulcan Viper:

I could not hope to disagree more, with discouraging the use of SLT in Second Life. At least then you use the same short-cut, regardless of DST. What could possibly be more logical, than using '''Second Life''' Time in '''Second Life'''?

Linden Lab...please, see the logic in using the term Second Life Time in Second Life. Put SLT back where it reads either PDT or PST now.

Talk:What does "SLT" stand for?

2009-11-09T19:43:46Z

Vulcan Viper: Created page with 'I could not hope to disagree more, with discouraging the use of SLT in Second Life. At least then you use the same short-cut, regardless of DST. What could possibly be more logic...'

I could not hope to disagree more, with discouraging the use of SLT in Second Life. At least then you use the same short-cut, regardless of DST. What could possibly be more logical, then using '''Second Life''' Time in '''Second Life'''?

Linden Lab...please, see the logic in using the term Second Life Time in Second Life. Put SLT back where it reads either PDT or PST now.