Second Life Wiki - User contributions [en]

Category talk:LSL Events

2007-08-21T18:37:58Z

CrazyTB Oh: Attach under S letter

Why all events have a code ender? should be starting with both brackets.

Not this... event(integer);

Should be this... event(integer){ }

But I am unable to correct this format in the wiki, what's the deal? -Vincent Nacon

:Sorry thats my fault, I've been meaning to fix it, it's a bug in the template. I just kept forgetting. [[User:Strife Onizuka|Strife Onizuka]]
:Fixed, the variable for that part of the title was getting double defined; the latter overwriting the former. [[User:Strife Onizuka|Strife Onizuka]] 18:17, 6 April 2007 (PDT)

== Attach under S letter ==

The [[Attach]] event is listed under '''S''' letter. I have no idea about how to fix it. Can someone fix that? (and explain here how it was done)
--[[User:CrazyTB Oh|CrazyTB Oh]] 11:37, 21 August 2007 (PDT)

Clothing Tutorials

2007-08-17T05:24:16Z

CrazyTB Oh: /* General */ Added link to Robin Wood UV templates

The following help for making clothing was originally posted on [http://torley.com Torley's blog]. Recognizing that info wants to be free and the list would be more useful it was updated regularly, the contents have been migrated here. Please add your fave tuts, remove obviated bits, and improve the usefulness of this resource!

== General ==
* '''[http://secondlife.com/community/templates.php Linden Lab Official Templates]''' - A solid general base to work from.

* '''[http://forums.secondlife.com/showthread.php?t=40762 Clothing & Skin Templates]''' - By Chip Midnight. You’ll need to be signed into your account on the SL Forums to read this, and more down the page. These templates are even higher-rez than the official ones. Chip Midnight is an original master of fine fashions in SL. Once you get really serious about detail, you’ll want to get these and have a deep look.

* '''[http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLTutSet.html Second Life tutorials]''' - By Robin Sojourner AKA Robin Wood. She has a really elegant, organized approach. Check out her fantasy art as proof! She’s mentioned that she’ll be adding more to this site, so keep watching, and check out her posts on the forums too, like her fab [http://forums.secondlife.com/showthread.php?t=77501 T-Shirt Template] — learn how to make wrinkles without photo-sourcing! Download also her [http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLPages/AVUVTemplates.html UV templates].

* '''[http://nicolaescher.com/tutorials.php Tutorials]''' - By Nicola Escher. The presentation of these tuts is aesthetically pleasing. These have been newly updated for ‘07, and are [http://www.nicolaescher.com/journal/article/28/new-translations also available in] [http://www.nicolaescher.com/journal/article/21/all-my-second-life-tutorials-in-deutsch German], Dutch (Nederlands), Chinese, and Norwegian translations. Nicola says: "I’ve got Spanish and Italian on the way." Very easy to follow, effectively illustrated. These elegant episodes include:
** '''[http://nicolaescher.com/tutorials/clothing-in-second-life.php Introduction to Creating Clothing]'''
** '''[http://nicolaescher.com/tutorials/creating-your-first-shirt.php Creating Your First Shirt]'''
** '''[http://nicolaescher.com/tutorials/alpha-channel-primer.php Alpha Channel Primer]'''
** '''[http://nicolaescher.com/tutorials/creating-a-tattoo.php Creating A Tattoo]'''
** '''[http://nicolaescher.com/tutorials/creating-a-mannequin.php Creating A Mannequin]'''

* '''[http://forums.secondlife.com/showthread.php?t=12684 T-Shirt Tutorial]''' - By Nephilaine Protagonist, head of PixelDolls, quality in quantity for the avatar. Here she shows how to make a shirt. It’s a bit hard to read, but follow the directions and keep at it. ''Note: the tutorial is currently missing, but Nephi left a note that she's planning to rewrite it.''

* '''[http://forums.secondlife.com/search.php?do=finduser&u=26252 Chosen Few's SL forum posts]''' - This sci-fi expert is a texturing databank. Watching him answer questions is like a cross between classical opera and a current events talk show, without the boring parts. The often-messy structure of the SL Forums has ironically lent itself well to his clarity. Just read his posts!

* '''[http://www.sluniverse.com/kb/ SLUniverse Knowledge Base]''' - By Cristiano Midnight. More than just clothing tutorials, this is a whole potpourri of SLinfo you’ll want to plunge into.

* '''[http://forums.secondlife.com/showthread.php?t=76703 Tattoo Creation]''' - By Amber Stonecutter. Tattoos may be likened to clothes that are harder to take off, at least offline. The magic unfolds in this thread. Amber had never made a tutorial before, and in response to Flugel inquiring, she spontaneously cooked one up — pictures and all! She even got props from Chosen and Robin.

* '''[http://slnatalia.blogspot.com/2006/11/build.html Natalia's SL Diary]''' - By Natalia Zelmanov. A listing of over 30 tutorials from her blog, including clothing, hair, jewelry, particle, shoes, and techniques. Here are some highlights:
** '''[http://slnatalia.blogspot.com/2007/03/day-181-creating-clothes-with-gimp.html Creating Clothes with GIMP]'''
** '''[http://slnatalia.blogspot.com/2007/04/day-195-creating-clothes-with-photoshop.html Creating Clothes with Photoshop]'''
** '''[http://slnatalia.blogspot.com/2006/12/day-97-making-flexi-prim-skirts-with.html Creating Flexi Skirts]'''
** '''[http://slnatalia.blogspot.com/2007/04/day-209-creating-jewelry-part-1.html Creating Jewelry]'''
** '''[http://slnatalia.blogspot.com/2007/03/day-158-creating-attachments-with.html Creating Particle Effects]'''
** '''[http://slnatalia.blogspot.com/2007/01/day-129-creating-prim-hair-part-1.html Creating Prim Hair]'''
** '''[http://slnatalia.blogspot.com/2007/01/day-101-creating-prim-shoes-part-2.html Creating Prim Shoes (Heels)]'''

* '''[http://www.slellowpages.com/slseamstress/ The SL Seamstress]''' by Jennifer McLuhan - Have you admired the clothing designers in Second Life and wished you could make clothing like them? Or, maybe you just want to make something better than the "change the tint and shorten the sleeves" Appearance sliders approach? If so, maybe this site can help you? So, don’t be shy, dive it and be come a SL seamstress or, for you guys, a tailor.

[[Category:Tutorials]]

Snapshot resources

2007-08-17T05:13:26Z

CrazyTB Oh: /* Tips 'n' tricks */ Added a notice about a non-working URL.

The following consists of miscellaneous info which often isn't easy to find, but very useful if you take Second Life snapshots, including postcards. Historically, documentation in this area has been sparse, and Residents have provided some great resources, so this is an ongoing endeavor at compiling those in an easy place — please help keep this updated!

== A state of snapshots ==
The history of snapshots in Second Life hasn't been well-chronicled. Every Resident ''vérité'' takes a picture at one point during their Second Life or another, but until recently, there's been a poor understanding of fundamental "pillars", including how many postcards get sent out, how many snapshots are uploaded to inventory, as well as the finer points of taking beautiful pictures.

Dismissing snapshots as "just for fun" neglects much context: in increasing amounts, the first exposure someone who's not yet part of Second Life may get of our world are Resident-taken snapshots. Especially on sites with a much broader audience like [http://www.flickr.com/photos/torley/ Flickr], the art of fine photography helps communicate our passion for capturing real emotions experienced in our online world.

In addition, taking better snapshots also helps increase your self-confidence. Snapshots require a combination of skills, including precise camera control, knowledge of lateral features (like adjusting the sun to get desired lighting), and frequently, avatar customization. Putting all of them together to get "the perfect shot" is a testament to how "[http://en.wikipedia.org/wiki/Meta meta]" quality snapshotting can be.

Better snapshots also hint at dreams for a lovelier Second Life. Applied post-processing effects are done in absence of the ability to perform the same magic in realtime. But as new features emerge, avid virtual shutterbugs can indulge in them, and build on their repertoire of techniques used to create beauty as they see it! For example, the [http://torley.com/be-luminous-enjoy-with-renderglow-true RenderGlow] ([[Help:Glow_Rendering|more info]]) feature added in 1.15, and planned to be a more accessible part of the interface, has already captured the imaginations of photogs in search of softer looks.

So where do we stand today? Bert Linden recently began work on regular metrics reports for postcards. For the first quarter of 2007, over 300,000 postcards were sent out. That's substantially more than the almost-269,000 sent during the whole year of 2006! We've seen an enormous surge in postcard sending, much of it prompted by the new Orientation Islands, which feature a postcard station as a basic first step in learning your Second Life. Also, as Resident-run social sites continue to expand, there can be no stopping the sharing!

With so much photographic activity trackable, and much of it not (we don't know how many snapshots you saved to disk), it's clear that more resources prominently be put forth to educate and entertain snapshot enthusiasts, new, old, and everything in-between. By improving our quality in quantity, we gain more of an appreciation for the Grid we live on, and preserve our digital cultures in ways never thought possible before. All of this also challenges preconceived norms: parallel to [http://en.wikipedia.org/wiki/Machinima machinima] being taken seriously, are Second Life snapshots merely ''computer screenshots'', or a ''new form of art''? Hindsight will make us wiser, as it tends to do.

In the present, as the old adage goes, "practice makes perfect", and what's important is you're enjoying yourself as you "capture the moments". The resources below are intended to aid in rewarding your continued self-discovery.

Enjoy your photographic memories!

: -[[User:Torley Linden|Torley Linden]], 2007-04-26

== Tips 'n' tricks ==
Video tutorials:

* '''[http://youtube.com/watch?v=iFzbvZc1BX4 How to send a postcard]''' - Self-explanatory fun!

* '''[http://youtube.com/watch?v=AZyBNBW2yjI Advanced Snapshot Magic]''' - Shows you how to zoom, get great lighting effects, and more.

From the [http://secondlife.com/support Knowledge Base] (sadly, we can't link to direct articles there, so try searching for these titles):

* '''How do I take pictures or snapshots of things inworld?''' - Start here first!

* '''Guide to the snapshot window's options''' - Intermediate-level skillz!

Did you also know you can:

* '''Change image size and quality settings when sending postcards?''' [http://blog.secondlife.com/2007/08/02/postcards-from-the-sledge/ See this blog post] for more info.

* '''[http://secondlife.com/knowledgebase/article.php?id=391 Save textures to your hard drive?]''' For example, if you've uploaded snapshots to your inventory, this lets you export them so you can upload them to other sites and post them outside of Second Life. ''[Note: This does not work for me. Could someone please add a working URL or, at least, copy that information to the wiki or somewher else?]''

* '''[http://torley.com/snapshot-tip-turn-render-ground-off Hide the ugly gap between the water and horizon?]''' (This is workaround for a bug, SL-24381, and will be deprecated when First Look: WindLight comes out.)

* '''Hide foot shadows?''' [http://secondlife.com/knowledgebase/article.php?id=339 Client menu] > Rendering > Features > Foot Shadows.

* '''[http://www.flickr.com/groups/secondlife/discuss/72157600062846532/ Use "Slow Motion Animations" to make action shots easier?]'''

* '''[http://www.flickr.com/groups/secondlife/discuss/72157600055309030/ Move the camera around while taking a freeze-frame snapshot?]''' Great for getting an ideal angle with little fuss.

* '''[http://emmanowhere.blogspot.com/2007/04/using-flickr-photos-in-second-life.html Use Flickr photos as streaming media in SL?]'''

== Social sites featuring postcards ==
* '''[http://slpics.com Snapzilla]''' - The original pioneer to really make use of postcards in such a widespread manner, its success has encouraged many Residents to share their inworld memories. As of April 2007, Snapzilla currently boasts over 150,000 pictures and is en route to a "2.0" upgrade.

* '''[http://slbuzz.com SLBuzz]''' - Postcards are [http://snapshots.slbuzz.com/search part of] SLBuzz's community site offerings. It also allows uploading of [http://photos.slbuzz.com/search photos] from your hard drive.

* '''[http://slprofiles.com/postcards.asp SL Profiles]''' - This page allows you to quickly add Second Life pictures to your profile on this community site.

* '''[http://flickr.com Flickr]''' - The popular photo-sharing service. They recently abolished their [http://tinyurl.com/2f4hx6 NIPSA restrictions] in favor of a [http://blog.flickr.com/flickrblog/2007/03/introducing_fil.html content filtering system], so Residents can show their SL snapshots in public searches.
** Via '''[http://www.sluniverse.com/pics/flickr.aspx Snapzilla-to-Flickr]''' and '''[http://snapshots.slbuzz.com/crosspost SLBuzz-to-Flickr]''', Residents can crosspost to another service to have their pictures also show up on Flickr, where they can be easily organized.
** '''[http://www.flickr.com/groups/secondlife/ Flickr's Second Life group]''' - The largest. Look inside the [http://www.flickr.com/groups/secondlife/discuss/ discussion] area for varied photographic tips 'n' tricks.
** '''[http://www.flickr.com/groups/secondlife/discuss/72157594588674941/ Links to all Second Life Groups on Flickr]''' - There are many Second Life-related groups. More keep appearing, so this likely isn't "all" of them — add ones you notice are missing!
** You can also use Flickr's [http://www.flickr.com/tools/ tools] to upload snapshots from your hard drive, and there are a variety of 3rd-party amusements like [http://bighugelabs.com/flickr/ fd's Flickr toys] and [http://www.dumpr.net/ Dumpr] which you can apply to your images.

== Useful utilities ==
Add programs you've personally found valuable.

* '''[http://picasa.google.com/ Picasa] (free, Windows and Linux)''' - Elegant photo organizer. Add your folders to be scanned and perform some light image enhancement while you're at it.

* '''[http://www.den4b.com/projects.php ReNamer] (free, Windows-only)''' - Batch-renames your files. Great for taking a heap of snapshots named "Snapshot" and turning them into something more descriptive. Also see [http://torley.com/renamer-great-utility-to-rename-your-files Torley's review].

* '''[http://www.cs.ubc.ca/~mbrown/autostitch/autostitch.html Autostitch] (free, Windows-only, Mac and Linux versions planned)''' - Easy-to-use 2D image stitcher that turn a collection of snapshots into a breathtaking, wide-angle panorama. Also see [http://torley.com/tutorial-how-to-make-a-beautiful-second-life-panorama-in-15-minutes/ Torley's tutorial] on how to specifically use it with Second Life.

* '''[http://www.optikvervelabs.com/ virtualPhotographer] (free, Windows-only)''' - Incredibly tasty little Photoshop plugin to add extra "pop" to your snapshots. Had a nice collection of presets and can simulate film grain, sepia, bloom, etc.

* '''[http://www.gimp.org GIMP] (free, Windows, Mac, and Linux)''' - The "GNU Image Manipulation Program" is a freely distributed piece of software for such tasks as photo retouching, image composition, and image authoring. It works on many operating systems, in many languages. A lot of Photoshop's features are also available in GIMP, and there's also a [http://en.wikipedia.org/wiki/Gimpshop GIMPshop], which emulates PS' functionality even closer.

== Related resources ==
You may also be interested in seeing this wiki's compilation of:
* '''[[Texture Tools]]''' - Image-editing stuff you can use to prettify your pictures. Some overlap with this page.
* '''[[Video Tutorials]]''' - An assortment of multimedia guides, good for those who enjoy seeing how things actually work inworld.

[[Category:Tutorials]]

LlParticleSystem

2007-08-08T21:39:23Z

CrazyTB Oh: Fixed some mistyped constants

{{LSL Function/color}}{{LSL Function/alpha}}{{LSL_Function|func_id=229|func_sleep=0.0|func_energy=10.0
|func=llParticleSystem
|p1_type=list|p1_name=rules|p1_desc=Particle system rules list in the format [ rule1, data1, rule2, data2 . . . rulen, datan ]
|func_desc=Defines a particle system for the containing prim based on a list of '''rules'''.
|return_text
|spec=
Defines a particle system that sets the state of the {{LSLG|particle emitter}} within the {{LSLG|primitive|prim}} which the {{LSLG|script}} is contained. Any other scripts in the same prim which call this function will modify the state of the same particle emitter. As such, the particle system defined by this function is a {{LSLG|primitive property|prim property}}, just like its size, shape, color, et cetera.
Each prim has only '''one (1)''' particle emitter, located at its {{LSLG|geometric center}}, and aligned along the prim's [[Viewer coordinate frames#Local|local]] Z-axis, pointing in the positive Z direction.

This is the only function which alters the state of the prim's particle emitter; thus, if you wish to change the emitter to a different state (i.e., emitting a different particle system entirely, or shut off the emitter completely), just call this same function with the parameters of the new particle system you wish to render instead. Specifying an empty list (i.e., llParticleSystem([]); ) turns the emitter off.

Particles are essentially 2D "sprites" and are always rendered facing the viewer's camera.

The rule / data values are defined below.
|caveats=
# Due to a bug/limitation in the implementation of the particle system, any alpha change defined by setting PSYS_PART_END_ALPHA and the PSYS_PART_INTERP_COLOR_MASK flag '''always''' goes from a higher alpha value to a lower one. In other words, particles can only "fade-out" and can never "fade-in". This is true even if you specify it in the list where PSYS_PART_START_ALPHA is less than PSYS_PART_END_ALPHA, as the values will be re-ordered internally when the particle system is rendered.
# When using particle systems that have a non-zero emitter age (PSYS_SRC_MAX_AGE) setting, you may notice that the particle system may restart without any scripted trigger going off. This is due to a bug which causes the emitter to "reset" when any of the prim properties are updated or otherwise sent to the viewer. As a result, you may have to use a {{LSLG|timer}} or a forced {{LSLG|llSleep|sleep}} and then clear the particle system once the age has expired.
# The spin defined by PSYS_SRC_OMEGA is relative to the [[Viewer coordinate frames#Region|region]] coordinate system, NOT the prim's [[Viewer coordinate frames#Local|local]] coordinate system.
# Particles moving towards a humanoid avatar, specified by PSYS_SRC_TARGET_KEY rule and setting the PSYS_PART_TARGET_POS_MASK flag, will end up at the geometric center of the avatar's bounding box which, unfortunately, make them appear to be striking the person in the groin area. If you want them to end up at another point on a target avatar, you instead have to place a target prim that is moved to the position where you wish them to end up, and use the key of that prim for the value of the PSYS_SRC_TARGET_KEY rule.
# The Second Life viewer uses optimizations in culling objects which are too small to see at certain distances. If your emitter is very small, and is culled due to distance, the particle system associated with it will not be rendered either.
|examples=[[Example Particle Script]]

This example produces an effusion of glowing red spheres:
<pre>
llParticleSystem(
[PSYS_PART_FLAGS, PSYS_PART_WIND_MASK | PSYS_PART_EMISSIVE_MASK,
PSYS_SRC_PATTERN, PSYS_SRC_PATTERN_EXPLODE,
PSYS_PART_START_COLOR, <1,0,0>
] );
</pre>

|helpers=
'''Useful functions for storing/retrieving color and alpha values to/from integers:''' 
<pre>
integer ColorAlphatoRGBA(vector color, float alpha) {
return (((integer)(alpha * 255.0) & 0xFF) << 24) |
(((integer)(color.x * 255.0) & 0xFF) << 16) |
(((integer)(color.y * 255.0) & 0xFF) << 8) |
((integer)(color.z * 255.0) & 0xFF);
}

vector RGBAtoColor(integer rgba) {
return < ((rgba >> 16) & 0xFF) / 255.0, ((rgba >> 8) & 0xFF) / 255.0, (rgba & 0xFF) / 255.0 >;
}

float RGBAtoAlpha(integer rgba) {
return ((rgba >> 24) & 0xFF) / 255.0;
}
</pre>
|also_articles
|also_events
|also_functions
|sort=ParticleSystem
|notes=
* The default particle count for the client is normally set at 4096. That is the max particle count the client will render for ALL active particle systems within view range. Good particle system design is key to avoid "spamming" everyone with your particles, and starving out other people's particle systems. As such, if you are experiencing trouble getting your particle emitter to emit as many particles as you like, it may be the victim of particle starvation. Client/viewer lag (low frame rates) can also cause this issue, as particles are a rather low priority for rendering. The best solution for this is to move to a less laggy environment relatively free of other particle systems when designing and testing your own.
* Once particles are emitted, their direction of motion can only be affected by PSYS_SRC_ACCEL, the PSYS_PART_TARGET_POS_MASK flag, or the PSYS_PART_FOLLOW_SRC_MASK flag. As such, there is no good way to create the "swirling vortex" effect (like the one used in the viewer to indicate an object talking, begin derezzed, or when an avatar leaves the sim/grid).
|constants={{{!}} {{prettytable}}
{{!}}{{Hl2}}{{!}}
{{!}}{{Hl2}}{{!}} Rule / Value Constant
{{!}}{{Hl2}}{{!}} Type
{{!}}{{Hl2}}{{!}} Description
{{!}}{{Hl2}}{{!}} Value
{{!}}- style="background-color:#ccffcc;"
{{!}} colspan="5" align="left"{{!}}'''System Behavior'''
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_FLAGS{{!}}{{!}}{{LSLG{{!}}integer}}{{!}}{{!}}Various flags controlling the behavior of the particle system. The value may be specified as an integer in decimal or {{LSLG{{!}}hexadecimal{{!}}hex}} format, or by ORing together (using the <nowiki>|</nowiki> operator) one or more of the following flag constants:{{!}}{{!}}align="center"{{!}}0
{{!}}- style="background-color:#e0e0e0;"
{{!}}rowspan="14" style="background-color:#c0c0c0;" align="center" valign="center"{{!}}'''V a l u e s'''{{!}}{{!}}colspan="2"{{!}}PSYS_PART_BOUNCE_MASK{{!}}{{!}}When set, specifies particles will bounce off a plane at the [[Viewer coordinate frames#Region|region]] Z height of the emitter. On "bounce", each particle reverses velocity and angle. This only works for particles above the plane falling down on it.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x004|4}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_EMISSIVE_MASK{{!}}{{!}}When set, particles are full-bright and are unaffected by global lighting (sunlight). Otherwise, particles will be lit depending on the current global lighting conditions. Note that point lights '''do''' illuminate non-emissive particles.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x100|256}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_FOLLOW_SRC_MASK{{!}}{{!}}When set, particles move relative to the position of the emitter. Otherwise, particle position and movement are unaffected by the position/movement of the emitter. This flag disables the PSYS_SRC_BURST_RADIUS rule.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x010|16}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_FOLLOW_VELOCITY_MASK{{!}}{{!}}When set, particles rotate to orient their "top" towards the direction of movement or emission. Otherwise, particles are always emitted based on the current rotation of the emitter.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x020|32}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_INTERP_COLOR_MASK{{!}}{{!}}When set, particle color and alpha transition from their START settings to their END settings during the particle's lifetime. The transition is a smooth interpolation.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x001|1}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_INTERP_SCALE_MASK{{!}}{{!}}When set, particle size/scale transitions from its START setting to its END setting during the particle's lifetime.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x002|2}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_TARGET_LINEAR_MASK{{!}}{{!}}(''not officially documented'') When set, emitted particles move in a straight line towards the target specified by the PSYS_SRC_TARGET_KEY rule. In this mode, PSYS_SRC_ACCEL, PSYS_SRC_BURST_RADIUS, and possibly other rules are ignored.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x080|128}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_TARGET_POS_MASK{{!}}{{!}}When set, emitted particles change course during their lifetime, attempting to move towards the target specified by the PSYS_SRC_TARGET_KEY rule by the time they expire. Note that if no target is specified, the target moves out of range, or an invalid target is specified, the particles target the prim itself.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x040|64}}
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}PSYS_PART_WIND_MASK{{!}}{{!}}When set, particle movement is affected by the {{LSLG{{!}}llWind{{!}}wind}}. It is applied as a secondary force on the particles.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x008|8}}

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

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

{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}<s>PSYS_PART_RANDOM_ACCEL_MASK</s>{{!}}{{!}}(''unimplemented'') Presumed to be used to apply random acceleration to the particles.{{!}}{{!}}align="center"{{!}} -
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}<s>PSYS_PART_RANDOM_VEL_MASK</s>{{!}}{{!}}(''unimplemented'') Presumed to be used to specify random velocity for the particles upon emission.{{!}}{{!}}align="center"{{!}} -
{{!}}- style="background-color:#e0e0e0;"
{{!}} colspan="2"{{!}}<s>PSYS_PART_TRAIL_MASK</s>{{!}}{{!}}(''unimplemented'') Presumed to be used for implementing "trails" via emitting more particles at shorter bursts.{{!}}{{!}}align="center"{{!}} -
{{!}}- style="background-color:#ccffcc;"
{{!}} colspan="5" align="left"{{!}}'''System Presentation'''
{{!}}-
{{!}} colspan="2"{{!}}PSYS_SRC_PATTERN{{!}}{{!}}{{LSLG{{!}}integer}}{{!}}{{!}}Specifies the general emission pattern.{{!}}{{!}}align="center"{{!}}9
{{!}}- style="background-color:#e0e0e0;"
{{!}}rowspan="5" style="background-color:#c0c0c0;" align="center" valign="center"{{!}}'''V a l u e s'''{{!}}{{!}} colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE{{!}}{{!}}Present particles in a 2-dimensional circular section as defined by PSYS_SRC_ANGLE_BEGIN and PSYS_SRC_ANGLE_END. The orientation of the particle plane is at X=0 relative to the emitter's [[Viewer coordinate frames#Region|region]] rotation.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x04|4}}
{{!}}- style="background-color:#e0e0e0;"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE_CONE{{!}}{{!}}Present particles in a 3-dimensional spherical section, as defined by PSYS_SRC_ANGLE_BEGIN and PSYS_SRC_ANGLE_END.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x08|8}}
{{!}}- style="background-color:#e0e0e0;"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY{{!}}{{!}}(''not officially documented; appears to be non-functional'') Present particles in a 3-dimensional spherical section, as defined by PSYS_SRC_ANGLE_BEGIN and PSYS_SRC_ANGLE_END, but inversely compared to the ANGLE_CONE pattern (i.e., where there were voids in ANGLE_CONE, there are particles in ANGLE_CONE_EMPTY, and vice-versa.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x10|16}}
{{!}}- style="background-color:#e0e0e0;"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_DROP{{!}}{{!}}Present particles by dropping them at the emitter position with no force. Ignores the PSYS_SRC_BURST_RADIUS, PSYS_SRC_BURST_SPEED_MIN, and PSYS_SRC_BURST_SPEED_MAX rules.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x01|1}}
{{!}}- style="background-color:#e0e0e0;"
{{!}}colspan="2"{{!}}PSYS_SRC_PATTERN_EXPLODE{{!}}{{!}}Present particles by shooting them out in all directions according to the burst motion rules.{{!}}{{!}}align="center"{{!}}{{LSL_Hex|0x02|2}}
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_RADIUS{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the distance from the emitter where particles will be created. This rule is ignored when the PSYS_PART_FOLLOW_SRC_MASK flag is set.{{!}}{{!}}align="center"{{!}}16
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_ANGLE_BEGIN{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies a half angle, in radians, of a circular or spherical "dimple" or conic section (starting from the emitter facing) within which particles will NOT be emitted. Valid values are the same as for PSYS_SRC_ANGLE_END, though the effects are reversed accordingly. If the pattern is PSYS_SRC_PATTERN_ANGLE, the presentation is a 2D flat circular section. If PSYS_SRC_PATTERN_ANGLE_CONE or PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY is used, the presentation is a 3D spherical section. Note that the value of this parameter and PSYS_SRC_ANGLE_END are internally re-ordered such that this parameter gets the smaller of the two values.{{!}}{{!}}align="center"{{!}}22
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_ANGLE_END{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies a half angle, in radians, of a circular or spherical "dimple" or conic section (starting from the emitter facing) within which particles will NOT be emitted. Valid values are 0.0, which will result in particles being emitted in a straight line in the direction of the emitter facing, to PI, which will result in particles being emitted in a full circular or spherical arc around the emitter, not including the "dimple" or conic section defined by PSYS_SRC_ANGLE_BEGIN. If the pattern is PSYS_SRC_PATTERN_ANGLE, the presentation is a 2D flat circular section. If PSYS_SRC_PATTERN_ANGLE_CONE or PSYS_SRC_PATTERN_ANGLE_CONE_EMPTY is used, the presentation is a 3D spherical section. Note that the value of this parameter and PSYS_SRC_ANGLE_BEGIN are internally re-ordered such that this parameter gets the larger of the two values.{{!}}{{!}}align="center"{{!}}23
{{!}}-
{{!}}colspan="2"{{!}}<del>PSYS_SRC_INNERANGLE</del>{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}'''DEPRECATED: Use PSYS_SRC_ANGLE_BEGIN instead.''' Works similar to its replacement rule, except the edge of the section is aligned with the emitter facing, rather than its center.{{!}}{{!}}align="center"{{!}}10
{{!}}-
{{!}}colspan="2"{{!}}<del>PSYS_SRC_OUTERANGLE</del>{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}'''DEPRECATED: Use PSYS_SRC_ANGLE_END instead.''' Works similar to its replacement rule, except the edge of the section is aligned with the emitter facing, rather than the section's center.{{!}}{{!}}align="center"{{!}}11
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_TARGET_KEY{{!}}{{!}}{{LSLG{{!}}key}}{{!}}{{!}}Specifies the key of a target object, prim, or agent towarads which the particles will change course and move. They will attempt to end up at the geometric center of the target at the end of their lifetime. Requires the PSYS_PART_TARGET_POS_MASK flag be set. [[#Caveats{{!}}caveat 4]]{{!}}{{!}}align="center"{{!}}20
{{!}}- style="background-color:#ccffcc;"
{{!}}colspan="5" align="left"{{!}}'''Particle Appearance'''
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_START_COLOR{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}A {{LSLG{{!}}unit vector}} specifying the {{LSLG{{!}}color}} of the particles upon emission.{{!}}{{!}}align="center"{{!}}1
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_END_COLOR{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}A {{LSLG{{!}}unit vector}} specifying the {{LSLG{{!}}color}} the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_COLOR_MASK flag is set.{{!}}{{!}}align="center"{{!}}3
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_START_ALPHA{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the {{LSLG{{!}}alpha}} of the particles upon emission. Valid values are in the range 0.0 to 1.0. Higher values are more opaque; lower ones are more transparent.{{!}}{{!}}align="center"{{!}}2
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_END_ALPHA{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the {{LSLG{{!}}alpha}} the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_COLOR_MASK flag is set. Valid values are the same as PSYS_PART_START_ALPHA. ([[#Caveats{{!}}caveat 1]]){{!}}{{!}}align="center"{{!}}4
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_START_SCALE{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}Specifies the {{LSLG{{!}}scale}} or size of the particles upon emission. Valid values for each direction are 0.04 (0.03125) to 4.0, in meters. Since particles are essentially 2D sprites, the Z component of the vector is ignored and can be set to 0.0.{{!}}{{!}}align="center"{{!}}5
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_END_SCALE{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}Specifies the {{LSLG{{!}}scale}} or size the particles transition to during their lifetime. Only used if the PSYS_PART_INTERP_SCALE_MASK flag is set. Valid values are the same as PSYS_PART_START_SCALE.{{!}}{{!}}align="center"{{!}}6
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_TEXTURE{{!}}{{!}}{{LSLG{{!}}string}}{{!}}{{!}}Specifies the name of a texture in the prim's inventory to use for each particle. Alternatively, you may specify an asset key UUID for a texture.{{!}}{{!}}align="center"{{!}}12
{{!}}- style="background-color:#ccffcc;"
{{!}}colspan="5" align="left"{{!}}'''Particle Flow'''
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_MAX_AGE{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the length of time, in seconds, that the emitter will operate upon coming into view range (if the particle system is already set) or upon execution of this function (if already in view range). Upon expiration, no more particles will be emitted, except as specified above. Zero will give the particle system an infinite duration. ([[#Caveats{{!}}caveat 2]]){{!}}{{!}}align="center"{{!}}19
{{!}}-
{{!}}colspan="2"{{!}}PSYS_PART_MAX_AGE{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the lifetime of each particle emitted, in seconds. Maximum is 30.0 seconds. During this time, the particle will appear, change appearance and move according to the parameters specified in the other sections, and then disappear.{{!}}{{!}}align="center"{{!}}7
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_RATE{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the time interval, in seconds, between "bursts" of particles being emitted. Specifying a value of 0.0 will cause the emission of particles as fast as the viewer can do so.{{!}}{{!}}align="center"{{!}}13
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_PART_COUNT{{!}}{{!}}{{LSLG{{!}}integer}}{{!}}{{!}}Specifies the number of particles emitted in each "burst".{{!}}{{!}}align="center"{{!}}15
{{!}}- style="background-color:#ccffcc;"
{{!}}colspan="5" align="left"{{!}}'''Particle Motion'''
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_ACCEL{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}Specifies a directional acceleration vector applied to each particle as it is emitted, in meters per second. Valid values are 0.0 to 100.0 for each direction, as [[Viewer coordinate frames#Region|region]] coordinates.{{!}}{{!}}align="center"{{!}}8
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_OMEGA{{!}}{{!}}{{LSLG{{!}}vector}}{{!}}{{!}}Specifies the rotational spin of the emitter in radians per second along each axis. This "unsticks" the emitter facing from the prim's positive Z axis and is noticeable in directional presentations. Prim spin (via {{LSLG{{!}}llTargetOmega}}) has no effect on emitter spin. ([[#Caveats{{!}}caveat 3]]){{!}}{{!}}align="center"{{!}}21
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_SPEED_MIN{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the minimum value of a random range of values which is selected for each particle in a burst as its initial speed upon emission, in meters per second. Note that the value of this parameter and PSYS_SRC_BURST_SPEED_MAX are internally re-ordered such that this parameter gets the smaller of the two values.{{!}}{{!}}align="center"{{!}}17
{{!}}-
{{!}}colspan="2"{{!}}PSYS_SRC_BURST_SPEED_MAX{{!}}{{!}}{{LSLG{{!}}float}}{{!}}{{!}}Specifies the maximum value of a random range of values which is selected for each particle in a burst as its initial speed upon emission, in meters per second. Note that the value of this parameter and PSYS_SRC_BURST_SPEED_MIN are internally re-ordered such that this parameter gets the larger of the two values.{{!}}{{!}}align="center"{{!}}18
{{!}}}
|cat1=Effects
|cat2=Light
|cat3=Particles
|cat4
}}

Talk:Voice FAQ

2007-08-05T00:48:53Z

CrazyTB Oh: /* Wrong URL && Linux */

One interesting part is missing here: How can i change my voice, will a voice changer be supported? --[[User:Sascha Vandyke|Sascha Vandyke]] 17:52, 2 August 2007 (PDT)
::Although Linden Lab at some point did mention that an in-built voice-changing/morphing editor will be supported in SL, in the mean time, you can use any of the popular voice morphing tools, like [http://www.audio4fun.com/voice-changer.htm AV Voice Changer] or [http://www.morphvox.com MorphVox]. Gwygory Voom is an employee of Screaming Bee who is glad to help you out with setting up MorphVox properly, and they have even designed [http://www.screamingbee.com/product/furryvoicesforsecondlife.aspx a voice pack specifically for SL Furries]. Sadly, they haven't got a Mac version (yet — also working on it!) but if you've got a Mac, you can use GarageBand and use [http://secondlife.funwithstuff.com/2007/03/whatever-you-want-to-sound-like-on-mac.html Ali Maltz tips to get it working with SL].

::Don't expect miracles with either of these technologies, though :) They work, but they're no perfect. Still, they have been progressively advancing in technology and at least you'll have some fun sounding like a Bunny or Dragon :)
::— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] 03:44, 3 August 2007 (PDT)

==Question Typo==
--You have a wikifying typo at the end: 
''"====Is Voice open source>"'' should be ''"====Is Voice open source?===="'', right?
-[[User:Smiley Barry|Smiley]].

Just to let you know ... there are countries where VoIP is actively being blocked, like in the UAE in the Middle East. If you happen to live in one of these countries, don't expect Voice to work in SL. Skype does not work here either.

== Wrong URL ==

The very first question points to an invalid URL: http://secondlife.com/community/downloads.com
The correct is http://secondlife.com/community/downloads.php

== Linux ==

Linux client is not supported. Looks like SLVoice.exe is closed-source and was not ported to Linux machine, but I'm not sure.

Some people told me it could be possible to run SLVoice.exe on Windows (under vmware or something) or Wine and Linux client would be able to use it, maybe with some hacks.

Meanwhile, people are forced to use skype or any other voip service.

Talk:Voice FAQ

2007-08-04T19:52:34Z

CrazyTB Oh: Wrong URL && Linux

One interesting part is missing here: How can i change my voice, will a voice changer be supported? --[[User:Sascha Vandyke|Sascha Vandyke]] 17:52, 2 August 2007 (PDT)
::Although Linden Lab at some point did mention that an in-built voice-changing/morphing editor will be supported in SL, in the mean time, you can use any of the popular voice morphing tools, like [http://www.audio4fun.com/voice-changer.htm AV Voice Changer] or [http://www.morphvox.com MorphVox]. Gwygory Voom is an employee of Screaming Bee who is glad to help you out with setting up MorphVox properly, and they have even designed [http://www.screamingbee.com/product/furryvoicesforsecondlife.aspx a voice pack specifically for SL Furries]. Sadly, they haven't got a Mac version (yet — also working on it!) but if you've got a Mac, you can use GarageBand and use [http://secondlife.funwithstuff.com/2007/03/whatever-you-want-to-sound-like-on-mac.html Ali Maltz tips to get it working with SL].

::Don't expect miracles with either of these technologies, though :) They work, but they're no perfect. Still, they have been progressively advancing in technology and at least you'll have some fun sounding like a Bunny or Dragon :)
::— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] 03:44, 3 August 2007 (PDT)

==Question Typo==
--You have a wikifying typo at the end: 
''"====Is Voice open source>"'' should be ''"====Is Voice open source?===="'', right?
-[[User:Smiley Barry|Smiley]].

Just to let you know ... there are countries where VoIP is actively being blocked, like in the UAE in the Middle East. If you happen to live in one of these countries, don't expect Voice to work in SL. Skype does not work here either.

== Wrong URL && Linux ==

The very first question points to an invalid URL: http://secondlife.com/community/downloads.com
The correct is http://secondlife.com/community/downloads.php

By the way, is Voice supported on Linux? (I haven't downloaded it yet)

Getting started with LSL

2007-07-15T06:24:03Z

CrazyTB Oh: Linkified most of function and event names (when outside sample codes).

{{LSL Header}}

== Getting started in LSL scripting in Second Life ==

LSL stands for "Linden Scripting Language" and is used to script the objects you will encounter and make in Second Life.

'''FOR WHOM IS THIS TUTORIAL:'''

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.

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.

== What is LSL? ==

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

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.

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

(note: all scripts will be placed in LSL tags when it goes active)

<pre>
default
{
touch_start(integer total_number)
{
llSay(0,"Hello World");
}
}
</pre>

'''WHAT CAN I DO WITH SCRIPTS?'''

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.

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.

Scripting is harder to learn than basic object manipulation, but is very rewarding once you make progress.

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.

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.

== Running Your First Script ==

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.

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

By default, you should see a '''wand''' icon with which you can click and create a cube on the ground.

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.

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

This window shows the contents of an object which can hold scripts, notecards, even other objects. Press '''new script''' to add a new script.

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.

Before explaining the code, lets run it. Hit '''save''' and close your edit window (not the LSL editor window).

You should see the words "Hello Avatar" from "object"

If you touch the object, it will say "Touched." The "edit" building window must be closed for touching to work.

Congratulations! You have compiled and run your first LSL script!

== Wash / Rinse / Repeat ==

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.

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.

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

Each time you re-write your code you'll want to reset the script.

Try resetting the script in the following ways.

1. Press Reset in the script window.
2. Select the object and go to TOOLS>RESET SCRIPTS IN SELECTION

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.

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.

'''WHY STOP AND START?'''

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.

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!

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.

== A Closer Look ==

Lets take a look at the default code.

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

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}

The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually.

Any line starting with two forward slashes is a comment. It will not run and is used to help you document your code.

// This is a comment

'''STATES'''

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.

default
{
// contents of state go here
}

state playing
{
// this is a state called "playing"
}

'''EVENTS'''

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.

Lets take a look at the default code.

// Code start
default
{
touch_start(integer total_number)
// this is an event
{
// this is the content of the event
}
// end of event
}
// end of state

'''FUNCTIONS'''

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.

== Putting it all together ==

Line by line, here is the hello avatar script. Copy and paste this to a new script to see it color coded.

// All Scripts need a Default State
default
// this open curly bracket denotes the start of the state
{
state_entry() // an event
// another curly bracket starts the body of the event
{
llSay(0, "Hello, Avatar!"); // a function inside the event
}
// closed curly bracked closes the state_entry event

touch_start(integer total_number) // another event inside default state
{
llSay(0, "Touched."); // a function between the brackets of the touch_start body
}
// end of touch start
}
// Code end

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.

After this, the program waits idle in the default state until a new event is called.

Touching the box triggers the event "[[touch_start]]" which also makes the object speak.

== Introducing States and Events ==

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.

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.

Let's look at a script with two states with two events in each.

default //default state is mandatory
{
state_entry() // runs each time the state is entered
{
llSay(0, "turning on!"); //object speaks!
llSetColor(<1,1,1>, ALL_SIDES); // sets all sides to most bright
// note the semicolons at the end of each instruction.
}

touch_start(integer total_number) // another event with only one function inside
{
state off; // sets the script to a new "state" and starts running "state off"
}
} // this curly bracket ends the body of the default state.

state off // a second state besides "default"
{
state_entry() // this is run as soon as the state is entered
{
llSay(0, "turning off!");
llSetColor(<0,0,0>, ALL_SIDES); // sets all sides as dark as possible
}

touch_start(integer total_number)
{
state default;
}
}

A simplification of this would be

default
{
//set color to light and, if touched, enter the "off" state.
}

state off
{
//set color to dark and, if touched, enter the "default" state.
}

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.

== A closer look ==

Let's examine the default state.

First we see the "[[state_entry]]" event, which gets triggered each time the default state is entered.

'''SPEAK TO ME!'''

The first line in the event state_entry is...

[[LSL_llSay|llSay]](0, "turning on!");

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.

A semicolon ends the line and yet another instruction follows.

[[llSetColor]](<1,1,1>, ALL_SIDES);

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.

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.

'''TOUCHED BY AN AVATAR'''

While idle in the default state a touch will trigger the "[[touch_start]]" event.

Inside of the "touch_start" event is only one command:

state off;

This is a command to move immediately to a new state named "off".

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.

# Enters default state
# Runs code in "state entry"
# Waits to be touched
# When touched enters "state off"
# Enters "state off"
# Runs code in "state entry" (note in the "off" state's body)
# Waits to be touched
# When touched enters "default" state

Then the whole thing starts over.

== A final word on words ==

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.

'''SHHHH WHISPER'''

[[llWhisper]]( ) is just like [[llSay]]( ) but only broadcasts at half the distance. You still must state what channel. So...

llWhisper(0,"turning on!");

...might work a bit to save the sanity of your neighbors.

Using [[llShout]]( ) doubles the distance heard, but can cut the amount of friends you have in half.

[[llOwnerSay]]( ) uses no channel and is heard only by you. Very useful and can triple the amount of friends you have!

llOwnerSay("turning on!");

'''THE SOUND OF SILENCE'''

You can make a totally silent message via [[llSetText]]( ) like this.

llSetText("I am on", <1,1,1>,1.0);

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

llSetText("I am off", <0,0,0>,1.0);

The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible).

{{LSLC|Tutorials}}