Second Life Wiki - User contributions [en]

Template:LSL Constant/string

2014-01-19T04:03:42Z

Ibrew Meads: Updated for Mono

{{#vardefine:notes|{{#if:{{#var:notes}}|<br/>}}Like any [[LSO]] string constants longer then 3 characters and used in multiple places in the code, they should be stored in a global variable. The result will be a considerable memory savings. This does not apply to scripts compiled with [[Mono]]. See [[LSL Constants vs Globals]] for more information about this and examples.}}

LSL Constants vs Globals

2014-01-18T00:13:14Z

Ibrew Meads: Updated for Mono

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

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

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

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

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

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

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

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

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

Limits

2012-11-21T22:07:58Z

Ibrew Meads: /* Land */ removed reference to closed jiri issue SVC-3895

<noinclude>{{KBmaster}}</noinclude>
== Summary ==
{{RightToc}}
The Second Life Viewer and simulators have a division of labor, keeping track of the data that makes Second Life run. The Viewer's job is to:

* Handle locations of objects.
* Get velocities and other physics information, and does simple physics to keep track of what is moving where.

The simulator's job is to:

* Run the physics engine.
* Detect collisions.
* Keep track of where everything is
* Send locations of content to the Viewer along with updates when certain changes occur.

Limits are necessary for all of these components to work together. The list below outlines many of the '''Second Life numerical limits that affect your inworld experience'''. Some of these will likely change over time, so if you spot something incorrect/outdated, please take a moment to update it.

{{KBcaution|1=The scope of this page is focused on Linden Lab's official Viewers, keeping in mind [[Third_Party_Viewer_Directory|3rd-party viewers may differ]]. Cite sources and provide substantiation for limits that aren't provided by Linden Lab. Also, unconfirmed speculation [[Talk:Limits|goes on this discussion page]]. Don't add data without a hard limit, and don't add obscure trivia that doesn't practically affect the general inworld experience.|width=80%}}

== [[Avatar]] ==

* '''Max. # of attachments''' - 38 combined [[HUD]] or body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Take Off''' > '''HUD''' or '''Detach'''.
** With the formal introduction of [[multiple attachments|multiple attachments to a single point]] in Viewer 2.4, you can attach up to 38 total objects, and they can all be attached to a single point.
* '''Max. # of clothing layers per slot''' - 5 (this includes alpha and Tattoo Layers)
* '''Max. unassisted fly height''' - Stable hover at 4096m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Most women's shoes are designed for a size 0 (zero) foot. Men's generally scale up to 14.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.

* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).

* '''Max. length of {{LSLGC|Username}}''' - All lower case and a maximum of 63 including the '.'(eg; firstname.lastname)
**Older account user names are a combination of the First and last name in lower case separated by a period(.)(eg; lilmix.pixelmaid)
**Modern user names are a single name(no period)(eg; john1234) - '''Max.''' length is 31 characters
**The {{LSLGC|Legacy Name}}s for modern user names always shows Resident as the last name. So the Max is 40 characters in total for a new avatar's legacy name(including the space and last name 'Resident')
*'''Min. length of [[Display_Names]]''' - At least one script character
*'''Max. length of Display Names''' - 31 characters
**Display Names can include most Unicode script characters, spaces, and some punctuation.

* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed'''
** '''Server 1.27.1''' - 10 teleports per 15 seconds
** '''Server 1.27.0''' - 3 teleports per 15 seconds

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Animation]]
||Length of animation
| {{no|n/a}}
| {{yes|30.0 seconds}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Animation]]
||animation priority
| {{yes|0}}
| {{yes|4, with custom tools 5}}
| {{no|n/a}}
| {{yes|[[Animation_Priority]]}}
|-
||[[Animation]]
||Number of unique joints per animation
| {{no|n/a}}
| {{yes|32}}
| {{no|n/a}}
| {{no|n/a}}
|}

== Building ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||'''BUILDING'''
||[[Prim]] dimensions
| {{yes|<0.01, 0.01, 0.01>}}
| {{yes|<64.0, 64.0, 64.0>}}
| {{yes|Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770}}
| {{yes|[[llSetScale]] and [[PRIM_SIZE]] and [[Megaprim]]}}
|-
||'''BUILDING'''
||Number of prims in a linkset
| {{no|n/a}}
| {{yes|256 prims}}
| {{yes|Used to be 255 prior to Second Life Server version 1.26}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Linking distance
| {{no|n/a}}
| {{yes}}
| {{no|n/a}}
| {{yes|[[Linkability_Rules]]}}
|-
||'''BUILDING'''
||Physics weight for a physical object
| {{no|n/a}}
| {{yes|32.0}}
||Additional notes:
* If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
* On server versions 1.38 and below, each sitting avatar counted as 1 prim. From 1.40.2 the limit is only on actual prims.
| {{no|n/a}}
|-
||'''BUILDING'''
||Build or rez height
| {{no|n/a}}
| {{yes|4096.0 meters}}
| {{yes|768.0 meters for Viewers prior to version 1.20}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Prim name length
| {{no|n/a}}
| {{yes|63 bytes UTF-8 [[String|string]]}}
| {{yes|same limit for avatar names, although the character set for avatar names is significantly limited.}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Prim description length
| {{no|n/a}}
| {{yes|127 bytes UTF-8 [[String|string]]}}
| {{no|n/a}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Temporary prims' lifetime
| {{no|n/a}}
| {{yes|up to around 60 seconds}}
| {{yes|depends on when the next garbage collector cycle is.}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Number of temporary prims
| {{no|n/a}}
| {{yes|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| {{no|n/a}}
| {{no|n/a}}
|-
||'''BUILDING'''
||Length of hovertext
| {{no|n/a}}
| {{yes|a UTF-8 [[String|string]] with 254 bytes or single-byte characters}}
| {{no|n/a}}
| {{yes|[[llSetText]] and [[PRIM_TEXT]]}}
|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Communication]]
||Whisper distance
| {{no|n/a}}
| {{yes|10 meters}}
| {{yes|<code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.}}
| {{no|n/a}}
|-
||[[Communication]]
||Chat distance
| {{no|n/a}}
| {{yes|20 meters}}
| {{yes|text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered.}}
| {{no|n/a}}
|-
||[[Communication]]
||Shout distance
| {{no|n/a}}
| {{yes|100 meters}}
| {{yes|<code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.}}
| {{no|n/a}}
|-
||[[Communication]]
||Length of a chat message and whether or not it is truncated
| {{yes|1 byte or single-byte character}}
| {{yes|1024 bytes or single-byte characters}}
| {{yes|Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1180 bytes or single-byte characters. This is true as of 2012-08-13.}}
| {{yes|[[llInstantMessage]]}}
|-
||[[Communication]]
||Number of offline messages
| {{no|n/a}}
| {{yes|Capped at 25 messages.}}
| {{yes|Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped.}}
| {{yes|[[IM]]}}
|-
||[[Communication]]
||Length of a properly delivered email reply to an [[IM]]
| {{no|n/a}}
| {{yes|1023 bytes or single-byte characters}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Communication]]
||Time after which a reply to an [[IM]] can be sent via email.
| {{yes|when receiving the IM via email.}}
| {{yes|5 days after receiving the offline IM via email.}}
| {{no|n/a}}
| {{yes|[https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]}}
|-
||[[Communication]]
||Time period for which [[IM|IMs]] are stored within Second Life.
| {{no|n/a}}
| {{yes|31 days after receiving the [[IM]]}}
| {{yes|[[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]}}
| {{no|n/a}}
|-
||[[Communication]]
||Number of [[IM|IMs]] sent by an object within an hour
| {{no|n/a}}
| {{yes|5000 per hour}}
| {{no|n/a}}
| {{no|n/a}}
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Gesture]]
||Shortcut key mappings
| {{no|n/a}}
| {{yes|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| {{no|n/a}}
| {{yes|[[All_keyboard_shortcut_keys]] and [[Viewer_2_Quick_Start_Guide/Appendix_-_Keyboard_Shortcuts]]}}
|-
||[[Gesture]]
||Chat step length
| {{no|n/a}}
| {{yes|127 bytes or single-byte characters}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Gesture]]
||Wait time
| {{no|n/a}}
| {{yes|3600 seconds (which is one hour)}}
| {{no|n/a}}
| {{no|n/a}}
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Minimum number of members in a group:''' 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Maximum number of roles allowed in a group:''' 10 (including "Owners" and "Everyone", which cannot be deleted)
* '''Maximum Group Name:''' 35 single-byte characters.
* '''Maximum Group Title:''' 20 single-byte characters.
* '''Maximum Length of a Group Notice:''' 512 single-byte characters.

== [[Inventory]] ==

* '''Maximum number of inventory items that can be sent in a folder:''' 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references.
* '''Maximum notecard line:''' None, but scripts can only read the first 255 bytes.
* '''Maximum notecard size:''' 65,536 bytes
* '''Number of items in the Library:''' 1,248 as of 2010-06-17
* '''Number of items in the Library:''' 2,210 as of 2012-11-04
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.

== [[Land]] ==

* '''Maximum [[Land#Parcel|parcel]] size:''' 65,536 meters²
** Covering a whole region, or square on the World Map.
* '''Minimum parcel size:''' 16 meters²
* '''Maximum parcel name length:''' 63 single-byte characters
* '''Maximum parcel description length:''' 255 characters
* '''Region name length:''' Under Linden Concierge policy, minimum of 3 characters, and a maximum of 25 characters (including spaces). See [[Linden Lab Official:Guidelines for Private Region Naming|Guidelines for Private Region Naming]].
** Rare exceptions exist, like [http://slurl.com/secondlife/Q/128/128/24 Q].
* '''Maximum "NO ENTRY" ban line height:''' is for all options 80 meter. Only the option 'Banned Residents' (named) has a 5020 meter ban line high, which is visible up to a high of 800 meter above the terrain mesh.
* '''Maximum prims in a [[Land#Region|region]]:'''
** Full region: 15,000
** [[Land#Homestead|Homestead]]: 3,750
** [[Land#Openspace|Openspace]]: 750
* '''Maximum auto return value''': Besides "0" (which means ''never''), {{HoverText|999,999|Almost 23 months}} minutes is the highest auto return value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by 4 meters (+/-).
** Some mainland cannot be terraformed, including: Bay City Regions, Blumfield, Boardman, Brown, De Haro, Nautilus City Regions, Nova Albion Regions, Shermerville Regions, and West Haven.
** A few, very old mainland Regions like Da Boom have a terraform range of 40 meters (+/-).
** Estate (private island) terraformability is settable to a maximum of 100 meters (+/-) by the estate owner or managers.
* '''Maximum water height:''' 100 meters using inworld controls (mainland limit), 255 meters by using a *.raw file upload.
** Region water height is usually 20 meters, and adjacent regions should have the same water height, or else they will look discontinuous.
* '''Maximum terrain height:''' 255 meters using inworld controls (mainland limit), 510 meters by using a *.raw file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 10 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Mainland maximum number of agents'''
** Full region: 100 (Historically set to 40 by LL but this does vary. Some meeting areas have this set to 60 and higher.)
*** Recent server performance improvements make regions with 60 agents in them perform quite well.
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Island maximum number of agents:'''
** Full region: 100
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Freeze Time:''' Land owners can [[freeze]] other Residents for up to 30 seconds. Members of land owning groups can also be granted this ability.
* '''Minimum parcel that can be listed in Places or All search:''' 144 meters² 
* '''Minimum parcel that can be listed in Events:''' 512 meters²
* '''Maximum altitude for event listings:''' 768 meters ({{JIRA|WEB-814}})
* '''Maximum heights that objects can be seen on the [[World Map]]:''' 400.005m
* '''[[Classic clouds]] layer:''' Approximately 150-225 meters, although the edges of particles can appear to exceed that.

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Mesh]]
||Number of vertices
| {{no|n/a}}
| {{yes|65536 vertices per LOD for each [[mesh]]}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Mesh]]
||COLLADA file size
| {{no|n/a}}
| {{yes|Maximum mesh asset size after compression is 8 MB, roughly equivalent to a 256 MB Raw COLLADA file.}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Mesh]]
||Bone influence weights per vertex
| {{no|n/a}}
| {{yes|4}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Mesh]]
||Number of materials per mesh
| {{no|n/a}}
| {{yes|8}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Mesh]]
||Number of materials per face
| {{no|n/a}}
| {{yes|1}}
| {{no|n/a}}
| {{no|n/a}}
|-
||[[Mesh]]
||Physics weight for a vehicle
| {{no|n/a}}
| {{yes|32.0}}
| {{no|n/a}}
| {{no|n/a}}
|}

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.
*'''Contacts in Communication > Friends tab ''' - A maximum of 20 simultaneous contacts can be selected to change permissions, remove, or invite for a conference chat.

== Navigation ==

[[File:Max Alt.jpg|thumb|right|435px|'''Height counter error above 2147483647 meters''']]
* '''Absolute height limit:''' [http://en.wikipedia.org/wiki/2147483647#2147483647_in_computing 2147483647] = 2<sup>31</sup> − 1 meters, which causes the altitude counter to roll over. Altitudes well below this cause graphics errors probably due to limited floating point number precision.
* '''Highest z-value of an [[SLurl]], that will still teleport you to a positive altitude:''' 2147483583
** This is lower than the ''Absolute height limit'' above probably because of precision issues. Any value higher than 2147483583 would be rounded up to something beyond 2147483647 and thus cause an [http://en.wikipedia.org/wiki/Arithmetic_overflow overflow], while 2147483583 will still be rounded down to 2147483520 (see below).
* '''Highest altitude you can teleport to with an SLurl:''' 2147483520 meters

== [[Profile]] ==

Each 7-bit ASCII character is encoded in one byte. International characters might need more bytes. When pasting text instead of typing, you can get in one byte more into each of the below.

* '''2nd Life tab's About field''' - 510 bytes
* '''Picks tab''' - 10 picks with 1022 bytes each
* '''1st Life tab's Info field''' - 253 bytes
* '''Classified tab''' - 100 listings with x bytes each
* '''My Notes''' - 1022 bytes

== Performance ==

* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via Help menu > Lag Meter, or for more advanced usage, see View menu > Statistics Bar.
* '''Avatar Rendering Cost scores''' - [[Avatar Rendering Cost|Learn all about it!]]

== [[Scripting]] ==

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls continue to remain active when you fly down or enter a no-script parcel.
* '''Maximum height where scripts can run''' - none, as long as the object remains rezzed or attached.
* '''Maximum script source code size''' - 65536 single byte characters.
* For specific scripting limits, lookup calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Category'''
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Sound]]
||Soung length
| {{no|n/a}}
| {{yes|10.0 seconds}}
| {{yes|You're advised to cut longer sounds into 9.9-second-pieces.}}
| {{no|n/a}}
|}

== [[Textures]] ==
* '''[http://en.wikipedia.org/wiki/Aspect_ratio Aspect ratios]''' of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000:

=== 1.x Series Viewers ===

(official Viewer up to 1.23.5, most [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pi×els)
* '''Search > Places and Classified tabs''' - ~7:5 (398×282 pixels)
* '''Search > Land tab''' - ~7:5 (358×252 pixels)
* '''Profile > 2nd Life tab''' - ~4:3 (178×133 pixels)
* '''Profile > Picks tab''' - 16:9 (288×162 pixels)
* '''Profile > 1st Life tab''' - 1:1 (133×133 pixels)
* '''Profile > Classifieds tab''' - ~3:2 (206×137 pixels)
* '''Profile > Web tab''' - 1:1 (400×400 pixels)
** A scrollbar uses 15 pixels on the right-hand side.
* '''About Land > Options tab''' - ~3:2 (178×117 pixels)
* '''Group Information > General tab's "Group Insignia"''' - 1:1 (126×126 pixels)
** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.
** [[Texture_aspect_ratios|Learn how to get correct texture aspect ratios when editing images.]]

=== 2.x Series Viewers ===

* '''Search > Classifieds thumbnail''' - 4:3 (60×45 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (252×188 pixels)
* '''Search > Classifieds expanded > Details''' - 17:7 (272×112 pixels)
* '''Search > People''' - 4:3 (188×141 pixels)
* '''Search > Destination Guide thumbnail''' - ~4:3 (45×34 pixels)
* '''Search > Destination Guide expanded''' - 5:3 (250×150 pixels)
* '''Profile > 2nd Life tab''' - ~1:1 (100×99 pixels)
* '''Profile > Picks thumbnail''' - 8:5 (88×55 pixels)
* '''Profile > Pick expanded''' - ~5:3 (285×172 pixels)
* '''About Land > Options tab''' - ~20:13 (193×125 pixels)
* '''Places > More information''' - ~11:7 (272×173 pixels)

=== All Viewers ===

* '''Maximum texture size''' - 1024×1024 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** Some textures inworld have a resolution as high as 2048×2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load.
** Where large textures are being forced by import to only 512×512, lower your ...> Preferences >...> UI Size under 1.0, to increase import size to the max 1024×1024.

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

=== Notes ===
In general 1 byte is enough to contain one character.

Category:LSL Base64

2012-10-22T01:55:58Z

Ibrew Meads: Added a description of Base64.

{{LSL Header|ml=*}}{{LSLC|}}{{LSLC|Encoding}}
== About Base64 encoding ==
Base64 conversion expands three bytes of arbitrary binary data into four bytes of common ASCII characters in a completely reversible algorithm. It is generally used to convert binary data to strings so they can be sent across a text interface where ASCII control characters might be misinterpreted as end of string (\0) newline (\n) or otherwise not be transferred properly to the receiving process. In LSL this might be used to store binary data in an object's description, break data into bytes for cryptographic processing, or send data from one process to another using chat or linked messages.

Base64 input can be any sequence of bytes, the output consists exclusively of uppercase and lowercase letters, digits and the plus (+), slash (/) and equals (=) characters. Conversion to Base64 is done in blocks of three bytes (24 bits), padded if needed. These twenty-four bits are split into four six bit numbers which become an index to the conversion key ("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/") and written out as the eight bit ASCII character. Since the data is converted three bytes at a time, zero one or two equals characters are added to indicate how much padding was done in the last block. See [http://en.wikipedia.org/wiki/Base64 the Wikipedia article] for more information.

== Examples ==
String and integer data in Base64.
<div align="left">
{| style="border:1px solid #A3B1BF; text-align:left; background:#f5faff"
|-
| width="50%" style="background: #cee0f2; padding: 0.3em; text-align:center;"|'''Text'''
| style="background: #cee0f2; padding: 0.3em; text-align:center;"|'''Base64'''
|-
|Abcde
|QWJjZGU=
|-
|ⓐⓑⓒⓓⓔ
|4pOQ4pOR4pOS4pOT4pOU
|-
|12345 (as an integer)
|AAAwOQ==
|}

How can I view more than 35 avatars at once?

2010-01-15T19:07:44Z

Ibrew Meads: Added actual instructions on what debug setting to change.

{{KBmaster}}

For performance reasons, the Second Life® viewer only allows you to see up to 35 avatars at one time; if you are in an area with more than 35 other avatars, you may notice that some of them fade in and out of visibility as you move your camera. By rendering only the avatars closest to your camera, the Second Life viewer can provide you with a much smoother experience.

However, we understand that there may be times when you absolutely ''need'' to see all the avatars in an area; it wouldn't be very fun to go to a live music or theatre event and not see the performers! Luckily, there is a way to change the maximum number of avatars you can see at once:

{{KBwarning| Follow the instructions in this article at your own risk; changing debug settings in the Second Life viewer can have unexpected negative effects. You should always keep a log of which debug settings you change, so that you can restore their defaults if you notice a decrease in performance or usability. Our support team may not be able to provide help if you experience problems as a result of a debug setting change.}}

==How to increase the maximum number of avatars you can see==

Set the debug setting RenderAvatarMaxVisible to the number of avatars you want to be able to see.

{{KBcaution| Forcing the Second Life viewer to render a very large number of avatars can have a negative impact on the performance of the viewer. You should only increase this number if you absolutely ''need'' to view more than 35 avatars at once!}}
[[Category:Improving Performance]]
[[Category:Educators]]
[[Category:Performance]]
[[Category:Menus and Controls]]
[[Category:Inworld]]

[[Category:Knowledge Base]]

User:Ibrew Meads

2009-09-26T03:45:39Z

Ibrew Meads: Just something to get the page here

Computer programmer and basic geek grrl who still hasn't learned that programming isn't supposed to be fun and wishes she could live here in SL full time.

LSL Protocol/RestrainedLifeAPI

2009-09-17T13:45:11Z

Ibrew Meads:

=Restrained Life viewer v1.20 Specification=

By [[User:Marine Kelley|Marine Kelley]]

==Audience==

This document is aimed at people who wish to modify or create their own [[LSL]] scripts to use the functionalities of the [http://realrestraint.blogspot.com RestrainedLife viewer]. It does not, however, explain [[LSL]] concepts such as messages and events, nor universal concepts such as [[UUID]]s.

==Introduction==

The [http://realrestraint.blogspot.com RestrainedLife viewer] is meant to execute certain behaviours when receiving special messages from scripts in-world. These messages are mostly calls to the [[llOwnerSay]]() [[LSL]] function.

==Architecture==

The [http://realrestraint.blogspot.com RestrainedLife viewer] parses every [[llOwnerSay]] call and executes every command beginning with ''''@''''. For instance, a call to [[llOwnerSay]] ("@detach=n") will tell the viewer that the object sending the message cannot be detached until further notice.

Version '''1.10''' and above are able to parse multiple commands in one message, in order to avoid spamming the user who is not using this viewer. The format of a message is therefore :

@<behaviour1>[:option1]=<param1>,<behaviour2>[:option2]=<param2>,...,<behaviourN>[:optionN]=<paramN>

Note that there is only one '@' sign, placed at the beginning of the message. The viewer understands this as "this whole [[llOwnerSay]]() is actually a command to execute", so no need to put a '@' before every command, it wouldn't even work. If at least one command fails (typo), the viewer says "... fails command : ... " and mentions it all. However correct commands are parsed and executed, only incorrect ones are discarded.

'''Warning''' : These behaviours are '''not''' persistent between sessions, and an object changes [[UUID]] everytime it [[rez]]zes. This means the object must resend its "status" (undetachable, preventing IMs...) in the [[on_rez]] () event as well as when it changes.

==List of commands==

''Note : These commands are not case-sensitive but are spacing-sensitive. In other words, "@detach = n" will '''not''' work.''

* '''''Automated version checking''''' : "@version=<channel_number>"
''Implemented in v1.0b''
Makes the viewer automatically say its version immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout.

'''Warning''' : when logging in, the [[on_rez]] event of all the attachments occurs way before the avatar can actually send chat messages (about half the way through the login progress bar). This means the timeout should be long enough, like 30 seconds to one minute in order to receive the automatic reply from the viewer.

* '''''Automated version checking, second way''''' : llGetAgentLanguage (key id) '''''DEPRECATED: DO NOT USE !'''''
''Implemented in v1.16''
When calling this LSL function, the result is obtained immediately (no need to use a listener and a timer), is exactly equal to the one given by "@version" and cannot be hidden by the user. This string takes the place of the language returned by the regular SL viewer, which could answer values like "en-us", "fr", "ko" etc. Or nothing at all, if the user chose to hide their language setting. Being optional in the regular viewer, it cannot be trusted by a script, so "hijacking" this feature for the much more useful synchronous version checking in the RLV makes sense. IMPORTANT NOTE: this feature cannot be implemented in viewers prior to v1.21, even when they do implement RestrainedLife v1.16, so make sure you do fall back to the @version method whenever llGetAgentLanguage() returns an empty string. ALSO NOTE: In RestrainedLife 1.16, llGetAgentLanguage() will return an empty string when called by on_rez during login unless the call is delayed by several seconds (how many seconds may vary). FINAL NOTE: This feature was removed from v1.16.1 (and v1.16b, for the Cool SL Viewer).

* '''''Manual version checking''''' : "@version"
''Implemented in v1.0a''
This command must be sent in IM from an avatar to the user (will not work from objects). The viewer automatically answers its version to the sender in IM, but neither the message nor the answer appears in the user's IM window, so it's totally stealthy.

* '''''Render an object detachable/nondetachable''''' : "@detach=<y/n>"
''Implemented in v1.0a''
When called with the "n" option, the object sending this message (which must be an attachment) will be made nondetachable. It can be detached again when the "y" option is called.

* '''''Unlock/Lock an attachment point''''' : "@detach:<attach_point_name>=<y/n>"
''Implemented in v1.20''
When called with the "n" option, the attachment point of name <attach_point_name> will be locked either full (if it is occupied by an object at that time) or empty (if not). Any object that is occupying this point when the restriction is issued will be considered as undetachable, exactly like if it had issued a "@detach=n" command itself. If the point is empty it will stay that way, no item will be able to be attached there, and llAttachToAvatar() calls will fail (the object will be attached, then detached right away).

* '''''Start/stop notifications on a private channel''''' : "@notify:<channel_number>[;word]=add/rem"
''Implemented in v1.20''
Makes the viewer automatically repeat any restriction it adds or removes on the specified channel, or only the restrictions which name contains the word specified after the semicolon (";") character. The response on the private channel <channel_number> is preceded with a slash ("/") to avoid making the avatar send commands to other scripts without knowing it, and followed by an equal sign ("=") and "n" or "y" according to whether the restriction is applied or lifted respectively. The "@clear" command will not add an equal sign. There is no way to know what object issued the restriction or lifted it, to avoid disclosing too much information about foreign scripts. It does not repeat one-shot commands either (force commands). For example, "@notify:2222,detach=add" will send "/detach=n" whenever an object is locked, and "/detach=y" whenever an object is unlocked, on channel 2222 to which the script will listen to.

* '''''Allow/prevent sending chat messages''''' : "@sendchat=<y/n>"
''Implemented in v1.0b''
When prevented, everything typed on [[channel]] 0 will be discarded. However, emotes and messages beginning with a slash ('/') will go through, truncated to strings of 30 and 15 characters long respectively (likely to change later). Messages with special signs like ()"-*=_^ are prohibited, and will be discarded. When a period ('.') is present, the rest of the message is discarded.

* '''''Remove/add an exception to the emote truncation above''''' : "@emote=<rem/add>"
''Implemented in v1.01''
When adding this exception, the emotes are not truncated anymore (however, special signs will still discard the message).

* '''''Allow/prevent shouting''''' : "@chatshout=<y/n>"
''Implemented in v1.15''
When prevented, the avatar will chat normally even when the user tries to shout. This does not change the message in any way, only its range.

* '''''Allow/prevent chatting at normal volume''''' : "@chatnormal=<y/n>"
''Implemented in v1.15''
When prevented, the avatar will whisper even when the user tries to shout or chat normally. This does not change the message in any way, only its range.

* '''''Allow/prevent whispering''''' : "@chatwhisper=<y/n>"
''Implemented in v1.15''
When prevented, the avatar will chat normally even when the user tries to whisper. This does not change the message in any way, only its range.

* '''''Redirect public chat to private channels''''' : "@redirchat:<channel_number>=<rem/add>"
''Implemented in v1.16''
When active, this restriction redirects whatever the user says on the public channel ("/0") to the private channel provided in the option field. If several redirections are issued, the chat message will be redirected to each channel. It does not apply to emotes, and will not trigger any animation (typing start, typing stop, nodding) when talking. This restriction does not supercede @sendchannel.

* '''''Redirect public emotes to private channels''''' : "@rediremote:<channel_number>=<rem/add>"
''Implemented in v1.19''
When active, this restriction redirects whatever emote the user says on the public channel ("/0") to the private channel provided in the option field. If several redirections are issued, the emote will be redirected to each channel.

* '''''Allow/prevent sending instant messages''''' : "@sendim=<y/n>"
''Implemented in v1.0b''
When prevented, everything typed in IM will be discarded and a bogus message will be sent to the receiver instead.

* '''''Remove/add exceptions to the instant message sending prevention''''' : "@sendim:<UUID>=<rem/add>"
''Implemented in v1.01''
When adding an exception, the user can send IMs to the receiver whose [[UUID]] is specified in the command. This overrides the prevention for this avatar only (there is no limit to the number of exceptions), don't forget to remove it when it becomes obsolete.

* '''''Allow/prevent receiving chat messages''''' : "@recvchat=<y/n>"
''Implemented in v1.0b''
When prevented, everything heard in public chat will be discarded except emotes.

* '''''Remove/add exceptions to the chat message receiving prevention''''' : "@recvchat:<UUID>=<rem/add>"
''Implemented in v1.01''
When adding an exception, the user can hear chat messages from the sender whose [[UUID]] is specified in the command. This overrides the prevention for this avatar only (there is no limit to the number of exceptions), don't forget to remove it when it becomes obsolete.

* '''''Allow/prevent seeing emotes''''' : "@recvemote=<y/n>"
''Implemented in v1.19''
When prevented, every emote seen in public chat will be discarded.

* '''''Remove/add exceptions to the emote seeing prevention''''' : "@recvemote:<UUID>=<rem/add>"
''Implemented in v1.19''
When adding an exception, the user can see emotes from the sender whose [[UUID]] is specified in the command. This overrides the prevention for this avatar only (there is no limit to the number of exceptions), don't forget to remove it when it becomes obsolete.

* '''''Allow/prevent receiving instant messages''''' : "@recvim=<y/n>"
''Implemented in v1.0b''
When prevented, every incoming IM will be discarded and the sender will be notified that the user cannot read them.

* '''''Remove/add exceptions to the chat message receiving prevention''''' : "@recvim:<UUID>=<rem/add>"
''Implemented in v1.01''
When adding an exception, the user can read instant messages from the sender whose [[UUID]] is specified in the command. This overrides the prevention for this avatar only (there is no limit to the number of exceptions), don't forget to remove it when it becomes obsolete.

* '''''Allow/prevent teleporting to a landmark''''' : "@tplm=<y/n>"
''Implemented in v1.0''
When prevented, the user cannot use a [[landmark]], pick or any other preset location to [[teleport]] there.

* '''''Allow/prevent teleporting to a location''''' : "@tploc=<y/n>"
''Implemented in v1.0''
When prevented, the user cannot use [[teleport]] to a coordinate by using the [[map]] and such.

* '''''Allow/prevent teleporting by a friend''''' : "@tplure=<y/n>"
''Implemented in v1.0''
When prevented, the user automatically discards any [[teleport]] offer, and the avatar who initiated the offer is notified.

* '''''Remove/add exceptions to the friend teleport prevention''''' : "@tplure:<UUID>=<rem/add>"
''Implemented in v1.0''
When adding an exception, the user can be teleported by the avatar whose [[UUID]] is specified in the command. This overrides the prevention for this avatar only (there is no limit to the number of exceptions), don't forget to remove it when it becomes obsolete.

* '''''Unlimit/limit sit-tp''''' : "@sittp=<y/n>"
''Implemented in v1.0''
When limited, the avatar cannot sit on a [[prim]] unless it is closer than 1.5 m. This allows cages to be secure, preventing the avatar from warping its position through the walls (unless the prim is too close).

* '''''Clear all the rules tied to an object''''' : "@clear"
''Implemented in v1.0a, but working only since v1.04a''
This command clears all the restrictions and exceptions tied to a particular [[UUID]].

* '''''Clear a subset of the rules tied to an object''''' : "@clear=<string>"
''Implemented in v1.0a, but working only since v1.04a''
This command clears all the restrictions and exceptions tied to a particular [[UUID]] which name contains <string>. A good example would be "@clear=tp" which clears all the [[teleport]] restrictions and exceptions tied to that object, whereas "@clear=tplure:" would only clear the exceptions to the "teleport-by-friend" restriction

* '''''Allow/prevent editing objects''''' : "@edit=<y/n>"
''Implemented in v1.03''
When prevented from editing and opening objects, the Build & Edit window will refuse to open.

* '''''Allow/prevent rezzing inventory''''' : "@rez=<y/n>"
''Implemented in v1.03''
When prevented from [[rez]]zing stuff, creating and deleting objects, drag-dropping from inventory and dropping attachments will fail.

* '''''Allow/prevent wearing clothes''''' : @addoutfit[:<part>]=<y/n>
''Implemented in v1.10, added skin hair and eyes in v1.10.1''
Where part is :
gloves|jacket|pants|shirt|shoes|skirt|socks|underpants|undershirt|skin|eyes|hair|shape
If part is not specified, prevents from wearing anything beyond what the avatar is already wearing.

* '''''Allow/prevent removing clothes''''' : @remoutfit[:<part>]=<y/n> (underpants and undershirt are kept for teens)
''Implemented in v1.10, added skin hair and eyes in v1.10.1''
Where part is :
gloves|jacket|pants|shirt|shoes|skirt|socks|underpants|undershirt|skin|eyes|hair|shape
If part is not specified, prevents from removing anything in what the avatar is wearing.

* '''''Force removing clothes''''' : @remoutfit[:<part>]=force (*) (teens can't be forced to remove underpants and undershirt)
''Implemented in v1.10''
Where part is :
gloves|jacket|pants|shirt|shoes|skirt|socks|underpants|undershirt|skin|eyes|hair|shape
If part is not specified, removes everything.

* '''''Force removing attachments''''' : @detach[:attachpt]=force (*)
''Implemented in v1.10''
Where part is :
chest|skull|left shoulder|right shoulder|left hand|right hand|left foot|right foot|spine|
pelvis|mouth|chin|left ear|right ear|left eyeball|right eyeball|nose|r upper arm|r forearm|
l upper arm|l forearm|right hip|r upper leg|r lower leg|left hip|l upper leg|l lower leg|stomach|left pec|
right pec|center 2|top right|top|top left|center|bottom left|bottom|bottom right
If part is not specified, removes everything.

* '''''Get the list of worn clothes''''' : @getoutfit[:part]=<channel_number>
''Implemented in v1.10, added skin hair and eyes in v1.10.1''
Makes the viewer automatically answer the current occupation of clothes layers as a list of 0s (empty) and 1s (occupied) immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout.

The list of 0s and 1s corresponds to :
gloves,jacket,pants,shirt,shoes,skirt,socks,underpants,undershirt,skin,eyes,hair,shape
in that order.

If a part is specified, answers a single 0 (empty) or 1 (occupied) corresponding to the part.
Ex 1 : @getoutfit=2222 => "0011000111" => avatar is wearing pants, shirt, underpants and undershirt, and of course a skin.
Ex 2 : @getoutfit:socks=2222 => "0" => the avatar is not wearing socks.

* '''''Get the list of worn attachments''''' : @getattach[:attachpt]=<channel_number>
''Implemented in v1.10''
Makes the viewer automatically answer the current occupation of attachment points as a list of 0s (empty) and 1s (occupied) immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout.

The list of 0s and 1s corresponds to :
none,chest,skull,left shoulder,right shoulder,left hand,right hand,left foot,right foot,spine,
pelvis,mouth,chin,left ear,right ear,left eyeball,right eyeball,nose,r upper arm,r forearm,
l upper arm,l forearm,right hip,r upper leg,r lower leg,left hip,l upper leg,l lower leg,stomach,left pec,
right pec,center 2,top right,top,top left,center,bottom left,bottom,bottom right
in that order.

If an attachment point is specified, answers a single 0 (empty) or 1 (occupied) corresponding to the point.
Ex 1 : @getattach=2222 => "011000011010000000000000100100000000101" => avatar is wearing attachments on
chest, skull, left and right foot, pelvis, l and r lower leg, HUD bottom left and HUD bottom right.
Ex 2 : @getattach:chest=2222 => "1" => avatar is wearing something on the chest.

''Note'' : The first character ("none") is always '0', so the index of each attach point in the string is '''exactly equal''' to the corresponding ATTACH_* macro in LSL. For instance, the index 9 in the string is ATTACH_BACK (which means "spine"). Remember the indices start at zero.

* '''''Force the viewer to automatically accept attach and take control permission requests''''' : @acceptpermission=<rem/add>
''Implemented in v1.16''
Forces the avatar to automatically accept attach and take control permission requests. The dialog box doesn't even show up. This command does not supercede @denypermission, of course.

* '''''Allow/prevent accepting attach and take control permissions''''' : @denypermission=<rem/add>
''Implemented in v1.16, DEPRECATED in v1.16.2''
When prevented, all attach and take control permission requests are automatically declined, without even showing the dialog box. Due to the extreme annoyance it was making, and because locked objects automatically reattach themselves since v1.16.1, this command is NOW DEPRECATED, DON'T USE IT !

* '''''Allow/prevent using inventory''''' : @showinv=<y/n>
''Implemented in v1.10''
Forces the [[inventory]] windows to close and stay closed.

* '''''Allow/prevent reading notecards''''' : @viewnote=<y/n>
''Implemented in v1.10''
Prevents from opening [[notecards]] but does not close the ones already open.

* '''''Allow/prevent standing up''''' : @unsit=<y/n>
''Implemented in v1.10, modified in v1.15 to prevent teleporting as well''
Hides the Stand up button. From v1.15 it also prevents teleporting, which was a way to stand up.

* '''''Force sit on an object''''' : @sit:<UUID>=force (*)
''Implemented in v1.10''
Does not work if the user is prevented from sit-tping and further than 1.5 meters away, or when prevented from unsitting.

* '''''Force unsit''''' : @unsit=force (*)
''Implemented in v1.10''
Self-explanatory but for some reason it randomly fails, so don't rely on it for now. Further testing is needed.

* '''''Allow/prevent sitting down''''' : @sit=<y/n>
''Implemented in v1.16.2''
Prevents the user from sitting on anything, including with @sit:UUID=force.

* '''''Allow/prevent using any chat channel but certain channels''''' : @sendchannel[:<channel>]=<y/n>
''Implemented in v1.10''
Complimentary of @sendchat, this command prevents the user from sending messages on non-public [[channel]]s. If channel is specified, it becomes an exception to the aforementioned restriction. It does not prevent the viewer automatic replies like @version=nnnn, @getstatus=nnnn etc.

* '''''Get the list of restrictions the avatar is currently submitted to''''' : @getstatus[:<part_of_rule>]=<channel>
''Implemented in v1.10, slightly tweaked in v1.16''
Makes the viewer automatically answer the list of rules the avatar is currently under, only for the object containing the script issuing that command, immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. The answer is a list of rules, separated by slashes ('/'). Attention : since v1.16 a slash is prepended at the beginning of the string. This does not confuse llParseString2List() calls, but does confuse llParseStringKeepNulls() calls !

This command is useful for people who write scripts that may conflict with other scripts in the same object (for instance : third-party plugins). Conflicts do not occur in different objects, that's why this command only applies to the object calling it.

<part_of_rule> is the name of a rule, or a part of it, useful if the script only needs to know about a certain restriction.

Example : If the avatar is under tploc, tplure, tplm and sittp, here is what the script would get :
@getstatus=2222 => tploc/tplure/tplm/sittp
@getstatus:sittp=2222 => sittp
@getstatus:tpl=2222 => tploc/tplure/tplm (because "tpl" is part of "tploc", "tplure" and "tplm" but not "sittp")

* '''''Get the list of all the restrictions the avatar is currently submitted to''''' : @getstatusall[:<part_of_rule>]=<channel>
''Implemented in v1.15, slightly tweaked in v1.16''
Makes the viewer automatically answer the list of rules the avatar is currently under, for all the objects regardless of their UUID, contrary to @getstatus, immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. The answer is a list of rules, separated by slashes ('/'). Attention : since v1.16 a slash is prepended at the beginning of the string. This does not confuse llParseString2List() calls, but does confuse llParseStringKeepNulls() calls !

* '''''Get the list of shared folders in the avatar's inventory''''' : @getinv[:folder1/.../folderN]=<channel_number>
''Implemented in v1.11, added sub-folders in v1.13''
Makes the viewer automatically answer the list of folders contained into the folder named "#RLV" (if it exists), immediately on the chat channel number <channel_number> that the script can listen to. If folders are specified, it will give the list of sub-folders contained into the folder located at that path instead of the shared root (example : "@getinv:Restraints/Leather cuffs/Arms=2222"). Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout.

The answer is a list of names, separated by commas (","). Folders which names begin with a dot (".") will be ignored.

* '''''Get the list of shared folders in the avatar's inventory, with information about worn items''''' : @getinvworn[:folder1/.../folderN]=<channel_number>
''Implemented in v1.15''
Makes the viewer automatically answer the list of folders contained into the folder named "#RLV" (if it exists), immediately on the chat channel number <channel_number> that the script can listen to. If folders are specified, it will give the list of sub-folders contained into the folder located at that path instead of the shared root (example : "@getinvworn:Restraints/Leather cuffs/Arms=2222"). Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout.

The answer is a comma-separated list of names, each one followed with a pipe ("|") and two digits. The current folder is put in first position (as opposed to @getinv which does not show the current folder, obviously), but without a name, only the pipe and the two digits.

Object : "@getinvworn:Restraints/Leather cuffs=2222"
Viewer : "|02,Arms|30,Legs|10"

Folders which names begin with a dot (".") will be ignored. The two digits are calculated as follows :

First digit : Proportion of items worn in the corresponding folder (including no-mod items). In this example, the "3" of "30" means "all the items in the "Arms" folder are currently worn, while the "1" of "10" means "no item in the Legs folder is currently worn, but there are items to wear".

Second digit : Proportion of items globally worn in all the folders contained inside the corresponding folder. In this example, the "2" of "02" means "some items are worn in some of the folders contained into "Leather cuffs".

The digits, comprised between 0 and 3 included, have the following meaning :

* 0 : No item is present in that folder
* 1 : Some items are present in that folder, but none of them is worn
* 2 : Some items are present in that folder, and some of them are worn
* 3 : Some items are present in that folder, and all of them are worn

* '''''Get the path to a shared folder by giving a search criterion''''' : @findfolder:part1[&&...&&partN]=<channel_number>
''Implemented in v1.13.1''
Makes the viewer automatically answer the path to the first shared folder which name contains <part1> and <part2> and ... and <partN>, immediately on the chat channel number <channel_number> that the script can listen to. The search is in depth first, notice the separator which is "&&" like "and". Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. It does not take disabled folders into account (folders which name begins with a dot "."). The answer is a list of folders, separated by slashes ('/').

* '''''Force attach items contained inside a shared folder''''' : @attach:<folder1/.../folderN>=force (*)
''Implemented in v1.11, added no-mod items in v1.12, added sub-folders in v1.13''
Forces the viewer to attach every object and wear every piece of clothing contained inside the folder located at the specified path (which must be under "#RLV"). Objects names '''must''' contain the name of their target attachment point or they won't be attached. Each no-modify object '''must''' be contained inside a folder (one object per folder), which name contains the name of its target attachment point since it can't be renamed. Names cannot begin with a dot (".") since such folders are invisible to the scripts.

Attachment point names are the same as the ones contained into the "Attach To" submenu : "skull", "chest", "l forearm"...

Note : Folder names '''can''' contain slashes, and will be chosen in priority when able (for instance, if "@attach:Restraints/cuffs=force" is issued, the "Restraints/cuffs" folder will be chosen before a "cuffs" folder contained inside a "Restraints" parent folder.

* '''''Force attach items contained inside a shared folder, and its children recursively''''' : @attachall:<folder1/.../folderN>=force (*)
''Implemented in v1.15''
This command works exactly like @attach described hereabove, but also attaches whatever is contained into children folders.

* '''''Force detach items contained inside a shared folder''''' : @detach:<folder_name>=force (*)
''Implemented in v1.11''
Forces the viewer to detach every object and unwear every piece of clothing contained inside <folder_name>(which must be directly under "#RLV"). If "@detach" is used with an attachment point name (skull, pelvis... see above), it takes priority over this way of detaching since it is the same command.

* '''''Force detach items contained inside a shared folder, and its children recursively''''' : @detachall:<folder1/.../folderN>=force (*)
''Implemented in v1.15''
This command works exactly like @detach described hereabove, but also detaches whatever is contained into children folders.

* '''''Get the path to the shared folder containing a particular object/clothing''''' : @getpath[:<attachpt> or <clothing_layer>]=<channel_number>
''Implemented in v1.16''
Makes the viewer automatically answer the path to the shared folder containing the item that :
** issues this command if no option is set
** is attached on the attach point provided in the option field, ex : @getpath:spine=2222 => "Restraints/Collar"
** is worn on the clothing layer provided in the option field, ex : @getpath:pants=2222 => "Casual/Jeans/Tight"
Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. It does not take disabled folders into account (folders which name begins with a dot "."). The answer is a list of folders, separated by slashes ('/').

* '''''Force attach items contained into a shared folder that contains a particular object/clothing''''' : @attachthis[:<attachpt> or <clothing_layer>]=force (*)
''Implemented in v1.16''
This command is a shortcut for a @getpath followed with an @attach command (this saves a listener and a timeout).

* '''''Force attach items contained into a shared folder that contains a particular object/clothing, and its children folders''''' : @attachallthis[:<attachpt> or <clothing_layer>]=force (*)
''Implemented in v1.16''
This command is a shortcut for a @getpath followed with an @attachall command (this saves a listener and a timeout).

* '''''Force detach items contained into a shared folder that contains a particular object/clothing''''' : @detachthis[:<attachpt> or <clothing_layer>]=force (*)
''Implemented in v1.16''
This command is a shortcut for a @getpath followed with a @detach command (this saves a listener and a timeout).

* '''''Force detach items contained into a shared folder that contains a particular object/clothing, and its children folders''''' : @detachallthis[:<attachpt> or <clothing_layer>]=force (*)
''Implemented in v1.16''
This command is a shortcut for a @getpath followed with a @detachall command (this saves a listener and a timeout).

* '''''Force detach an item''''' : @detachme=force (*)
''Implemented in v1.16.2''
This command forces the object that issues it to detach itself from the avatar. It is there as a convenience to avoid a race condition when calling @clear then llDetachFromAvatar(), sometimes the object could detach itself before clearing its restrictions, making it reattach automatically after a while. With this command one can issue a @clear,detachme=force to be sure @clear is executed first.

* '''''Allow/prevent touching objects located further than 1.5 meters away from the avatar''''' : @fartouch=<y/n>
''Implemented in v1.11''
When prevented, the avatar is unable to touch/grab objects from more than 1.5 m away, this command makes restraints more realistic since the avatar litterally has to press against the object in order to click on it.

* '''''Allow/prevent viewing the world map''''' : @showworldmap=<y/n>
''Implemented in v1.11''
When prevented, the avatar is unable to view the world map, and it closes if it is open when the restriction becomes active.

* '''''Allow/prevent viewing the mini map''''' : @showminimap=<y/n>
''Implemented in v1.11''
When prevented, the avatar is unable to view the mini map, and it closes if it is open when the restriction becomes active.

* '''''Allow/prevent knowing the current location''''' : @showloc=<y/n>
''Implemented in v1.12''
When prevented, the user is unable to know where they are : the world map is hidden, the parcel and region name on the top menubar are hidden, they can't create landmarks, nor buy the land, nor see what land they have just left after a teleport, nor see the location in the About box, and even system and object messages are obfuscated if they contain the name of the region and/or the name of the parcel. However, [[llOwnerSay]] calls are ''not'' obfuscated so radars ''will'' still work (and RL commands as well).

* '''''Force-Teleport the user''''' : @tpto:X/Y/Z=force (*)
''Implemented in v1.12''
This command forces the avatar to teleport to the indicated coordinates. Note that these coordinates are always '''global''', hence the script that calls this command will not be trivial. Moreso, if the destination contains a telehub or a landing point, the user will land there instead of the desired point. This is a SL limitation. Also keep in mind that @tpto is inhibited by @tploc=n, and from v1.15 and above, by @unsit too.

Here is a sample code to call that command properly :

<lsl>

// FORCE TELEPORT EXAMPLE
// Listens on channel 4 for local coordinates and a sim name
// and tells your viewer to teleport you there.
//
// By Marine Kelley 2008-08-26
// RLV version required : 1.12 and above
//
// HOW TO USE :
// * Create a script inside a box
// * Overwrite the contents of the script with this one
// * Wear the box
// * Say the destination coords Region/X/Y/Z on channel 4 :
// Example : /4 Help Island Public/128/128/50

key kRequestHandle; // UUID of the dataserver request
vector vLocalPos; // local position extracted from the

Init () {
kRequestHandle = NULL_KEY;
llListen (4, "", llGetOwner (), "");
}

default
{
state_entry () {
Init ();
}

on_rez(integer start_param) {
Init ();
}

listen(integer channel, string name, key id, string message) {
list tokens = llParseString2List (message, ["/"], []);
integer L = llGetListLength (tokens);

if (L==4) {
// Extract local X, Y and Z
vLocalPos.x = llList2Float (tokens, 1);
vLocalPos.y = llList2Float (tokens, 2);
vLocalPos.z = llList2Float (tokens, 3);

// Request info about the sim
kRequestHandle=llRequestSimulatorData (llList2String (tokens, 0), DATA_SIM_POS);
}
}

dataserver(key queryid, string data) {
if (queryid == kRequestHandle) {
// Parse the dataserver response (it is a vector cast to a string)
list tokens = llParseString2List (data, ["<", ",", ">"], []);
string pos_str = "";
vector global_pos;

// The coordinates given by the dataserver are the ones of the
// South-West corner of this sim
// => offset with the specified local coordinates
global_pos.x = llList2Float (tokens, 0);
global_pos.y = llList2Float (tokens, 1);
global_pos.z = llList2Float (tokens, 2);
global_pos += vLocalPos;

// Build the command
pos_str = (string)((integer)global_pos.x)
+"/"+(string)((integer)global_pos.y)
+"/"+(string)((integer)global_pos.z);
llOwnerSay ("Global position : "+(string)pos_str); // Debug purposes

// Fire !
llOwnerSay ("@tpto:"+pos_str+"=force");
}
}

}

</lsl>

* '''''Remove/add auto-accept teleport offers from a particular avatar''''' : "@accepttp[:<UUID>]=<rem/add>"
''Implemented in v1.15, slightly improved in v1.16''
Adding this rule will make the user automatically accept any teleport offer from the avatar which key is <UUID>, exactly like if that avatar was a Linden (no confirmation box, no message, no Cancel button). This rule does not supercede nor deprecate @tpto because the former teleports to someone, while the latter teleports to an arbitrary location. Attention : in v1.16 the UUID becomes optional, which means that @accepttp=add will force the user to accept teleport offers from anyone ! Use with caution !

* '''''Allow/prevent seeing the names of the people around''''' : @shownames=<y/n>
''Implemented in v1.12.2, added more dummy names in v1.16''
When prevented, the user is unable to know who is around. The names don't show on the screen, the names on the chat are replaced by "dummy" names such as "Someone", "A resident", the tooltips are hidden, the pie menu is almost useless so the user can't get the profile directly etc.

* '''''Allow/prevent seeing all the hovertexts''''' : @showhovertextall=<y/n>
''Implemented in v1.19''
When prevented, the user is unable to read any hovertext (2D text floating above some prims).

* '''''Allow/prevent seeing one hovertext in particular''''' : @showhovertext:<UUID>=<y/n>
''Implemented in v1.19''
When prevented, the user is unable to read the hovertext floating above the prim which id is UUID. This is made that way so that the restriction can be issued on an object, by another one (unlike @detach which can only set this restriction on itself).

* '''''Allow/prevent seeing the hovertexts on the HUD of the user''''' : @showhovertexthud=<y/n>
''Implemented in v1.19''
When prevented, the user is unable to read any hovertext showing over their HUD objects, but will be able to see the ones in-world.

* '''''Allow/prevent seeing the hovertexts in-world''''' : @showhovertextworld=<y/n>
''Implemented in v1.19''
When prevented, the user is unable to read any hovertext showing over their in-world objects, but will be able to see the ones over their HUD.

* '''''Allow/prevent flying''''' : @fly=<y/n>
''Implemented in v1.12.2''
When prevented, the user is unable to fly.

* '''''Get the UUID of the object the avatar is sitting on''''' : @getsitid=<channel_number>
''Implemented in v1.12.4''
Makes the viewer automatically answer the UUID of the object the avatar is currently sitting on, or NULL_KEY if they are not sitting.

* '''''Force rotate the avatar to a set direction''''' : @setrot:<angle_in_radians>=force
''Implemented in v1.17''
Forces the avatar to rotate towards a direction set by an angle in radians from the north. Note that this command is not very precise, nor will do anything if the action attempts to rotate the avatar by less than 10° (experimental value, it has been mentioned somewhere that 6° was the minimum). In other words, it is best to either check with a llGetRot() first, or to make the avatar turn twice, first 180° plus the desired angle, then by the angle we need. It isn't very elegant but it works.

* '''''Allow/prevent changing some debug settings''''' : @setdebug=<y/n>
''Implemented in v1.16''
When prevented, the user is unable to change some viewer debug settings (Advanced > Debug Settings). As most debug settings are either useless or critical to the user's experience, a whitelist approach is taken : only a few debug settings are locked, the others are always available and untouched. At the time of this writing, the allowed debug settings are :
** AvatarSex (0 : Female, 1 : Male) : gender of the avatar at creation.
** RenderResolutionDivisor (1 -> ...) : "blurriness" of the screen. Combined to clever @setenv commands, can simulate nice effects. Note: renderresolutiondivisor is a Windlight only option (Basic Shaders must be enabled in graphics preferences) and as such, is not available in v1.19.0.5 or older viewers.

* '''''Force change a debug setting''''' : @setdebug_<setting>:<value>=force (*)
''Implemented in v1.16''
Forces the viewer to change a particular debug setting and set it to <value>. This command is actually a package of many sub-commands, that are regrouped under "@setdebug_...", for instance "@setdebug_avatarsex:0=force", "@setdebug_renderresolutiondivisor:64=force" etc.

See the list of allowed debug settings in the @setdebug command hereabove.

* '''''Get the value of a debug setting''''' : @getdebug_<setting>=<channel_number>
''Implemented in v1.16''
Makes the viewer automatically answer the value of a debug setting, immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. The answer is the value that has been set with the <setting> part of the matching @setdebug command, or by hand.

See the list of allowed debug settings in the @setdebug command hereabove.

* '''''Allow/prevent changing the environment settings''''' : @setenv=<y/n>
''Implemented in v1.14''
When prevented, the user is unable to change the viewer environment settings (World > Environment Settings > Sunrise/Midday/Sunset/Midnight/Revert to region default/Environment editor are all locked out).

* '''''Force change an environment setting''''' : @setenv_<setting>:<value>=force (*)
''Implemented in v1.14''
Forces the viewer to change a particular environment setting (time of day or Windlight) and set it to <value>. This command is actually a package of many sub-commands, that are regrouped under "@setenv_...", for instance "@setenv_daytime:0.5=force", "@setenv_bluehorizonr:0.21=force" etc.

This command (like any other "force" command) is silently discarded if the corresponding restriction has been set, here "@setenv", but in this case the restriction is ignored if the change is issued from the object that has created it. In other words, a collar can restrict environment changes, yet force a change by itself, while another object could not do it until the collar lifts the restriction.

Although a range is specified for every value, no check is made in the viewer so a script can do what the UI can't do, for interesting effects. Use at your own risk, though. The ranges indicated here are merely the ones available on the sliders on the Environment Editor, for reference.

Each particular sub-command works as follows (the names are chosen to be as close to the Windlight panels of the viewer as possible) :

{| border="1" cellpadding="5"
| '''@setenv_XXX:<value>=force where XXX is...''' || '''<value> range''' || '''Sets...'''
|-
| daytime || 0.0-1.0 and <0 || Time of day (sunrise:0.25, midday:0.567, sunset:0.75, midnight:0.0, set back to region default:<0). '''Attention, resets all other Windlight parameters'''
|-
| preset || String || A Preset environment, e.g. Gelatto, Foggy. '''Attention, loading a Preset is heavy on the viewer and can slow it down for a short while, don't do it every second'''
|-
| ambientr || 0.0-1.0 || Ambient light, Red channel
|-
| ambientg || 0.0-1.0 || Ambient light, Green channel
|-
| ambientb || 0.0-1.0 || Ambient light, Blue channel
|-
| ambienti || 0.0-1.0 || Ambient light, Intensity
|-
| bluedensityr || 0.0-1.0 || Blue Density, Red channel
|-
| bluedensityg || 0.0-1.0 || Blue Density, Green channel
|-
| bluedensityb || 0.0-1.0 || Blue Density, Blue channel
|-
| bluedensityi || 0.0-1.0 || Blue Density, Intensity
|-
| bluehorizonr || 0.0-1.0 || Blue Horizon, Red channel
|-
| bluehorizong || 0.0-1.0 || Blue Horizon, Green channel
|-
| bluehorizonb || 0.0-1.0 || Blue Horizon, Blue channel
|-
| bluehorizoni || 0.0-1.0 || Blue Horizon, Intensity
|-
| cloudcolorr || 0.0-1.0 || Cloud color, Red channel
|-
| cloudcolorg || 0.0-1.0 || Cloud color, Green channel
|-
| cloudcolorb || 0.0-1.0 || Cloud color, Blue channel
|-
| cloudcolori || 0.0-1.0 || Cloud color, Intensity
|-
| cloudcoverage || 0.0-1.0 || Cloud coverage
|-
| cloudx || 0.0-1.0 || Cloud offset X
|-
| cloudy || 0.0-1.0 || Cloud offset Y
|-
| cloudd || 0.0-1.0 || Cloud density
|-
| clouddetailx || 0.0-1.0 || Cloud detail X
|-
| clouddetaily || 0.0-1.0 || Cloud detail Y
|-
| clouddetaild || 0.0-1.0 || Cloud detail density
|-
| cloudscale || 0.0-1.0 || Cloud scale
|-
| cloudscrollx || 0.0-1.0 || Cloud scroll X
|-
| cloudscrolly || 0.0-1.0 || Cloud scroll Y
|-
| densitymultiplier || 0.0-0.9 || Density multiplier of the fog
|-
| distancemultiplier || 0.0-100.0 || Distance multiplier of the fog
|-
| eastangle || 0.0-1.0 || Position of the east, 0.0 is normal
|-
| hazedensity || 0.0-1.0 || Density of the haze
|-
| hazehorizon || 0.0-1.0 || Haze at the horizon
|-
| maxaltitude || 0.0-4000.0 || Maximum altitude of the fog
|-
| scenegamma || 0.0-10.0 || Overall gamma, 1.0 is normal
|-
| starbrightness|| 0.0-2.0 || Brightness of the stars
|-
| sunglowfocus || 0.0-0.5 || Focus of the glow of the sun
|-
| sunglowsize || 1.0-2.0 || Size of the glow of the sun
|-
| sunmooncolorr || 0.0-1.0 || Sun and moon, Red channel
|-
| sunmooncolorg || 0.0-1.0 || Sun and moon, Green channel
|-
| sunmooncolorb || 0.0-1.0 || Sun and moon, Blue channel
|-
| sunmooncolori || 0.0-1.0 || Sun and moon, Intensity
|-
| sunmoonposition || 0.0-1.0 || Position of the sun/moon, different from "daytime", '''use this to set the apparent sunlight after loading a Preset'''
|}

Note: from the above settings, only the "daytime" one is supported by v1.19.0 (or older) viewers implementing RestrainedLife v1.14 and later. The other settings are ignored. This is because these viewers do not implement the Windlight renderer.

(*) Silently discarded if the user is prevented from doing so by the corresponding restriction. This is on purpose.
Ex : Force detach won't work if the object is undetachable. Force undress won't work if the user is prevented from undressing.

* '''''Get the value of an environment setting''''' : @getenv_<setting>=<channel_number>
''Implemented in v1.15''
Makes the viewer automatically answer the value of an environment setting, immediately on the chat channel number <channel_number> that the script can listen to. Always use a positive integer. Remember that regular viewers do not answer anything at all so remove the listener after a timeout. The answer is the value that has been set with the <setting> part of the matching @setenv command, or by hand. See the table hereabove for a list of settings.<br />
Note: only @getenv_daytime is supported by v1.19.0 (or older, i.e. non Windlight) viewers implementing RestrainedLife v1.15 and later.

==Important note about the global behaviours such as sendchat==
Such behaviours are global, which means they don't depend on a particular object. However, they are triggered by objects with a set [[UUID]] which can change, and several objects can add the same behaviour, which will be stored several times as the [[UUID]]s are different.

This has a nice side effect : when wearing 2 locked devices that prevent chat, it is necessary to unlock them both to be able to chat again. But it has a nasty side effect, too : if the item changes [[UUID]] (for instance it was derezzed and rezzed again), and it doesn't allow chat beforehand, then the user will have to wait a short moment because the rule stays "orphaned" (its [[UUID]] is defunct) until the '''garbage collector''' kicks in.

Therefore :
'''ALWAYS DEACTIVATE A BEHAVIOUR WHEN THE OBJECT THAT HAS ACTIVATED IT DEREZZES FOR ANY REASON BESIDES LOGGING OUT ! "@CLEAR" IS YOUR FRIEND !'''

==Shared Folders==

Since v1.11, the viewer can "share" some of your items with scripts in world in order to let them force you to attach, detach and list what you have shared.

"Share" does NOT mean they will be taken by other people if they want to (some of the items may be no-transfer anyway), but only that they can force YOU to wear/unwear them at will through the use of a script YOUR restraints contain. They will remain in your inventory.

To do this :
* Create a folder named "#RLV" (without the quotes) directly under "My Inventory" (right-click on "My Inventory", select "New Folder"). We'll call this folder the "shared root".
* Move a folder containing restraints or other attachments directly into this new folder.
* Wear the contents of that folder, that's it !

So it would look like this :

My Inventory
|- #RLV
| |- cuffs
| | |- left cuff (l forearm) (no copy)
| | \- right cuff (r forearm) (no copy)
| \- gag
| \- gag (mouth) (no copy)
|- Animations
|- Body Parts
.
.
.

For example : If you're owning a set of RR Straps and want to share them, just move the folder "Straps BOXED" under the shared root.

Either wear all the items of the folders you have just moved (one folder at a time !) or rename your items yourself, so that each item name contains the name of the target attachment point. For example : "left cuff (l forearm)", "right ankle cuff (r lower leg)". Please note that no-modify items are a bit more complex to share, because they cannot be renamed either by you or by the viewer. More on that below.

The attachment point name is the same as the one you find in the "Attach To" menu of your inventory, and is case insensitive (for example : "chest", "skull", "stomach", "left ear", "r upper arm"...). If you wear the item without renaming it first it will be renamed automatically, but only if it is in a shared folder, and does not contain any attachment point name already, and is mod. If you want to wear it on another attachment point, you'll need to rename it by hand first.

Pieces of clothing are treated exactly the same way (in fact they can even be put in the folder of a set of restraints and be worn with the same command). Shoes, for instance, are a good example of mixed outfits : some attachments and the Shoes layer. Clothes are NOT renamed automatically when worn, since their very type decides where they are to be worn (skirt, jacket, undershirt...).

HOW TO SHARE NO-MODIFY ITEMS :
As you already know, no-mod items cannot be renamed so the technique is a bit more complex. Create a sub-folder inside the outfit folder (such as "cuffs" in the example above), put ONE no-modify item in it. When wearing the object, you'll see the folder itself be renamed (that's why you must not put more than one object inside it). So if your outfit contains several no-mod objects, you'll need to create as many folders and put the no-mod objects in them, one in each folder.

Example with no-modify shoes :

My Inventory
|- #RLV
| \- shoes
| |- left shoe (left foot)
| | \- left shoe (no modify) (no transfer) <-- no-mod object
| |- right shoe (right foot)
| | \- right shoe (no modify) (no transfer) <-- no-mod object
| \- shoe base (no modify) (no transfer) <-- this is not an object
|- Animations
|- Body Parts
.
.
.

GOTCHAS :
* Do NOT put a comma (',') in the name of the folders under the shared root or it would screw the list up.
* Don't forget to rename the items in the shared folders (or to wear these items at least once to have them be renamed automatically) or the force attach command will appear to do nothing at all.
* Avoid cluttering the shared root with many folders, since some scripts may rely on the list they got with the @getinv command and chat messages are limited to 1023 characters. Choose wisely, and use short names. But with 9 characters per folder name average, you can expect to have about 100 folders available.
* Remember to put no-modify items in sub-folders, one each, so their names can be used by the viewer do find out where to attach them. They can't be shared like modify items since they can't be renamed, and the outfit folder itself will not be renamed (since it contains several items).

'''''Accept sub-folders given via llGiveInventoryList() into the shared folder''''' :

Starting with RestrainedLife v1.16.2, you may give a list of items to a victim and have them stored as a sub-folder inside the #RLV folder (thus allowing you to @attach the given items later).

Issuing a llGiveInventoryList(victim_id, "#RLV/~subfolder_name", list_of_stuff) command in a script makes a standard Keep/Discard/Mute dialog appear in the viewer of the victim (the avatar which key is victim_id).

Should the victim accept the offer, the list_of_stuff items are put into a new sub-folder of the #RLV folder. The name of this sub-folder is "~subfolder_name" (it is the scripter's responsibility to use unique sub-folder names: if the name is the same as an existing sub-folder, two sub-folders with the same name will appear in the #RLV folder).

Note that the tilde character *must* be used as the first character for the name of the sub-folder (this is so that the victim can easily spot any sub-folder given to them in this way, and so that such sub-folder names appear last in the #RLV folder).

Note also that this feature may be disabled by the user, (by setting the RestrainedLifeForbidGiveToRLV debug setting to TRUE): in this case the given items are put into a folder named "#RLV/~subfolder_name" at the root of the inventory instead of inside the #RLV folder.

Since the user may either refuse the offer or have the feature disabled in their viewer, and since SL may take quite some time to perform the actual transfer of the objects on laggy days, you must check that the given folder is present (with @getinv), before attempting to @attach the given objects.

==For your information==
Here is how it works internally, for a better understanding of the gotchas you may encounter :
* Each command is parsed into a '''Behaviour''' (ex: "remoutfit"), an '''Option''' (ex: "shirt") and a '''Param''' (ex: "force") and comes from an [[UUID]] (the unique identifier of the emitting object).

* There are two types of commands : '''one-shot''' commands (those which Param is "force" and those which Param is a number such as the channel number of a "version" call) and '''rules''' (those which Param is "y", "n", "add" or "rem"). "clear" is special but can be seen as a one-shot command.

* Parameters "n" and "add" are '''exactly equal''' and are treated '''exactly the same way''', they are just '''synonyms'''. Same goes for "y" and "rem". The only purpose is to distinguish rules ("sendchannel=n") from exceptions ("sendchannel:8=add") in a script for clarity.

* Rules are stored inside a table linking the [[UUID]] of the emitter to the rule itself. They are '''added''' when receiving a "n"/"add" Param, and '''removed''' when receiving a "y"/"rem" Param.
If '''''UUID1''''' is a collar and '''''UUID2''''' is a gag :

'''''UUID1''''' => detach, tploc, tplm, tplure, sittp

'''''UUID2''''' => detach, sendim, sendim:(keyholder)

Those two rules mean that the user cannot send IMs except to their keyholder, and cannot TP at all. Those two items are not detachable. Now if the collar sends "@sendim=n", the table becomes :

'''''UUID1''''' => detach, tploc, tplm, tplure, sittp, sendim

'''''UUID2''''' => detach, sendim, sendim:(keyholder)

If it sends "@sendim=n" a second time nothing changes, as there is a check for its existence prior to adding it. If the gag is unlocked and detached, either it sends a "@clear" or the garbage collector kicks in so the rules linked to '''''UUID2''''' disappear. However, the avatar is still unable to send IMs even to their keyholder, as the exception has disappeared as well. This is because rules linked to one object don't conflict with rules linked to another one.

* One-shot commands, on the other hand, are executed on-the-fly and are not stored.

* When logging on, the avatar stays non-operational (cannot chat, cannot move) for some time, while the user sees the progress bar. However, worn scripted objects [[rez]] in the meantime and start sending rules and commands before the viewer can execute them. Therefore it stores them in a buffer and executes them only when the user is given controls (when the progress bar disappears).

* The viewer periodically (every N seconds) checks all its rules and removes the ones linked to an [[UUID]] that does not exist around anymore ("garbage collector"). This means that rules issued by an '''unworn''' owned object will be discarded as soon as the avatar [[teleports]] elsewhere.

[[Category:Third Party Client]]

PRIM TEXTURE

2008-11-12T22:21:52Z

Ibrew Meads: Negative repeats flip the texture.

<onlyinclude>{{#if:

{{#vardefine:return|[ {{HoverText|""|string texture}}, {{HoverLink|ZERO_VECTOR|{{LSL VR|0.0|0.0|0.0}} vector repeats}}, {{HoverLink|ZERO_VECTOR|{{LSL VR|0.0|0.0|0.0}} vector offsets}}, {{HoverText|0.0|float rotation_in_radians}} ]}}

{{#vardefine:texture_const|{{LSL Const|PRIM_TEXTURE|integer|17|c=Used to {{GetSet|{{{1|}}}|get|set|/}} the texture settings of a prim's face}}}}

{{#vardefine:p_rotation_in_radians_desc|angle in radians}}
{{#vardefine:p_repeats_desc|x and y range from 0.0 to 100, or -0.0 to -100 in 0.01 increments. Negative values flip the texture (z is ignored)}}
{{#vardefine:p_offsets_desc|x and y range from -1 to 1 (z is ignored)}}

{{LSL_Function/inventory|texture|uuid=true|type=texture|{{#ifeq:{{{1|}}}|get|no_caveat=true}}|full={{{remote|}}}}}

{{#vardefine:facetable|{{#var:facetable}}
{{!}}-
{{!}} [ {{#var:texture_const}} ]
{{!}} {{#var:return}} }}

}}</onlyinclude>{{#if:

{{#vardefine:caveats_set|{{#var:caveats}}}}
{{#vardefine:caveats|}}

{{LSL_Function/face|face|{{#var:texture_const}}|!footer=*|return={{#var:return}}}}

}}{{LSL Constant
|name=PRIM_TEXTURE
|type=integer
|value=17
|desc=Used to get or set the texture settings of a prim's face.
|examples=
|pa={{LSL Constant/List|i_front=[ {{#var:texture_const}}, |i_end= ]|
|text=Used with [[llSetPrimitiveParams]] & [[llSetLinkPrimitiveParams]].
====Caveats====
{{#var:caveats_set}}{{#vardefine:caveats_set}}

====<tt>texture</tt> Constants====
The following constants can (optionally) be used for the '''texture''' value:
[[TEXTURE_BLANK]], [[TEXTURE_DEFAULT]], [[TEXTURE_MEDIA]], [[TEXTURE_PLYWOOD]] and [[TEXTURE_TRANSPARENT]].

====Examples====
<lsl>llSetPrimitiveParams([ PRIM_TEXTURE, ALL_SIDES, "5748decc-f629-461c-9a36-a35a221fe21f", <1.0, 1.0, 0.0>, <0.0, 0.0, 0.0>, 0.0 ]);
llSetPrimitiveParams([ PRIM_TEXTURE, ALL_SIDES, llGetInventoryName(INVENTORY_TEXTURE, 0), <1.0, 1.0, 0.0>, <0.0, 0.0, 0.0>, 0.0 ]);
llSetPrimitiveParams([ PRIM_TEXTURE, 0, TEXTURE_PLYWOOD, <2.0, 5.0, 0.0>, <0.1, 0.2, 0.0>, 1.0 ]);</lsl>

|toc=llSetPrimitiveParams
|i1_type=integer|i1_name=face
|i2_type=string|i2_name=texture
|i3_type=vector|i3_name=repeats
|i4_type=vector|i4_name=offsets
|i5_type=float|i5_name=rotation_in_radians
}}
|pb={{LSL Constant/List|i_front=[[llGetPrimitiveParams]]([ {{#var:texture_const}}, |i_end= ]);|
|r_front=Returns the list [ |r_end= ]
|text=
====Caveats====
{{#var:caveats}}{{#vardefine:caveats}}
|toc=llGetPrimitiveParams
|i1_type=integer|i1_name=face
|r1_type=string|r1_name=texture
|r2_type=vector|r2_name=repeats
|r3_type=vector|r3_name=offsets
|r4_type=float|r4_name=rotation_in_radians
}}
|constants=
{{LSL DefineRow||[[CHANGED_TEXTURE]]|}}
{{LSL DefineRow||[[TEXTURE_BLANK]]|}}
{{LSL DefineRow||[[TEXTURE_DEFAULT]]|}}
{{LSL DefineRow||[[TEXTURE_PLYWOOD]]|}}
{{LSL DefineRow||[[TEXTURE_TRANSPARENT]]|}}
{{LSL DefineRow||[[TEXTURE_MEDIA]]|}}
|functions=
{{LSL DefineRow||[[llSetPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|}}
|events=
{{LSL DefineRow||[[changed]]|}}
|location
|cat1=Prim
|cat2
|cat3
|cat4
}}