Second Life Wiki - User contributions [en]

https://wiki.secondlife.com/w/api.php?action=feedcontributions&feedformat=atom&user=Blueman+Steele Second Life Wiki - User contributions [en] 2026-07-28T20:24:50Z User contributions MediaWiki 1.42.1 https://wiki.secondlife.com/w/index.php?title=LSL_101/Integers&diff=497913 LSL 101/Integers 2009-09-29T12:59:18Z

<p>Blueman Steele: </p> <hr /> <div>[[Category:LSL 101]]<br /> {{NavNextPrev|prev=Strings and Simple Output|next=The touch_start Event}}<br /> <br /> Integers are another data type found in LSL along with Strings. LSL can handle whole numbers from −2,147,483,648 to +2,147,483,647. Integers can either be represented literally in a script or placed within a [https://wiki.secondlife.com/wiki/LSL_101/Variables variable] at runtime. Integers can use the following mathematial operations.<br /> <br /> * + add<br /> * - subtract<br /> * * multiply<br /> * / divide<br /> * % modulus<br /> <br /> <br /> To be able to print these numbers however, you'll need to [https://wiki.secondlife.com/wiki/Typecast typcast] then into a string. <br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)5 );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> Why do we preface the number 5 with (string)? llSay is only expecting a string and will not be able to print a number without you [https://wiki.secondlife.com/wiki/Typecast typcasting] it first. We can do the following.<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "5" );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> In the example above, 5 is represented as a string so no typecasting is needed. However in this form it's not really the integer 5. If it's not an integer, you won't be able to perform math on the number. Here's an example where math is performed before printing.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)(2+3) );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> With some [https://wiki.secondlife.com/wiki/LSL_101/String_Concatenation string concatenation] you can combine two strings (including typecast numbers) to help label the output.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "two plus three equals " + (string)(2 + 3) );<br /> llSay(0, "100 minus 1 equals " + (string)(100 - 1) );<br /> llSay(0, "5 times 5 equals " + (string)(5 * 5) );<br /> llSay(0, "six divides in twelve " + (string)(12 / 6) + " times." );<br /> llSay(0, "20 divided by 7 equals " + (string)(20 / 7) + " with a remainder of " + (string)(20 % 7));<br /> }<br /> <br /> }<br /> </lsl></div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_101/Integers&diff=497903 LSL 101/Integers 2009-09-29T12:58:16Z

<p>Blueman Steele: </p> <hr /> <div>[[Category:LSL 101]]<br /> {{NavNextPrev|prev=Strings and Simple Output|next=The touch_start Event}}<br /> <br /> Integers are another data type found in LSL along with Strings. LSL can handle whole numbers from −2,147,483,648 to +2,147,483,647. Integers can either be represented literally in a script or placed within a [https://wiki.secondlife.com/wiki/LSL_101/Variables variable] at runtime. Integers can use the following mathematial operations.<br /> <br /> + add<br /> - subtract<br /> * multiply<br /> / divide<br /> % modulus<br /> <br /> <br /> To be able to print these numbers however, you'll need to [https://wiki.secondlife.com/wiki/Typecast typcast] then into a string. <br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)5 );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> Why do we preface the number 5 with (string)? llSay is only expecting a string and will not be able to print a number without you [https://wiki.secondlife.com/wiki/Typecast typcasting] it first. We can do the following.<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "5" );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> In the example above, 5 is represented as a string so no typecasting is needed. However in this form it's not really the integer 5. If it's not an integer, you won't be able to perform math on the number. Here's an example where math is performed before printing.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)(2+3) );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> With some [https://wiki.secondlife.com/wiki/LSL_101/String_Concatenation string concatenation] you can combine two strings (including typecast numbers) to help label the output.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "two plus three equals " + (string)(2 + 3) );<br /> llSay(0, "100 minus 1 equals " + (string)(100 - 1) );<br /> llSay(0, "5 times 5 equals " + (string)(5 * 5) );<br /> llSay(0, "six divides in twelve " + (string)(12 / 6) + " times." );<br /> llSay(0, "20 divided by 7 equals " + (string)(20 / 7) + " with a remainder of " + (string)(20 % 7));<br /> }<br /> <br /> }<br /> </lsl></div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_101/Integers&diff=497893 LSL 101/Integers 2009-09-29T12:42:21Z

<p>Blueman Steele: </p> <hr /> <div>[[Category:LSL 101]]<br /> {{NavNextPrev|prev=Strings and Simple Output|next=The touch_start Event}}<br /> <br /> Integers are whole numbers from −2,147,483,648 and +2,147,483,647. Integers can be represented literally in a scripts or placed within a [https://wiki.secondlife.com/wiki/LSL_101/Variables variable] at runtime. To be able to see these numbers however, you'll need to [https://wiki.secondlife.com/wiki/Typecast typcast] then into a string. <br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)5 );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> Why do we preface the number 5 with (string)? llSay is only expecting a string and will not be able to print a number without you [https://wiki.secondlife.com/wiki/Typecast typcasting] it first. We can do the following.<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "5" );<br /> }<br /> <br /> }<br /> </lsl><br /> <br /> Here 5 is represented as a string so no typecasting is needed. However in this form it's not really the integer 5 (which can be added and subtracted). Here's an example where math is performed before printing.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, (string)(2+3) );<br /> }<br /> <br /> }<br /> </lsl></div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlSensor&diff=291643 LlSensor 2009-03-24T16:00:04Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function/object|id|object or avatar|sim=*}}{{#vardefine:constants_nb|{{LSL Constants/Sensing|type}}}}{{LSL_Function<br /> |func_id=28|func_sleep=0.0|func_energy=10.0<br /> |sort=Sensor|func=llSensor<br /> |func_desc=Performs a single scan for '''name''' and '''id''' with '''type''' within '''range''' meters and '''arc''' radians of forward vector<br /> |p1_type=string|p1_name=name|p1_desc=object or avatar name<br /> |p2_type=key|p2_name=id|p2_desc=<br /> |p3_type=integer|p3_name=type|p3_desc=mask ({{#var:AGENT}}, {{#var:ACTIVE}}, {{#var:PASSIVE}}, and/or {{#var:SCRIPTED}})|p3_hover=mask (AGENT, ACTIVE, PASSIVE, and/or SCRIPTED)<br /> |p4_type=float|p4_name=range|p4_desc=range 0.0 to 96.0m<br /> |p5_type=float|p5_name=arc|p5_desc=the max angle between the local x-axis of the prim and detectable objects, range 0.0 to {{#var:PI}}|p5_hover=the max angle between the local x-axis of the prim and detectable objects, range 0.0 to PI<br /> |func_footnote=If '''name''' or '''id''' is empty then that empty constraint is ignored.<br/>If '''id''' is an invalid key or [[NULL_KEY]] it is treated as empty.<br /> |return_text<br /> |spec<br /> |caveats=<br /> *Attachments cannot not detect their wearer (this includes HUD attachments).<br /> *If '''type''' is zero, the sensor will silently fail, neither [[sensor]] or [[no_sensor]] will be triggered.<br /> *Only 16 objects will be scanned each time.<br /> |examples=<br /> This sensor scans a 45 degree cone about the x-axis. ([[PI]]/2 or [[PI_BY_TWO]] scans a hemisphere. [[PI]] is a spherical scan.)<br /> <lsl>llSensor( "Gigs Taggart", NULL_KEY, AGENT, 96.0, PI/4 );</lsl><br /> <br /> This sensor detects all prims and agents with a given name within 15m of the sensor. (AGENT, PASSIVE and ACTIVE behave inclusively. SCRIPTED is not inclusive and will exclude non-scripted targets (like avatars) from the detected set.)<br /> <lsl>llSensor( "", NULL_KEY, ( AGENT | PASSIVE | ACTIVE ), 15.0, PI );</lsl><br /> <br /> |helpers<br /> |also_functions=<br /> {{LSL DefineRow||[[llSensorRepeat]]| Runs a sensor on a timer}}<br /> {{LSL DefineRow||[[llSensorRemove]]| Stops the llSensorRepeat timer}}<br /> |also_events=<br /> {{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}<br /> {{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}<br /> |also_articles<br /> |notes<br /> |permission<br /> |negative_index<br /> |cat1=Sensor<br /> |cat2=Detected<br /> |cat3<br /> |cat4<br /> }}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Talk:Getting_started_with_LSL&diff=44990 Talk:Getting started with LSL 2007-12-17T13:55:00Z

<p>Blueman Steele: </p> <hr /> <div>;Question: Is there a reason the code isn't indented? I badly whitespaced code makes it hard to sit still; like walking into someones house and finding a picture hanging crooked on the wall. Maybe whitespace should be mentioned somewhere in the article too... [[User:Strife Onizuka|Strife Onizuka]] 09:41, 1 February 2007 (PST)<br /> <br /> ;Answer: I didn't want to touch the indentation until we got syntax highlighting, (which is here now, wow took 10 months) I'll clean these up -- [[User:Blueman Steele|Blueman Steele]] 05:50, 17 December 2007 (PST)<br /> <br /> <br /> ;Note: Moved the page, it's all the rage to have spaces in names. As to the capitalization of the name thats not my can of worms. [[User:Strife Onizuka|Strife Onizuka]] 09:46, 1 February 2007 (PST)<br /> <br /> <br /> ;Question: Code sample doesn't match what the article is saying. "The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually." Where's the two comments?<br /> <br /> ;Answer: Fixed it, I had the idea of commenting the code but decided instead to show it in its original form. -- [[User:Blueman Steele|Blueman Steele]] 05:46, 17 December 2007 (PST)<br /> <br /> <br /> ;Question: RESET SCRIPTS IN SELECTION" etc. is greyed out How do I activate these options ?<br /> <br /> ;Answer: Could be a number of things including permissions or if you have the right object (or sub object selected) [[User:Blueman Steele|Blueman Steele]] 05:54, 17 December 2007 (PST)</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Talk:Getting_started_with_LSL&diff=44989 Talk:Getting started with LSL 2007-12-17T13:45:54Z

<p>Blueman Steele: /* Code sample doesn't match what the article is saying */</p> <hr /> <div>Is there a reason the code isn't indented? I badly whitespaced code makes it hard to sit still; like walking into someones house and finding a picture hanging crooked on the wall. Maybe whitespace should be mentioned somewhere in the article too... [[User:Strife Onizuka|Strife Onizuka]] 09:41, 1 February 2007 (PST)<br /> <br /> Moved the page, it's all the rage to have spaces in names. As to the capitalization of the name thats not my can of worms. [[User:Strife Onizuka|Strife Onizuka]] 09:46, 1 February 2007 (PST)<br /> <br /> * Code sample doesn't match what the article is saying <br /> <br /> "The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually."<br /> <br /> Where's the two comments?<br /> <br /> Fixed it, I had the idea of commenting the code but decided instead to show it in its original form. -- [[User:Blueman Steele|Blueman Steele]] 05:46, 17 December 2007 (PST)<br /> <br /> == RESET SCRIPTS IN SELECTION" etc. is greyed out ==<br /> <br /> How do I activate these options ?</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44988 Getting started with LSL 2007-12-17T13:42:44Z

<p>Blueman Steele: /* Dissecting "Hello World" */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == Dissecting "Hello World" ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> === Putting it all together ===<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself. <br /> <br /> === On/Off Example Using States ===<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> === Default State ===<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered. Which is this case in entered the first time the script is run.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44987 Getting started with LSL 2007-12-17T13:36:10Z

<p>Blueman Steele: /* A closer look */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == Dissecting "Hello World" ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> === Putting it all together ===<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself. <br /> <br /> === On/Off Example Using States ===<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> === Default State ===<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered. Which is this case in entered the first time the script is run.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44986 Getting started with LSL 2007-12-17T13:35:00Z

<p>Blueman Steele: /* Introducing States and Events */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == Dissecting "Hello World" ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> === Putting it all together ===<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself. <br /> <br /> === On/Off Example Using States ===<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44985 Getting started with LSL 2007-12-17T13:32:14Z

<p>Blueman Steele: /* Putting it all together */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == Dissecting "Hello World" ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> === Putting it all together ===<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44984 Getting started with LSL 2007-12-17T13:31:10Z

<p>Blueman Steele: /* A Closer Look */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == Dissecting "Hello World" ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44983 Getting started with LSL 2007-12-17T13:27:19Z

<p>Blueman Steele: /* Wash / Rinse / Repeat */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Development Cycle ==<br /> <br /> (aka Wash / Rinse / Repeat)<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> ===WHY STOP AND START?===<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44982 Getting started with LSL 2007-12-17T13:25:27Z

<p>Blueman Steele: /* A Closer Look */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> ===STATES===<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> ===EVENTS===<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> ===FUNCTIONS===<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44981 Getting started with LSL 2007-12-17T13:21:28Z

<p>Blueman Steele: /* Putting it all together */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. <br /> <br /> <lsl><br /> <br /> default // All Scripts need a Default State<br /> <br /> { // this open curly bracket denotes the start of the state<br /> state_entry() // an event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event's curly braces<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44980 Getting started with LSL 2007-12-17T13:19:49Z

<p>Blueman Steele: /* A Closer Look */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number) // this is an event<br /> {<br /> // this is the content of the event (between curly braces)<br /> }<br /> <br /> }<br /> // end of default state<br /> </lsl><br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> <lsl><br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44979 Getting started with LSL 2007-12-17T13:18:11Z

<p>Blueman Steele: /* What is LSL? */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> </lsl><br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> <lsl><br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=44978 Getting started with LSL 2007-12-17T13:15:08Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''FOR WHOM IS THIS TUTORIAL:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the [[touch_start]]() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose '''create''' (for one button macs use command+click).<br /> <br /> By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter '''edit''' mode and an edit window will pop up. To place a script in an existing object, right click it and hit edit to open the edit window.<br /> <br /> In the edit window you may see a button marked '''more>>>''' click it to reveal five tabs marked '''general''', '''object''', '''features''', '''content''', and '''texture'''. Click '''content'''.<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed (resurrected) again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and resetting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car...while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> </lsl><br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> <lsl><br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> </lsl><br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "[[state_entry]]" which is triggered by the state being entered, and "[[touch_start]]" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> <lsl><br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> </lsl><br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lowercase Ls. We've seen [[llSay]]() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> <lsl><br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracket closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> </lsl><br /> <br /> The instant you save your script, it enters default state, which in turn runs the "[[state_entry]]" event which in turn runs the function [[llSay]]() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "[[touch_start]]" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Let's look at a script with two states with two events in each.<br /> <br /> <lsl><br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction (do not put them at the end of if statements)<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0.0, 0.0, 0.0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> </lsl><br /> A simplification of this would be<br /> <br /> <br /> <lsl><br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> </lsl><br /> <br /> Note that after "[[default]]" all new states begin with the word "[[state]]". Also, while the object has a texture, the color will affect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> <lsl>llSay(0, "turning on!");</lsl><br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> <lsl>llSetColor(<1.0, 1.0, 1.0>, ALL_SIDES);</lsl><br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1s stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "[[touch_start]]" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> <lsl>state off;</lsl><br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> [[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...<br /> <br /> <lsl>llWhisper(0,"turning on!");</lsl><br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> [[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> <lsl>llOwnerSay("turning on!");</lsl><br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via [[llSetText]]( ) like this.<br /> <br /> <lsl>llSetText("I am on", <1.0, 1.0, 1.0>,1.0);</lsl><br /> <br /> What do the numbers mean? The <1.0, 1.0, 1.0> we've seen before. It represents the values for red, green, and blue. For now just know that <1.0, 1.0, 1.0> means "white" and <0.0, 0.0, 0.0> means "black". Replace the [[llSay]](0,"turning off!"); with...<br /> <br /> <lsl>llSetText("I am off", <0.0, 0.0, 0.0>,1.0);</lsl><br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> <br /> <br /> == Next steps ==<br /> <br /> Now than you can edit and run LSL code, move on to one of the more advanced [[LSL_Tutorial|LSL Tutorial]]s.<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlSetAlpha&diff=38766 LlSetAlpha 2007-11-01T15:05:52Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function/face|face}} {{LSL_Function/alpha|alpha}} {{LSL_Function<br /> |func_id=51|func_sleep=0.0|func_energy=10.0<br /> |func=llSetAlpha|sort=SetAlpha<br /> |p1_type=float|p1_name=alpha<br /> |p2_type=integer|p2_name=face<br /> |func_footnote<br /> |func_desc=Sets the '''alpha''' on '''face'''<br /> |return_text<br /> |spec<br /> |caveats<br /> |constants<br /> |examples=<pre><br /> float cloakSpeed = .1;<br /> <br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> integer x;<br /> float xf;<br /> for (x=9; x>0; x--)<br /> {<br /> xf = x * .1;<br /> llSleep(cloakSpeed);<br /> llSetAlpha(xf,ALL_SIDES); <br /> }<br /> state cloaked;<br /> }<br /> }<br /> <br /> state cloaked<br /> {<br /> touch_start(integer total_number)<br /> {<br /> integer x;<br /> float xf;<br /> for (x=1; x<11; x++)<br /> {<br /> xf = x * .1;<br /> llSleep(cloakSpeed);<br /> llSetAlpha(xf,ALL_SIDES); <br /> }<br /> state default;<br /> }<br /> }<br /> </pre><br /> |helpers<br /> |also_functions=<br /> {{LSL DefineRow||[[llGetAlpha]]|Gets the prim's alpha}}<br /> {{LSL DefineRow||[[llGetColor]]|Gets the prim's color}}<br /> {{LSL DefineRow||[[llSetColor]]|Sets the prim's color}}<br /> {{LSL DefineRow||[[llSetLinkColor]]|Sets link's color}}<br /> {{LSL DefineRow||[[llSetLinkAlpha]]|Sets link's alpha}}<br /> |also_tests<br /> |also_events=<br /> {{LSL DefineRow||[[changed]]|[[CHANGED_COLOR]]}}<br /> |also_articles<br /> |notes<br /> |deprecated<br /> |cat1<br /> |cat2<br /> |cat3<br /> |cat4<br /> }}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlGetPizza&diff=15736 LlGetPizza 2007-03-20T08:48:22Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function<br /> |func_id|func_sleep=1800|func_energy=10.0<br /> |mode=request|func=llPizza|sort=Pizza<br /> |func_desc=Order pizza while logged into Second Life.<br /> |p1_type=key|p1_name=destination|p1_desc=Avatar [[UUID]].<br /> |func_footnote=The avatar '''destination''' does not have to be in the same sim, but should be close by to reduce delivery latency.<br /> |return_text<br /> |spec<br /> |caveats=...or your money back! (Successful delivery may cause user to sleep too)<br /> |examples=<pre><br /> llPizza(llGetOwner());<br /> </pre><br /> |helpers<br /> |related<br /> |also<br /> |notes=A long time feature of a popular MMO. Should be added to Second Life to keep up.}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Category:LSL_Color&diff=14679 Category:LSL Color 2007-03-05T16:44:27Z

<p>Blueman Steele: added/rearranged colors (orange and violet forthcoming)</p> <hr /> <div>{{LSL Header<br /> }}{{#vardefine:header_title|Color in LSL<br /> }}{{#vardefine:header_text|LSL has it's own special format for color. LSL uses a [[vector]] to store color. Unlike traditional RGB where each channel is 0 -&gt; 255, LSL's color channels are 0 -&gt; 1.<br/><br /> ===Format: {{LSL VR|'''R'''|'''G'''|'''B'''}}===<br /> {{{!}}<br /> {{LSL DefineRow|float|x|Red value|[0, 1]}}<br /> {{LSL DefineRow|float|y|Green value|[0, 1]}}<br /> {{LSL DefineRow|float|z|Blue value|[0, 1]}}<br /> {{!}}}<br /> <br /> }}{{#vardefine:helpers|<br /> ===Useful functions for storing/retrieving color and alpha values to/from integers===<br /> <pre><br /> integer ColorAlphatoRGBA(vector color, float alpha) {<br /> return (((integer)(alpha * 255.0) & 0xFF) << 24) |<br /> (((integer)(color.x * 255.0) & 0xFF) << 16) |<br /> (((integer)(color.y * 255.0) & 0xFF) << 8) |<br /> ((integer)(color.z * 255.0) & 0xFF);<br /> }<br /> <br /> vector RGBAtoColor(integer rgba) {<br /> return < ((rgba >> 16) & 0xFF) / 255.0, ((rgba >> 8) & 0xFF) / 255.0, (rgba & 0xFF) / 255.0 >;<br /> }<br /> <br /> float RGBAtoAlpha(integer rgba) {<br /> return ((rgba >> 24) & 0xFF) / 255.0;<br /> }</pre><br /> }}{{#vardefine:examples|<br /> <pre><br /> vector white = <1.0, 1.0, 1.0>;<br /> vector grey = <0.5, 0.5, 0.5>;<br /> vector black = <0.0, 0.0, 0.0>;<br /> vector red = <1.0, 0.0, 0.0>;<br /> vector green = <0.0, 1.0, 0.0>;<br /> vector blue = <0.0, 0.0, 1.0>;<br /> vector yellow = <1.0, 1.0, 0.0>;<br /> vector cyan = <0.0, 1.0, 1.0>;<br /> vector magenta = <1.0, 0.0, 1.0>;<br /> <br /> <br /> </pre><br /> }}{{LSL Generic}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Talk:LSL_Useful_Function_WishList&diff=14678 Talk:LSL Useful Function WishList 2007-03-05T16:29:15Z

<p>Blueman Steele: </p> <hr /> <div>== Useful/Joke Functions ==<br /> I have been noticing that some of the "feature request" functions are here only as documentation of a funny idea someone had. IMHO these joke functions (and some are really funny, don't get me wrong,) should be organized into a different category/page. That would allow for less clutter and make it more likely that useful suggestions would be seen by the eyes of those who have tha ability to implement them. Does anyone else concur or disagree? [[User:Cron Stardust|Cron Stardust]] 15:52, 4 March 2007 (PST)<br /> :I really really don't like joke functions. I don't think they should be on the wiki at all. It's not that I don't appreciate humor, it's just that I don't want LL wasting their time processing requests for joke functions. If we treat things like a joke, then LL will not take the wiki seriously; the effect will be a loss of influence. [[User:Strife Onizuka|Strife Onizuka]] 21:04, 4 March 2007 (PST)<br /> ::That was why I suggested a different page/template for them. No-one can prevent them being added, but why have them dilute this space when they can be put in a slightly different category. :D [[User:Cron Stardust|Cron Stardust]] 21:29, 4 March 2007 (PST)<br /> :::I'll make up a new modifier-template, it's not a time consuming task. Or maybe, make it a mode of the request template. [[User:Strife Onizuka|Strife Onizuka]] 22:28, 4 March 2007 (PST)<br /> :My "llPizza" is nearly both. If we had to remove humor to achieve better focus I'm all for it. However I would welcome the idea of two separate areas. We are talking about a program with an easter egg of "hippos". I think humor is a huge part of Second Life.[[User:Blueman Steele|Blueman Steele]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Weapon&diff=12767 Weapon 2007-02-23T07:04:36Z

<p>Blueman Steele: Modified towards "neutral" tone required by the Wiki. Removed TOS violating subjects.</p> <hr /> <div>=== Weapon Types ===<br /> <br /> There are hundreds of weapons in Second Life to choose from. They can be classified in several categories:<br /> <br /> *Basic Guns - Guns that fire basic physical bullets. These bullets are stopped by most quality shield systems.<br /> *Advanced "Guns" - Guns that fire tracking, non-physical bullets. These can't be stopped by all but the most advanced (and expensive) defense systems.<br /> *Explosives and "Nukes" - These range from basic explosives to nukes that can kill everyone (if in a damage enabled area) within 96m of the detonation point.<br /> *HUD Weapons - There are several quality HUD based combat systems available.<br /> *Robots and Turrets - These can be remote controlled, or set to fire on certain targets automatically.<br /> *Annoying Crap - Stuff like caging guns, anything that flings people into the air. Considered "noobish" and frowned upon by experienced combat people.<br /> <br /> For more information, see [[Combat]]<br /> <br /> === Weapon Damage ===<br /> <br /> Weapons in Second Life can inflict the following types of [[damage]].<br /> <br /> * Kill with one hit<br /> * Partial [[damage]] from physical bullets<br /> * Push<br /> * Shieldbreaker<br /> * Caging - can confine an avatar<br /> <br /> === Weapon Quality ===<br /> <br /> Free weapons tend to be badly scripted such that they cause lag and other problems. Second Life weapons are a case where you really do get what you pay for.<br /> <br /> [[Category:Tutorials|Combat]]<br /> <br /> <br /> == See Also ==<br /> * [[Help:Weapons in Second Life]]<br /> * [[Damage]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=12403 Getting started with LSL 2007-02-22T19:00:16Z

<p>Blueman Steele: grammar change</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''WHO THIS TUTORIAL IS FOR:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. A script in Second Life is a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL special is its emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life behaviors can be modeled with "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life, but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). For example, when an avatar touches an object, a ''touch_start'' message is sent to the object, which causes the touch_start() event handler to begin executing. So the minimum LSL program must have one state with one event handler in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose "create". (for one button macs use command+click)<br /> <br /> By default, you should see a "wand" icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter "edit" mode and an edit window will pop up.<br /> (Note: to place a script in an existing object, right click it and hit edit to open the edit window.)<br /> <br /> In the edit window you may see a button marked "more>>>" click it to reveal five tabs marked general, object, features, content, and texture. Click "content".<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press "new script" to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit "save" and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched."<br /> (make sure the "edit" building window is closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and reseting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car.... while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> <br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "state_entry" which is triggered by the state being entered, and "touch_start" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> <br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lower case L's. We've seen llSay() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracked closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> <br /> The instant you save your script, it enters default state, which in turn runs the "state_entry" event which in turn runs the function llSay() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "touch_start" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Lets look at a script with two states with two events in each.<br /> <br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction.<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> <br /> A simplification of this would be<br /> <br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> <br /> Note that after "default" all new states begin with the word "state". Also, while the object has a texture, the color will effect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "state_entry" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> [[LSL_llSay|llSay]](0, "turning on!");<br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> llSetColor(<1,1,1>, ALL_SIDES);<br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1's stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "touch_start" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> state off;<br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> llWhisper( ) is just like llSay( ) but only broadcasts at half the distance. You still must state what channel. So....<br /> <br /> llWhisper(0,"turning on!");<br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using llShout( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> llOwnerSay( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> llOwnerSay("turning on!");<br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via llSetText( ) like this.<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> What do the numbers mean? The <1,1,1> we've seen before. It represents the values for red, green, and blue. For now just know that <1,1,1>, means "white" and <0,0,0> means "black". Replace the llSay(0,"turning off!"); with...<br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_in_Second_Life&diff=9620 Getting started in Second Life 2007-02-11T11:13:48Z

<p>Blueman Steele: </p> <hr /> <div>''This is an experiment of the multi-language set up, please do not edit this page.''<br /> <br /> This page is being translated into Spanish. [[https://wiki.secondlife.com/wiki/Help:Getting_started_in_Second_Life/es | Link]]<br /> <br /> <br /> == Quick Tips for Second Life ==<br /> <br /> Lost? Confused? Both?! This card will be your guide to getting started in Second Life. Check the bottom of the card for links to more help. <br /> <br /> <br /> == The first things you should learn ==<br /> <br /> There is a lot to learn about Second Life, but here is the minimum you need to get started.<br /> <br /> '''-- Movement --'''<br /> Movement includes walking, running, and flying. To walk forward, backwards and turn left and right you can use the arrow keys. You can also do the same with the letters WASD on your keyboard. Pressing CTRL + R will toggle if you are running or not. Hold shift to strafe sideways.<br /> <br /> '''-- Flying --'''<br /> To fly, you can hit the blue fly button at the bottom of your screen, or hit F, or press and hold the Page Up key. Once airborne, you can use either Page Up and Page Down to rise and fall, or E and C on your keyboard. Tapping those will make you jump. Hit the Home key or F again or "stop flying" to do just that.<br /> <br /> '''-- Focus --''' <br /> If you notice that some keys work differently when you are chatting, it's due to focus. Where you last click can change the WASD keys to only let you type. To restore focus to movement, hit ESC up to 3 times or click once on the ground in front of you.<br /> <br /> '''-- Camera Control --'''<br /> Click and drag on your back to take a look around. ALT+click and drag on an object to zoom in and out and pan around it. CTRL+ALT+click and drag to "orbit". CTRL+ALT+SHIFT+click and drag to pan left right up and down. Hitting the esc key twice will reset your view.<br /> <br /> '''-- Mouse Look --'''<br /> Mouse look will have you see from your avatar's point of view and change your controls a little. You will now strafe left and right and steer with the mouse. Hit M to enter mouse look and esc to get out of it.<br /> <br /> '''-- Communication --'''<br /> Make sure you know how to Instant Message people you can see, and people you can't see via your Search and Friends buttons. Also make sure you get an idea of how far you can be "heard" when you chat or shout. As you join groups, you will see that you can start chats with entire groups. Gestures in your inventory are another way to communicate or add to what you say.<br /> <br /> '''-- Interaction --'''<br /> Interacting with objects is a big part of Second Life. Have you tried sitting on poseballs? Playing a game? Buying and object? Make sure you know about the pie menu as well as when to right click or left click. If you have one mouse button, use CMD + click for right click.<br /> <br /> '''-- New Interactions --'''<br /> While most actions still are accessable via right click. Many can now happen with a left click. For example, if you see a chair icon when you hover over an object, touching (left-clicking) it will automatically seat you. Similar icons exist for buying, paying money to, and opening objects.<br /> <br /> '''-- Objects and Inventory --'''<br /> While not everyone builds in Second Life, it's a good idea to learn the basics of moving things in edit, attaching and detaching objects from your avatar, how to find things in your inventory, and how to "unpack" a box you may receive.<br /> <br /> ''-- Respect --''<br /> There is no set of rules to define respect, except to treat others as you would like to be treated. The ability to do something does not imply permission. <br /> <br /> <br /> <br /> <br /> <br /> <br /> == CONCEPTS OF THE MAIN LAND ==<br /> <br /> <br /> ''-- Map and Teleporting --''<br /> The map lets you see nearly the whole world at once if you zoom out. Each tiny square represents an area as big as help island. Each one is a "simulator" (sim). Second Life is at about 1600 sims as of January 2006. Some are connected so that you can walk and fly between them. Others are individual islands that can be reached only via teleport. Walking or even flying everywhere would take hours.<br /> <br /> Double click on an area to be transported there, you will either arrive there directly, or as close as possible and be given a red beacon to follow. When you want to bring someone to a location, you can offer them a teleport via their profile.<br /> <br /> '''-- Landmarks --'''<br /> Landmarks are the Second Life equivalent of a bookmark. They save a place that you or someone else has been. You can find them in your inventory. Double click them and you will get a teleport option as a pop up. Create your own by pulling down the WORLD menu and choosing "Create Landmark Here"<br /> <br /> '''-- Search --'''<br /> Find will let you look up events, people, products, and also let you teleport to the various areas you find.<br /> <br /> '''-- Friends --'''<br /> As you explore you may make many friends. When you offer friendship it is reciprocal and gives the ability to see each other on the map. You can also offer a calling card instead.<br /> <br /> '''-- Damage Enabled Areas --'''<br /> In certain areas you will see a heart and "100%" at the top of your screen. This means you can take damage. If your health reaches zero you get sent back to where you have set as your "home".<br /> <br /> <br /> == WHERE TO GET MORE HELP ==<br /> <br /> It's best to get help where it's already offered. Not everyone you meet in Second Life is experienced and knowledgeable in every area. Some people specialize. Others may be brand new, like yourself. If you missed Help Island or left too soon, a public version of Help Island exists. Pressing on the links below should give you a landmark into your inventory. Also listed are some other locations where people are happy to help you out.<br /> <br /> : Island with tutorials <br /> : Classrooms and lots of help to be found<br /> <br /> If you have an immediate issue, pull dodwn the "Help" menu at the top of your screen and choose "Help Request".</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_in_Second_Life&diff=9619 Getting started in Second Life 2007-02-11T11:13:20Z

<p>Blueman Steele: </p> <hr /> <div>''This is an experiment of the multi-language set up, please do not edit this page.''<br /> <br /> This page is being translated into Spanish. [[https://wiki.secondlife.com/wiki/Help:Getting_started_in_Second_Life/es| Link]]<br /> <br /> <br /> == Quick Tips for Second Life ==<br /> <br /> Lost? Confused? Both?! This card will be your guide to getting started in Second Life. Check the bottom of the card for links to more help. <br /> <br /> <br /> == The first things you should learn ==<br /> <br /> There is a lot to learn about Second Life, but here is the minimum you need to get started.<br /> <br /> '''-- Movement --'''<br /> Movement includes walking, running, and flying. To walk forward, backwards and turn left and right you can use the arrow keys. You can also do the same with the letters WASD on your keyboard. Pressing CTRL + R will toggle if you are running or not. Hold shift to strafe sideways.<br /> <br /> '''-- Flying --'''<br /> To fly, you can hit the blue fly button at the bottom of your screen, or hit F, or press and hold the Page Up key. Once airborne, you can use either Page Up and Page Down to rise and fall, or E and C on your keyboard. Tapping those will make you jump. Hit the Home key or F again or "stop flying" to do just that.<br /> <br /> '''-- Focus --''' <br /> If you notice that some keys work differently when you are chatting, it's due to focus. Where you last click can change the WASD keys to only let you type. To restore focus to movement, hit ESC up to 3 times or click once on the ground in front of you.<br /> <br /> '''-- Camera Control --'''<br /> Click and drag on your back to take a look around. ALT+click and drag on an object to zoom in and out and pan around it. CTRL+ALT+click and drag to "orbit". CTRL+ALT+SHIFT+click and drag to pan left right up and down. Hitting the esc key twice will reset your view.<br /> <br /> '''-- Mouse Look --'''<br /> Mouse look will have you see from your avatar's point of view and change your controls a little. You will now strafe left and right and steer with the mouse. Hit M to enter mouse look and esc to get out of it.<br /> <br /> '''-- Communication --'''<br /> Make sure you know how to Instant Message people you can see, and people you can't see via your Search and Friends buttons. Also make sure you get an idea of how far you can be "heard" when you chat or shout. As you join groups, you will see that you can start chats with entire groups. Gestures in your inventory are another way to communicate or add to what you say.<br /> <br /> '''-- Interaction --'''<br /> Interacting with objects is a big part of Second Life. Have you tried sitting on poseballs? Playing a game? Buying and object? Make sure you know about the pie menu as well as when to right click or left click. If you have one mouse button, use CMD + click for right click.<br /> <br /> '''-- New Interactions --'''<br /> While most actions still are accessable via right click. Many can now happen with a left click. For example, if you see a chair icon when you hover over an object, touching (left-clicking) it will automatically seat you. Similar icons exist for buying, paying money to, and opening objects.<br /> <br /> '''-- Objects and Inventory --'''<br /> While not everyone builds in Second Life, it's a good idea to learn the basics of moving things in edit, attaching and detaching objects from your avatar, how to find things in your inventory, and how to "unpack" a box you may receive.<br /> <br /> ''-- Respect --''<br /> There is no set of rules to define respect, except to treat others as you would like to be treated. The ability to do something does not imply permission. <br /> <br /> <br /> <br /> <br /> <br /> <br /> == CONCEPTS OF THE MAIN LAND ==<br /> <br /> <br /> ''-- Map and Teleporting --''<br /> The map lets you see nearly the whole world at once if you zoom out. Each tiny square represents an area as big as help island. Each one is a "simulator" (sim). Second Life is at about 1600 sims as of January 2006. Some are connected so that you can walk and fly between them. Others are individual islands that can be reached only via teleport. Walking or even flying everywhere would take hours.<br /> <br /> Double click on an area to be transported there, you will either arrive there directly, or as close as possible and be given a red beacon to follow. When you want to bring someone to a location, you can offer them a teleport via their profile.<br /> <br /> '''-- Landmarks --'''<br /> Landmarks are the Second Life equivalent of a bookmark. They save a place that you or someone else has been. You can find them in your inventory. Double click them and you will get a teleport option as a pop up. Create your own by pulling down the WORLD menu and choosing "Create Landmark Here"<br /> <br /> '''-- Search --'''<br /> Find will let you look up events, people, products, and also let you teleport to the various areas you find.<br /> <br /> '''-- Friends --'''<br /> As you explore you may make many friends. When you offer friendship it is reciprocal and gives the ability to see each other on the map. You can also offer a calling card instead.<br /> <br /> '''-- Damage Enabled Areas --'''<br /> In certain areas you will see a heart and "100%" at the top of your screen. This means you can take damage. If your health reaches zero you get sent back to where you have set as your "home".<br /> <br /> <br /> == WHERE TO GET MORE HELP ==<br /> <br /> It's best to get help where it's already offered. Not everyone you meet in Second Life is experienced and knowledgeable in every area. Some people specialize. Others may be brand new, like yourself. If you missed Help Island or left too soon, a public version of Help Island exists. Pressing on the links below should give you a landmark into your inventory. Also listed are some other locations where people are happy to help you out.<br /> <br /> : Island with tutorials <br /> : Classrooms and lots of help to be found<br /> <br /> If you have an immediate issue, pull dodwn the "Help" menu at the top of your screen and choose "Help Request".</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_in_Second_Life/es&diff=9618 Getting started in Second Life/es 2007-02-11T11:10:09Z

<p>Blueman Steele: </p> <hr /> <div>''This is a translation of (link goes here), please do not edit while translation is being finalized.''<br /> <br /> <br /> == Ayuda básica para la Segunda Vida. ==<br /> <br /> ¿Perdido? ¿Confuso? ¡Las dos cosas?! Esta tarjeta será su guía para usar Segunda Vida. <br /> <br /> <br /> == Las primeras cosas que usted debe aprender ==<br /> <br /> Hay mucho que aprender sobre la Segunda Vida, pero aquí les presento el mínimo que usted necesita saber.<br /> <br /> -- Movimiento --<br /> El movimiento incluye caminar, correr, y volar. Para caminar adelante, al revés y manejar a la izquierda y a la derecha usted puede utilizar las llaves de flecha. También puedes usar las letras WASD en su teclado. Presionando CTRL + R cambiara si estas corriendo o caminando. Oprima la tecla de mayúsculas (SHIFT) mientras que caminas a la izquierda y a la derecha para no cambiar de vista (strafe).<br /> <br /> -- Volar --<br /> Para volar, usted puede hacer clic en el botón azul que dice "fly" en el fondo de su pantalla, o oprima F, o presiona y sostén la tecla "page up". Una vez que comienzas volar, usted pueda utilizar "page up" o "page down" para levantarse y para descender. "E" y "C" en su teclado hace lo mismo. Tocando "page up" y "page down" una ves rapido te hace brincar o agacharte. Tocando la tecla HOME o F otra vez te hace caer. También el botón "stop flying".<br /> <br /> -- Foco -- <br /> Si usted nota que algunas llaves trabajan diferentemente cuando usted está charlando, es debido al foco. Donde usted toca su ratón puede cambiar los teclados de WASD para ser solamente para mecanografiar. Para restaurar el foco al movimiento, oprime el teclado "esc" 3 veces o haga clic una vez en la tierra delante de usted.<br /> <br /> -- Control de la vista -- <br /> Si haces clic en su espalda y lo mantienes, puedes tomar una mirada alrededor. Si oprimes ALT mientras que haces clic en objeto, moviendo el raton para ariba y abajor te cambia la vista mas serca or mas lejos del objeto. Con CTRL + ALT y clic mueves su vista en un "órbita". CTRL+ALT+SHIFT+clic para mover la vista para arriba, abajor, y a los dos lados (truck). Pprime el teclado "esc" para reajustará su vista normal.<br /> <br /> -- Mirada del ratón (Mouse Look)-- <br /> La mirada del ratón hará que usted vea desde el punto de vista de su avatar y cambiara sus controles un poco. Usted ahora cambiaras su vista a la con el ratón y manejaras adelande, atras y par los dos lados con sus flechas (o WASD). Oprime M para incorporar mirada del ratón (mouse look) y oprime el teclado "esc" para salir de ella.<br /> <br /> -- Comunicación -- <br /> Debe Uster saber como comunicarse con gente que estan serca y lejos con botones de la búsqueda, charlar, y de los amigos (Chat, Search and Friends). Cuando uno usa Charlar te pueden escuchar todos dentro de un sierto distancia. Tambien existen grupos con quein puedes mandar mesajes. Los gestos en su inventario son otra manera de comunicarse.<br /> <br /> -- interacción --<br /> el obrar recíprocamente con los objetos es una parte grande de Segunda Vida. ¿Usted ha intentado sentarse en poseballs? ¿Jugar un juego? ¿Compra y objeto? Se cerciora de usted saber sobre el menú de la empanada así como cuándo enderezar tecleo o tecleo izquierdo. Si usted tiene un botón de ratón, utilice CMD + tecleo para el tecleo derecho.<br /> -- nuevas interacciones -- mientras que la mayoría de las acciones siguen siendo accesibles vía tecleo derecho. Muchos pueden ahora suceder con un tecleo izquierdo. Por ejemplo, si usted ve un icono de la silla cuando usted asoma sobre un objeto, el tacto (el izquierdo-chascar) de él le asentará automáticamente. Los iconos similares existen para comprar, pagar el dinero a, y abrir objetos.<br /> -- objetos e inventario -- mientras que no cada una las estructuras en la Segunda Vida, él es una buena idea de aprender que los fundamentos de cosas móviles adentro corrigen, uniendo y separar objetos de su avatar, cómo encontrar cosas en su inventario, y cómo "desempaqueta" una caja que usted puede recibir. <br /> -- respecto -- no hay sistema de reglas para definir respecto, a menos que para tratar otros pues usted quisiera ser tratado. La capacidad de hacer algo no implica el permiso.<br /> <br /> <br /> == CONCEPTOS DEL DE LA TIERRA ==<br /> <br /> <br /> PRINCIPAL DE LA TIERRA -- mapa y el teleporting -- el mapa le deja ver casi el mundo entero inmediatamente si usted enfoca hacia fuera. Cada cuadrado minúsculo representa un área tan grande como la isla de la ayuda. Cada es un "simulador" (sim). La Segunda Vida está en los sims cerca de 1600 en fecha enero de 2006. Algunos están conectados de modo que usted pueda caminar y volar entre ellos. Otras son las islas individuales vía las cuales puede ser alcanzado solamente teleport. El caminar o aún el volar por todas partes tomaría horas.<br /> <br /> -- búsqueda -- el hallazgo le dejará mirar para arriba los acontecimientos, gente, productos, y también le dejó teleport a las varias áreas que usted encuentra. -- amigos -- como usted le explora puede hacer a muchos amigos. Cuando usted ofrece amistad que es recíproco y da la capacidad de verse en el mapa. Usted puede también ofrecer una tarjeta para el teléfono en lugar de otro.<br /> <br /> -- áreas permitidas daños -- en ciertas áreas usted verá un corazón y un "100%" en la tapa de su pantalla. Esto significa que usted puede tomar daño. Si su salud alcanza cero usted consigue enviado de nuevo a donde usted ha fijado como su "hogar".</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_in_Second_Life&diff=9617 Getting started in Second Life 2007-02-11T11:04:18Z

<p>Blueman Steele: formating</p> <hr /> <div>''This is an experiment of the multi-language set up''<br /> <br /> <br /> == Quick Tips for Second Life ==<br /> <br /> <br /> Lost? Confused? Both?! This card will be your guide to getting started in Second Life. Check the bottom of the card for links to more help. <br /> <br /> <br /> == The first things you should learn ==<br /> <br /> There is a lot to learn about Second Life, but here is the minimum you need to get started.<br /> <br /> '''-- Movement --'''<br /> Movement includes walking, running, and flying. To walk forward, backwards and turn left and right you can use the arrow keys. You can also do the same with the letters WASD on your keyboard. Pressing CTRL + R will toggle if you are running or not. Hold shift to strafe sideways.<br /> <br /> '''-- Flying --'''<br /> To fly, you can hit the blue fly button at the bottom of your screen, or hit F, or press and hold the Page Up key. Once airborne, you can use either Page Up and Page Down to rise and fall, or E and C on your keyboard. Tapping those will make you jump. Hit the Home key or F again or "stop flying" to do just that.<br /> <br /> '''-- Focus --''' <br /> If you notice that some keys work differently when you are chatting, it's due to focus. Where you last click can change the WASD keys to only let you type. To restore focus to movement, hit ESC up to 3 times or click once on the ground in front of you.<br /> <br /> '''-- Camera Control --'''<br /> Click and drag on your back to take a look around. ALT+click and drag on an object to zoom in and out and pan around it. CTRL+ALT+click and drag to "orbit". CTRL+ALT+SHIFT+click and drag to pan left right up and down. Hitting the esc key twice will reset your view.<br /> <br /> '''-- Mouse Look --'''<br /> Mouse look will have you see from your avatar's point of view and change your controls a little. You will now strafe left and right and steer with the mouse. Hit M to enter mouse look and esc to get out of it.<br /> <br /> '''-- Communication --'''<br /> Make sure you know how to Instant Message people you can see, and people you can't see via your Search and Friends buttons. Also make sure you get an idea of how far you can be "heard" when you chat or shout. As you join groups, you will see that you can start chats with entire groups. Gestures in your inventory are another way to communicate or add to what you say.<br /> <br /> '''-- Interaction --'''<br /> Interacting with objects is a big part of Second Life. Have you tried sitting on poseballs? Playing a game? Buying and object? Make sure you know about the pie menu as well as when to right click or left click. If you have one mouse button, use CMD + click for right click.<br /> <br /> '''-- New Interactions --'''<br /> While most actions still are accessable via right click. Many can now happen with a left click. For example, if you see a chair icon when you hover over an object, touching (left-clicking) it will automatically seat you. Similar icons exist for buying, paying money to, and opening objects.<br /> <br /> '''-- Objects and Inventory --'''<br /> While not everyone builds in Second Life, it's a good idea to learn the basics of moving things in edit, attaching and detaching objects from your avatar, how to find things in your inventory, and how to "unpack" a box you may receive.<br /> <br /> ''-- Respect --''<br /> There is no set of rules to define respect, except to treat others as you would like to be treated. The ability to do something does not imply permission. <br /> <br /> <br /> <br /> <br /> <br /> <br /> == CONCEPTS OF THE MAIN LAND ==<br /> <br /> <br /> ''-- Map and Teleporting --''<br /> The map lets you see nearly the whole world at once if you zoom out. Each tiny square represents an area as big as help island. Each one is a "simulator" (sim). Second Life is at about 1600 sims as of January 2006. Some are connected so that you can walk and fly between them. Others are individual islands that can be reached only via teleport. Walking or even flying everywhere would take hours.<br /> <br /> Double click on an area to be transported there, you will either arrive there directly, or as close as possible and be given a red beacon to follow. When you want to bring someone to a location, you can offer them a teleport via their profile.<br /> <br /> '''-- Landmarks --'''<br /> Landmarks are the Second Life equivalent of a bookmark. They save a place that you or someone else has been. You can find them in your inventory. Double click them and you will get a teleport option as a pop up. Create your own by pulling down the WORLD menu and choosing "Create Landmark Here"<br /> <br /> '''-- Search --'''<br /> Find will let you look up events, people, products, and also let you teleport to the various areas you find.<br /> <br /> '''-- Friends --'''<br /> As you explore you may make many friends. When you offer friendship it is reciprocal and gives the ability to see each other on the map. You can also offer a calling card instead.<br /> <br /> '''-- Damage Enabled Areas --'''<br /> In certain areas you will see a heart and "100%" at the top of your screen. This means you can take damage. If your health reaches zero you get sent back to where you have set as your "home".<br /> <br /> <br /> == WHERE TO GET MORE HELP ==<br /> <br /> It's best to get help where it's already offered. Not everyone you meet in Second Life is experienced and knowledgeable in every area. Some people specialize. Others may be brand new, like yourself. If you missed Help Island or left too soon, a public version of Help Island exists. Pressing on the links below should give you a landmark into your inventory. Also listed are some other locations where people are happy to help you out.<br /> <br /> : Island with tutorials <br /> : Classrooms and lots of help to be found<br /> <br /> If you have an immediate issue, pull dodwn the "Help" menu at the top of your screen and choose "Help Request".</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_in_Second_Life&diff=9616 Getting started in Second Life 2007-02-11T10:57:26Z

<p>Blueman Steele: </p> <hr /> <div>''This is an experiment of the multi-language set up''<br /> <br /> Quick Tips for Second Life<br /> ======================<br /> Lost? Confused? Both?! This card will be your guide to getting started in Second Life. Check the bottom of the card for links to more help. <br /> <br /> The first things you should learn<br /> ======================<br /> There is a lot to learn about Second Life, but here is the minimum you need to get started.<br /> <br /> -- Movement --<br /> Movement includes walking, running, and flying. To walk forward, backwards and turn left and right you can use the arrow keys. You can also do the same with the letters WASD on your keyboard. Pressing CTRL + R will toggle if you are running or not. Hold shift to strafe sideways.<br /> <br /> -- Flying --<br /> To fly, you can hit the blue fly button at the bottom of your screen, or hit F, or press and hold the Page Up key. Once airborne, you can use either Page Up and Page Down to rise and fall, or E and C on your keyboard. Tapping those will make you jump. Hit the Home key or F again or "stop flying" to do just that.<br /> <br /> -- Focus -- <br /> If you notice that some keys work differently when you are chatting, it's due to focus. Where you last click can change the WASD keys to only let you type. To restore focus to movement, hit ESC up to 3 times or click once on the ground in front of you.<br /> <br /> -- Camera Control --<br /> Click and drag on your back to take a look around. ALT+click and drag on an object to zoom in and out and pan around it. CTRL+ALT+click and drag to "orbit". CTRL+ALT+SHIFT+click and drag to pan left right up and down. Hitting the esc key twice will reset your view.<br /> <br /> -- Mouse Look --<br /> Mouse look will have you see from your avatar's point of view and change your controls a little. You will now strafe left and right and steer with the mouse. Hit M to enter mouse look and esc to get out of it.<br /> <br /> -- Communication --<br /> Make sure you know how to Instant Message people you can see, and people you can't see via your Search and Friends buttons. Also make sure you get an idea of how far you can be "heard" when you chat or shout. As you join groups, you will see that you can start chats with entire groups. Gestures in your inventory are another way to communicate or add to what you say.<br /> <br /> -- Interaction --<br /> Interacting with objects is a big part of Second Life. Have you tried sitting on poseballs? Playing a game? Buying and object? Make sure you know about the pie menu as well as when to right click or left click. If you have one mouse button, use CMD + click for right click.<br /> <br /> -- New Interactions --<br /> While most actions still are accessable via right click. Many can now happen with a left click. For example, if you see a chair icon when you hover over an object, touching (left-clicking) it will automatically seat you. Similar icons exist for buying, paying money to, and opening objects.<br /> <br /> -- Objects and Inventory --<br /> While not everyone builds in Second Life, it's a good idea to learn the basics of moving things in edit, attaching and detaching objects from your avatar, how to find things in your inventory, and how to "unpack" a box you may receive.<br /> <br /> -- Respect --<br /> There is no set of rules to define respect, except to treat others as you would like to be treated. The ability to do something does not imply permission. <br /> <br /> <br /> <br /> <br /> <br /> CONCEPTS OF THE MAIN LAND<br /> ==================<br /> <br /> -- Map and Teleporting --<br /> The map lets you see nearly the whole world at once if you zoom out. Each tiny square represents an area as big as help island. Each one is a "simulator" (sim). Second Life is at about 1600 sims as of January 2006. Some are connected so that you can walk and fly between them. Others are individual islands that can be reached only via teleport. Walking or even flying everywhere would take hours.<br /> <br /> Double click on an area to be transported there, you will either arrive there directly, or as close as possible and be given a red beacon to follow. When you want to bring someone to a location, you can offer them a teleport via their profile.<br /> <br /> -- Landmarks --<br /> Landmarks are the Second Life equivalent of a bookmark. They save a place that you or someone else has been. You can find them in your inventory. Double click them and you will get a teleport option as a pop up. Create your own by pulling down the WORLD menu and choosing "Create Landmark Here"<br /> <br /> -- Search --<br /> Find will let you look up events, people, products, and also let you teleport to the various areas you find.<br /> <br /> -- Friends --<br /> As you explore you may make many friends. When you offer friendship it is reciprocal and gives the ability to see each other on the map. You can also offer a calling card instead.<br /> <br /> -- Damage Enabled Areas --<br /> In certain areas you will see a heart and "100%" at the top of your screen. This means you can take damage. If your health reaches zero you get sent back to where you have set as your "home".<br /> <br /> WHERE TO GET MORE HELP<br /> ======================<br /> It's best to get help where it's already offered. Not everyone you meet in Second Life is experienced and knowledgeable in every area. Some people specialize. Others may be brand new, like yourself. If you missed Help Island or left too soon, a public version of Help Island exists. Pressing on the links below should give you a landmark into your inventory. Also listed are some other locations where people are happy to help you out.<br /> <br /> : Island with tutorials <br /> : Classrooms and lots of help to be found<br /> <br /> If you have an immediate issue, pull dodwn the "Help" menu at the top of your screen and choose "Help Request".</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Talk:LSL_Portal&diff=9536 Talk:LSL Portal 2007-02-11T02:17:08Z

<p>Blueman Steele: /* Syntax Highlighting */</p> <hr /> <div>{{LSL Header}}<br /> = Please do not copy content from LSLwiki =<br /> <br /> From [http://forums.secondlife.com/showpost.php?p=1392697&postcount=44 Rob Linden's post to the forum]:<br /> :Hi folks, sorry for dropping into this conversation late. I haven't read through everything here, but I'd like to present an alternative.<br /> <br /> :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".<br /> <br /> :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)<br /> <br /> ----<br /> <br /> OK, so let's talk about formatting rules for entries.<br /> <br /> (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)<br /> <br /> [[User:Talarus Luan|Talarus Luan]] 14:28, 24 January 2007 (PST)<br /> <br /> ----<br /> <br /> =Other Discussion=<br /> <br /> 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)<br /> <br /> ----<br /> <br /> Yeah i think so... (Unsigned by Dimentox Travanti}<br /> :Remember to sign your post with four tildes. [[User:Gigs Taggart|Gigs Taggart]] 14:26, 24 January 2007 (PST)<br /> <br /> <br /> 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].<br /> --[[User:Thraxis Epsilon|Thraxis Epsilon]] 15:00, 24 January 2007 (PST)<br /> <br /> == Regarding copying content from the existing Wiki ==<br /> <br /> 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?<br /> [[User:Talarus Luan|Talarus Luan]] 16:03, 24 January 2007 (PST)<br /> :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)<br /> <br /> == Syntax Highlighting ==<br /> <br /> Updated info on the syntax highlighting is available here [[http://rpgstats.com/wiki/index.php?title=GeSHiHiLight.php GeSHiHiLight]]<br /> --[[User:Thraxis Epsilon|Thraxis Epsilon]] 16:10, 24 January 2007 (PST)<br /> <br /> :Lets hope they include it soon ^^ [[User:Strife Onizuka|Strife Onizuka]] 21:21, 24 January 2007 (PST)<br /> :Is there anyone we can ask? [[User:Dimentox Travanti|Dimentox Travanti]] 10:50, 25 January 2007 (PST)<br /> :any news or update on this? [[User:Blueman Steele|Blueman Steele]] 6:12, 10 February 2007 (PST)<br /> <br /> == Let's refer to this simply as the "LSL portal" ==<br /> <br /> 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)<br /> :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)<br /> :: Simple, consistent messaging: I've gotten into the habit of using "LSL Portal" regularly myself.<br /> :: --[[User:Torley Linden|Torley Linden]] 10:40, 31 January 2007 (PST)<br /> <br /> == A way back... ==<br /> <br /> Every page should have a header that goes back to the portal index not the wiki index.<br /> if we could even geta link in the left hand would be great.<br /> <br /> [[User:Dimentox Travanti|Dimentox Travanti]] 10:47, 25 January 2007 (PST)<br /> <br /> == Transitions ==<br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Thanx to each and all of you building up this resource so far!<br /> <br /> --[[User:Torley Linden|Torley Linden]] 10:21, 26 January 2007 (PST)<br /> <br /> == LSL Header/Footer ==<br /> Below is the header/footer template: <nowiki>{{LSL Header}}</nowiki><br /> {{LSL Header}}<br /> 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)<br /> :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)<br /> <br /> == LSL wiki-namespace ==<br /> <br /> 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) <br /> :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)<br /> ::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)<br /> <br /> == LSL conformance test ==<br /> <br /> 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)<br /> <br /> == LSL Categories List ==<br /> 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)<br /> :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)<br /> :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)</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=9417 Getting started with LSL 2007-02-10T17:25:27Z

<p>Blueman Steele: /* What is LSL? */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''WHO THIS TUTORIAL IS FOR:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. Scripts in Second Life are a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL unique is its heavy emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life objects have "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life but rather predefined. They are either caused by objects and avatars interacting in the world, or they are created in a script. Events trigger event handlers (sometimes just called "events" as well). One called Touch_start(), will trigger the code in it when the object running the script is touched. So the minimum LSL program must have one state with one event in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose "create". (for one button macs use command+click)<br /> <br /> By default, you should see a "wand" icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter "edit" mode and an edit window will pop up.<br /> (Note: to place a script in an existing object, right click it and hit edit to open the edit window.)<br /> <br /> In the edit window you may see a button marked "more>>>" click it to reveal five tabs marked general, object, features, content, and texture. Click "content".<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press "new script" to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit "save" and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched."<br /> (make sure the "edit" building window is closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and reseting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car.... while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> <br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "state_entry" which is triggered by the state being entered, and "touch_start" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> <br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lower case L's. We've seen llSay() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracked closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> <br /> The instant you save your script, it enters default state, which in turn runs the "state_entry" event which in turn runs the function llSay() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "touch_start" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Lets look at a script with two states with two events in each.<br /> <br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction.<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> <br /> A simplification of this would be<br /> <br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> <br /> Note that after "default" all new states begin with the word "state". Also, while the object has a texture, the color will effect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "state_entry" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> [[LSL_llSay|llSay]](0, "turning on!");<br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> llSetColor(<1,1,1>, ALL_SIDES);<br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1's stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "touch_start" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> state off;<br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> llWhisper( ) is just like llSay( ) but only broadcasts at half the distance. You still must state what channel. So....<br /> <br /> llWhisper(0,"turning on!");<br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using llShout( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> llOwnerSay( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> llOwnerSay("turning on!");<br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via llSetText( ) like this.<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> What do the numbers mean? The <1,1,1> we've seen before. It represents the values for red, green, and blue. For now just know that <1,1,1>, means "white" and <0,0,0> means "black". Replace the llSay(0,"turning off!"); with...<br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=9415 Getting started with LSL 2007-02-10T17:20:46Z

<p>Blueman Steele: /* Getting started in LSL scripting in Second Life */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''WHO THIS TUTORIAL IS FOR:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and have general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. Scripts in Second Life are a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL unique is its heavy emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life objects have "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life but rather predefined in LSL. One called Touch_start(), will trigger the code in it when the object running the script is touched. So the minimum LSL program must have one state with one event in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose "create". (for one button macs use command+click)<br /> <br /> By default, you should see a "wand" icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter "edit" mode and an edit window will pop up.<br /> (Note: to place a script in an existing object, right click it and hit edit to open the edit window.)<br /> <br /> In the edit window you may see a button marked "more>>>" click it to reveal five tabs marked general, object, features, content, and texture. Click "content".<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press "new script" to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit "save" and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched."<br /> (make sure the "edit" building window is closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and reseting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car.... while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> <br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "state_entry" which is triggered by the state being entered, and "touch_start" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> <br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lower case L's. We've seen llSay() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracked closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> <br /> The instant you save your script, it enters default state, which in turn runs the "state_entry" event which in turn runs the function llSay() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "touch_start" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Lets look at a script with two states with two events in each.<br /> <br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction.<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> <br /> A simplification of this would be<br /> <br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> <br /> Note that after "default" all new states begin with the word "state". Also, while the object has a texture, the color will effect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "state_entry" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> [[LSL_llSay|llSay]](0, "turning on!");<br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> llSetColor(<1,1,1>, ALL_SIDES);<br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1's stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "touch_start" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> state off;<br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> llWhisper( ) is just like llSay( ) but only broadcasts at half the distance. You still must state what channel. So....<br /> <br /> llWhisper(0,"turning on!");<br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using llShout( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> llOwnerSay( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> llOwnerSay("turning on!");<br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via llSetText( ) like this.<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> What do the numbers mean? The <1,1,1> we've seen before. It represents the values for red, green, and blue. For now just know that <1,1,1>, means "white" and <0,0,0> means "black". Replace the llSay(0,"turning off!"); with...<br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=9413 Getting started with LSL 2007-02-10T17:18:11Z

<p>Blueman Steele: I'll just rephrase that. :-)</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''WHO THIS TUTORIAL IS FOR:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. Scripts in Second Life are a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL unique is its heavy emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life objects have "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life but rather predefined in LSL. One called Touch_start(), will trigger the code in it when the object running the script is touched. So the minimum LSL program must have one state with one event in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose "create". (for one button macs use command+click)<br /> <br /> By default, you should see a "wand" icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter "edit" mode and an edit window will pop up.<br /> (Note: to place a script in an existing object, right click it and hit edit to open the edit window.)<br /> <br /> In the edit window you may see a button marked "more>>>" click it to reveal five tabs marked general, object, features, content, and texture. Click "content".<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press "new script" to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit "save" and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched."<br /> (make sure the "edit" building window is closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and reseting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car.... while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> <br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "state_entry" which is triggered by the state being entered, and "touch_start" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> <br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lower case L's. We've seen llSay() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracked closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> <br /> The instant you save your script, it enters default state, which in turn runs the "state_entry" event which in turn runs the function llSay() which makes the object talk.<br /> <br /> After this, the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "touch_start" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Lets look at a script with two states with two events in each.<br /> <br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction.<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> <br /> A simplification of this would be<br /> <br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> <br /> Note that after "default" all new states begin with the word "state". Also, while the object has a texture, the color will effect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "state_entry" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> [[LSL_llSay|llSay]](0, "turning on!");<br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> llSetColor(<1,1,1>, ALL_SIDES);<br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1's stand for the Red, Green, and Blue values of the tint.<br /> <br /> At this point the event is finished with the two lines of commands. Then the script waits idle in the default state for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "touch_start" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> state off;<br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> llWhisper( ) is just like llSay( ) but only broadcasts at half the distance. You still must state what channel. So....<br /> <br /> llWhisper(0,"turning on!");<br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using llShout( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> llOwnerSay( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> llOwnerSay("turning on!");<br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via llSetText( ) like this.<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> What do the numbers mean? The <1,1,1> we've seen before. It represents the values for red, green, and blue. For now just know that <1,1,1>, means "white" and <0,0,0> means "black". Replace the llSay(0,"turning off!"); with...<br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Getting_started_with_LSL&diff=9411 Getting started with LSL 2007-02-10T17:13:16Z

<p>Blueman Steele: period goes after quotes in this case.</p> <hr /> <div>{{LSL Header|{{LSLGC|Tutorials}}}}<br /> <br /> == Getting started in LSL scripting in Second Life ==<br /> <br /> LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.<br /> <br /> '''WHO THIS TUTORIAL IS FOR:'''<br /> <br /> This tutorial is intended for those who have never programmed before, Second Life or elsewhere. However, this tutorial will make little sense outside of Second Life. LSL is very specific to Second Life.<br /> <br /> You will begin by running the standard "hello world" script and eventually move towards making your own. You will need to be familiar with the basic principles of Second Life and general building skills before you can make use of everything in this tutorial.<br /> <br /> == What is LSL? ==<br /> <br /> LSL is the Linden Scripting Language. This is the language all scripts in Second Life are written in. Its structure is based on Java and C. Scripts in Second Life are a set of instructions that can be placed inside any primitive object in the world, but not inside an avatar. Avatars, however, can wear scripted objects. LSL scripts are written with a built-in editor/compiler which we will access in "Running Your First Script".<br /> <br /> One thing that makes LSL unique is its heavy emphasis on "States" and "Events". A door can be "open" or "closed" and a light can be "on" or "off". A person can be "hyper", "calm", or "bored". Many real life objects have "states" and the same can be true for LSL programs. Minimally a script will have one state, the default state.<br /> <br /> An event can be thought of as a "Trigger". Events are not user defined in Second Life but rather predefined in LSL. One called Touch_start(), will trigger the code in it when the object running the script is touched. So the minimum LSL program must have one state with one event in it. Here is a look at a minimal program written in LSL that can loosely be translated as...."When I am in the default state, and I am touched, say "Hello World" on channel zero".<br /> <br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> <br /> (note: all scripts will be placed in LSL tags when it goes active)<br /> <br /> <lsl><br /> default<br /> {<br /> touch_start(integer total_number)<br /> {<br /> llSay(0,"Hello World");<br /> }<br /> }<br /> </lsl><br /> <br /> '''WHAT CAN I DO WITH SCRIPTS?'''<br /> <br /> Scripts can make an object move, listen, talk, operate as a vehicle or weapon, change color, size or shape. A script can make an object listen to your words as well as talk back to you, scripts even let objects talk to each other.<br /> <br /> The most basic object in Second Life is the "Prim" or primitive, the basic building block of all objects you can build in Second Life. When several prims are linked, they can each contain a script which speaks to the rest of the object via Link Messages. These are faster and more private than having objects "chat" or email each other. These are beyond the scope of this tutorial and we will instead focus on single scripts in a single prim.<br /> <br /> Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.<br /> <br /> If you've built in Second Life, everything you can define in the edit window can be defined in a script. All interaction you see between objects or between avatars and objects is via scripts.<br /> <br /> Learning more about the world and building model is vital to some aspects of scripting, thus I'd recommend a good foundation in building as you learn to script.<br /> <br /> == Running Your First Script ==<br /> <br /> Traditionally one starts by writing the smallest program possible to print "hello world". Since LSL only runs inside objects, you must know how to create an object and put a script inside it.<br /> <br /> You must be on land which allows building. Either your own land, or land where you have permission to build on such as a sandbox. Right click on the ground and choose "create". (for one button macs use command+click)<br /> <br /> By default, you should see a "wand" icon with which you can click and create a cube on the ground.<br /> <br /> You will automatically enter "edit" mode and an edit window will pop up.<br /> (Note: to place a script in an existing object, right click it and hit edit to open the edit window.)<br /> <br /> In the edit window you may see a button marked "more>>>" click it to reveal five tabs marked general, object, features, content, and texture. Click "content".<br /> <br /> This window shows the contents of an object which can hold scripts, notecards, even other objects. Press "new script" to add a new script.<br /> <br /> This will open the LSL editor with a default script. This editor will color code your syntax and provide some info about keywords when you hold your mouse over them. It will also do basic syntax checking.<br /> <br /> Before explaining the code, lets run it. Hit "save" and close your edit window (not the LSL editor window).<br /> <br /> You should see the words "Hello Avatar" from "object"<br /> <br /> If you touch the object, it will say "Touched."<br /> (make sure the "edit" building window is closed for touching to work.<br /> <br /> Congratulations! You have compiled and run your first LSL script!<br /> <br /> == Wash / Rinse / Repeat ==<br /> <br /> We now have a running script, however most scripts you make won't run the first time you run them. It will take many tries as you correct errors and make improvements. When you hit "save" on a script, the LSL editor "compiles" the code to something LSL can understand. It will stop however if it finds an error.<br /> <br /> Brackets, parenthesis, and semicolons must all be perfectly in place before a script will run. If you are new to programing this can be one of the most infuriating steps and lead you to screaming DWIM (Do what I mean!) Part of becoming a programmer in ANY language is learning how to precisely define steps and correctly type them into the language you are working in. Thus you will find yourself writing, running, then RE-writing your code several times.<br /> <br /> The script you made runs the instant you hit save. If you take it into inventory, it will "suspend" what it was doing but go right back to it when rezzed again. (If you are not familiar with "taking" and "rezzing" an object you may need to revisit your building skills).<br /> <br /> Each time you re-write your code you'll want to reset the script.<br /> <br /> Try resetting the script in the following ways.<br /> <br /> 1. Press Reset in the script window.<br /> 2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION<br /> <br /> Also try stopping and starting the script from running via checking and unchecking the "running" button, or the TOOLS>SET SCRIPTS TO NOT RUNNING IN SELECTION and then TOOLS>SET SCRIPTS TO RUNNING IN SELECTION.<br /> <br /> Once you get comfortable with stopping, starting, and reseting a script, try changing the words "Hello Avatar" and see what else you can make it say.... for goodness sakes keep it PG.<br /> <br /> '''WHY STOP AND START?'''<br /> <br /> Scripting in Second Life can be a little bit like fixing your car.... while going 60mph down the freeway. Thus you need ways to stop the programs for they may affect others.<br /> <br /> Objects can hold more than one script and they will all run at once. This can be used in the following manner. Say you write a script that makes a prim change color every few seconds. You also write one to make it follow you. Put them both in one object and it will follow you while changing colors!<br /> <br /> For simplicity's sake, the following examples will all be used individually so be sure not to put two or more into the same object.<br /> <br /> == A Closer Look ==<br /> <br /> Lets take a look at the default code.<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.<br /> <br /> Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.<br /> <br /> // This is a comment<br /> <br /> '''STATES'''<br /> <br /> A "State" in LSL is a section that is running, and waiting for events. Only one state can be active at any one time per script. Every script must have a default state with at least one event in it. Except for the default state, each state is defined by the word STATE followed by the name of the state. The contents of the state are enclosed in two curly brackets.<br /> <br /> default<br /> {<br /> // contents of state go here<br /> }<br /> <br /> state playing<br /> {<br /> // this is a state called "playing"<br /> }<br /> <br /> <br /> '''EVENTS'''<br /> <br /> Events are inside of states. By "inside" I mean it is between the open and closed curly brackets that represent the body of the state. When that state is active, those events wait to be triggered and run the code inside them. We've seen "state_entry" which is triggered by the state being entered, and "touch_start" which is triggered when you, or anyone, touches an object.<br /> <br /> Lets take a look at the default code.<br /> <br /> // Code start<br /> default<br /> {<br /> touch_start(integer total_number)<br /> // this is an event<br /> {<br /> // this is the content of the event<br /> }<br /> // end of event<br /> }<br /> // end of state<br /> <br /> <br /> '''FUNCTIONS'''<br /> <br /> Functions lay inside of events and are either defined by you or built-in. Those built in to LSL all start with two lower case L's. We've seen llSay() so far. Functions take "arguments" or values in the parentheses that follow it. If you hover over the function in the editor, a popup will show that tell you what the function is expecting. In the case of llSay it expects a number and a string. We send it the number zero and the string "Hello, Avatar!" separated by commas. The function is "expecting" a number and strings and won't take anything else.<br /> <br /> == Putting it all together ==<br /> <br /> Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.<br /> <br /> // All Scripts need a Default State<br /> default<br /> // this open curly bracket denotes the start of the state<br /> {<br /> state_entry() // an event<br /> // another curly bracket starts the body of the event<br /> {<br /> llSay(0, "Hello, Avatar!"); // a function inside the event<br /> }<br /> // closed curly bracked closes the state_entry event<br /> <br /> touch_start(integer total_number) // another event inside default state<br /> {<br /> llSay(0, "Touched."); // a function between the brackets of the touch_start body<br /> }<br /> // end of touch start<br /> }<br /> // Code end<br /> <br /> The instant you save your script, it enters default state, which in turn runs the "state_entry" event which in turn runs the function llSay() which makes the object talk.<br /> <br /> After this the program waits idle in the default state until a new event is called.<br /> <br /> Touching the box triggers the event "touch_start" which also makes the object speak.<br /> <br /> == Introducing States and Events ==<br /> <br /> LSL scripts will not run beginning to end. Instead, they will look for a default state and wait for an event. Within those events, there can be a call to go to a new state.<br /> <br /> All programs must contain the default state, inside of which must be one event. Events are triggered either by actions happening to or around the object the script resides in, or are triggered from the script itself.<br /> <br /> Lets look at a script with two states with two events in each.<br /> <br /> default //default state is mandatory<br /> {<br /> state_entry() // runs each time the state is entered<br /> {<br /> llSay(0, "turning on!"); //object speaks!<br /> llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright<br /> // note the semicolons at the end of each instruction.<br /> }<br /> <br /> touch_start(integer total_number) // another event with only one function inside<br /> {<br /> state off; // sets the script to a new "state" and starts running "state off"<br /> }<br /> } // this curly bracket ends the body of the default state.<br /> <br /> state off // a second state besides "default"<br /> {<br /> state_entry() // this is run as soon as the state is entered<br /> {<br /> llSay(0, "turning off!");<br /> llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> state default;<br /> }<br /> }<br /> <br /> A simplification of this would be<br /> <br /> default<br /> {<br /> //set color to light and, if touched, enter the "off" state.<br /> }<br /> <br /> state off<br /> {<br /> //set color to dark and, if touched, enter the "default" state.<br /> }<br /> <br /> Note that after "default" all new states begin with the word "state". Also, while the object has a texture, the color will effect the "tint" more than the true color.<br /> <br /> == A closer look ==<br /> <br /> Let's examine the default state.<br /> <br /> First we see the "state_entry" event, which gets triggered each time the default state is entered.<br /> <br /> '''SPEAK TO ME!'''<br /> <br /> The first line in the event state_entry is...<br /> <br /> [[LSL_llSay|llSay]](0, "turning on!");<br /> <br /> This makes the object speak "turning on!" on channel zero. What is channel zero? It is the same channel you see all public chat on.<br /> <br /> A semicolon ends the line and yet another instruction follows.<br /> <br /> llSetColor(<1,1,1>, ALL_SIDES);<br /> <br /> This turns the prim to its brightest tint. If you take the texture off the prim, you'd see it as bright white; with a texture, it looks "normal." The three 1's stand for the Red, Green, and Blue values of the tint.<br /> <br /> After that the event is done with the two lines of commands, and the script waits idle in default waiting for more events to happen.<br /> <br /> '''TOUCHED BY AN AVATAR'''<br /> <br /> While idle in the default state a touch will trigger the "touch_start" event.<br /> <br /> Inside of the "touch_start" event is only one command:<br /> <br /> state off;<br /> <br /> This is a command to move immediately to a new state named "off".<br /> <br /> This state is defined after the default state and nearly mirrors the default state, except that it turns the prim dark and, when touched, will put the script back into default mode, thus creating a loop.<br /> <br /> # Enters default state<br /> # Runs code in "state entry"<br /> # Waits to be touched<br /> # When touched enters "state off"<br /> # Enters "state off"<br /> # Runs code in "state entry" (note in the "off" state's body)<br /> # Waits to be touched<br /> # When touched enters "default" state<br /> <br /> Then the whole thing starts over.<br /> <br /> == A final word on words ==<br /> <br /> Making your object speak is a great way to know what a script is doing, but everyone can hear it for 30m all around you. As you get into more complex scripts this can get pretty noisy! Three alternative ways to see what is going on exist.<br /> <br /> '''SHHHH WHISPER'''<br /> <br /> llWhisper( ) is just like llSay( ) but only broadcasts at half the distance. You still must state what channel. So....<br /> <br /> llWhisper(0,"turning on!");<br /> <br /> ...might work a bit to save the sanity of your neighbors.<br /> <br /> Using llShout( ) doubles the distance heard, but can cut the amount of friends you have in half. <br /> <br /> llOwnerSay( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!<br /> <br /> llOwnerSay("turning on!");<br /> <br /> <br /> <br /> '''THE SOUND OF SILENCE'''<br /> <br /> You can make a totally silent message via llSetText( ) like this.<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> What do the numbers mean? The <1,1,1> we've seen before. It represents the values for red, green, and blue. For now just know that <1,1,1>, means "white" and <0,0,0> means "black". Replace the llSay(0,"turning off!"); with...<br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).<br /> <br /> {{LSLC|Tutorials}}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8978 Inworld Locations for Volunteers 2007-02-09T01:16:06Z

<p>Blueman Steele: </p> <hr /> <div>== InfoHubs ==<br /> * {{SLurl/Infohub|Ambat|97|212|59}}<br /> * {{SLurl/Infohub|Anzere|97|212|59}}<br /> * {{SLurl/Infohub|Bear|26|181|110|Bear Dream Lodge (Bear Infohub)}}<br /> * {{SLurl/Infohub|Braunworth|92|155|179}}<br /> * {{SLurl/Infohub|Calleta|128|206|26|Calleta Hobo Railroad (Calleta Infohub)}}<br /> * {{SLurl/Infohub|Clementina|184|123|61|Governor Lindens Mansion (Clementina Infohub)}}<br /> * {{SLurl/Infohub|Hyles|38|30|22|Hyles Swamp (Hyles Infohub)}}<br /> * {{SLurl/Infohub|Iris|202|125|29|Temple of Iris (Iris Infohub)}}<br /> * {{SLurl/Infohub|Isabel|44|107|57}}<br /> * {{SLurl/Infohub|Mahulu|58|193|85}}<br /> * {{SLurl/Infohub|Mauve|122|184|42}}<br /> * {{SLurl/Infohub|Miramare|3|24|25}}<br /> * {{SLurl/Infohub|Ross|34|224|57}}<br /> * {{SLurl/Infohub|Violet|175|95|26}}<br /> * {{SLurl/Infohub|Wengen|8|231|85}}<br /> <br /> == Welcome Areas ==<br /> * {{SLurl/WA|Ahern|6|6|40}}<br /> * {{SLurl/WA|Hangeul|1|4|108}}<br /> * {{SLurl/WA|Plum|73|250|47}}<br /> * {{SLurl/WA|Violet|181|94|27|Violet Welcome Area (Temporary)}}<br /> * {{SLurl/WA|Waterhead|41|78|25}}<br /> <br /> == Linden Meeting Spaces ==<br /> * {{Slurl/simple|Pooley|247|5|39|Pooley Stage}}<br /> * {{SLurl/simple|Orientation Island Public|127|129|32|Orientation Island (Public)}}<br /> <br /> <br /> == Volunteer Support ==<br /> * {{SLurl/simple|Tenera|208|83|70|Volunteer HQ}}<br /> * {{SLurl/simple|Portage|24|178|85|Second Life Helper's Lyceum}}<br /> * {{SLurl/simple|Pro Racer|144|127|36|Teh Mental House}}: ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * {{SLurl/HI|Public}}<br /> * {{SLurl/HI}}<br /> * {{SLurl/HI|2}}<br /> * {{SLurl/HI|3}}<br /> * {{SLurl/HI|4}}<br /> * {{SLurl/HI|5}}<br /> * {{SLurl/HI|6}}<br /> * {{SLurl/HI|7}}<br /> * {{SLurl/HI|8}}<br /> * {{SLurl/HI|9}}<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> ==== Resident owned ====<br /> * {{SLurl/simple|Gaia|147|124|28|French school - Accueil francophone}}: a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by [[User:kerunix Flan|kerunix Flan]])''<br /> * {{SLurl/simple|area 51|138|125|27|Area 51}}: The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> <br /> ==== See Also ====<br /> These sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> * {{SLurl/simple|Europe|217|155|75|Europe}}<br /> * {{SLurl/simple|ile de france|128|104|75|Ile de France}}<br /> * {{SLurl/simple|Solaria|123|115|75|Loisir Area}}<br /> * {{SLurl/simple|Trantor|184|24|75|La Playa Del Noob}} (with a linden gallery)<br /> * {{SLurl/simple|Terminus|149|139|75|SL Ecosystem Working Group}}(international ALife project hosted in french sim)<br /> * {{SLurl/simple|Wild Vertigo|50|42|75|Wild Vertigo}}<br /> <br /> <br /> === German ===<br /> <br /> ==== Resident owned ====<br /> * {{SLurl/simple|Pixel Expo II|182|112|28|Deutsches Tutorium}}<br /> * {{SLurl/simple|Samoa|109|158|557|German Tutorial}}<br /> * {{SLurl/simple|Die Insel|135|142|22|German Newbie Center}}<br /> <br /> === Korean ===<br /> ==== Linden Lab owned ====<br /> * {{SLurl/Infohub|Korea1|226|23|25}}<br /> * {{SLurl/Infohub|Korea2|1|24|25}}<br /> * {{SLurl/Infohub|Korea3|239|228|25}}<br /> * {{SLurl/Infohub|Korea4|13|228|25}}<br /> <br /> === Spanish ===<br /> ==== Resident owned ====<br /> * {{SLurl/simple|Quantum Fields|84|167|56|Centro de Ayuda en Castellano (Quantum Fields)}}: Center of welcome and orientation for all the ones that speak Spanish. Gifts, help, notecards.. a place where newbies can find friends and clear doubts. <br /> * {{SLurl/simple|Nangrim|185|246|75|SecondLifeSpain.com (Nangrim)}}: Headquarters of the community of Spanish-speaking residents [http://secondlifespain.com secondlifespain.com]. Newbies can find help, classes, and translated notecards.<br /> <br /> ===== See Also =====<br /> * {{SLurl/simple|La Isla|122|129|28|La Isla}}: Great place to take Spanish speakers. Active community and Spanish speaking DJ's.<br /> * {{SLurl/simple|Cycnia|168|175|30|Mirando al Mar (Cycnia)}}: A place for make new friends, speak in spanish and have fun. Free help, spanish notecards..etc.<br /> * {{SLurl/simple|Ibiza The Island|195|46|21|Ibiza The Island (Spain)}}<br /> <br /> ===== Spanish speaking Groups =====<br /> <br /> There are many groups where people that speak spanish can find help and make friends, some of the most important are: '''Segunda Vida''' (founded by long term Resident, Greeter and Mentor [[User:Blueman Steele|Blueman Steele]]), '''Spanish From Spain=SpaniardS in SL''' and '''secondlifespain.com'''.<br /> <br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content.<br /> <br /> There is an island for Brazilian users run by residents called, very appropriately, {{SLurl/simple|Brasil|128|128|0|Brasil}}. Another place is listed as having information for Brazilian users: {{SLurl/simple|Delphi|37|84|26|PSDB - Diretorio SL}}. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 on www.forumpt.com].<br /> <br /> == Note: Some SLURS not working ==<br /> <br /> ''SLURLS not working on two name sims? Some of these links work when using the templates, others do not. The only pattern I can see is that the two name Sims seem to break. The space is parsed as a "+". Is this correct?''<br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_Tutorial&diff=8666 LSL Tutorial 2007-02-07T20:21:04Z

<p>Blueman Steele: /* External Tutorials */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Beginner Tutorials ==<br /> <br /> '''[[GettingStartedInLSL|Getting Started In LSL]]:''' Tutorial for absolute beginners. Basic SL inventory and navigation required.<br /> <br /> == In-World Tutorials ==<br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/206/40 Free interactive in-world Linden Script Tutorial]:''' Bromley College have developed a free interactive scripting tutorial exhibition in-world.<br /> <br /> <br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/11/79/21/?x=300&y=300&img=http%3A//cd.bromley.ac.uk/bteccourses/sl/images/shimmer_island.jpg&title=Learning%20in%20Virtual%20Reality&msg=Here%20at%20Shimmer%20island%2C%20I%20shall%20be%20exploring%20the%20potential%20of%20Second%20Life%20in%20support%20of%20my%20current%20trials%20with%20the%20Moodle%20vle%20for%20Virtual%20Learning.%20So%20please%20feel%20free%20to%20drop%20in%20for%20a%20chat%20with%20us%20to%20see%20how%20things%20are%20going.%20Regards%20Skipper%20Abel Bromley College in-world Virtual Learning trials]:''' Please feel free to come over and look around<br /> <br /> == External Tutorials ==<br /> <br /> '''[http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial]:''' Video tutorial for building and scripting a clock.<br /> <br /> '''[http://www.kan-ed.org/second-life/using-LSL.html Using the Linden Script Language]:''' A short tutorial from Kan-ed.<br /> <br /> '''[http://johannahyacinth.blogspot.com/2006/12/scripting-basics-part-1.html Scripting Basics (Part 1)]:''' Scripting basics from Johanna Hyacinth. Also try [http://johannahyacinth.blogspot.com/2006/12/scripting-basics-part-2_18.html part2] and [http://johannahyacinth.blogspot.com/2006/11/lsl-magic-barrier.html part3].</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_Tutorial&diff=8664 LSL Tutorial 2007-02-07T20:15:48Z

<p>Blueman Steele: /* External Tutorials */</p> <hr /> <div>{{LSL Header}}<br /> <br /> == Beginner Tutorials ==<br /> <br /> '''[[GettingStartedInLSL|Getting Started In LSL]]:''' Tutorial for absolute beginners. Basic SL inventory and navigation required.<br /> <br /> == In-World Tutorials ==<br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/206/40 Free interactive in-world Linden Script Tutorial]:''' Bromley College have developed a free interactive scripting tutorial exhibition in-world.<br /> <br /> <br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/11/79/21/?x=300&y=300&img=http%3A//cd.bromley.ac.uk/bteccourses/sl/images/shimmer_island.jpg&title=Learning%20in%20Virtual%20Reality&msg=Here%20at%20Shimmer%20island%2C%20I%20shall%20be%20exploring%20the%20potential%20of%20Second%20Life%20in%20support%20of%20my%20current%20trials%20with%20the%20Moodle%20vle%20for%20Virtual%20Learning.%20So%20please%20feel%20free%20to%20drop%20in%20for%20a%20chat%20with%20us%20to%20see%20how%20things%20are%20going.%20Regards%20Skipper%20Abel Bromley College in-world Virtual Learning trials]:''' Please feel free to come over and look around<br /> <br /> == External Tutorials ==<br /> <br /> '''[http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial]:''' Video tutorial for building and scripting a clock.<br /> <br /> '''[http://www.kan-ed.org/second-life/using-LSL.html Using the Linden Script Language]:''' A short tutorial from Kan-ed.</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_Tutorial&diff=8663 LSL Tutorial 2007-02-07T20:10:39Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL Header}}<br /> <br /> == Beginner Tutorials ==<br /> <br /> '''[[GettingStartedInLSL|Getting Started In LSL]]:''' Tutorial for absolute beginners. Basic SL inventory and navigation required.<br /> <br /> == In-World Tutorials ==<br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/206/40 Free interactive in-world Linden Script Tutorial]:''' Bromley College have developed a free interactive scripting tutorial exhibition in-world.<br /> <br /> <br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/11/79/21/?x=300&y=300&img=http%3A//cd.bromley.ac.uk/bteccourses/sl/images/shimmer_island.jpg&title=Learning%20in%20Virtual%20Reality&msg=Here%20at%20Shimmer%20island%2C%20I%20shall%20be%20exploring%20the%20potential%20of%20Second%20Life%20in%20support%20of%20my%20current%20trials%20with%20the%20Moodle%20vle%20for%20Virtual%20Learning.%20So%20please%20feel%20free%20to%20drop%20in%20for%20a%20chat%20with%20us%20to%20see%20how%20things%20are%20going.%20Regards%20Skipper%20Abel Bromley College in-world Virtual Learning trials]:''' Please feel free to come over and look around<br /> <br /> == External Tutorials ==<br /> <br /> '''[http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial]:''' Video tutorial for building and scripting a clock.</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8629 Inworld Locations for Volunteers 2007-02-07T06:10:21Z

<p>Blueman Steele: /* Spanish */</p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> === German ===<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> === Korean ===<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> === Spanish ===<br /> <br /> * [http://slurl.com/secondlife/La%20Isla/122/129/28/?title=La%20Isla La Isla] : Great place to take Spanish speakers. Active community and Spanish speaking DJ's.<br /> * [http://slurl.com/secondlife/Ibiza%20The%20Island/195/46/21/?title=Ibiza%20The%20Island%20-%20Spain Ibiza The Island (Spain)]:<br /> <br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content. There is an island for Brazilian users run by residents called, very appropriately, [http://slurl.com/secondlife/Brasil/128/128/0/?msg=Brasil Brasil]. Another place is listed as having information for Brazilian users: [http://slurl.com/secondlife/Delphi/37/84/26/?msg=PSDB%20-%20Diretorio%20SL PSDB - Diretorio SL]. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 here].<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8628 Inworld Locations for Volunteers 2007-02-07T06:07:37Z

<p>Blueman Steele: /* Spanish */</p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> === German ===<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> === Korean ===<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> === Spanish ===<br /> <br /> * [http://slurl.com/secondlife/La%20Isla/122/129/28/?title=La%20Isla La Isla]<br /> * [http://slurl.com/secondlife/Ibiza%20The%20Island/195/46/21/?title=Ibiza%20The%20Island%20-%20Spain Ibiza The Island (Spain)]<br /> <br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content. There is an island for Brazilian users run by residents called, very appropriately, [http://slurl.com/secondlife/Brasil/128/128/0/?msg=Brasil Brasil]. Another place is listed as having information for Brazilian users: [http://slurl.com/secondlife/Delphi/37/84/26/?msg=PSDB%20-%20Diretorio%20SL PSDB - Diretorio SL]. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 here].<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8627 Inworld Locations for Volunteers 2007-02-07T06:05:51Z

<p>Blueman Steele: </p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> === German ===<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> === Korean ===<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> === Spanish ===<br /> <br /> * {{SLurl<br /> |region=La Isla<br /> |x=122<br /> |y=129<br /> |z=28<br /> |title=~:: La Isla ::~<br /> |}}<br /> <br /> * [http://slurl.com/secondlife/Ibiza%20The%20Island/195/46/21/?title=Ibiza%20The%20Island%20-%20Spain Ibiza The Island (Spain)]<br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content. There is an island for Brazilian users run by residents called, very appropriately, [http://slurl.com/secondlife/Brasil/128/128/0/?msg=Brasil Brasil]. Another place is listed as having information for Brazilian users: [http://slurl.com/secondlife/Delphi/37/84/26/?msg=PSDB%20-%20Diretorio%20SL PSDB - Diretorio SL]. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 here].<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8626 Inworld Locations for Volunteers 2007-02-07T05:57:39Z

<p>Blueman Steele: </p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> === German ===<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> === Korean ===<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> === Spanish ===<br /> <br /> * {{SLurl<br /> |region=La Isla<br /> |x=122<br /> |y=129<br /> |z=28<br /> |title=~:: La Isla ::~<br /> |}}<br /> <br /> * {{SLurl<br /> |region=Ibiza The Island<br /> |x=195<br /> |y=46<br /> |z=21<br /> |title=Ibiza The Island (Spain)<br /> |}}<br /> <br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content. There is an island for Brazilian users run by residents called, very appropriately, [http://slurl.com/secondlife/Brasil/128/128/0/?msg=Brasil Brasil]. Another place is listed as having information for Brazilian users: [http://slurl.com/secondlife/Delphi/37/84/26/?msg=PSDB%20-%20Diretorio%20SL PSDB - Diretorio SL]. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 here].<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8625 Inworld Locations for Volunteers 2007-02-07T05:50:18Z

<p>Blueman Steele: /* International Areas */</p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> === French ===<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> === German ===<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> '''Korean'''<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> === Spanish ===<br /> <br /> * {{SLurl<br /> |region=La Isla<br /> |x=122<br /> |y=129<br /> |z=28<br /> |title=~:: La Isla ::~<br /> |}}<br /> <br /> === Portuguese ===<br /> <br /> There are no "permanent" help structures for either Brazilian or Portuguese users, but you can join their respective major groups for more help: "Brasileiros no SL" (for Brazil) and "Tugas no SL" (for Portugal). People there will usually point new users to the most recently built areas with Portuguese content. There is an island for Brazilian users run by residents called, very appropriately, [http://slurl.com/secondlife/Brasil/128/128/0/?msg=Brasil Brasil]. Another place is listed as having information for Brazilian users: [http://slurl.com/secondlife/Delphi/37/84/26/?msg=PSDB%20-%20Diretorio%20SL PSDB - Diretorio SL]. A low-traffic Portuguese forum is available [http://www.forumpt.com/2/modules/newbb/viewforum.php?forum=4 here].<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=Inworld_Locations_for_Volunteers&diff=8618 Inworld Locations for Volunteers 2007-02-07T02:37:35Z

<p>Blueman Steele: </p> <hr /> <div>== InfoHubs ==<br /> * [http://slurl.com/secondlife/Ambat/97/212/59/?msg=Ambat%20Infohub Ambat Infohub]<br /> * [http://slurl.com/secondlife/Anzere/82/56/124/?msg=Anzere%20Infohub Anzere Infohub] <br /> * [http://slurl.com/secondlife/Bear/26/181/110/?msg=Bear%20Dream%20Lodge%20Infohub Bear Infohub]<br /> * [http://slurl.com/secondlife/Braunworth/92/155/179/?msg=Braunworth%20Infohub Braunworth Infohub] <br /> * [http://slurl.com/secondlife/Calleta/128/206/26/?msg=Calleta%27s%20Hobo%20Railroad%20Infohub Calleta Infohub]<br /> * [http://slurl.com/secondlife/Clementina/184/123/61/?msg=Governor%20Lindens%20Mansion Clementina Infohub] <br /> * [http://slurl.com/secondlife/Hyles/38/30/22/?msg=Hyles%20Swamp%20Infohub Hyles Infohub]<br /> * [http://slurl.com/secondlife/Iris/202/125/29/?title=Iris_Infohub-Temple_of_Iris Iris Infohub ]<br /> * [http://slurl.com/secondlife/Isabel/44/107/57/?msg=Isabel%20Infohub Isabel Infohub] <br /> * [http://slurl.com/secondlife/Mahulu/58/193/85/?msg=Mahulu%20Infohub Mahulu Infohub] <br /> * [http://slurl.com/secondlife/Mauve/233/184/42/?msg=Mauve%20Infohub Mauve Infohub]<br /> * [http://slurl.com/secondlife/Miramare/3/24/25/?msg=Miramare%20Infohub Miramare Infohub] <br /> * [http://slurl.com/secondlife/Ross/34/224/57/?msg=Ross%20Infohub Ross Infohub]<br /> * [http://slurl.com/secondlife/Violet/175/95/26/?msg=Violet%20Infohub Violet Infohub]<br /> * [http://slurl.com/secondlife/Wengen/8/231/85/?msg=Chalet%20Linden Wengen Infohub]<br /> <br /> <br /> == International Areas ==<br /> <br /> '''French'''<br /> * [http://slurl.com/secondlife/Gaia/147/124/28 French school - Accueil francophone] : a full sim with dedicated french helper, classes, and translated notecard. ''(yet another non-profit sim hosted and paid by "kerunix Flan")''<br /> * [http://slurl.com/secondlife/area%2051/138/125/27 Area 51] : The main french sim. Usually full and laggy, but with usefull ressources, classes and sandbox. (it's just next to the French School)<br /> * See also (still french) : [http://slurl.com/secondlife/ile%20de%20france/128/104/75 Ile de France] , [http://slurl.com/secondlife/Wild%20Vertigo/50/42/75 Wild Vertigo] , [http://slurl.com/secondlife/Europe/217/155/75 Europe] , [http://slurl.com/secondlife/Trantor/184/24/75 La Playa Del Noob](with a linden gallery) , [http://slurl.com/secondlife/Solaria/123/115/75 Loisir Area], [http://slurl.com/secondlife/Terminus/149/139/75 SL Ecosystem Working Group] (international ALife project hosted in french sim) , and Tohama, Nebuleuse, Croix du sud, Aurore. Those sim are not dedicated to SL Education, but you'll usually find french helper. Usefull groups dedicated to French support : "cooperation francaise" (over 1000 members).<br /> <br /> <br /> <br /> '''German'''<br /> <br /> * {{SLurl<br /> |region=Pixel Expo II<br /> |x=182<br /> |y=112<br /> |z=28<br /> |title=Deutsches Tutorium<br /> |}}<br /> * {{SLurl<br /> |region=Samoa<br /> |x=109<br /> |y=158<br /> |z=557<br /> |title=German Tutorial<br /> |}}<br /> * {{SLurl<br /> |region=Die Insel<br /> |x=135<br /> |y=142<br /> |z=22<br /> |title=German Newbie Center<br /> |}}<br /> <br /> '''Korean'''<br /> * [http://slurl.com/secondlife/Korea1/226/23/25/?msg=Korea1%20Infohub Korea1 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/1/24/25/?msg=Korea2%20Infohub Korea2 Infohub] <br /> * [http://slurl.com/secondlife/Korea2/239/228/25/?msg=Korea3%20Infohub Korea3 Infohub] <br /> * [http://slurl.com/secondlife/Korea4/13/228/25/?msg=Korea4%20Infohub Korea4 Infohub]<br /> <br /> '''Spanish'''<br /> <br /> == Welcome Areas ==<br /> * [http://slurl.com/secondlife/Waterhead/6/6/40/?msg=Ahern%20Welcome%20Area Ahern Welcome Area]<br /> * [http://slurl.com/secondlife/Waterhead/41/78/25/?msg=Waterhead%20Welcome%20Area Waterhead Welcome Area]<br /> <br /> <br /> == Linden Meeting Spaces ==<br /> * [http://slurl.com/secondlife/Pooley/247/5/39/?msg=Pooley%20Stage Pooley Stage]<br /> * [http://slurl.com/secondlife/Orientation%20Island%20Public/127/129/23/?msg=Orientation%20Island%20Public Orientation Island Public]<br /> <br /> <br /> == Volunteer Support ==<br /> * [http://slurl.com/secondlife/Tenera/208/83/70/?title=Second%20Life%20Volunteer%20HQ Volunteer HQ]<br /> * [http://slurl.com/secondlife/Portage/24/178/85/?title=Second%20Life%20Helper%27s%20Lyceum Second Life Helper's Lyceum]<br /> * [http://slurl.com/secondlife/Pro%20Racer/144/127/36/?title=Teh%20Mental%20House Teh Mental House] : ''Access restricted to mentor, greeter and live helper. Just a peacefull full sim for (spammmmm) stressed volunteers :D. Feel free to build anything cool, if you can find some free space (Sim hosted and paid by "kerunix Flan")''<br /> <br /> == Help Islands ==<br /> Please note that only Volunteers can access Help Islands. However, "Help Island Public" is accessible by anyone.<br /> * [http://slurl.com/secondlife/Help%20Island%20Public/124/124/26/ Help Island Public]<br /> * [http://slurl.com/secondlife/Help%20Island/124/124/26/ Help Island]<br /> * [http://slurl.com/secondlife/Help%20Island%202/124/124/26/ Help Island 2]<br /> * [http://slurl.com/secondlife/Help%20Island%203/124/124/26/ Help Island 3]<br /> * [http://slurl.com/secondlife/Help%20Island%204/124/124/26/ Help Island 4]<br /> * [http://slurl.com/secondlife/Help%20Island%205/124/124/26/ Help Island 5]<br /> * [http://slurl.com/secondlife/Help%20Island%206/124/124/26/ Help Island 6]<br /> * [http://slurl.com/secondlife/Help%20Island%207/124/124/26/ Help Island 7]<br /> * [http://slurl.com/secondlife/Help%20Island%208/124/124/26/ Help Island 8]<br /> * [http://slurl.com/secondlife/Help%20Island%209/124/124/26/ Help Island 9]<br /> <br /> <br /> [[Category:Second Life Volunteers]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlSetText&diff=8598 LlSetText 2007-02-06T19:44:51Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function<br /> |function name = llSetText<br /> |func_id=llSetText<br /> |func_sleep=<br /> |func_energy=<br /> |func=llSetText<br /> |sort=SetText<br /> |p1_type=String<br /> |p1_name=text<br /> |p1d = text to display between the quotes<br /> |p2_type=Vector<br /> |p2_name=color<br /> |p2d = color in RGB enclosed between <> signs, as in <0,0,0> = black, <1,1,1> = white.<br /> |p3_type=Float<br /> |p3_name=alpha<br /> |p3d = visibility, a number between 0 and 1. 0 is fully transparent (invisible), 1.0 is fully visible (opaque).<br /> llSetText(String text, Vector color, Float alpha);<br /> <br /> |func_desc=This function is used to set text to display over an object in SL.<br /> |return_text<br /> |spec=Displays text placed over object -- programmer specifies text, color and visibility/transparency.<br /> |caveats=The floating text is a property of the prim and not the script, thus the text will remain if the script is deactivated or removed. To remove floating text, one must assign an empty string with llSetText("", <1,1,1>,1.0);<br /> |examples=<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> <1,1,1> represents the values for red, green, and blue. <1,1,1>, means "white" and <0,0,0> means "black". <br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible). <br /> <br /> Example of how llSetText could be included in default code:<br /> <br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> llSetText("Prize Box", <0,1,0>, 1.0);<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> <br /> |helpers<br /> |also_functions<br /> |also<br /> |notes=Most commonly, this is included in the default code for an object (see example above).<br /> <br /> }}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlSetText&diff=8597 LlSetText 2007-02-06T19:43:16Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function<br /> |function name = llSetText<br /> |func_id=llSetText<br /> |func_sleep=<br /> |func_energy=<br /> |func=llSetText<br /> |sort=SetText<br /> |p1_type=String<br /> |p1_name=text<br /> |p1d = text to display between the quotes<br /> |p2_type=Vector<br /> |p2_name=color<br /> |p2d = color in RGB enclosed between <> signs, as in <0,0,0> = black, <1,1,1> = white.<br /> |p3_type=Float<br /> |p3_name=alpha<br /> |p3d = visibility, a number between 0 and 1. 0 is fully transparent (invisible), 1.0 is fully visible (opaque).<br /> llSetText(String text, Vector color, Float alpha);<br /> <br /> |func_desc=This function is used to set text to display over an object in SL.<br /> |return_text<br /> |spec=Displays text placed over object -- programmer specifies text, color and visibility/transparency.<br /> |caveats=The floating text is a property of the prim and not the script, thus the text will remain if the script is deactivated or removed. To remove floating text, one must assign an empty string with llSetText("", <1,1,1>,1.0);<br /> |examples=<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> <1,1,1> represents the values for red, green, and blue. <1,1,1>, means "white" and <0,0,0> means "black". <br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible). <br /> <br /> Example of how llSetText could be included in default code:<br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> llSetText("Prize Box", <0,1,0>, 1.0);<br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> <br /> |helpers<br /> |also_functions<br /> |also<br /> |notes=Most commonly, this is included in the default code for an object (see example above).<br /> <br /> }}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LlSetText&diff=8596 LlSetText 2007-02-06T19:39:46Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL_Function<br /> |function name = llSetText<br /> |func_id=llSetText<br /> |func_sleep=<br /> |func_energy=<br /> |func=llSetText<br /> |sort=SetText<br /> |p1_type=String<br /> |p1_name=text<br /> |p1d = text to display between the quotes<br /> |p2_type=Vector<br /> |p2_name=color<br /> |p2d = color in RGB enclosed between <> signs, as in <0,0,0> = black, <1,1,1> = white.<br /> |p3_type=Float<br /> |p3_name=alpha<br /> |p3d = visibility, a number between 0 and 1. 0 is fully transparent (invisible), 1.0 is fully visible (opaque).<br /> llSetText(String text, Vector color, Float alpha);<br /> <br /> |func_desc=This function is used to set text to display over an object in SL.<br /> |return_text<br /> |spec=Displays text placed over object -- programmer specifies text, color and visibility/transparency.<br /> |caveats=None known.<br /> |examples=<br /> <br /> llSetText("I am on", <1,1,1>,1.0);<br /> <br /> <1,1,1> represents the values for red, green, and blue. <1,1,1>, means "white" and <0,0,0> means "black". <br /> <br /> llSetText("I am off", <0,0,0>,1.0);<br /> <br /> The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible). <br /> <br /> Example of how llSetText could be included in default code:<br /> default<br /> {<br /> state_entry()<br /> {<br /> llSay(0, "Hello, Avatar!");<br /> llSetText("Prize Box", <0,1,0>, 1.0);<br /> <br /> }<br /> <br /> touch_start(integer total_number)<br /> {<br /> llSay(0, "Touched.");<br /> }<br /> }<br /> <br /> <br /> |helpers<br /> |also_functions<br /> |also<br /> |notes=Most commonly, this is included in the default code for an object (see example above).<br /> <br /> }}</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_Tutorial&diff=8577 LSL Tutorial 2007-02-06T17:26:00Z

<p>Blueman Steele: </p> <hr /> <div>{{LSL Header}}<br /> <br /> '''[[GettingStartedInLSL|Getting Started In LSL]]:''' Tutorial for absolute beginners. Basic SL inventory and navigation required.<br /> <br /> == In-World Tutorials ==<br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/206/40 Free interactive in-world Linden Script Tutorial]:''' Bromley College have developed a free interactive scripting tutorial exhibition in-world.<br /> <br /> <br /> '''[http://slurl.com/secondlife/Daydream%20SE%20Islands/11/79/21/?x=300&y=300&img=http%3A//cd.bromley.ac.uk/bteccourses/sl/images/shimmer_island.jpg&title=Learning%20in%20Virtual%20Reality&msg=Here%20at%20Shimmer%20island%2C%20I%20shall%20be%20exploring%20the%20potential%20of%20Second%20Life%20in%20support%20of%20my%20current%20trials%20with%20the%20Moodle%20vle%20for%20Virtual%20Learning.%20So%20please%20feel%20free%20to%20drop%20in%20for%20a%20chat%20with%20us%20to%20see%20how%20things%20are%20going.%20Regards%20Skipper%20Abel Bromley College in-world Virtual Learning trials]:''' Please feel free to come over and look around<br /> <br /> == External Tutorials ==<br /> <br /> '''[http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial]:''' Video tutorial for building and scripting a clock.</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=List_of_external_tutorials&diff=8571 List of external tutorials 2007-02-06T17:19:47Z

<p>Blueman Steele: </p> <hr /> <div>{{old-info}}<br /> <br /> == Alpha Channels ==<br /> * [http://forums.secondlife.com/showthread.php?t=80851 Alpha channels: the definitive guide]<br /> * [http://www.nicolaescher.com/tutorials.php Clothing, alpha channels, maniquinn]<br /> * [http://forums.secondlife.com/showthread.php?t=12684&highlight=tutorial Basic clothing tutorial by owner of Pixel Dolls]<br /> * [http://wave.prohosting.com/shebangs/alpha-psp.html Alpha Channels in PSP]<br /> * [http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLPages/SLTranspStart.html Alpha Channels in PS CS]<br /> * [http://www.spacethinkdream.com/articles/article/6/alpha-channel-primer Alpha channel tutorial]<br /> * [http://forums.secondlife.com/showthread.php?t=40762&highlight=templates BETTER CLOTHING TEMPLATES]<br /> <br /> [[Category:Text from In-world Notecards]]<br /> [[Category:Articles in need of expansion]]<br /> [[Category:Tutorials]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=List_of_external_tutorials&diff=8570 List of external tutorials 2007-02-06T17:16:27Z

<p>Blueman Steele: /* Alpha Channels */</p> <hr /> <div>{{old-info}}<br /> <br /> <br /> == Scripting ==<br /> [http://www.slbuilding.com/Clock_video.html Building a Clock in Second Life - Full Video Tutorial] (added 02/06/2007)<br /> <br /> == Alpha Channels ==<br /> * [http://forums.secondlife.com/showthread.php?t=80851 Alpha channels: the definitive guide]<br /> * [http://www.nicolaescher.com/tutorials.php Clothing, alpha channels, maniquinn]<br /> * [http://forums.secondlife.com/showthread.php?t=12684&highlight=tutorial Basic clothing tutorial by owner of Pixel Dolls]<br /> * [http://wave.prohosting.com/shebangs/alpha-psp.html Alpha Channels in PSP]<br /> * [http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLPages/SLTranspStart.html Alpha Channels in PS CS]<br /> * [http://www.spacethinkdream.com/articles/article/6/alpha-channel-primer Alpha channel tutorial]<br /> * [http://forums.secondlife.com/showthread.php?t=40762&highlight=templates BETTER CLOTHING TEMPLATES]<br /> <br /> [[Category:Text from In-world Notecards]]<br /> [[Category:Articles in need of expansion]]<br /> [[Category:Tutorials]]</div>

Blueman Steele https://wiki.secondlife.com/w/index.php?title=LSL_Useful_Function_WishList&diff=8569 LSL Useful Function WishList 2007-02-06T17:02:58Z

<p>Blueman Steele: /* Other functionality */</p> <hr /> <div>__NOTOC__<br /> ==A==<br /> {{LSLG|llAddToEstateBanList}}<br /> ==G==<br /> {{LSLG|llGetParcelBanList}}<br /> {{LSLG|llGetEstateBanList}}<br /> {{LSLG|llGetAvatarKeysOnParcel}}<br /> {{LSLG|llGetAvatarKeysOnEstate}}<br /> {{LSLG|llGetMyAccountBalance}}<br /> ==N==<br /> {{LSLG|llName2Key}}<br /> ==P==<br /> {{LSLG|llPizza}}<br /> ==R==<br /> {{LSLG|llRemoveFromEstateBanList}}<br /> {{LSLG|llReturnObject}}<br /> {{LSLG|llReturnOwnersObjects}}<br /> ==T==<br /> {{LSLG|llTeleportAgent}}<br /> ==Other functionality==<br /> {{LSLG|Block comments}}<br /> {{LSLG|True tab-stops}}<br /> {{LSLG|Code Folding}}</div>

Blueman Steele