Second Life Wiki - User contributions [en]

Widget talk:YouTube

2024-07-04T13:07:14Z

MoiraAtropos Resident: /* Needs update! */

== Needs update! ==

Flash has been gone for ages. Youtube embedding uses iframes and the html5 player now.<ref>https://support.google.com/youtube/answer/171780?hl=en</ref> Can someone please update this? -- [[User:MoiraAtropos Resident|MoiraAtropos Resident]] ([[User talk:MoiraAtropos Resident|talk]]) 06:07, 4 July 2024 (PDT)

</references>

Sculpted prim

2024-07-04T12:59:49Z

MoiraAtropos Resident: /* An informal introduction to Sculpted Prims */ Update video embed to current widget

{{Help|Object=*}}{{Navbox/Media}}[[Image:Sculpted_fruit_small.png|frame|right|Sculpted Prims]]
[[Image:Sculpted_couch_Xenius_Revere.png|frame|right|Seven prim couch by Xenius Revere, using baked ambient occlusion.]]
[[Image:Sculpted_head_Chip_Midnight.png|frame|right|One prim head by Chip Midnight, using baked diffuse lighting.]]
[[Image:Sculpted_vases_Damanios_Thetan.jpg|frame|right|Vase sculpture by Damanios Thetan]]

{|cellspacing="5px"
|valign="top"|
__TOC__
|valign="top" width="48%"|
{{Sculpted Prims/Links}}
|}

<videoflash>LlfpACg_lww</videoflash>

A '''Sculpted Prim''', or ''sculptie'', is a [[prim]] whose shape is determined by an array of x, y, z coordinates stored as RGB values in an image file
(a '''[[Sculpted Prims: FAQ#SculptTextures|Sculpt Texture]]''' or '''[[Sculpted Prims: FAQ#SculptTextures|Sculpt Map]]''').
Sculpted prims can be used to create more complex, organic shapes that were not previously possible with the Second Life prim system. Each piece of fruit to the right is one prim (and so is the plate). For technical details, see [[Sculpted Prims: Technical Explanation]].

== An informal introduction to Sculpted Prims ==

Here is a video about the most important things you should know about Sculpted Prims. The video is made with Blender, but it focusses on the principles of Sculpted Prims, and thus it is completely independent from any 3D-tool.

{{#widget:YouTube|id=4CJxwvvgFzE}}

== How do I make Sculpted Prims ==

Presently, there are only a few limited tools '''inside''' Second Life for creating sculpties. They are usually created externally using a 3D modeling tool such as Blender, Maya, or Wings 3D, and then uploaded to Second Life, where they are applied to a prim with the build tools.

Further Informations can be found here:
*[[Sculpted Prims: Creator's Guide]] for more guidance
*[[Sculpted Prims: 3d Software Guide]] for a list of supporting software.

== News ==

=== 20 June 2007 ===

In-world group '''Sculptie Dev''': group primarily for the communication/announcement of sculpted prim development.

=== 24 May 2007 ===

Linden Lab is running a contest: show off your sculpties for fun, fame and schwag! [http://blog.secondlife.com/2007/05/24/second-life-sculpted-prim-contest-show-us-your-sculpties/ Read the blog for details.] Deadline for submissions is June 1st.

=== 23 May 2007 ===

Sculpted prims are now available on the [http://blog.secondlife.com/2007/05/23/the-grid-is-down-for-scheduled-maintenance/ Main Grid] as of version 1.16.0(5).

=== 16 May 2007 ===

An update to sculpted prims, included in the [http://blog.secondlife.com/2007/05/15/beta-grid-updated-to-second-life-11601/ latest build] of the beta viewer ([http://secondlife.com/community/preview.php 1.16.0(1)]), has two changes that are not backwards-compatible:

1) The orientation of the '''sculpt map''' (sculpt texture) is reversed. This means all previously created sculpt maps/textures need to be horizontally flipped (otherwise they'll appear inside out.) This change fixes the orientation discrepancy between sculpt maps/textures and surface textures (which have required a 90 degree rotate and flip.) ([http://blog.secondlife.com/2007/05/15/beta-grid-updated-to-second-life-11601/ source])

2) The LSL call to set sculpted prims is changing to require two parameters: the texture and the topology type. (source: [[Talk:Sculpted_Prims#HEADS_UP.21|Talk page]])

=== 27 April 2007 ===

Sculpted Prims made available on the [http://www.secondlife.com/community/preview.php preview grid].

== Where can I find out more about Sculpted Prims? ==

Sculpted Prims have now a comprehensive [[Sculpted Prims: FAQ|FAQ]] wiki page.

== See also ==

*[[Sculpted Prims: Technical Explanation]]
*[[Sculpted Prims: FAQ| Sculpted Prims FAQ]]
*[[Sculpted_Prims:_Sculpt_Maps_and_Textures|Sculpt Maps and Textures]]
*[[Sculpted_Prims:_3d_Software_Guide|3D Software Guide]]
*[[Sculpted_Prims:_3d_Modeling_Glossary|3D Modeling Glossary]]
*[[Sculpt_Textures_in_Paint_Programs|Sculpt Maps and 2D Graphics Software]]
*[[Sculpted_Prims:_Resident-made_Tools|Sculpted Prims: Resident-made Tools]]

[[Category:Sculpted Prims]]

[[Category:Features]]

[[Category:Creation]]

Profile Image

2024-06-19T07:59:29Z

MoiraAtropos Resident: /* Aspect Ratio */ Updated to current behaviour

==PROFILE IMAGE==

===Aspect Ratio===
The [[Profile]] Image to be uploaded (thereafter to be referred to as a Texture) needs a Pixel Aspect Ratio of 1:1, which means that the width should qual the height.
So, the image might be 512 x 512 pixels, 800 x 800 pixels, or 1024 x 1024, for example. You may need to use an image editor to crop your image accordingly.

'''''NOTE'''''; ''if you have previously saved [[Snapshots]] from within Second Life to your inventory without altering the standard proportions given (this would be done in the Snapshot tool by unchecking Constrain Proportions and then changing the pixel measurements for either width or height in isolation), your image will already have the right proportions. There will no need to use an image editor such as Photoshop or GIMP to alter it. If you have saved the image to disk or altered proportions, you'll likely want to crop the image.''

===Uploading the Image===
To upload the image into Second Life, click
File
Upload - > Image

===Profile Image Picker===
To set this texture (image) as the Profile Image, right-click your [[avatar]] and select Profile.
In the General tab, click on the Profile Image placeholder (blue image with silhouette). The Pick window will appear. You can search for the uploaded texture/image using the search field on this tab.
Select the texture and click
Select
OK.

'''''NOTE''''': ''the placeholder image in the Pick window appears squashed in from the sides so that the contents are tall and thin. This does NOT mean that you have to stretch your prospective image in an image editor before uploading it, with the idea of compensating for the narrow/thin squashing effect. Once you select the image, it will appear with normal proportions in the profile.
''(But if you ever DO need to do this for some other application within Second Life, expand your image laterally so that the contents will appear wide/fat, by multiplying the width measurement by the number 1.33.)''

[[Category:UPLOAD]]
[[Category:IMAGE]]
[[Category:PROFILE]]
[[Category:TEXTURE]]
[[Category:Textures and Snapshots]]

CONTENT TYPE LLSD

2024-06-19T07:45:26Z

MoiraAtropos Resident:

<onlyinclude>{{#vardefine:CONTENT_TYPE_LLSD|{{LSL Const|CONTENT_TYPE_LLSD|integer|6|c={{#if:{{{direct|}}}|Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml}}</code> ([[Linden Lab Structured Data]]).}}}}}}</onlyinclude>{{LSL Constant
|name={{#var:cname}}
|type={{#var:type}}
|value=6
|desc=Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml}}</code> ([[Linden Lab Structured Data]]).
|comment={{#var:comment}}
|examples=
|constants=
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_TEXT}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_HTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XHTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_ATOM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_JSON}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_FORM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_RSS}}|3={{#var:comment}}}}
|functions=
{{LSL DefineRow||[[llSetContentType]]|}}
{{LSL DefineRow||[[llHTTPResponse]]|}}
|events=
{{LSL DefineRow||[[http_request]]|}}
{{LSL DefineRow||[[http_response]]|}}
|articles={{LSL DefineRow||[[LSL HTTP server]]}}
|cat1=Chat
|cat2
|cat3
|cat4
}}

CONTENT TYPE LLSD

2024-06-19T07:44:19Z

MoiraAtropos Resident: link Linden Lab Structured Data

<onlyinclude>{{#vardefine:CONTENT_TYPE_LLSD|{{LSL Const|CONTENT_TYPE_LLSD|integer|6|c={{#if:{{{direct|}}}|Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml}}</code> ([[Linden Lab Structured Data]]).}}}}}}</onlyinclude>{{LSL Constant
|name={{#var:cname}}
|type={{#var:type}}
|value=6
|desc=Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml ([[Linden Lab Structured Data]]).}}</code>.
|comment={{#var:comment}}
|examples=
|constants=
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_TEXT}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_HTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XHTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_ATOM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_JSON}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_FORM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_RSS}}|3={{#var:comment}}}}
|functions=
{{LSL DefineRow||[[llSetContentType]]|}}
{{LSL DefineRow||[[llHTTPResponse]]|}}
|events=
{{LSL DefineRow||[[http_request]]|}}
{{LSL DefineRow||[[http_response]]|}}
|articles={{LSL DefineRow||[[LSL HTTP server]]}}
|cat1=Chat
|cat2
|cat3
|cat4
}}

CONTENT TYPE LLSD

2024-06-19T07:43:12Z

MoiraAtropos Resident: link Linden Lab Structured Data

<onlyinclude>{{#vardefine:CONTENT_TYPE_LLSD|{{LSL Const|CONTENT_TYPE_LLSD|integer|6|c={{#if:{{{direct|}}}|Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml}}</code> ([[Linden Lab Structured Data]]).}}}}}}</onlyinclude>{{LSL Constant
|name={{#var:cname}}
|type={{#var:type}}
|value=6
|desc=Sets the {{Wikipedia|Internet media type|Internet media type}} <code>{{String|Content-Type}}</code> header of any subsequent [[LSL HTTP server]] response via [[llHTTPResponse]] to <code>{{String|application/llsd+xml}}</code>.
|comment={{#var:comment}}
|examples=
|constants=
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_TEXT}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_HTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_XHTML}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_ATOM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_JSON}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_FORM}}|3={{#var:comment}}}}
{{LSL DefineRow|1=|2={{LSL Const|CONTENT_TYPE_RSS}}|3={{#var:comment}}}}
|functions=
{{LSL DefineRow||[[llSetContentType]]|}}
{{LSL DefineRow||[[llHTTPResponse]]|}}
|events=
{{LSL DefineRow||[[http_request]]|}}
{{LSL DefineRow||[[http_response]]|}}
|articles={{LSL DefineRow||[[LSL HTTP server]]}}
|cat1=Chat
|cat2
|cat3
|cat4
}}

Linden Lab Structured Data

2024-06-19T07:41:20Z

MoiraAtropos Resident: redirect to llsd

#redirect [[LLSD]]

Clothing Tutorials

2024-05-21T20:16:00Z

MoiraAtropos Resident: Removed Nicola Escher's tutorials as the website no longer exists.

{{Help|Object=*|Avatar=*}}
{{Navbox/Media}}

This page links to '''tools & tutorials for making clothing and skins''' Please add your fave tuts, remove obviated bits, and improve the usefulness of this resource!

== Clothing texture templates ==
* '''[http://static-secondlife-com.s3.amazonaws.com/downloads/textures/fashion/All_Fashion_Design_Templates.zip Linden body and clothing templates]''', for eyes, head, face, hair, upper and lower body, skirt; templates as PSD with instructions as PDF; 7 MB. Available under the [http://creativecommons.org/licenses/by/3.0/ Creative Commons 3.0 license].
* '''[http://static-secondlife-com.s3.amazonaws.com/templates/CMFF_Template_Set.zip Chip Midnight's improved clothing templates]''', ZIP of 512x512 PSD files for head, upper and lower body, skirt; 10.7 MB
* '''[http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLPages/AVUVTemplates.html Robin Wood's clothing templates]'''
* '''[http://amblabs.ath.cx/ Higher Resolution Clothing & Skin Templates]''' - By Chip Midnight. 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. (Note: The higher resolution is just to help you with your creation work in your paint program. They won't affect the resolution of your in-world clothing and skins. All outfit textures in SL are baked at 512x512 when worn on the avatar, no matter what. So, don't forget to downsize your output files to 512x512, before you upload them to SL. Otherwise, you'll just be wasting resources.)

== Second Life avatar models ==

* '''[http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip Second Life avatar meshes]''' in .obj and .cr2 format, includes assets to preview the avatar in Poser, SLCP, Photoshop Extended, etc. Available under the [http://creativecommons.org/licenses/by/3.0/ Creative Commons 3.0 license].
** Also see '''[[Mesh/Rigging Fitted Mesh|Rigging Fitted Mesh]]''' for .ma, .fbx, .blend and .dae formats with revised skeletons.

* '''[http://web.archive.org/web/20120711023730/http://abbloch.com/slAvatars_OBJ_Fixed/ Improved Second Life avatar meshes for 3D texture painting]''' - By Chosen Few. These OBJ files feature cleaned up geometry and proper UV tilings, for painting textures directly onto the models, in Mudbox, Zbrush, Photoshop Extended, etc.
**[http://pastebin.com/raw.php?i=UXmvJngs avatarSLMale.mtl]
**[http://pastebin.com/raw.php?i=cRjdGhTa avatarSLFemale.mtl]
**[http://pastebin.com/raw.php?i=Qzb6WRYV avatarSLFemale.obj]
**[http://pastebin.com/raw.php?i=inBjmuGj avatarSLMale.obj]
**[http://pastebin.com/raw.php?i=GPWGFkWq changelog.txt]
**[http://pastebin.com/raw.php?i=uwAPkDe2 LICENSE.txt]

*'''[http://www.ccccybernetics.com/avatar_databank/ Avatar Databank]''' is an extended alternative avatar mesh library that includes all avatar extremes (fat, skinny, etc...). Models are in AC3D and .obj formats with .png format 1024x1024 texture templates. For the very advanced clothing and make-up designers.

==Tutorials==

* '''[http://www.robinwood.com/Catalog/Technical/SL-Tuts/SLTutSet.html Second Life tutorials]''' - By [http://wiki.secondlife.com/wiki/User:Robin_Sojourner 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!

* '''[http://leezu-tutorials.blogspot.com/ Second Life Clothing Tutorials]''' - By LeeZu Baxter. The creator of [LeeZu!] Designs, LeeZu Baxter offers step by step tutorials to assist new builders as they face the challenges of creating their own original designs.

* '''[http://www.secondlife-shirts.com/secondlife_tutorials.htm Second Life Clothing Tutorials]''' - By Minmo Dreadlow. A Simple tutorial on how to create a t-shirt using photoshop, or turn your own clothing into secondife clothes with photoshop. Offers several free shirt fabrics as well.

* '''[http://blog.nalates.net/2012/05/20/second-life-mesh-clothes-blender-2-6-setup-2012-tutorial/ Blender 2.63a Setup Tutorial for Mesh Clothes]''' - By Nalates Urriah May 2012. Includes information on selecting the base/default avatar for future Mesh Deformer.
** [http://blog.nalates.net/?p=7381 Page 1 – Blender Install, Base Mesh Selection]
** [http://blog.nalates.net/?p=7381&page=2 Page 2 – Details on Files and Base Avatar Meshes Available]
** [http://blog.nalates.net/?p=7381&page=3 Page 3 – Deconfuser, File to Use, Actual Mesh Differences, Easy File Fix]
** [http://blog.nalates.net/?p=7381&page=4 Page 4 – Not So Easy Fix for Learning, Exporting Shapes from SL, What’s Needed]
** [http://blog.nalates.net/?p=7381&page=5 Page 5 – Getting Started, Customize Blender, GPU Kick-in, Load Mesh – Import OBJ, Setup Layers]
** [http://blog.nalates.net/?p=7381&page=6 Page 6 – Join Parts or Not, Remove Doubles, Parenting, Check Parenting, Start Weighting – Vertex Weight Painting]
** [http://blog.nalates.net/?p=7381&page=7 Page 7 – Weight Painting, Checking Weight Painting, ]
** [http://blog.nalates.net/?p=7381&page=8 Page 8 – Checking the Weighting, Exporting Collada for Second Life]

* '''[http://blog.nalates.net/2013/04/23/second-life-shape-export/ Second Life Shape Export]''' - 4/2013 - There are currently problems with all the OBJ export features for SL. '''''Only the XML exports produce correctly sized avatar exports.''''' All the importers for XML are, so far, retail products. This article shows how to get an OBJ export correctly sized in Blender, or any modeling program.

* '''[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://seshat-czeret.blogspot.com/2008/06/how-to-make-sl-clothes-in-gimp.html How to make SL clothes in the Gimp]''' - By Seshat Czeret. The first installment of a series of SL clothing tutorials, each linked to the next. The series starts with preparation, and continues with making a simple t-shirt and adding highlights and shadows. It explains why you do each step, as well as how.
:Also see '''[http://seshat-czeret.blogspot.com/2009/04/theory-of-second-life-skin-and-clothing.html The Theory of Second Life Skin and Clothing]'''. This is useful regardless of which image program you use.

* '''[http://metavirtual.us/template Cassie Clowes Clothing Videos]''' - By Cassie Clowes. Read the FAQ regarding information. Video tutorials that are high quality and with clothing templates (socks, tshirts, pants, etc)

* '''[http://mistressofdesign.wordpress.com/ Random Rambling, Tips & Tricks]''' - By Claire Hartford. Sporadically updated blog with tutorials for clothing (and skin) creation. Of particular note is the [http://mistressofdesign.wordpress.com/2011/01/19/multi-chan-hax-its-all-kinds-of-awesome-2/ video tutorial on the use of Multi Chan Hax].

* '''[http://chimerafire.wordpress.com/sl-clothing-creation-guide/ Guide to Making Second Life Clothing]''' - By Chimera Firecaster. Nicely presented, Chimera's site includes a number of fully illustrated, well researched, and up-to-date tutorials. Complementing the tutorials are free packages composed of useful tools, templates and graphic files. Also found on the site are annotated lists of SL clothing resources found elsewhere on the web.

* '''[http://www.tdtemplates.com/basictutorial/ SL Clothes Creation: The Basics (Feb 2012)]''' - By TD Templates. An introduction for beginners providing an overview of the basics when creating SL clothing and starting your fashion store in Second Life.

* '''[http://createmesh.com/ Create Mesh Video Tutorials for Maya]''' - Everything you need to know to make clothing for Second Life with Maya, from various modeling techniques, sizing around an avatar, rigging, and even draping cloth around your model. The Clothing Course is about eight hours of step-by-step instruction from leading designer, [https://wiki.secondlife.com/wiki/User:Leviathan_Flux Leviathan Flux]. The site currently offers other courses on using Maya with basic introductory tutorials and an introduction to architecture, focusing on efficient builds, LODs, lighting, and physics.

== See also ==

* '''[[Texture Tools]]'''
* '''[[Clothes design starter tips]]'''

[[Category:Tutorials]] [[Category:Creation]]

LlBase64ToString

2024-01-24T17:15:54Z

MoiraAtropos Resident: return_text=that is the {{LSLGC|Base64}} '''str''' decoded into a conventional string, interpreting the Base64-encoded bytes as UTF-8 character sequence.

{{LSL Function
|func=llBase64ToString|func_id=261|func_sleep=0.0|func_energy=10.0
|return_type=string
|p1_type=string|p1_name=str|p1_desc=Base64 string
|return_text=that is the {{LSLGC|Base64}} '''str''' decoded into a conventional string, interpreting the Base64-encoded bytes as UTF-8 character sequence.
|caveats=*If the conversion creates any unprintable characters, they are converted to spaces.
*Converts invalid characters into question marks ('?').
|spec
|examples=
<source lang="lsl2">default {
state_entry()
{
string test = llBase64ToString("U2VjcmV0Ok9wZW4=");
llSay(0,test );
}
}</source>

This can be used in {{Wikipedia|Basic access authentication|Basic Authentication}}, such as this login:
<pre>
GET / HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2)
Host: www.example.com
Authorization: Basic U2VjcmV0Ok9wZW4=
</pre>
<source lang="lsl2">llBase64ToString("U2VjcmV0Ok9wZW4="); //will return the string "Secret:Open"</source>
|helpers
|related
|also_header
|also_events
|also_functions=
{{LSL DefineRow||[[llXorBase64]]|Article also discusses xor based Cryptography.}}
{{LSL DefineRow||[[llStringToBase64]]|}}
{{LSL DefineRow||[[llBase64ToInteger]]|}}
|also_articles=
{{LSL DefineRow||{{LSLGC|Base64}}|}}
|also_footer
|notes
|mode
|deprecated
|cat1=Base64
|cat2=String
|cat3
|cat4
}}

LlStringLength

2024-01-24T13:13:53Z

MoiraAtropos Resident: *To quickly find out the number of bytes (in UTF-8), you can use llStringToBase64 (see also snippet there)

{{LSL_Function
|func_id=128|func_sleep=0.0|func_energy=10.0
|func=llStringLength|return_type=integer|p1_type=string|p1_name=str
|func_footnote
|func_desc
|return_text=that is the number of characters in '''str'''.
|spec
|caveats=
*The index of the last character is not equal to the string length.
**Character indexs start at zero (the index of the first character is zero).
*llStringLength() gets the number of characters, not bytes
**LSL-2 sees all strings as UTF-8
**LSL-Mono sees all string as UTF-16
**Both UTF-8 and UTF-16 use multibyte characters
*Some communication functions (e.g. llHTTPResponse) are limited by number of Bytes, and work with UTF-8 strings
**To quickly find out the number of bytes (in UTF-8), you can use [[llStringToBase64]] (see also snippet there)
|constants
|examples=
<source lang="lsl2">
// assumptions:
// object name: LSLWiki
// script name: _lslwiki

default
{
state_entry()
{
string HowLongAmI = "123";
integer strlen = llStringLength(HowLongAmI);
llOwnerSay( "'" + HowLongAmI + "' has " +(string) strlen + " characters.");
// The owner of object LSLWiki will hear
// LSLWiki: '123' has 3 characters.
}
}

</source>

|helpers
|also_functions={{LSL DefineRow||[[llGetListLength]]|}}
|also_events
|also_tests
|also_articles
|notes
|permission
|negative_index
|sort=StringLength
|cat1=String
|cat2
|cat3
|cat4
}}

LlHTTPRequest

2023-12-23T20:02:56Z

MoiraAtropos Resident: When the response is received, a http_response event is raised.

{{LSL_Function
|func=llHTTPRequest
|func_id=230
|func_energy=10.0
|func_sleep=0.0
|func_desc=Sends an HTTP request to the specified URL with the body of the request and parameters. When the response is received, a [[http_response]] event is raised.
|sort=HTTPRequest
|func_footnote=
|return_type=key|return_subtype=handle
|return_text=identifying the HTTP request made.
|p1_type=string|p1_name=url|p1_desc=A valid HTTP/HTTPS URL.
|p2_type=list|p2_subtype=instructions|p2_name=parameters|p2_desc=configuration parameters, specified as HTTP_* flag-value pairs
[ parameter1, value1, parameter2, value2, . . . parameterN, valueN]
|p3_type=string|p3_name=body|p3_desc=Contents of the request.
|constants={{LSL_Constants_HTTP}}
{{LSL_Constants/HTTP_Headers}}
{{LSL_Extended_Error_HTTP}}
|spec=
|caveats=
*Spaces, control characters, and other characters that are not allowed in URLs will cause a run time error.
*The corresponding [[http_response]] event will be triggered in all scripts in the [[prim]], not just in the requesting script.
*Requests must fully complete after 60 seconds, or else the response will be thrown away and the [[http_response]] status code will be 499.
*The response body is limited to 2048 bytes by default, see [[HTTP_BODY_MAXLENGTH]] above to increase it. If the response is longer, it will be truncated.
*The request body size (e.g., of POST and PUT requests) is limited only by available script memory. Scripts can hold at most 32k characters in a string, under [[Mono]], as characters are two bytes each, so, scripts cannot upload over 32k UTF-8 characters
*Cannot be used to load textures or images from the internet, for more information see [[Web Textures]].
*If the accessed site is relying on the LSL script to report [[L$]] transactions, then it '''must''' check the <code>X-SecondLife-Shard</code> header to see if the script is running on the beta grid.
* Some servers will return a <code>405</code> error if you send POST to a file that can't accept metadata, such as a text or HTML file. Make sure you use the GET method to ensure success in any environment.
* While the HTTP status code from the server is provided to the script, redirect codes such as <code>302</code> will result in the redirect being automatically and transparently followed ONLY IF the [[HTTP_METHOD]] is GET, with the resulting response being returned. If the [[HTTP_METHOD]] is anything other than GET then you'll get back an [[http_response]] with a status code of <code>302</code>, but without any way to view the headers, you can't know where you were being redirected to unless that was also included in the body.
* The following applies when making a request to a script using HTTP-In:
**When appending a query string to a cap URL there '''MUST''' be a trailing slash between the cap guid and the query string token <code>"?"</code>. For example: [https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322?arg=gra {{HoverTextStyle|style=color:green;|<nowiki>https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322</nowiki>|2={{String|x-script-url}} = {{String|https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322}}}}?{{HoverTextStyle|style=color:red;|1=arg=gra|2={{String|x-query-string}} = {{String|1=arg=gra}}}}] will return a 500 HTTP status {{Wikipedia|List_of_HTTP_status_codes#5xx_Server_Error|Server Error code}}, but [https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/?arg=gra {{HoverTextStyle|style=color:green;|<nowiki>https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322</nowiki>|2={{String|x-script-url}} = {{String|https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322}}}}{{HoverTextStyle|style=color:blue;|/|2={{String|x-path-info}} = {{String|/}}}}?{{HoverTextStyle|style=color:red;|1=arg=gra|2={{String|x-query-string}} = {{String|1=arg=gra}}}}] will succeed.
* <code>X-SecondLife-Owner-Name</code> may return <code>"(Loading...)"</code> instead of owner name (still true, 30th of March, 2022)
* Requests made at approx 0625 SLT may fail with a <code>503</code> status code, with <code>"ERROR: The requested URL could not be retrieved"</code>, and <code>"(111) Connection refused"</code> in the body of the response. This has been confirmed as expected behavior by Kelly, due to the nightly maintenance and log rotation. It does reliably impact object to object HTTP at that time, and quite probably may impact object to/from web around the same time. The interruption in service is fairly brief, and the precise timing may vary as LL adjust their nightly maintenance processes, or due to server load.
* Use <code>HTTP_MIMETYPE</code> to set the <code>Content-Type</code> header. Attempts to use <code>HTTP_CUSTOM_HEADER</code> to set it will cause a runtime script error.
* If the origin server does not include a content-type header in its response, LSL will attempt to treat the incoming data as "text/plain; charset=utf-8". This behavior diverges from [https://datatracker.ietf.org/doc/html/rfc2616#section-7.2.1 RFC 2616].

==== Throttles ====

The LSL function [[llHTTPRequest]] is throttled in two ways: by prim and owner. All group-owned objects are considered together in the same throttle.

The current limits are 25 requests in 20 seconds for each object, and 1000 in 20 seconds for each owner. These may change in the future if needed to prevent problems in regions.

It is possible for a large collection of objects or scripts to make many calls to [[llHTTPRequest]] and reach this throttle. When a script calls [[llHTTPRequest]] with the throttle blocking the request, it will return [[NULL_KEY]].

The calling script must check for the [[NULL_KEY]] result and react properly for the script and object to function correctly. Some things to consider:

* Pause further requests until the throttle clears
* Do not make any additional [[llHTTPRequest]] calls until enough time has passed for the throttle to reset. They will fail and continue to return [[NULL_KEY]] otherwise.
* Once reached, the throttles will remain in effect as long as requests continue, but will clear if there is a silent period with no requests at least twice the throttle interval, in this case 2 * 20 or 40 seconds.‎

:Consider how a group of objects behaves. Developers must consider how multiple objects will interact and how that will affect clearing the throttle.‎

:The [[llHTTPRequest]] throttle is most likely to be an issue with a large number of objects in a region making requests. To clear the throttle fastest, when an object encounters the throttle, it should broadcast a region-wide chat message to other objects informing them of the event and stopping their requests. If those objects continue making requests, those requests will fail and just prolong recovery.‎

:If an object waits and still gets a failure, it may be a good idea to increase the time before the next request and/or add a small random value to the wait time. This may help prevent failures caused by large groups of objects acting nearly in unison.

* Object requests are throttled at approximately 25 requests per 20 seconds. This is to support a sustained rate of one per second or a maximum burst of up to 25 every 40 seconds (twice the interval for maximum burst), smaller bursts are recommended.
* [[NULL_KEY]] is returned if the request is throttled.
* See [http://forums-archive.secondlife.com/139/72/108960/1.html this thread] and [http://forums-archive.secondlife.com/139/2c/109571/1.html this thread] for older details.
----
|examples=

*[[Writing Headers and HTTP POST Body to a File]]

<syntaxhighlight lang="lsl2">
key http_request_id;

default
{
state_entry()
{
http_request_id = llHTTPRequest("url", [], "");
}

http_response(key request_id, integer status, list metadata, string body)
{
if (request_id != http_request_id) return;// exit if unknown

vector COLOR_BLUE = <0.0, 0.0, 1.0>;
float OPAQUE = 1.0;

llSetText(body, COLOR_BLUE, OPAQUE);
}
}
</syntaxhighlight>

Example PHP test script:
<syntaxhighlight lang="php">
<?php header("content-type: text/plain; charset=utf-8"); ?>
Headers received:
<?php

/**
* @author Wouter Hobble
* @copyright 2008
*/

foreach ($_SERVER as $k => $v)
{
if( substr($k, 0, 5) == 'HTTP_')
{
print "\n". $k. "\t". $v;
}
}
?>
</syntaxhighlight>

Example PHP wrapper script both capturing Apache headers and global methods
<syntaxhighlight lang="php">
<?php
// Author Waster Skronski.
// General Public License (GPL).
// Mind that some headers are not included because they're either useless or unreliable.

$USE_APACHE_HEADERS = TRUE;// switch to false if you need CGI methods

if ($USE_APACHE_HEADERS)
{
$headers = apache_request_headers();
$objectgrid = $headers["X-SecondLife-Shard"];
$objectname = $headers["X-SecondLife-Object-Name"];
$objectkey = $headers["X-SecondLife-Object-Key"];
$objectpos = $headers["X-SecondLife-Local-Position"];
$ownerkey = $headers["X-SecondLife-Owner-Key"];
$ownername = $headers["X-SecondLife-Owner-Name"];
$regiondata = $headers["X-SecondLife-Region"];
$regiontmp = explode ("(",$regiondata); // cut coords off
$regionpos = explode (")",$regiontmp[1]);
$regionname = substr($regiontmp[0],0,-1); // cut last space from region name
} else {
$db = $GLOBALS;
$headers = $db['$_ENV'];
$objectgrid = $headers["HTTP_X_SECONDLIFE_SHARD"];
$objectname = $headers["HTTP_X_SECONDLIFE_OBJECT_NAME"];
$objectkey = $headers["HTTP_X_SECONDLIFE_OBJECT_KEY"];
$ownerkey = $headers["HTTP_X_SECONDLIFE_OWNER_KEY"];
$objectpos = $headers["HTTP_X_SECONDLIFE_LOCAL_POSITION"];
$ownername = $headers["HTTP_X_SECONDLIFE_OWNER_NAME"];
$regiondata = $headers["HTTP_X_SECONDLIFE_REGION"];
$regiontmp = explode ("(",$regiondata);
$regionpos = explode (")",$regiontmp[1]);
$regionname = substr($regiontmp[0],0,-1);
}
?>
</syntaxhighlight>

Example wrapper script for GoDaddy.com Linux PHP servers (fix made by Thomas Conover):
<syntaxhighlight lang="php">
<?php
// FETCH HEADERS START

if (!function_exists('apache_request_headers'))
{
function apache_request_headers() {
foreach($_SERVER as $key=>$value) {
if (substr($key,0,5)=="HTTP_") {
$key=str_replace(" ","-",ucwords(strtolower(str_replace("_"," ",substr($key,5)))));
$out[$key]=$value;
}else{
$out[$key]=$value;
}
}
return $out;
}
}
// Mind that some headers are not included because they're either useless or unreliable (e.g. X-Secondlife-Local-Position)
$headers = apache_request_headers();
$objectgrid = $headers["X-Secondlife-Shard"];
$objectname = $headers["X-Secondlife-Object-Name"];
$objectkey = $headers["X-Secondlife-Object-Key"];
$objectpos = $headers["X-Secondlife-Local-Position"];
$ownerkey = $headers["X-Secondlife-Owner-Key"];
$ownername = $headers["X-Secondlife-Owner-Name"];
$regiondata = $headers["X-Secondlife-Region"];
$regiontmp = explode ("(",$regiondata); // cut coords off
$regionname = substr($regiontmp[0],0,-1); // cut last space from region name
$regiontmp = explode (")",$regiontmp[1]);
$regionpos = $regiontmp[0];

// FETCH HEADERS END
?>
</syntaxhighlight>

|helpers
|also_header
|also_events={{LSL DefineRow||[[http_response]]}}
|also_functions={{LSL DefineRow||[[llEscapeURL]]}}
{{LSL DefineRow||[[llHTTPResponse]]}}
{{LSL DefineRow||[[llUnescapeURL]]}}
|also_articles={{LSL DefineRow||[[Simulator IP Addresses]]}}
|also_footer
|notes=If for some reason while using the function [[llHTTPRequest]] or the event [[http_response]] you are unable to parse a known good RSS feed or some other form of web contents, you will need to work around it outside of Second Life. This is unlikely to change in the near future since checking the headers requires more overhead at the simulator level.

You may find that some web servers return either a null or a nonsensical result when [[llHTTPRequest]] is used, even though the same URL in a PC web browser returns the expected result. This may be due to the fact that the [[llHTTPRequest]] User Agent string is not recognised by some web servers as it does not contain <code>"Mozilla"</code>, which would identify it as a web browser instead of, for example, a [https://www.shoutcast.com/ Shoutcast] or an RSS client. This is also true when the PHP script relies on [https://www.php.net/manual/en/reserved.variables.cookies.php $_COOKIE]. Neither can the function [[llHTTPRequest]] set a cookie nor can the event [[http_request]] retrieve them.

CGI environments may place the headers into variables by capitalizing the entire name, replacing dashes with underscores, and prefixing the name with <code>HTTP_</code>, e.g. <code>HTTP_X_SECONDLIFE_OBJECT_NAME</code>. PHP <code>$_SERVER</code> variables do this as well.

Apache can include the headers in its logs, using the <code>CustomLog</code> and <code>LogFormat</code> directives. See [https://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats the docs] for details on the syntax.

|mode
|deprecated
|permission
|cat1=HTTP
|cat2=XML-RPC
|cat3=Communications
|cat4=HTTP/Client
|haiku={{Haiku|Shining break of day|Lov'ly web, carefully spun|Of bytes and prims}}
}}

LlDialog

2023-12-23T02:01:52Z

MoiraAtropos Resident: buttonLabel() function, because the original snippet sometimes fails for unicode inputs.

{{LSL_Function
|func=llDialog
|sort=Dialog
|func_id=247|func_sleep=1.0|func_energy=10.0
|inject-2=
{{Issues/VWR-17064}}
{{Issues/VWR-14537}}
{{Issues/SVC-1815}}
{{Issues/SCR-43}}
{{Issues/STORM-1718}}
{{LSL_Function/avatar|avatar|sim=*}}
{{LSL_Function/chat|channel|message|dialog=dialog box}}
|p1_type=key|p1_name=avatar|p1_desc
|p2_type=string|p2_name=message|p2_desc
|p3_type=list|p3_name=buttons|p3_desc=button labels
|p4_type=integer|p4_name=channel|p4_desc
|func_desc=Shows a dialog box in the lower right corner of the {{LSLP|avatar}}'s screen (upper right in Viewer 1.x) with a {{LSLP|message}} and choice {{LSLP|buttons}}, as well as an ignore button. This has many uses ranging from simple message delivery to complex menu systems.
|func_footnote=When a button is pressed, the {{LSLP|avatar}} says the text of the button label on {{LSLP|channel}}.<br/>The position where the chat is generated is where the root prim of the dialog generating object was when the dialog button was pressed.
|spec
|caveats=
*This function '''only''' opens a dialog box. The script must then also register a listener on the same ''channel'' using [[llListen]] and have a [[listen]] event handler to receive the response.
*There is no way by script to kill a dialog box.
*There is no way for the script to detect if the user clicked the small <code>["Ignore"]</code> button (no chat is generated as a result of pressing this button).
*There is no way to distinguish the input from a dialog box and regular chat made by the same user.
**It is important to expect that the response may not be one of the buttons.
*In most cases, the listener will be in the same script as the llDialog, however if not, the distance between the root prim of the [[listen]]ing object and the dialog generating prim becomes a factor. If this distance is greater than 20 meters when a button is pressed, the response will not be heard. See [[#Limits]].
**This limitation affects attachments too if the wearer moves more than 20 meters from where the listener is located. See [[#Limits]].
**If the [[listen]]er resides in the same script that created the dialog, then the dialog button is heard sim-wide.
*By default, only one dialog can be displayed per object in the Second Life Viewer. This can be overridden by the [[Debug_Settings|ScriptDialogLimitations debug setting]] in the Viewer.
----
*The '''dialog response''' (the generated chat) has its in world location at the '''root prim's global position'''.
: It can generate a listen event within 20 meters from that position.
*The listening location for a child prim in the object is either at the child prim's location or at the root prim's location
: see bugtrace JIRA [https://jira.secondlife.com/browse/SCR-43 SCR-43]

===<tt>message</tt> limits===
*{{LSLP|message}} must be fewer than 512 bytes in length and be not empty. If it is empty, [[llDialog]] will shout <code>"[[llDialog]]: must supply a message"</code> on the [[DEBUG_CHANNEL]]. If you want to create an empty message, however, you can do it legally by using a line feed as your message, as in <source lang="lsl2">llDialog(avatar_key," \n",button_list,dialog_channel);</source> If the message length is greater than or equal to 512 bytes, it shouts (again on the [[DEBUG_CHANNEL|debug channel]]): <code>"[[llDialog]]: message too long, must be less than 512 characters"</code>; in both instances, the dialog box will not be created for {{LSLP|avatar}}.
*The client only displays 20 lines of {{LSLP|message}} at a time, not counting the top line containing the owner and name of the object. If there are more than 20 lines the dialog displays a scroll bar. See [[#Appearance]].

===<tt>buttons</tt> limits===
*If {{LSLP|buttons}} is an empty list, it will default to as if it were <code>["OK"]</code>
*Buttons named "Client_Side_Mute" or "Client_Side_Ignore" will be interpreted by the viewer as if the user click the special "Mute" or "Ignore" buttons, respectively.
**Prior to [[Release_Notes/Second_Life_Release/3.3.1|SL viewer 3.3.1]] (released in 2012) the viewer treated the buttons with values of "Mute" and "Ignore" as being equivalent to the dialogs special buttons "Mute" and "Ignore". This was changed as a result of {{JIRA|STORM-1718}}. Some very old versions of some viewer, especially those with a V1-style interface, could still have this old behavior and should be tested.
**If you need a button in your menu that will collide with one of these special values, please consider adding spaces in the button name (e.g. <code>[" Ignore "]</code>).
*An error will be shouted on [[DEBUG_CHANNEL]], if...
**there are more than 12 buttons.
**any list item is not a string.
**any list item string length (measured in bytes, using UTF-8 encoding) is zero or greater than 24.
***In other words, a button's text when encoded as UTF-8 cannot be longer than 24 bytes or a empty string.
***The following function can be used to truncate the string without giving an error: <source lang="lsl2">
string buttonLabel(string label) { //crop to valid UTF-8 of at most 24 bytes
string encoded = llStringToBase64(label);
if (llStringLength(encoded) <= 32) {
return label; }
integer end = 31;
//note: if we don't do this, llBase64ToString might add a "?" for the character we cut in half
string tailEnc = llGetSubString(encoded, 28, 33);
integer tail = llBase64ToInteger(tailEnc);
while ((tail & 0xc0) == 0x80) {
if (end % 4 == 1) {
end -= 2; }
else {
end--; }
tail = tail >> 8; }
return llBase64ToString(llGetSubString(encoded, 0, end)); }</source>
*The client will not display all the characters of a button if the text is wider than the text space of the button. See [[#Appearance]].
*If the script generates button labels from outside sources like inventory or object names, take care to avoid the special string <code>"!!llTextBox!!"</code>. This text, used as any button label, will cause [[llDialog]] to behave as [[llTextBox]] instead.
|examples=
<source lang="lsl2">
// When the prim is touched, give the toucher the option of killing the prim.

integer gListener; // Identity of the listener associated with the dialog, so we can clean up when not needed

default
{
touch_start(integer total_number)
{
// Kill off any outstanding listener, to avoid any chance of multiple listeners being active
llListenRemove(gListener);
// get the UUID of the person touching this prim
key user = llDetectedKey(0);
// Listen to any reply from that user only, and only on the same channel to be used by llDialog
// It's best to set up the listener before issuing the dialog
gListener = llListen(-99, "", user, "");
// Send a dialog to that person. We'll use a fixed negative channel number for simplicity
llDialog(user, "\nDo you wish this prim to die?", ["Yes", "No" ] , -99);
// Start a one-minute timer, after which we will stop listening for responses
llSetTimerEvent(60.0);
}
listen(integer chan, string name, key id, string msg)
{
// If the user clicked the "Yes" button, kill this prim.
if (msg == "Yes")
llDie();
// The user did not click "Yes" ...
// Make the timer fire immediately, to do clean-up actions
llSetTimerEvent(0.1);
}
timer()
{
// Stop listening. It's wise to do this to reduce lag
llListenRemove(gListener);
// Stop the timer now that its job is done
llSetTimerEvent(0.0);// you can use 0 as well to save memory
}
}
</source>
{{LSL Tip|Please make sure that you close open listeners where possible. You'll make the Second Life experience so much better when paying attention to details here.}}
{{LSL Tip|There are no built-in submenus nor pagination (like in a list with "previous" and "next") when using [[llDialog]]. You simply get one page with a max of 12 buttons, that's it. If you want a different dialog menu layout (other info and/or other buttons), you'll have to build that functionality into your script as the example below demonstrates. }}
<source lang="lsl2">
string mainMenuDialog = "\nWhich settings would you like to access?\nClick \"Close\" to close the menu.\n\nYou are here:\nMainmenu";
list mainMenuButtons = ["sub 01", "sub 02", "Close"];

string subMenu_01_Dialog = "\nClick \"Close\" to close the menu.\nClick \"-Main-\" to return to the main menu.\n\nYou are here:\nMainmenu > sub 01";
list subMenu_01_Buttons = ["action 01a", "action 01b", "Close", "-Main-"];

string subMenu_02_Dialog = "\nClick \"Close\" to close the menu.\nClick \"-Main-\" to return to the main menu.\n\nYou are here:\nMainmenu > sub 02";

list subMenu_02_Buttons = ["action 02a", "action 02b", "Close", "-Main-"];

integer dialogChannel;
integer dialogHandle;

open_menu(key inputKey, string inputString, list inputList)
{
dialogChannel = (integer)llFrand(DEBUG_CHANNEL)*-1;
dialogHandle = llListen(dialogChannel, "", inputKey, "");
llDialog(inputKey, inputString, inputList, dialogChannel);
llSetTimerEvent(30.0);
}

close_menu()
{
llSetTimerEvent(0.0);// you can use 0 as well to save memory
llListenRemove(dialogHandle);
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

touch_start(integer total_number)
{
key id = llDetectedKey(0);
// Ensure any outstanding listener is removed before creating a new one
close_menu();
open_menu(id, mainMenuDialog, mainMenuButtons);
}

listen(integer channel, string name, key id, string message)
{
if(channel != dialogChannel)
return;

close_menu();

if(message == "-Main-")
open_menu(id, mainMenuDialog, mainMenuButtons);

else if(message == "sub 01")
open_menu(id, subMenu_01_Dialog, subMenu_01_Buttons);

else if(message == "sub 02")
open_menu(id, subMenu_02_Dialog, subMenu_02_Buttons);

else if (message == "action 01a")
{
//do something
open_menu(id, subMenu_01_Dialog, subMenu_01_Buttons);
}
else if (message == "action 01b")
{
//do something else

//maybe not re-open the menu for this option?
//open_menu(id, subMenu_01_Dialog, subMenu_01_Buttons);
}
else if (message == "action 02a")
{
//do something
open_menu(id, subMenu_02_Dialog, subMenu_02_Buttons);
}
else if (message == "action 02b")
{
//do something else
open_menu(id, subMenu_02_Dialog, subMenu_02_Buttons);
}
}

timer()
{
close_menu();
}
}
</source>
|helpers=<source lang="lsl2">//Compact function to put buttons in "correct" human-readable order
integer channel;

list order_buttons(list buttons)
{
return llList2List(buttons, -3, -1) + llList2List(buttons, -6, -4)
+ llList2List(buttons, -9, -7) + llList2List(buttons, -12, -10);
}

default
{
state_entry()
{ // Create random channel within range [-1000000000,-2000000000]
channel = (integer)(llFrand(-1000000000.0) - 1000000000.0);

llListen(channel,"", "","");
}

touch_start(integer total_number)
{
llDialog(llDetectedKey(0),"\nPlease choose an option:\n",
order_buttons(["1", "2", "3", "4", "5", "6", "7", "8", "9", "10"]),channel);
}

listen(integer _chan, string _name, key _id, string _option)
{
llSay(0, _name + " selected option " + _option);
}
}</source>
<source lang="lsl2">
list make_ordered_buttons(integer input)
{
string output;

if (input == 12) output = "10, 11, 12, 7, 8, 9, 4, 5, 6, 1, 2, 3";
else if (input == 11) output = "10, 11, 7, 8, 9, 4, 5, 6, 1, 2, 3";
else if (input == 10) output = "10, 7, 8, 9, 4, 5, 6, 1, 2, 3";
else if (input == 9) output = "7, 8, 9, 4, 5, 6, 1, 2, 3";
else if (input == 8) output = "7, 8, 4, 5, 6, 1, 2, 3";
else if (input == 7) output = "7, 4, 5, 6, 1, 2, 3";
else if (input == 6) output = "4, 5, 6, 1, 2, 3";
else if (input == 5) output = "4, 5, 1, 2, 3";
else if (input == 4) output = "4, 1, 2, 3";
else if (input == 3) output = "1, 2, 3";
else if (input == 2) output = "1, 2";
else if (input == 1) output = "1";

// when we want to return [] avoid returning [""] here

if (output == "") return [];
/* else convert output */ return llCSV2List(output);
}

// Usage:

llDialog(id, "dialog message", make_ordered_buttons(5), -37812);

// Output:

// - - -
// - - -
// - [ 4 ] [ 5 ]
// [ 1 ] [ 2 ] [ 3 ]
</source>
=== Helper Functions ===
{{{!}}
{{LSL DefineRow||[[User:Void_Singer/Functions#uDlgBtnPagList|uDlgBtnPagList]]|Compact Pagination for [[llDialog]] lists, remenu, and multi-user support}}
{{!}}}
|constants={{#vardefine:constants_nb}}
{{{!}}
{{!}}- valign="top"
{{!}}
{{{!}}{{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! colspan="4" {{!}} Button Order
{{!}}-
{{!}}9  
{{!}}10
{{!}}11
{{!}}-
{{!}}6
{{!}}7
{{!}}8  
{{!}}-
{{!}}3
{{!}}4
{{!}}5
{{!}}-
{{!}}0
{{!}}1
{{!}}2
{{!}}}
{{!}}
{{!}}}
|related
|notes=
To use dialog boxes to make menu systems, see [[Dialog Menus|Dialog Menus: A step by step guide]] (aimed at learners).

===Tips===
It is a good idea to use a very negative channel (if never more negative than the most negative 32-bit integer that is -2,147,483,648), ''e.g.'',
<source lang="lsl2">// Create random channel within range [-1000000000,-2000000000]
integer channel = (integer)(llFrand(-1000000000.0) - 1000000000.0);

llDialog(llDetectedKey(0), "Please choose one of the below options:",
["Yes", "No", "0", "1"], channel);</source>
Negative channels are popular for script communications because for years the standard SL client was unable to chat directly on those channels. However, since late 2016 both third party and the Linden Lab viewer can use negative channels from the chat bar. Previously, the only way for viewers to use negative channels prior to [[llTextBox]] was to use [[llDialog]], which was limited to 24 bytes.

You can be reasonably confident that all of your scripted objects have a unique chat channel with this small function:

<source lang="lsl2">integer dialog_channel; // top of script in variables

integer channel() { // top of script in functions
return (integer)("0x"+llGetSubString((string)llGetKey(),-8,-1));
}

dialog_channel = channel(); // somewhere in actual script execution, such as state_entry()</source>

'''Note:''' Since this function uses public information to generate the channel number it should by no means considered secret.

The preceding code can produce both positive and negative channels, depending on the 8th to last character of the key.
The following examples will always produce negative channels:-
<source lang="lsl2">
gChannel = 0x80000000 | (integer)("0x"+(string)llGetKey());
gChannel = 0x80000000 | (integer)("0x"+(string)llGetOwner());
</source>

This next version returns a channel number between -1073741823 (0xBFFFFFFF) and -2147483648 (0x80000000). It is also only one line of code.
<source lang="lsl2">privchan = ((integer)("0x"+llGetSubString((string)llGetKey(),-8,-1)) & 0x3FFFFFFF) ^ 0xBFFFFFFF;</source>

===Appearance===

If {{LSLP|message}} requires more than 8 lines, a vertical scroll bar will appear in the dialog.
: In viewer 3 there is no scroll bar, only the 512 chars message limit is effective, so you may show more than 40 short lines in the message
: Too many lines will hide some of the buttons or all of them outside the window though

The message text can be formatted somewhat using "\n" (for newline) and "\t" (for tab). If URLs are in the text, they will appear as clickable links, and some [[Viewer URI Name Space|viewer application URLs]] will receive special formatting. (Clickable links were not available before Viewer 2.) You can do nothing though to influence the font face, size or weight.

There is no way to change the actual size of the dialog, nor change its color.

The average number of characters that can be displayed on a dialog line is about 35 characters per line in ASCII7 characters. It depends upon the width of the characters, the viewer version, and font settings.

The number of characters that can be displayed in a button depends upon the width of the characters. You should expect around 10 chars, give or take, not the full 24 in the button definition. The full button definition IS said, up to 24 chars, into the chat channel even though fewer characters may be displayed in the button itself.

===Limits===

My testing shows the a Dialog box now works anywhere in the same Region as the object OR any region it hands you off to (e.g. the region you teleport to). It will not work for any subsequent hand offs. I have tested this with teleport only, I haven't tested it walking between regions.

I've tested from the next SIM with an Alt, and from 2 SIMs away myself. Both worked without restriction apart from some lag on the messages. (OQ).

|also_events=
{{LSL DefineRow||[[listen]]|}}
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llTextBox]]|}}
{{LSL DefineRow||[[llRegionSay]]|}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to the specified user}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only}}
|also_tests
|also_articles=
{{LSL DefineRow||[[Dialog Menus|Dialog Menus: A step by step guide]]|A walk through of the entire dialog menu process (aimed at learners).}}
|cat1=Chat
|cat2=Communications
|cat3=Dialog
|cat4
|haiku={{Haiku|click here click there. But,|read the options carefully|you might get a shock.}}
}}

LlList2ListStrided

2023-10-25T19:46:14Z

MoiraAtropos Resident: /* Starting at an offset */ If you want every second (or third, etc.) item in each stride returned, rather than the first, use llList2ListSlice instead.

{{LSL_Function
|inject-2={{LSL_Function/negative index|true|start|end|noExclude=*}}{{LSL_Function/stride|stride}}
|func_id=198|func_sleep=0.0|func_energy=10.0
|func=llList2ListStrided
|return_type=list
|p1_type=list|p1_name=src
|p2_type=integer|p2_name=start
|p3_type=integer|p3_name=end
|p4_type=integer|p4_name=stride
|func_footnote
|func_desc
|return_text=of all the entries in the [[List#Strided_lists|strided list]] whose index is a multiple of {{LSLP|stride}} in the range {{LSLP|start}} to {{LSLP|end}}.
|spec
|caveats
|constants
|examples=
<source lang="lsl2">list mylist = [0,1,2,3,4,5,6];
list result_a = llList2ListStrided(mylist,0,-1,2); //start at first item in list, go to the end, return every 2nd item
//result_a == [0,2,4,6]

list result_b = llList2ListStrided(mylist,1,-1,2); //start at second item in list, go to the end, return every 2nd item
//result_b == [2,4,6]

list result_c = llList2ListStrided(mylist,2,-1,2); //start at third item in list, go to the end, return every 2nd item
//result_c == [2,4,6]</source>

<source lang="lsl2">list menu = ["1", "one", "2", "two", "3", "three"];
default
{
state_entry()
{
llListen(10, "", llGetOwner(), "");
}
touch_start(integer detected)
{
list buttons = llList2ListStrided(menu, 0, -1, 2);
llDialog(llDetectedKey(0), "choose a number", buttons, 10);
}
listen(integer channel, string obj, key id, string message)
{
integer index = llListFindList(menu, [message]);
if (index != -1)
{
llOwnerSay("you chose " + llList2String(menu, index + 1) + " (" + message + ")");
}
}
}</source>

|helpers
|also_functions=
{{LSL DefineRow||[[llList2ListSlice]]|}}

|also_events
|also_tests
|also_articles
|notes=
=== Starting at an offset ===
If you want every second (or third, etc.) item in each stride returned, rather than the first, use [[llList2ListSlice]] instead.
|permission
|negative_index
|haiku={{Haiku|Ah, the strided list.|C had structs in the '70s.|Someday, we will, too...}}
|sort=List2ListStrided
|cat1=List
|cat2
|cat3
|cat4
}}

LlList2ListStrided

2023-10-25T19:40:40Z

MoiraAtropos Resident: hint on llList2ListSlice() and replace workarounds emulating it

{{LSL_Function
|inject-2={{LSL_Function/negative index|true|start|end|noExclude=*}}{{LSL_Function/stride|stride}}
|func_id=198|func_sleep=0.0|func_energy=10.0
|func=llList2ListStrided
|return_type=list
|p1_type=list|p1_name=src
|p2_type=integer|p2_name=start
|p3_type=integer|p3_name=end
|p4_type=integer|p4_name=stride
|func_footnote
|func_desc
|return_text=of all the entries in the [[List#Strided_lists|strided list]] whose index is a multiple of {{LSLP|stride}} in the range {{LSLP|start}} to {{LSLP|end}}.
|spec
|caveats
|constants
|examples=
<source lang="lsl2">list mylist = [0,1,2,3,4,5,6];
list result_a = llList2ListStrided(mylist,0,-1,2); //start at first item in list, go to the end, return every 2nd item
//result_a == [0,2,4,6]

list result_b = llList2ListStrided(mylist,1,-1,2); //start at second item in list, go to the end, return every 2nd item
//result_b == [2,4,6]

list result_c = llList2ListStrided(mylist,2,-1,2); //start at third item in list, go to the end, return every 2nd item
//result_c == [2,4,6]</source>

<source lang="lsl2">list menu = ["1", "one", "2", "two", "3", "three"];
default
{
state_entry()
{
llListen(10, "", llGetOwner(), "");
}
touch_start(integer detected)
{
list buttons = llList2ListStrided(menu, 0, -1, 2);
llDialog(llDetectedKey(0), "choose a number", buttons, 10);
}
listen(integer channel, string obj, key id, string message)
{
integer index = llListFindList(menu, [message]);
if (index != -1)
{
llOwnerSay("you chose " + llList2String(menu, index + 1) + " (" + message + ")");
}
}
}</source>

|helpers
|also_functions=
{{LSL DefineRow||[[llList2ListSlice]]|}}

|also_events
|also_tests
|also_articles
|notes=
=== Starting at an offset ===
If you want the items starting at index {{LSLP|start}} returned, rather than starting at the next multiple of {{LSLP|stride}}, use [[llList2ListSlice]] instead.
|permission
|negative_index
|haiku={{Haiku|Ah, the strided list.|C had structs in the '70s.|Someday, we will, too...}}
|sort=List2ListStrided
|cat1=List
|cat2
|cat3
|cat4
}}

User:Fred Gandt/Scripts/Functions

2023-10-25T19:19:39Z

MoiraAtropos Resident: /* StrideOfList */ Note: this functionality is no directly provided by llList2ListSlice.

{{User:Fred Gandt/Template|content=

== Functions ==
A collection of functions that perform defined actions. Things we can't use one [[:Category:LSL_Functions|Linden Library function]] to do.

=== GetUniqueListEntries ===
Feed a list in and get out a list which contains no duplicate entries. Fast.

<syntaxhighlight lang="lsl2">// V1 //

list GetUniqueListEntries(list src)
{
integer index = 0;
list output = [];
list entry = [];
do
{
output += (entry = llList2List(src, 0, 0));
src = llDeleteSubList(src, 0, 0);
while((index = llListFindList(src, entry)) != -1)
src = llDeleteSubList(src, index, index);
}
while(llGetListLength(src));
return output;
}

// Usage Example //

list source = ["How", "much", "wood", "would", "a", "woodchuck", "chuck", "if", "a", "woodchuck", "could", "chuck", "wood", "?"];

default
{
state_entry()
{
llOwnerSay(llDumpList2String(GetUniqueListEntries(source), ", "));
// Return == "How, much, wood, would, a, woodchuck, chuck, if, could, ?"
}
}</syntaxhighlight>

=== MultiListReplace ===
Replace entries in a list with other entries.

<syntaxhighlight lang="lsl2">// V1 //

list MultiListReplace(list src, list thisnthats)
{
integer index = 0;
integer lc = 0;
integer ll = llGetListLength(thisnthats);
do
{
list this = llList2List(thisnthats, lc, lc);
++lc;
while((index = llListFindList(src, this)) != -1)
src = llListReplaceList(src, llList2List(thisnthats, lc, lc), index, index);
}
while((++lc) < ll);
return src;
}

// Usage Example //

list source = ["How", "much", "wood", "would", "a", "woodchuck", "chuck", "if", "a", "woodchuck", "could", "chuck", "wood", "?"];

default
{
state_entry()
{
llOwnerSay(llDumpList2String(MultiListReplace(source, ["woodchuck", "primrezzer", "much", "many", "wood", "prims", "chuck", "rez"]), ", "));
// Return == "How, many, prims, would, a, primrezzer, rez, if, a, primrezzer, could, rez, prims, ?"
}
}</syntaxhighlight>

=== MultiStringReplace ===
Replace parts of a string with other strings.

<syntaxhighlight lang="lsl2">// V5 //

string MultiStringReplace(string src, list thisnthats)
{
integer index = 0;
integer lc = 0;
integer ll = llGetListLength(thisnthats);
do
{
string this = llList2String(thisnthats, lc);
++lc;
while((index = llSubStringIndex(src, this)) != -1)
src = llInsertString(llDeleteSubString(src, index, (index + (llStringLength(this) - 1))), index, llList2String(thisnthats, lc));
}
while((++lc) < ll);
return src;
}

// Usage Examples //

string source = "How much wood would a woodchuck chuck if a woodchuck could chuck wood?";

default
{
state_entry()
{
llOwnerSay(MultiStringReplace(source, ["woodchuck", "primrezzer", "much", "many", "wood", "prims", "chuck", "rez"]));
// Return == "How many prims would a primrezzer rez if a primrezzer could rez prims?"

llOwnerSay(MultiStringReplace(source, ["much", "many", "wood", "prims", "woodchuck", "primrezzer", "chuck", "rez"]));
// Return == "How many prims would a primsrez rez if a primsrez could rez prims?"

llOwnerSay(MultiStringReplace(source, ["farmers", "primrezzer", "much", "many", "wood", "prims", "chuck", "rez"]));
// Return == "How many prims would a primsrez rez if a primsrez could rez prims?"

llOwnerSay(MultiStringReplace(source, ["much", "many", "wood", "prims", "farmers", "primrezzer", "chuck", "rez"]));
// Return == "How many prims would a primsrez rez if a primsrez could rez prims?"

llOwnerSay(MultiStringReplace(source, ["woodchuck", "primrezzer", "much", "many", "wood", "prims", "farmers", "piggies", "chuck", "rez"]));
// Return == "How many prims would a primrezzer rez if a primrezzer could rez prims?"
}
}</syntaxhighlight>

=== StrideOfList ===
Get strided entries from a list. Note: this functionality is no directly provided by [[llList2ListSlice]].

<syntaxhighlight lang="lsl2">// V2 //

list StrideOfList(list src, integer stride, integer start, integer end)
{
list l = [];
integer ll = llGetListLength(src);
if(start < 0)start += ll;
if(end < 0)end += ll;
if(end < start) return llList2List(src, start, start);
while(start <= end)
{
l += llList2List(src, start, start);
start += stride;
}
return l;
}

// Usage Examples //

list source = ["How", "much", "wood", "would", "a", "woodchuck", "chuck", "if", "a", "woodchuck", "could", "chuck", "wood?"];

default
{
state_entry()
{
llOwnerSay(llDumpList2String(StrideOfList(source, 1, 0, -1), ", "));
// Return == "How, much, wood, would, a, woodchuck, chuck, if, a, woodchuck, could, chuck, wood?"

llOwnerSay(llDumpList2String(StrideOfList(source, 2, 0, -2), ", "));
// Return == "How, wood, a, chuck, a, could"

llOwnerSay(llDumpList2String(StrideOfList(source, 4, 3, -1), ", "));
// Return == "would, if, chuck"

llOwnerSay(llDumpList2String(StrideOfList(source, 5, 3, -4), ", "));
// Return == "would, a"

llOwnerSay(llDumpList2String(StrideOfList(source, 3, -10, -7), ", "));
// Return == "would, chuck"

llOwnerSay(llDumpList2String(StrideOfList(source, 3, 7, -7), ", ")); // Start index is closer to end than end index (whoops).
// Return == "if" // Start is returned only.
}
}</syntaxhighlight>

=== Capitalization Functions ===
==== ToNormal ====

Returns a string that holds true to a few simple rules.
*First person reference "I" is capitalized.
*Specified names are capitalized.
*The first word of each ''proper'' sentence is capitalized.
:*This includes quotes. E.g. "Time is an illusion; Lunchtime, doubly so." - [http://en.wikipedia.org/wiki/Douglas_Adams Douglas Adams]
:*Also new lines (see examples below).
I would imagine the results will be a mess if the source is not neatly written. I'll work on improving it as time goes on (it's a start).

<syntaxhighlight lang="lsl2">// V4 //

string ToNormal(string src, list names)
{
list abc = ["a","b","c","d","e","f","g","h","i","j","k","l","m", // The script needs to know what a letter is.
"n","o","p","q","r","s","t","u","v","w","x","y","z"];
list punc = [". ","; ","? ","! ", " \"","\n"]; // Punctuation we create a new sentance after.
src = llToLower(" " + src + " ");
string result = "";
integer index = 0;
integer lc = 0;
integer ll = 0;
string ko = "";
if((ll = llGetListLength(names)))
{
do
{
string name = llToLower(llList2String(names, lc));
while((index = llSubStringIndex(src, name)) != -1)
src = llInsertString(llDeleteSubString(src, index, (index + (llStringLength(name) - 1))),
index, llList2String(names, lc));
}
while((++lc) < ll);
index = 0;
}
while((index = llSubStringIndex(src, "i")) != -1)
{
if(ko == "")
ko = llGetSubString(src, 0, (index - 1));
if((llListFindList(abc, [llGetSubString(src, (index - 1), (index - 1))]) == -1)
&& (llListFindList(abc, [llGetSubString(src, (index + 1), (index + 1))]) == -1))
{
src = llDeleteSubString(src, index, index);
result += ("I" + llGetSubString(src, index, (llSubStringIndex(src, "i") - 1)));
}
else
{
src = llDeleteSubString(src, index, index);
result += ("i" + llGetSubString(src, index, (llSubStringIndex(src, "i") - 1)));
}
}
names = llParseString2List(llStringTrim((result = (ko + result)), STRING_TRIM), [], punc); // Reusing variable to save bytes.
lc = 0;
index = -1;
ll = llGetListLength(names);
string ABC = llToUpper(llDumpList2String(abc, ""));
do
{
string entry = llList2String(names, lc);
do
{
++index;
result = llToUpper(llGetSubString(entry, index, index));
}
while(llSubStringIndex(ABC, result) == -1);
names = llListReplaceList(names, [llInsertString(llDeleteSubString(entry, index, index), index, result)], lc, lc);
index = -1;
}
while((++lc) < ll);
return llDumpList2String(names, "");
}

// Usage Example //

//string source = "I can't help but wonder; \"What time should I and Sally arrive for dinner\"? For some reason, I like Tori Amos!! Should I?";

string source = "Confessions of a cigar smoker

I owe to smoking, more or less,
Through life the whole of my success;
With my Cigar I'm sage and wise -
Without, I'm dull as cloudy skies.
When smoking all my ideas soar,
When not, they sink upon the floor.
The greatest men have all been smokers,
And so were all the greatest jokers.
Then ye who'd bid adieu to care,
Come here and smoke it into air.";

default
{
state_entry()
{
source = llToUpper(source); // For whatever reason...

llOwnerSay(ToNormal(source, []));

// OR (depending on source)

//llOwnerSay(ToNormal(source, ["Sally", "Tori Amos"]));

// Return == "I can't help but wonder; "What time should I and Sally arrive for dinner"? For some reason, I like Tori Amos!! Should I?"

// OR (depending on source)

// Return == "Confessions of a cigar smoker

//I owe to smoking, more or less,
//Through life the whole of my success;
//With my cigar I'm sage and wise -
//Without, I'm dull as cloudy skies.
//When smoking all my ideas soar,
//When not, they sink upon the floor.
//The greatest men have all been smokers,
//And so were all the greatest jokers.
//Then ye who'd bid adieu to care,
//Come here and smoke it into air."
}
}</syntaxhighlight>

==== ToTitle ====
Returns a string with ALL first letters of ALL words capitalized.
A slower (source length being equal) function than [[#ToNormal|ToNormal]] but ''possibly'' more reliable.

<syntaxhighlight lang="lsl2">// V2 //

string ToTitle(string src)
{
list words = llParseString2List(llToLower(src), [], [".",";","?","!","\""," ","\n"]);
integer ll = llGetListLength(words);
integer lc = -1;
string word = "";
while((++lc) < ll)
{
string cap = llToUpper(llGetSubString((word = llList2String(words, lc)), 0, 0));
words = llListReplaceList(words, [(cap + llDeleteSubString(word, 0, 0))], lc, lc);
}
return llDumpList2String(words, "");
}

// Usage Example //

string source = "I can't help but wonder; \"What time should I and Sally arrive for dinner\"? For some reason, I like Tori Amos!! Should I?";

//string source = "Confessions of a cigar smoker
//
//I owe to smoking, more or less,
//Through life the whole of my success;
//With my Cigar I'm sage and wise -
//Without, I'm dull as cloudy skies.
//When smoking all my ideas soar,
//When not, they sink upon the floor.
//The greatest men have all been smokers,
//And so were all the greatest jokers.
//Then ye who'd bid adieu to care,
//Come here and smoke it into air.";

default
{
state_entry()
{
source = llToUpper(source); // For whatever reason...

llOwnerSay(ToTitle(source));

// Return == "I Can't Help But Wonder; "What Time Should I And Sally Arrive For Dinner"? For Some Reason, I Like Tori Amos!! Should I?"

// OR (depending on source)

// Return == "Confessions Of A Cigar Smoker

//I Owe To Smoking, More Or Less,
//Through Life The Whole Of My Success;
//With My Cigar I'm Sage And Wise -
//Without, I'm Dull As Cloudy Skies.
//When Smoking All My Ideas Soar,
//When Not, They Sink Upon The Floor.
//The Greatest Men Have All Been Smokers,
//And So Were All The Greatest Jokers.
//Then Ye Who'd Bid Adieu To Care,
//Come Here And Smoke It Into Air."
}
}</syntaxhighlight>}}

LSL Operators

2023-10-20T16:39:36Z

MoiraAtropos Resident: /* Useful Snippets */ Concatenation by list casting

{{LSL Header|ml=*}}{{LSLC|FixMe}}
Operators are used to cause an operation (or mathematical action) to be performed on one (such as !) or two operands. The easy and common example is 1 + 2 where 1 and 2 are operands, and the '''+''' is the operator. This concept can be extended much further with LSL since operands can be variables with the special case of the assignment operators requiring that the left hand side be a variable.

The following table lists the operators in descending order of evaluation, i.e. higher in the table means higher evaluation precedence. Multiple operators on the same line share evaluation precedence. Parenthesize an expression if you need to force an evaluation order.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Description
! Usage Example
|-
| <code>()</code>
|| parentheses: grouping and evaluation precedence
|| <code>integer val = a * (b + c);</code>
|-
| <code>[]</code>
|| brackets: list constructor
|| <code>list lst = [a, 2, "this", 0.01];</code>
|-
| <code>(''type'')</code>
|| typecasting
|| <code>string message = "The result is:" + (string)result;</code>
|-
| <code>!</code> <code>~</code> <code>++</code> <code>--</code>
|| logical NOT, bitwise NOT, increment, decrement
|| <code>counter++;</code>
|-
| <code>*</code> <code>/</code> <code>%</code>
|| multiply/dot product, divide, modulus/cross product
|| <code>integer rollover = (count + 1) % 5;</code>
|-
| <code>-</code>
|| subtraction, negation
|| <code>integer one = 3 - 2;</code>
<code>integer neg_one = -1;</code>
|-
| <code>+</code>
|| addition, string concatenation
|| <code>integer two = 1 + 1;</code>
<code>string text = "Hello" + " world";</code>
|-
| <code>+</code>
|| list concatenation
|| <code>list myList = [1, 2, 3] + [4, 5];</code>
<code>list newList = oldList + addList;</code>
|-
| <code><<</code> <code>>></code>
|| [https://en.wikipedia.org/wiki/Arithmetic_shift arithmetic] left shift, [https://en.wikipedia.org/wiki/Arithmetic_shift arithmetic] right shift
|| <code>integer eight = 4 << 1;</code>
<code>integer neg_one = -2 >> 1;</code>
|-
| <code><</code> <code><=</code> <code>></code> <code>>=</code>
|| less than, less than or equal to, greater than, greater than or equal to
|| <code>integer isFalse = (6 <= 4);</code>
|-
| <code>==</code> <code>!=</code>
|| comparison: equal, not equal
|| <code>integer isFalse = ("this" == "that");</code>
|-
| <code>&</code>
|| bitwise AND
|| <code>integer zero = 4 & 2;</code>
<code>integer four = 4 & 4;</code>
|-
| <code>^</code>
|| bitwise XOR
|| <code>integer zero = 4 ^ 4;</code>
<code>integer six = 4 ^ 2;</code>
|-
| <code><nowiki>|</nowiki></code>
|| bitwise OR
|| <code>integer four = 4 <nowiki>|</nowiki> 4;</code>
<code>integer six = 4 <nowiki>|</nowiki> 2;</code>
|-
| <code><nowiki>||</nowiki></code>
|| logical OR
|| <code>integer isTrue = (FALSE <nowiki>||</nowiki> TRUE);</code>
|-
| <code>&&</code>
|| logical AND
|| <code>integer isFalse = (FALSE && TRUE);</code>
|-
| <code>=</code> <code>+=</code> <code>-=</code> <code>*=</code> <code>/=</code> <code>%=</code>
|| assignment
|| <code>integer four = 4;</code>
<code>integer eight = four; eight *= 2;</code>
|}

'''Note:''' Modulus (<code>%</code>), like division, cause a ''Script run-time error. Math Error'' when its second operand equals zero.

'''Note:''' The <code>%</code> operator only accepts integer (<code>%</code> as modulus) and vector (<code>%</code> as cross product) operands.

'''Note:''' Unlike most other languages that use the C-style <code>&&</code> and <code>||</code> operators, '''both''' operands are '''always''' evaluated. For example,

<syntaxhighlight lang="lsl2">if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</syntaxhighlight>

: will cause a Math Error rather than say "Aha!"

'''Note:''' The <code>++</code> (increment) and <code>--</code> (decrement) operators have two versions, pre- and post-. The ''pre''-increment (or ''pre''-decrement) operator increments (or decrements) its operand by 1; the value of the expression is the incremented (or decremented) value. The ''post''-increment (or ''post''-decrement) operator increases (or decreases) the value of its operand by 1, but the value of the expression is the operand's original value ''prior'' to the operation.

<syntaxhighlight lang="lsl2">integer count = 0;
if( ++count == 1 ) // 'count' is incremented then evaluated.
llSay(PUBLIC_CHANNEL, "Aha"); // message will be said.</syntaxhighlight>

<syntaxhighlight lang="lsl2">integer count = 0;
if( count++ == 1 ) // 'count' is evaluated then incremented.
llSay(PUBLIC_CHANNEL, "Aha"); // message will not be said.</syntaxhighlight>

'''Note:''' The order of precedence of boolean operators is unclear. It is possible that there is a [http://jira.secondlife.com/browse/SVC-779 bug] in the expression parser, making precedence inconsistent, or it may simply be that '''||''' and '''&&''' have equal precedence; testing is inconclusive. Thus, when in doubt, parenthesize.
'''SubNote:''' As the above bug has been closed as expected behavior, one can only assume the boolean operators have equal precedence.

'''Note:''' The order of evaluation appears to be backwards from most languages. If the value of x starts as 1 then the first two conditions below evaluate false and the second two evaluate true:

<syntaxhighlight lang="lsl2">(x && (x = 0) == 0 && x)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x && (x = 0) == 0 && x == 0)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x == 0 && (x = 0) == 0)</syntaxhighlight>
<syntaxhighlight lang="lsl2">(x == 0 && (x = 0) == 0 && x)</syntaxhighlight>

Both sides are evaluated regardless of the the truth of either side.

'''Note:''' Equality test on lists does not compare contents, only the length.
{| {{Prettytable}}
|+
==+ Operator==
<code>result = left + right</code>
|-{{Hl2}}
!Left Type
!Right Type
!Result Type
!Description
|-
|integer
|integer
|integer
|Adds '''left''' and '''right'''
|-
|integer
|float
|float
|Adds '''left''' and '''right'''
|-
|float
|integer
|float
|Adds '''left''' and '''right'''
|-
|string
|string
|string
|Concatenates '''right''' onto the end of '''left'''.
|-
|list
|*
|list
|Concatenates '''right''' onto the end of '''left'''.
|-
|*
|list
|list
|Affixes '''left''' onto the start of '''right'''.
|-
|vector
|vector
|vector
|Adds '''left''' and '''right'''
|-
|rotation
|rotation
|rotation
|Adds '''left''' and '''right'''<br/>Not useful for combining rotations, use [[#* Operator|*]] or [[#/ Operator|/]] instead.
|}

{| {{Prettytable}}
|+
==Shorthand Operators==
Alternatives to the simple '=' operator...
|-{{Hl2}}
!Simple assignment operator
!Shorthand operator
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

=={{Wikipedia|De Morgan's laws|w=n}}==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitwise Equivalencies
!AND
!OR
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boolean Equivalencies
!AND
!OR
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Due to {{Wikipedia|De Morgan's laws|w=n}}, by row, code in the '''AND''' column is logically equivalent to code in the '''OR'''. '''a''' and '''b''' need not be variables, they can be expressions. In certain circumstances these equivalencies can be used to simplify complex code. It is important not to confuse the two sets when using them. The first two rows depict De Morgan's laws as it is formulated, the second two build upon it.

{{LSLC|}}{{LSLC|Syntax}}{{LSLC|Keywords}}

== Useful Snippets ==

Typecasting can also be used if you have to concatenate many parts into a string:

<syntaxhighlight lang="lsl2">// the following twp statements are equivalent:
string message1 = (string)["I have ", 5, " children at the average age of ", 8.2, " years"];
string message2 = "I have 5 children at the average age of 8.2000001 years";</syntaxhighlight>

LlListFindStrided

2023-09-26T21:04:58Z

MoiraAtropos Resident:

{{LSL_Function
|func=llListFindStrided
|func_id=201|func_sleep=0.0|func_energy=10.0
|return_type=integer
|Return_text=index of the first instance of {{LSLP|test}} in {{LSLP|src}} matching conditions.
|p1_type=list|p1_name=src|p1_desc=what to search in (haystack)
|p2_type=list|p2_name=test|p2_desc=what to search for (needle)
|p3_type=integer|p3_name=start|p3_desc=Start of range to search
|p4_type=integer|p4_name=end|p4_desc=End of range to search
|p5_type=integer|p5_name=stride|p5_desc=Number of entries per stride within src

|func_footnote=If {{LSLP|test}} matching range and stride conditions is not found in {{LSLP|src}}, -1 is returned.<br/>
The length of {{LSLP|test}} may be equal to or less than {{LSLP|stride}} in order to generate a match.<br/>
The index of the first entry in the list is {{HoverText|0|zero}}<br>
If {{LSLP|test}} is found at the last index in {{LSLP|src}} the positive index is returned (5th entry of 5 returns 4).<br>
If {{LSLP|start}} or {{LSLP|end}} is negative, it is counted from the end list. The last element in the list is -1, the first is -list_length
|func_desc
|spec
|caveats=
* Strict type matching and case sensitivity is enforced.
** "1" != 1
** "1.0" != 1.0
** 1 != 1.0
** "a822ff2b-ff02-461d-b45d-dcd10a2de0c2" != (key)"a822ff2b-ff02-461d-b45d-dcd10a2de0c2"
** "Justice" != "justice"
* If {{LSLP|test}} is an {{HoverText|empty list|[]}} the value returned is {{HoverText|0|zero}} rather than -1.
|constants
|examples=<source lang="lsl2">list mylist = ["a",0,"b",1,"c",2,"b",1];

integer result_a = llListFindStrided(mylist, ["b"], 0, -1, 1); //Stride 1 full range functionally equivalent to llListFindList(mylist,"b");
//result_a = 2

integer result_b = llListFindStrided(mylist, ["b",1], 2, -1, 1); //Inclusive range for start and end will find 2nd list in list
//result_b = 2

integer result_e = llListFindStrided(mylist, ["b"], 3, -1, 1); //The first "b" is at index 2 and will be skipped by starting at 3
//result_c = 6

integer result_d = llListFindStrided(mylist, ["b",1], 2, -1, 1); //Inclusive range for start and end will find 2nd item in list
//result_d = 2

integer result_e = llListFindStrided(mylist, ["b",1], 3, -1, 1); //The first "b",1 series is at index 2 and will be skipped by starting at 3
//result_e = 6

integer result_f = llListFindStrided(mylist, ["b",1], 3, -2, 1); //The first "b",1 series is at index 2 and will be skipped by starting at 3. The second ["b",1] set exceeds the range criteria of the search.
//result_f = -1

integer result_g = llListFindStrided(mylist, ["b",2], 0, -1, 1); //No consecutive elements match ["b",2]
//result_g = -1

integer result_h = llListFindStrided(mylist, ["c"], 0, -1, 2); //With a stride of 2, "c" will be found.
//result_h = 4

integer result_i = llListFindStrided(mylist, ["c"], 0, -1, 3); //With a stride of 3, "c" won't be found.
//result_i = -1

integer result_j = llListFindStrided(mylist, ["c"], 0, -1, 4); //With a stride of 4, "c" will be found.
//result_j = 4

integer result_k = llListFindStrided(mylist, ["c"], 1, -1, 2); //While the stride is even, starting at the 2nd element will miss this stride.
//result_k = -1

</source>
<source lang="lsl2">list numbers = [1, 2, 3, 4, 5];
default
{
state_entry()
{
integer index = llListFindStrided(numbers, [3], 0, -1, 1); //Functionally identical to llListFindList(numbers, [3]);
if (index != -1)
{
list three_four = llList2List(numbers, index, index + 1);
llOwnerSay(llDumpList2String(three_four, ","));
// Object: 3,4
}
}
}</source>
<source lang="lsl2">//You can also search for two items at once to find a pattern in a list
list avatarsWhoFoundMagicLeaves = ["Water Duck", "Green Ham", "Fire Centaur","Red Leaf"];
default
{
state_entry()
{
integer index = llListFindStrided(avatarsWhoFoundMagicLeaves, ["Fire Centaur","Red Leaf"],0,-1,2);
if (index != -1)
{
list output = llList2List(avatarsWhoFoundMagicLeaves, index, index + 1);
llOwnerSay(llDumpList2String(output, ","));
// Object: Fire Centaur, Red Leaf
}
}
}</source>
<source lang="lsl2">//It's nearly a database
list food_db = ["FIRSTNAME", "LASTNAME", "FAVORITE FOOD", "ALLERGIES",
"Awesome", "Resident","Apples",0,
"Charlie", "Kites", "Peanuts", "dogs",
"Cool", "McLastname", "Burgers","peanuts"];
default
{
state_entry()
{
list potential_allergen = ["peanuts"];
integer any_allergies = llListFindStrided(food_db, potential_allergen,4,-1,4);
if (any_allergies != -1)
{
llOwnerSay("Every can eat it");
}
else
{
list output = llList2List(food_db, any_allergens - 3, any_allergens - 2);
llOwnerSay(llDumpList2String(output, " ")+" is allergic to it!");
// Object: Cool McLastName is allergic to peanuts
}
}
}</source>

|helpers=
|also_functions=
{{LSL DefineRow||[[llSubStringIndex]]|Find a string in another string}}
|also_events
|also_tests
|also_articles
|notes
|sort=ListFindList
|cat1=List
|haiku={{Haiku|I made a database|Using Only Some Lists|Find by last name.}}
|cat2
|cat3
|cat4
}}

LlSetPayPrice

2023-08-11T11:10:08Z

MoiraAtropos Resident:

{{LSL_Function
|inject-2={{Issues/VWR-3048}}{{Issues/VWR-8744}}
|func_id=302|func_sleep=0.0|func_energy=10.0
|func=llSetPayPrice|sort=SetPayPrice
|p1_type=integer|p1_name=price|p1_desc=PAY_* constant or positive value (including zero)
|p2_type=list|p2_name=quick_pay_buttons|p2_desc=Four PAY_* constants and/or positive integer values (zero is not shown)
|func_desc=Suggest default amounts for the pay text field and pay buttons of the appearing dialog when someone chooses to pay this object.
|caveats=*This function should not be trusted to limit the values of money payable to the object; ''always'' verify the amount paid is the amount expected.
* Use only one call to this function in all the scripts on an object to prevent confusion about which values are used. You still need to check in the money event that the amount is as expected.
* This function only works when called from the root prim of an object. Its effect applies to all the prims in the object. Calling it from a child prim has no effect.
* Payment to a prim can be blocked by the llSetPayPrice() setting in the prim, which persists even if the script with llSetPayPrice() is removed.
* '''Caution:''' Calling this function will enable payment on the prim (or the whole object if it is the root prim) for the current state, even when this state has no money event.
* Otherwise, the pay option will only be shown in prims having a running script with a [[money]] event (or in all the prims of the object if the root has a running script with a money event).
* The effect seems to persist even if the script is recompiled with out the [[llSetPayPrice]] function, even if the script is replaced with another one which includes a [[money]] event, but not [[llSetPayPrice]].
* Money cannot be paid to an attachment; "Pay" will go directly to the wearer instead.
* If '''quick_pay_buttons''' contains a negative value or zero, the button will not be shown at all.
** However, zero is allowed for '''price''', which is used to set the custom text field's value within the Pay window.

|examples=This will give the user a dialog box without the '''price''' field and only one button with a value of 150.
<source lang="lsl2">llSetPayPrice(PAY_HIDE, [150,PAY_HIDE,PAY_HIDE,PAY_HIDE])</source>

<source lang="lsl2">integer price = 10;

default
{
state_entry()
{
llSetPayPrice(PAY_HIDE, [PAY_HIDE ,PAY_HIDE, PAY_HIDE, PAY_HIDE]);
llRequestPermissions(llGetOwner(), PERMISSION_DEBIT);
}
run_time_permissions(integer perm)
{
if(perm & PERMISSION_DEBIT)
state cash;
}
}

state cash
{
state_entry()
{
llSetPayPrice(price, [price ,PAY_HIDE, PAY_HIDE, PAY_HIDE]);
}
money(key id, integer amount)
{
if(amount != price)
{
llGiveMoney(id, amount);
llInstantMessage(id, "You paid "+(string)amount+", which is the wrong price, the price is: "+(string)price);
}
else
{
//insert your give code here.
llInstantMessage(id, "You paid the right price");
}
}
}</source>
|spec
|constants=
{{{!}}
{{!}}
{{{!}}{{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! colspan="2" {{!}} Constant
! {{HoverText|Alt|Alternate}}
! Description
{{!}}-
{{!}} [[PAY_HIDE]]
{{!}} -1
{{!}} <center>0</center>
{{!}} Hides this quick pay button.
{{!}}-
{{!}} [[PAY_DEFAULT]]
{{!}} -2
{{!}}
{{!}} Use the default value for this quick pay button.
{{!}}}
{{!}}
{{{!}} {{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! colspan="2" {{!}} Button Order
{{!}}-
{{!}} <center>1</center>
{{!}} <center>2</center>
{{!}}-
{{!}} <center>3</center>
{{!}} <center>4</center>
{{!}}}
{{!}}
{{{!}}{{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! colspan="2" {{!}} Defaults
{{!}}-
{{!}}$1
{{!}}$5
{{!}}-
{{!}}$10
{{!}}$20
{{!}}}
{{!}}}
|helpers
|also_functions={{LSL DefineRow||[[llGiveMoney]]|}}
|also_tests={{LSL DefineRow||[[llSetPayPrice Test]]|}}
|also_events={{LSL DefineRow||[[money]]|}}
|also_articles
|notes
|cat1=Money
|cat2=Prim
|cat3=Dialog
|cat4
|issues
}}

Simplex Text

2023-08-01T10:34:54Z

MoiraAtropos Resident: Script formatting

Simplex Text is, in the creator's opinion, the successor to XyzzyText. Whether that is true or not, the future will decide. Simplex provides end users an easy way to generate dynamic text on prims. Using only one texture and one script, this becomes a viable option for many users. Unfortunately, unlike XyzzyText, it uses a linkset, rather than a single prim, to visualize its contents.

Rudy Glassfield, the sole developer of Simplex Text, has made the script open-source and currently sells it on the Marketplace for free. The script comes packaged in a box, which doubles up as a demo for the Simplex Text System.

The script is also available here on the Wiki, for those intrepid users who wish to dive right in.

// PRELIMINARY NOTES:
//
// ALL CHARACTER PRIM BLOCKS MUST BE NAMED "CHARACTER" THIS IS DONE TO ENSURE NO OTHER PRIMS ARE ALTERED.
// ALL OBJECTS MUST BE LINKED. THIS SCRIPT IS IN THE ROOT PRIM.

// PLEASE MODIFY THESE VARIABLES TO YOUR LIKING

integer face = 3; // FACE NUMBER WHICH THE LETTERS WILL SHOW UP ON (USE ALL_SIDES IF YOU'RE NOT SURE)
vector color = <1, 1, 1>; // COLOR OF TEXT <1, 1, 1> = (RGB) WHITE, <0, 0, 0> = (RGB) BLACK

// END USER CONTENT

list charOrder = [];
key ascii = "b2e7394f-5e54-aa12-6e1c-ef327b6bed9e";
string gCharIndex = " !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz";
float xOrigin = -0.450;
float yOrigin = -0.550;
setCharacter(integer linknum, string msg)
{
integer index = llSubStringIndex(gCharIndex, msg);
float xOffset = xOrigin + (index % 10)/10.f;
if(xOffset > 1) xOffset -= 1.f;
if(xOffset < -1) xOffset += 1.f;
float yOffset = yOrigin - (index / 10)/10.f;
if(yOffset > 1) yOffset -= 1.f;
if(yOffset < -1) yOffset += 1.f;
llSetLinkPrimitiveParamsFast(linknum, [PRIM_TEXTURE, face, ascii, <0.1, 0.1, 0>, <xOffset, yOffset, 0>, 0, PRIM_COLOR, face, color, 1.0]);
}

setCharacters(string msg, list order)
{
integer i;
for(i = 0; i < llGetListLength(order); i ++)
{
setCharacter(llList2Integer(order, i), llGetSubString(msg, i, i));
}
}
default
{
state_entry()
{
list temp;

// Set Up Letter Blocks

integer linked = llGetNumberOfPrims();

integer i;
for(i = 2; i <= linked; i ++)
{
if(llGetLinkName(i) == "Character")
{
vector pos = llList2Vector(llGetLinkPrimitiveParams(i, [PRIM_POSITION]), 0);
vector posNorm = llVecNorm(pos)*llGetRot();
temp += pos*llRot2Up(llGetRot())+posNorm.x;
temp += i;
}
}
charOrder = llList2ListStrided(llDeleteSubList(llListSort(temp, 2, FALSE), 0, 0), 0, -1, 2);
}
link_message(integer linknum, integer num, string str, key id)
{
llSetLinkPrimitiveParamsFast(LINK_ALL_CHILDREN, [PRIM_COLOR, ALL_SIDES, <0, 0, 0>, 0.0]);
setCharacters(str, charOrder);
}
changed(integer change)
{
if(change & CHANGED_LINK)
{
llResetScript();
}
}
}

LlRegionSayTo

2023-06-05T13:25:44Z

MoiraAtropos Resident: Category:LSL_Chat

{{LSL_Function
|inject-2={{Issues/SCR-66}}
{{LSL_Function/uuid|target|sim=*|group=}}
|func_id=363
|func_sleep=0.0
|func_energy=10.0
|func=llRegionSayTo
|sort=RegionSayTo
|p1_type=key|p1_name=target
|p2_type=integer|p2_name=channel
|p3_type=string|p3_name=msg
|func_desc=Says<ref name="send">In this context, ''saying'' or ''speaking'' means that a message is being ''sent'' to the recipient (object or avatar); it's not about audio/voice chat!</ref> the text supplied in string {{LSLP|msg}} on channel supplied in [[integer]] {{LSLP|channel}} to the [[object]] or [[avatar]] specified by {{LSLP|target}}
|return_text
|spec
|caveats=
*Text is spoken<ref name="send" /> directly to the [[object]] or [[avatar]] within the same [[region]] as the [[script]].
*Script in tasks other than {{LSLP|target}} can neither listen for<ref>In this context, this means waiting to ''receive'' a message.</ref>, nor receive these text messages, with an exception for attachments as described below.
*Text can be a maximum of 1024 bytes. This can convey 1024 ASCII-7 characters, or 512 UTF-8 characters such as á
*A [[prim]] cannot hear itself, to prevent problems with recursion.
*Sending text on {{LSLP|DEBUG_CHANNEL}} is not supported.
*Text sent to an avatar's [[UUID|ID]] on channel [[PUBLIC_CHANNEL|zero]] will be sent to the receiver's viewer.
*Text sent to an avatar's ID on non-zero channels can be heard<ref>I.e., ''received''</ref> by any attachment on the avatar.
*A quick series of messages sent by [[llRegionSayTo]] cannot be relied on to arrive at their destination in the same order as sent.
*There is a per-destination throttle of 200 messages sent over 10 seconds on channel [[PUBLIC_CHANNEL|zero]]. Thereafter, there is also a per-sending-object throttle of 100 messages on channel zero over 300 seconds (5 minutes). This throttle is relevant only after the first throttle is activated. Messages sent on channels other than zero do not trigger the throttle but, once it is triggered, the block applies to ''all'' channels. The block is region-wide and applies to all objects with the same [[:Category:LSL_Owner|owner]]. The block apparently lasts until the region is restarted.
|examples=
<syntaxhighlight lang="lsl2">
default
{
touch_start(integer num_detected)
{
key id = llDetectedKey(0);

// send a message to the chat window of the avatar touching
llRegionSayTo(id, 0, "You touched this!");

// send a message to the attachments of the avatar touching
// example channel: -12345
llRegionSayTo(id, -12345, "Hello there attachments!");
}
}
</syntaxhighlight>
|helpers
|also_events=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[listen]]|Receives chat}}
|also_functions=
{{!}}-
{{!}}{{!}}{{!}} style="width:9em;" {{!}}
{{LSL DefineRow||[[llListen]]|Ask for [[listen]] events}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to a specific avatar, inside or outside the current region.}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the [[PUBLIC_CHANNEL]]}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
|also_tests
|also_articles={{LSL DefineRow||[[Hello Avatar]]}}
|notes=
* If one object 'says'<ref name="send" /> something to another object (''e.g.'', a button that, when touched, turns on a lamp), it is a good idea to use a very negative {{LSLP|channel}}<ref>This should be considered as an idiomatic way of programming in [[LSL]]; scripters will 'know' that negative channels are usually ''not'' meant for ''users'' to type, but only as a way for objects to communicate among themselves.</ref>, ''e.g.'',
:<syntaxhighlight lang="lsl2">llRegionSayTo("55499a64-45c3-4b81-8880-8ffb5a7c251b", -5243212, "turn on");</syntaxhighlight>
:Negative channels are popular for script communications because, before September 2016, the standard Second Life Viewer was unable to chat directly on those channels (<kbd>/-xxxx message</kbd> wouldn't chat {{mono|message}} on {{LSLPT|channel}} {{mono|-xxxx}}).
* Messages sent on channel zero via [[llRegionSayTo]]() are blocked after 200 messages on to the same destination in a 10 second period. After this throttle is activated, there is a further throttle, on objects belonging to the owner of the object that triggered the first throttle, of 100 messages per object over 5 minutes (see {{Jira|BUG-5457}}). The block is region-wide and applies to all objects belonging to the owner, so if a script triggers the throttle, all objects in the same region belonging to the same owner will also be blocked. Messages sent on channels other than zero do not trigger the throttles. The throttles apparently reset only when the region is restarted.

Therefore, [[llRegionSayTo]]() is unsuitable for (say) verbose script debugging, and even moderate use can break users' content completely unrelated to the script for an indeterminate (and potentially very long) period of time. Consider using [[llOwnerSay]]() for debugging instead or, if this is not appropriate, try {{mono|llRegionSayTo(avatar, non-zero-channel, message)}} and have an attachment relay the message using [[llOwnerSay]]().
|cat1
|cat2
|cat3
|cat4
|history = Date of Release [[ Release_Notes/Second_Life_Server/11#11.04.26.227686 | 26/04/2011 ]]
}}

[[Category:LSL_Chat]]

LSL Portal

2023-06-05T09:38:36Z

MoiraAtropos Resident: /* {{LSLGC||LSL Features by category}} */ Object / LinksetData

{{LSL Header|ml=*}}
__NOTOC__
LSL (Linden Scripting Language) is the scripting language that gives behavior to Second Life primitives, objects, and avatars. This is a community effort to provide an accurate & open documentation resource on LSL for scripters of all skill levels.

Feel free to edit and add content. For more information on how to edit the wiki, see [[Project:Editing Guidelines|Editing Guidelines]]. Do not copy any information from other sources, unless you are sure about the copyright agreements. See the [[Talk:LSL Portal|LSL Portal discussion]] page for more information.

'''Want to learn LSL? See [[LSL Tutorial]].'''

<div id="box">
{| width="100%" rules="all" style="border-width: 0px; border-spacing: 5px;"
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" width="30%"|

== LSL Portal ==
<div style="padding: 0.5em;">
* [[LSL Editing Primer|Editing Primer]] - Editing Instructions
* [[LSL Portal Guidelines|Guidelines]] - Administration and Design Standards (Mission, rules, layout, etc.)
* [[LSL Portal To-do|To-Do]] - Edit/Revisions To-Do Listing
* [[LSL Portal Translation Project|Translation Project]] - Translation Coordination
</div>
|height="1" width="30%" rowspan="2"|

== LSL Language Reference ==
<div style="padding: 0.5em;">
* [[:Category:LSL Constants|Constants]]
* [[:Category:LSL Events|Events]]
* {{LSLGC|Flow Control}}
** [[for]]
** [[if]]
** [[while]]
** [[do-while]]
** [[jump]]
** [[return]]
** [[state]]
* [[:Category:LSL Functions|Functions]]
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions}}#mw-pages (A..L)]</span>
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions|from=L}}#mw-pages (L..T)]</span>
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions|from=T}}#mw-pages (T..Z)]</span>
**[[LSL_Function_ID|(By internal index id)]]
* [[LSL Operators|Operators]]
* [[state|States]]
* [[:Category:LSL Types|Types]]
** [[integer]]
** [[float]]
** [[string]]
** [[key]]
** [[list]]
** [[vector]]
** [[rotation]]
* [[LSL Variables|Variables]]
* [[LSL Errors|Errors]]
</div>
|height="1" width="25%" rowspan="5"|

== {{LSLGC||LSL Features by category}} ==
<div style="padding: 0.5em;">
{| border="0" cellspacing="0" cellpadding="0"
|-valign="top"
|width="50%"|
* [[:Category:LSL Alpha|Alpha]]
* [[:Category:LSL Animation|Animation]]
* [[:Category:LSL Attachment|Attachments]]
* [[:Category:LSL Avatar|Avatar]]
* [[:Category:LSL Camera|Camera]]
* [[:Category:LSL Collision|Collision]]
* [[:Category:LSL Color|Color]]
* [[:Category:LSL Communications|Communications]]
* [[:Category:LSL Controls|Controls]]
* [[:Category:LSL Dataserver|Dataserver]]
* [[:Category:LSL Dialog|Dialog]]
* [[:Category:LSL Face|Face]]
* [[:Category:LSL Group|Group]]
* [[:Category:LSL Inventory|Inventory]]
* [[:Category:LSL Light|Light]]
* [[:Category:LSL Link|Link]]
* [[:Category:LSL LinksetData|Linkset Persistent {{abbr|KVP|Key-Value Pair}} Store]]
* [[:Category:LSL_List|Lists]]
* [[:Category:LSL Math|Math]]
* [[:Category:LSL Needs Example|Needs Example]]
* [[:Category:LSL Permissions|Permissions]]
* [[:Category:LSL Physics|Physics]]
* [[:Category:LSL Prim|Primitive]]
* [[:Category:LSL Rotation|Rotation]]
* [[:Category:LSL_Script|Scripts]]
* [[:Category:LSL Sensor|Sensor]]
* [[:Category:LSL Sound|Sound]]
* {{LSLGC|Text}}
** {{LSLGC|Chat}}
** {{LSLGC|Notecard}}
** {{LSLGC|String}}
* [[:Category:LSL Teleport|Teleport]]
* [[:Category:LSL Texture|Texture]]
* [[:Category:LSL Time|Time]]
* [[:Category:LSL Vehicle|Vehicle]]
* [[:Category:LSL Video|Video]]
* [[:Category:LSL World|World]]
|width="50%"|
* {{LSLGC|Avatar}}
** {{LSLGC|Animation}}
** {{LSLGC|Attachment}}
** {{LSLGC|Camera}}
** {{LSLGC|Controls}}
** {{LSLGC|Sit}}
* {{LSLGC|Communications}}
** {{LSLGC|Chat}}
** {{LSLGC|Dialog}}
** {{LSLGC|HTTP}}
** {{LSLGC|XML-RPC}}
* [[:Category:LSL Detected|Detection]]
** {{LSLGC|Collision}}
** {{LSLGC|Sensor}}
** {{LSLGC|Touch}}
* {{LSLGC|Functions}}
** {{LSLGC|God Mode}}
* {{LSLGC|Inventory}}
** {{LSLGC|Creator}}
** {{LSLGC|Notecard}}
** {{LSLGC|Owner}}
* {{LSLGC|Media}}
** {{LSLGC|Prim Media}}
** {{LSLGC|Sound}}
** {{LSLGC|Video}}
* {{LSLGC|Movement}}
** {{LSLGC|Physics}}
*** {{LSLGC|Damping}}
*** {{LSLGC|Hover}}
** {{LSLGC|Rotation}}
* {{LSLGC|Object}}
** [[:Category:LSL Dataserver|Dataserver]]
** [[:Category:LSL LinksetData|Linkset Persistent {{abbr|KVP|Key-Value Pair}} Store]]
** {{LSLGC|Link}}
** {{LSLGC|Vehicle}}
* {{LSLGC|Permissions}}
** [[:Category:LSL Permissions/Asset|Asset]]
** [[:Category:LSL Permissions/Script|Script]]
* {{LSLGC|Prim|Primitive}}
** {{LSLGC|Effects}}
*** {{LSLGC|Light}}
*** {{LSLGC|Particles}}
** {{LSLGC|Face}}
*** {{LSLGC|Alpha}}
*** {{LSLGC|Color}}
*** {{LSLGC|Texture}}
* {{LSLGC|Region}}
** {{LSLGC|Ground}}
** {{LSLGC|Parcel}}
** {{LSLGC|Security}}
** {{LSLGC|Time}}
* {{LSLGC|Script}}
** {{LSLGC|Error}}
*** [[:Category:LSL Error/Math|Math Errors]]
** {{LSLGC|Keywords}}
** {{LSLGC|Math}}
** {{LSLGC|Types}}
|}
</div>
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1"|

== Developer Resources ==
<div style="padding: 0.5em;">

* [[:Category:LSL_User-Defined_Functions|User-Defined Functions]]
* [[LSL Protocol|User-Defined Protocols & APIs]]
----
* [[:Category:LSL Mentors|Mentors]]
* [[:Category:LSL Teachers|Teachers]]
* [[LSL_Help|Help]]
----
* [[LSL Write Once Debug Everywhere|Write Once Debug Everywhere]]
* [[LSL_Alternate_Editors|Alternate Editors]]
----
* [[LSL Tutorial|Tutorials]]
* [[:Category:LSL Examples|Examples]]
* [[LSL Style Guide|Style Guide]]
* [[LSL Script Efficiency|Efficiency]]
* [[LSL Script Memory|Memory]]
* [[LSL Hacks|Hacks]]
* [[LSL Benchmarking Scripts|Benchmarking Scripts]]
----
* [[:Category:LSL Categorized Library|Categorized Library]]
* [[:Category:LSL Library|Library]]
----
* [[LSL Test Harness|Test Harness]]
* [[LSL Useful Function WishList|Useful Function Wish-List]]
</div>
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" colspan="2"|
{{LSL News}}
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" colspan="2"|
{{LSL Bugs}}
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| colspan="2"|

== Other LSL Wikis ==
<div style="padding: 0.5em;">
* {{strike|1=[http://lslwiki.net/lslwiki/wakka.php?wakka=HomePage LSL Wiki] (The original LSL Wiki.)}} (currently offline)
* [http://lsl.project.zone/lsl/ Unofficial LSL Reference Wiki] (work in progress)
</div>

== Snapshot Mirrors ==
<div style="padding: 0.5em;">
</div>
|}
</div>
[[Category:Portals]]
[[Category:Creation]]
[[Category:LSL|*]]

LSL Portal

2023-06-05T09:35:12Z

MoiraAtropos Resident: /* {{LSLGC||LSL Features by category}} */ Objectss / Dataserver

{{LSL Header|ml=*}}
__NOTOC__
LSL (Linden Scripting Language) is the scripting language that gives behavior to Second Life primitives, objects, and avatars. This is a community effort to provide an accurate & open documentation resource on LSL for scripters of all skill levels.

Feel free to edit and add content. For more information on how to edit the wiki, see [[Project:Editing Guidelines|Editing Guidelines]]. Do not copy any information from other sources, unless you are sure about the copyright agreements. See the [[Talk:LSL Portal|LSL Portal discussion]] page for more information.

'''Want to learn LSL? See [[LSL Tutorial]].'''

<div id="box">
{| width="100%" rules="all" style="border-width: 0px; border-spacing: 5px;"
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" width="30%"|

== LSL Portal ==
<div style="padding: 0.5em;">
* [[LSL Editing Primer|Editing Primer]] - Editing Instructions
* [[LSL Portal Guidelines|Guidelines]] - Administration and Design Standards (Mission, rules, layout, etc.)
* [[LSL Portal To-do|To-Do]] - Edit/Revisions To-Do Listing
* [[LSL Portal Translation Project|Translation Project]] - Translation Coordination
</div>
|height="1" width="30%" rowspan="2"|

== LSL Language Reference ==
<div style="padding: 0.5em;">
* [[:Category:LSL Constants|Constants]]
* [[:Category:LSL Events|Events]]
* {{LSLGC|Flow Control}}
** [[for]]
** [[if]]
** [[while]]
** [[do-while]]
** [[jump]]
** [[return]]
** [[state]]
* [[:Category:LSL Functions|Functions]]
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions}}#mw-pages (A..L)]</span>
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions|from=L}}#mw-pages (L..T)]</span>
**<span class="plainlinks">[{{fullurl:Category:LSL_Functions|from=T}}#mw-pages (T..Z)]</span>
**[[LSL_Function_ID|(By internal index id)]]
* [[LSL Operators|Operators]]
* [[state|States]]
* [[:Category:LSL Types|Types]]
** [[integer]]
** [[float]]
** [[string]]
** [[key]]
** [[list]]
** [[vector]]
** [[rotation]]
* [[LSL Variables|Variables]]
* [[LSL Errors|Errors]]
</div>
|height="1" width="25%" rowspan="5"|

== {{LSLGC||LSL Features by category}} ==
<div style="padding: 0.5em;">
{| border="0" cellspacing="0" cellpadding="0"
|-valign="top"
|width="50%"|
* [[:Category:LSL Alpha|Alpha]]
* [[:Category:LSL Animation|Animation]]
* [[:Category:LSL Attachment|Attachments]]
* [[:Category:LSL Avatar|Avatar]]
* [[:Category:LSL Camera|Camera]]
* [[:Category:LSL Collision|Collision]]
* [[:Category:LSL Color|Color]]
* [[:Category:LSL Communications|Communications]]
* [[:Category:LSL Controls|Controls]]
* [[:Category:LSL Dataserver|Dataserver]]
* [[:Category:LSL Dialog|Dialog]]
* [[:Category:LSL Face|Face]]
* [[:Category:LSL Group|Group]]
* [[:Category:LSL Inventory|Inventory]]
* [[:Category:LSL Light|Light]]
* [[:Category:LSL Link|Link]]
* [[:Category:LSL LinksetData|Linkset Persistent {{abbr|KVP|Key-Value Pair}} Store]]
* [[:Category:LSL_List|Lists]]
* [[:Category:LSL Math|Math]]
* [[:Category:LSL Needs Example|Needs Example]]
* [[:Category:LSL Permissions|Permissions]]
* [[:Category:LSL Physics|Physics]]
* [[:Category:LSL Prim|Primitive]]
* [[:Category:LSL Rotation|Rotation]]
* [[:Category:LSL_Script|Scripts]]
* [[:Category:LSL Sensor|Sensor]]
* [[:Category:LSL Sound|Sound]]
* {{LSLGC|Text}}
** {{LSLGC|Chat}}
** {{LSLGC|Notecard}}
** {{LSLGC|String}}
* [[:Category:LSL Teleport|Teleport]]
* [[:Category:LSL Texture|Texture]]
* [[:Category:LSL Time|Time]]
* [[:Category:LSL Vehicle|Vehicle]]
* [[:Category:LSL Video|Video]]
* [[:Category:LSL World|World]]
|width="50%"|
* {{LSLGC|Avatar}}
** {{LSLGC|Animation}}
** {{LSLGC|Attachment}}
** {{LSLGC|Camera}}
** {{LSLGC|Controls}}
** {{LSLGC|Sit}}
* {{LSLGC|Communications}}
** {{LSLGC|Chat}}
** {{LSLGC|Dialog}}
** {{LSLGC|HTTP}}
** {{LSLGC|XML-RPC}}
* [[:Category:LSL Detected|Detection]]
** {{LSLGC|Collision}}
** {{LSLGC|Sensor}}
** {{LSLGC|Touch}}
* {{LSLGC|Functions}}
** {{LSLGC|God Mode}}
* {{LSLGC|Inventory}}
** {{LSLGC|Creator}}
** {{LSLGC|Notecard}}
** {{LSLGC|Owner}}
* {{LSLGC|Media}}
** {{LSLGC|Prim Media}}
** {{LSLGC|Sound}}
** {{LSLGC|Video}}
* {{LSLGC|Movement}}
** {{LSLGC|Physics}}
*** {{LSLGC|Damping}}
*** {{LSLGC|Hover}}
** {{LSLGC|Rotation}}
* {{LSLGC|Object}}
** [[:Category:LSL Dataserver|Dataserver]]
** {{LSLGC|Link}}
** {{LSLGC|Vehicle}}
* {{LSLGC|Permissions}}
** [[:Category:LSL Permissions/Asset|Asset]]
** [[:Category:LSL Permissions/Script|Script]]
* {{LSLGC|Prim|Primitive}}
** {{LSLGC|Effects}}
*** {{LSLGC|Light}}
*** {{LSLGC|Particles}}
** {{LSLGC|Face}}
*** {{LSLGC|Alpha}}
*** {{LSLGC|Color}}
*** {{LSLGC|Texture}}
* {{LSLGC|Region}}
** {{LSLGC|Ground}}
** {{LSLGC|Parcel}}
** {{LSLGC|Security}}
** {{LSLGC|Time}}
* {{LSLGC|Script}}
** {{LSLGC|Error}}
*** [[:Category:LSL Error/Math|Math Errors]]
** {{LSLGC|Keywords}}
** {{LSLGC|Math}}
** {{LSLGC|Types}}
|}
</div>
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1"|

== Developer Resources ==
<div style="padding: 0.5em;">

* [[:Category:LSL_User-Defined_Functions|User-Defined Functions]]
* [[LSL Protocol|User-Defined Protocols & APIs]]
----
* [[:Category:LSL Mentors|Mentors]]
* [[:Category:LSL Teachers|Teachers]]
* [[LSL_Help|Help]]
----
* [[LSL Write Once Debug Everywhere|Write Once Debug Everywhere]]
* [[LSL_Alternate_Editors|Alternate Editors]]
----
* [[LSL Tutorial|Tutorials]]
* [[:Category:LSL Examples|Examples]]
* [[LSL Style Guide|Style Guide]]
* [[LSL Script Efficiency|Efficiency]]
* [[LSL Script Memory|Memory]]
* [[LSL Hacks|Hacks]]
* [[LSL Benchmarking Scripts|Benchmarking Scripts]]
----
* [[:Category:LSL Categorized Library|Categorized Library]]
* [[:Category:LSL Library|Library]]
----
* [[LSL Test Harness|Test Harness]]
* [[LSL Useful Function WishList|Useful Function Wish-List]]
</div>
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" colspan="2"|
{{LSL News}}
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| height="1" colspan="2"|
{{LSL Bugs}}
|- valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
| colspan="2"|

== Other LSL Wikis ==
<div style="padding: 0.5em;">
* {{strike|1=[http://lslwiki.net/lslwiki/wakka.php?wakka=HomePage LSL Wiki] (The original LSL Wiki.)}} (currently offline)
* [http://lsl.project.zone/lsl/ Unofficial LSL Reference Wiki] (work in progress)
</div>

== Snapshot Mirrors ==
<div style="padding: 0.5em;">
</div>
|}
</div>
[[Category:Portals]]
[[Category:Creation]]
[[Category:LSL|*]]