Second Life Wiki - User contributions [en]

Talk:QA Portal/Bacon Test

2026-06-05T06:09:31Z

Peter Stindberg: Created page with "Yum, bacon. --~~~~"

Yum, bacon.

--[[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 23:09, 4 June 2026 (PDT)

LlSetPrimMediaParams

2025-08-27T08:24:00Z

Peter Stindberg: Clarification about faces.

{{LSL_Function
|inject-1={{Issues/SVC-4939}}{{Issues/VWR-17719}}{{LSL_Function/face|face|notall=*}}
|func_id=350|func_sleep=1.0|func_energy=10.0|mode
|func=llSetPrimMediaParams|return_type=integer|return_subtype=status
|p1_type=integer|p1_name=face|p1_desc
|p2_type=list|p2_subtype=instructions|p2_name=params|p2_desc=a set of name/value pairs (in no particular order)
|func_footnote=
|func_desc=Set the media {{LSLP|params}} for a particular {{LSLP|face}}.
|return_text=that is a STATUS_* flag which details the success/failure of the operation(s).
|spec=
|caveats=*If prim-media is not already on this object, add it.
*Params not specified are unchanged, or if new media is added set to the default specified.
* Both width and height must be specified together to work, and they narrow the texture space while inversely widening the aperture.
** width and height scaled larger than 1024pixels will require the texture backdrop to be resized to fit(see [[#Useful_Snippets|Useful Snippets]])
*** if resized to fit, the resulting view will cut off scrolled content outside the bounds making it impossible to be viewed
* Face needs to be a single face. If you want the media on multiple faces (e. g. opposing sides of an object), you have to call the function multiple times with different face numbers. Bitwise AND for face numbers does not work.
|constants={{LSL Constants/ReturnStatus|table=*|sortable=*}}{{LSL Constants/PrimMedia|set}}
|examples
|helpers=<syntaxhighlight lang="lsl2">//-- expand media textures greater than 1024 pixel in a direction to fit the media face
//-- does exactly what the "align" button does in the edit window (width/height are in pixels)
//-- original by Edelman Linden (or Kate Linden), tweaked by Void Singer
uExpandMediaTexture( integer vIntWidth, integer vIntHeight, integer vIntFace ){
integer vIntTemp;
vector vSizScale;

while (vIntWidth >> ++vIntTemp);
vSizScale.x = vIntWidth / (float)(1 << vIntTemp);
vIntTemp = 0;
while (vIntHeight >> ++vIntTemp);
vSizScale.y = vIntHeight / (float)(1 << vIntTemp);
llSetPrimitiveParams( [PRIM_TEXTURE, vIntFace] +
llListReplaceList( llGetPrimitiveParams( [PRIM_TEXTURE, vIntFace] ),
[vSizScale, ((vSizScale - <1.0, 1.0, 0.0>) / 2.0)],
1,
2 ) );
}</syntaxhighlight>
ref: [[How_to_Align_a_Shared_Media_Texture_from_Linden_Script|original source]]
|also_functions=
{{LSL DefineRow||[[llSetLinkMedia]]}}
{{LSL DefineRow||[[llGetPrimMediaParams]]}}
{{LSL DefineRow||[[llClearPrimMedia]]}}
|also_tests
|also_events=
|also_articles=
{{LSL DefineRow||[[/Tricks]]}}
|notes
|deepnotes
|history=
*{{SVN|2816|rev=134947|trunk=*|anchor=|ver=|ser=}}
*{{JIRA|SVC-4939}}
* Functionality available in Client 2.0
|haiku={{Haiku|Media in dance,|Parameters find their place,|Object's form embrace.}}
|cat1=Prim Media
|cat2=Media
|cat3
|cat4
}}
[[Category:Shared Media]]

LlLinksetDataListKeys

2025-08-03T19:28:34Z

Peter Stindberg:

{{LSL_Function
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataListKeys
|p1_type=integer|p1_name=start|p1_desc=The first key to return.
|p2_type=integer|p2_name=count|p2_desc=The number of keys to return.
|return_type=list
|return_text=of the keys in the datastore, ordered alphabetically.
|func_footnote
|func_desc=The '''llLinksetDataListKeys''' function returns a list of up to {{LSLP|count}} keys in the datastore, starting at the one indicated by {{LSLP|start}}. If {{LSLP|count}} is less than 1, then all keys between {{LSLP|start}} and the end are returned. If {{LSLP|count}} minus {{LSLP|start}} exceeds the total number of keys, the returned list will be shorter than {{LSLP|count}}, down to a zero-length list if {{LSLP|start}} equals or exceeds the total number of keys.
|func_footnote
|spec

|examples=
The following code will list all the keys in a object. Only 1024 characters will be displayed due to limitations of [[llSay]].
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSay(0, llDumpList2String(llLinksetDataListKeys(0, 0), "\n"));
}
}
</syntaxhighlight>
|caveats
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

User talk:Frio Belmonte

2025-07-27T08:04:44Z

Peter Stindberg: Created page with "re-welcome -- ~~~~"

re-welcome

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 01:04, 27 July 2025 (PDT)

LlSetObjectName

2025-07-25T19:50:06Z

Peter Stindberg: Caveat about changed event not being triggered.

{{LSL Function
|inject-2={{LSL_Function/limits}}
|func_id=203
|func_sleep=0.0
|func_energy=10.0
|func=llSetObjectName|sort=SetObjectName
|p1_type=string
|p1_name=name
|func_desc=Sets the prim's name according to the {{LSLP|name}} parameter.
|func_footnote=If this function is called from a child prim in a linked set, it will change the name of the child prim and not the root prim.
|return_text
|spec
|caveats=
* The name is limited to 63 characters. Longer prim names are cut short.
* Names can only consist of the 95 printable characters found in the [http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters ASCII-7] (non-extended) character set, with the exception of the vertical bar/pipe ("<nowiki>|</nowiki>") character.
** Invalid characters in the range 1 to 31, as well as the pipe character (124) are replaced with a question mark ("?").
** Other invalid characters in the range 128 and above are replaced with two or more question marks, depending on how many bytes their UTF-8 representation requires.
** Objects with all-whitespace names (e.g., a space or a series of spaces) will appear as "(Unnamed)" if they emit chat via [[llSay]], [[llOwnerSay]], [[llInstantMessage]], etc., although this behaviour may vary in third-party viewers.
* While an object is attached, the script cannot change the name of the object as it appears in the user's inventory.{{Footnote|2=Whether or not this is a bug is still debated, regardless LL has said they will not fix it. This behavior was first recognized as a pain point in 2006 and only confirmed to be lava-flowed more recently (2011).|1=Whether or not this is a bug is still debated, regardless LL has said they will not fix it. This behavior was first recognized as a pain point in [http://forums-archive.secondlife.com/255/ab/84853/1.html 2006] and only confirmed to be lava-flowed [https://jira.secondlife.com/browse/SVC-3429?focusedCommentId=267372&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-267372 more recently (2011)].}}
** Changes to the name of the root prim (with [[llSetObjectName]] for example) will not be saved to inventory; when the attachment is detached (to inventory, not dropped) this name change is discarded and the name in inventory is used instead.
** When attachment is dropped (to the ground) and taking it into inventory, the inventory item will have the new name (not the old).
* Changes to the names of child prims will be saved back to inventory when the object is detached to inventory. They survive detachment.
* Changes to the object name do not trigger a [[changed]] event.
|constants
|examples=
{{{!}} width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Set this prim's name'''
! '''Set the root prim's name'''
{{!}}-
{{!!}}<source lang="lsl2">
default
{
state_entry()
{
llSetObjectName("NEW PRIM NAME");
}
}
</source>
{{!!}}
<source lang="lsl2">
default
{
state_entry()
{
llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_NAME, "NEW ROOT PRIM NAME"]);
}
}
</source>
{{!}}- {{Hl2}}
! colspan="2" {{!}} '''Test if a string is valid as an object name'''
{{!}}-
{{!}} colspan="2" {{!}}
<source lang="lsl2">
// Returns TRUE if 'name' is a valid object name, FALSE otherwise
integer isValidObjectName(string name)
{
string original_name = llGetObjectName();
llSetObjectName(name);
integer valid_name = llGetObjectName() == name;
llSetObjectName(original_name);
return valid_name;
}
</source>
{{!}}}
|helpers
|also_functions=
{{LSL DefineRow||[[llGetObjectName]]|Get the prims name}}
{{LSL DefineRow||[[llGetLinkName]]|Get a linked prims name}}
{{LSL DefineRow||[[llGetObjectDesc]]|Get the prims description}}
{{LSL DefineRow||[[llSetObjectDesc]]|Set the prims description}}
{{LSL DefineRow||[[llGetObjectDetails]]|Get a list of object details}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Prim
|cat2
|cat3
|cat4
|}}

LlSetObjectDesc

2025-07-25T19:48:10Z

Peter Stindberg: Caveat about event not being tripped (but in Notes section, since somehow I can't edit the caveats)

{{LSL_Function
|inject-2={{Issues/VWR-437}}{{Issues/SVC-3429}}{{Issues/VWR-8761}}{{LSL_Function/prim-desc|set}}
|func=llSetObjectDesc
|func_id=271|func_sleep=0.0|func_energy=10.0
|p1_type=string|p1_name=description
|func_footnote
|func_desc=Sets the prims description
|return_text
|spec
|caveats
|constants
|examples=
{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Set this prim's description'''
! '''Set the root prim's description'''
{{!}}-
{{!!}}<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSetObjectDesc("NEW PRIM DESCRIPTION");
}
}
</syntaxhighlight>
{{!!}}
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_DESC, "NEW ROOT PRIM DESCRIPTION"]);
}
}
</syntaxhighlight>
{{!}}}
|helpers
|also_functions=
{{LSL DefineRow||[[llGetObjectDesc]]|Gets the prim description.}}
{{LSL DefineRow||[[llGetObjectName]]|Gets the prim name.}}
{{LSL DefineRow||[[llSetObjectName]]|Sets the prim name.}}
|also_tests
|also_events
|also_articles
{{LSL DefineRow||}}
|notes=
* Object descriptions are often used to store data that needs to be protected from script resets (see, for example, [[Prim Attribute Overloading]]). However, descriptions are not immutable and can be tampered with by users or other scripts, either intentionally or accidentally, so this method should only be considered a last resort for data storage.
** [[llLinksetDataWrite]] and associated functions are generally better suited for this purpose, because they allow for significantly more data storage and are much more secure against tampering.
* Changing the object description does not trigger a [[changed]] event.
|cat1=Prim
|cat2
|cat3
|cat4
}}

LlGiveInventory

2025-05-17T16:54:47Z

Peter Stindberg: Caveat about changed event and transfer of no-copy items

{{LSL_Function
|inject-2={{LSL_Function/give|destination|inventory|uuid=false|copyok=*}}{{Issues/SVC-7631}}{{Issues/BUG-5656}}
|func_id=150|func_sleep=0.0|func_energy=10.0
|func_sleep_hover=If 'destination' is an avatar the script sleeps for 2.0 seconds. (Giving to objects or attachments has no delay)
|func_sleep_note=If {{LSLP|destination}} is an avatar the script sleeps for 2.0 seconds. (Giving to objects or attachments has no delay)
|func=llGiveInventory
|p1_type=key|p1_name=destination|p1_desc
|p2_type=string|p2_name=inventory
|func_footnote=If {{LSLP|destination}} is an object then it must be in the same [[region]]. If {{LSLP|destination}} is an avatar they do not have to be in the same region.
|func_desc=Give {{LSLP|inventory}} to {{LSLP|destination}}.
|return_text
|spec
|caveats=
* There is no way to know if the transaction failed. Unless you send a message when inventory is given to a prim and prim's script checks its inventory and sends a message back using llRegionSay.
* Scripts reach {{LSLP|destination}} disabled (not running, and cannot be made to run unless the destination object is taken to inventory and rezzed again, or the script is recompiled). To send a running script to a prim use [[llSetRemoteScriptAccessPin]] and [[llRemoteLoadScriptPin]].
* If {{LSLP|destination}} is locked then {{LSLP|inventory}} is not transferred and a '''Blocked by permissions''' error is shouted on the [[DEBUG_CHANNEL]].
* If {{LSLP|destination}} object is not modifiable then {{LSLP|inventory}} is not transferred and a '''Blocked by permissions''' error is shouted on the [[DEBUG_CHANNEL]].
* If {{LSLP|inventory}} is no-copy it is transfered to {{LSLP|destination}} without copying it. Since it is no-copy the only copy is given to {{LSLP|destination}}; removing it from the source prim's inventory.
** the [[changed]] event does '''not''' fire in this case
** To avoid this problem use [[llGetInventoryPermMask]] to check the permissions of {{LSLP|inventory}}.
* {{HoverLink|Attachment|Attachment - Any object that is currently attached to an avatar|Attachments}} cannot give or receive no-copy inventory. When attempted an error is shouted on [[DEBUG_CHANNEL]].
* When giving to an attachment that is not owned by the script owner, the receiving attachment must have [[llAllowInventoryDrop]] set to TRUE.
* If {{LSLP|destination}} is an avatar that refuses to accept it (by manual decline or muting), is in busy mode, or is offline with instant messages capped, it is not returned to the prim's inventory; it is deleted.
** It is not returned to the owner. It does not show up in their lost and found or any other inventory folder.
** It is not put in the target's trash folder.
* A successful send to an offline avatar by means of llGiveInventory() counts as an IM against that avatar’s IM cap.
* As of 31th January 2012, llGiveInventory now has similar throttle to instant messages. A throttle of 5k per hour per owner per region; with a maximum burst of 2.5k. This throttle only affects gives to agents, not to non-agents.
** "With 3k subscribers you will want to send slow enough that it takes ~45 minutes to send 1 item to each subscriber. A general safe way would be to send ~2k as fast as you can, then wait 31 minutes and send another 2k." [https://jira.secondlife.com/browse/SVC-7631?focusedCommentId=308665&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-308665 Kelly Linden on SVC-7631]
** Be aware that while you script a system to handle the top of these limits that other busy scripted objects can be adding up to the throttle as well, such as vendors.
|constants
|examples=
<source lang="lsl2">default
{
touch_start(integer n)
{
//Gives this script to whoever touches the object.
llGiveInventory(llDetectedKey(0), llGetScriptName());
}
}</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGiveInventoryList]]}}
{{LSL DefineRow||[[llGiveAgentInventory]]}}
{{LSL DefineRow||[[llRemoteLoadScriptPin]]}}
{{LSL DefineRow||[[llSetRemoteScriptAccessPin]]}}
{{LSL DefineRow||[[llMapDestination]]}}
|also_events=
{{LSL DefineRow||[[changed]]}}
|also_tests=
{{LSL DefineRow||[[llGiveInventory Test]]}}
|also_articles
|notes
|permission
|negative_index
|sort=GiveInventory
|cat1=Inventory
|cat2=Avatar
|cat3
|cat4
}}

LlEmail

2025-04-23T17:56:39Z

Peter Stindberg: Added useful snippet to get region name and object position, that is much simpler than the snippets under examples.

{{LSL_Function
|inject-2={{Issues/SVC-23}}{{Issues/SVC-391}}{{Issues/SVC-412}}{{Issues/SCR-499}}{{Issues/BUG-229767}}
|func_id=119|func_sleep=20.0|func_energy=10.0
|sort=Email|func=llEmail
|p1_type=string|p1_name=address
|p2_type=string|p2_name=subject
|p3_type=string|p3_name=message
|func_footnote=The entire message (including the address, subject and other miscellaneous fields) can't be longer than 4096 bytes combined.
|func_desc=Sends an email to {{LSLP|address}} with {{LSLP|subject}} and {{LSLP|message}}.
|return_text
|spec=The {{LSLP|message}} is prefixed with information about the [[Primitive|prim]] sending the email.
{{{!}}{{Prettytable}}
{{!}}-{{Hl2}}
!Template
!Example
{{!}}-
{{!}}<pre>
Object-Name: *prim*
Region: *simname* (*simpos.x*, *simpos.y*)
Local-Position: (*primpos.x*, *primpos.y*, *primpos.z*)

*message*
</pre>
{{!}}
<pre>
Object-Name: Object
Region: Gibson (254976, 256000)
Local-Position: (117, 129, 50)

The real message starts here.
</pre>
{{!}}}
|caveats=* If you're sending to the [[object]] [[:Category:LSL_Owner|owner]], prefer the [[llTargetedEmail]] method.
* There is a limit to the number of email messages an object can send in a given amount of time.
* There is a limit of 500 messages from a single [[agent]]'s objects in a one-hour period.
* The 4096-byte size limit includes the subject line and automatically added text. The practical maximum body size is approximately 3600 bytes.
* (Sept-2008) The Email Throttle was modified slightly, Per {{User|Prospero Linden}}'s comments:
{{quote|"there has long been a throttle that makes a single script sleep for 20 seconds after sending an email. The new throttle is per user... some were using many, many different [[scripts]] to send spam. (the new throttle applies) when the destination is outside of Second Life. I know that messages within the same [[region]] were not throttled (beyond the 20-second delay), and I *believe* that messages between different [[simulator|sims]] were not throttled (between the 20-second delay)."}}
* Due to the bug {{Jira|SVC-23}} (present since 2005), objects may stop receiving emails completely until either the region is restarted or the object crosses a region boundary (resetting the script doesn't help). Emails sent may eventually be received after a restart/region-cross. Hence, don't rely on this function for reliable inter-region messaging.
* Due to bug {{JIRA|BUG-229767}}, an object's email queue can still become suspended until the object crosses a region border (neither a region restart nor a script reset helps). First analysis has revealed a potential workaround, by implementing a delay of about 30 seconds before first trying to send email to a freshly rezzed script - apparently registering the [[email|email(...)]] event handler can take quite some time, and emails arriving prior to said registry process is what gets the entire queue stuck. Official Linden Lab response still pending.
* Due to the bug {{Jira|SVC-391}}, [[llEmail]] will silently fail (no mail will arrive) when {{Wikipedia|ASCII|non-ASCII}} characters are present in the subject. However, non-ASCII characters in the message body will be replaced by {{mono|"?"}}.
|constants
|examples=
<syntaxhighlight lang="lsl2">
string emailAddress = "somebody@example.com";
string emailHeader = "Someone touched me!";

default
{
touch_start(integer num_detected)
{
// llSay(PUBLIC_CHANNEL, "Sending eMail report now, this will take ~20 seconds.");

key id = llDetectedKey(0);
string name = llDetectedName(0);

llEmail(emailAddress, emailHeader,
"I was touched by: '" + name + "' (" + (string)id + ").");

// llSay(PUBLIC_CHANNEL, "Email has been sent.");
}
}
</syntaxhighlight>
|also_functions=
{{LSL DefineRow||[[llGetNextEmail]]}}
{{LSL DefineRow||[[llMessageLinked]]}}
|also_events=
{{LSL DefineRow||[[email]]}}
{{LSL DefineRow||[[link message]]}}
|also_tests={{LSL DefineRow|[https://osiris.lindenlab.com/mediawiki/index.php/Email_Test internal test]<ref>Probably broken (last tested Feb 2023); the server still exists but is password-protected.</ref>}}
|also_articles={{LSL DefineRow||[[IM to email]]}}
{{LSL DefineRow||[[Postcards]]}}
|notes=* Because of the long delay on this function, it is often called from a second script triggered by [[link_message]].
* If you are sending email to a prim within Second Life, its address is {{mono|''[key]''@lsl.secondlife.com}}
** Which means if the key returned by [[llGetKey]] is "{{mono|a2e76fcd-9360-4f6d-a924-000000000003}}", then its email address is "{{mono|a2e76fcd-9360-4f6d-a924-000000000003@lsl.secondlife.com}}".
** Agents do not have fixed email addresses, use [[llInstantMessage]] or [[llOwnerSay]]<ref>If the agent or object are ''known'' to be in the same region, then you can use [[llRegionSayTo]] instead.</ref>.

===Prim2Prim Email===

In LSL you can both send email with [[llEmail]] and receive it with the [[email]] event.

The email event is triggered with five pieces of information:
{{{!}}
{{LSL DefineRow|string|time|When the message was sent, in the <code>(string)[[llGetUnixTime]]</code> format}}
{{LSL DefineRow|string|address|Who sent the message}}
{{LSL DefineRow|string|subject|Subject of the message}}
{{LSL DefineRow|string|message|Body of the message}}
{{LSL DefineRow|integer|num_left|The number of emails left in the email queue}}
{{!}}}

When receiving a message sent with [[llEmail]] it helps to separate the message from the prefixed header. The header and original message body are separated by {{mono|"\n\n"}}

<syntaxhighlight lang="lsl2">integer divide = llSubStringIndex(message, "\n\n");
string header = llDeleteSubString(message, divide, -1);
message = llDeleteSubString(message, 0, divide + 1);</syntaxhighlight>

To get just one of the header items, do this:
<syntaxhighlight lang="lsl2">list lines = llParseStringKeepNulls(header, ["\n"], []);
string objname_line = llList2String(lines, 0);
string region_line = llList2String(lines, 1);
string localpos_line = llList2String(lines, 2);</syntaxhighlight>

To get a pure region name, do this:
<syntaxhighlight lang="lsl2">string region_name = llStringTrim(
(string)llDeleteSubList(
llParseStringKeepNulls(
llDeleteSubString(region_line, 0, 12),
[],
["("]
), -2, -1), STRING_TRIM);</syntaxhighlight>

This application uses email to have objects check with a central server to see if the owner has the latest version. In the objects:
<syntaxhighlight lang="lsl2">string version = "1"; //
string type = "lolcube";
default
{
on_rez(integer start_param)
{
llEmail("5a634b27-f032-283f-2df2-55ead7724b23@lsl.secondlife.com",
version,
(string)llGetOwner() + "," + type);
}
}</syntaxhighlight>
The server:
<syntaxhighlight lang="lsl2">default
{
state_entry()
{
llSetTimerEvent(15.0);
}

timer()
{
llGetNextEmail("", "");
}

email(string time, string address, string version, string message, integer num_left)
{
if ((integer)version < 2)
{
list info = llCSV2List(llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1));
llGiveInventory(llList2Key(info, 0), llList2String(info, 1));
}

if (num_left)
llGetNextEmail("","");
}
}</syntaxhighlight>
|helpers=
<syntaxhighlight lang="lsl2">
email(string time, string address, string subj, string message, integer num_left)
{
if (llGetSubString(address, -19, -1) == "@lsl.secondlife.com") //trim the header
message = llDeleteSubString(message, 0, llSubStringIndex(message, "\n\n") + 1);
}
</syntaxhighlight>
Get the region name and object position of the object that sent the email:
<syntaxhighlight lang="lsl2">
string region = llList2String(llParseString2List(message, ["Region: "," ("], []),1);
vector position = (vector) ("<" + llList2String(llParseString2List(message, ["Local-Position: (",")\n\n"], []),1) + ">");
</syntaxhighlight>
|permission
|negative_index
|cat1=Communications
|cat2=Email
|cat3
|cat4
}}

LlRequestSecureURL

2025-04-07T15:34:37Z

Peter Stindberg: Someone more knowledgable please rephrase this. New certificates as of Spring 2025.

{{KBwarning|[[llRequestSecureURL]] uses a self-issued certificate, which can cause all kinds of spurious errors. If you are encountering issues, check that your remote is configured to recognize the Linden Lab Certificate Authority. Check the [[#Caveats|Caveats]] section below for details.}}
{{LSL_Function
|func_id=346|func_sleep=0.0|func_energy=10.0
|func=llRequestSecureURL
|return_type=key|return_subtype=handle
|func_footnote
|func_desc=Requests one {{mono|HTTPS://}} ({{Wikipedia|SSL}}) {{Wikipedia|URL}} for use by this [[object]]. The [[http_request]] [[event]] is triggered with result of the request. [[LSL_HTTP_server#Introduction|HTTPS-in]] uses port {{mono|12043}}.
|return_text=used for identifying the result of the request in the [[http_request]] [[event]].
|spec
|caveats=*HTTPS-in uses port {{mono|12043}} (that port is in the URL returned by this method).
*When a [[region]] is (re)started all [[http_request|HTTP server]] URLs are automatically released and invalidated.
**Use [[CHANGED_REGION_START]] to detect this so a new URL can be requested.
* The {{Wikipedia|Public key certificate|server certificate}} is {{Wikipedia|Self-signed certificate|signed}} by our own Linden Lab {{Wikipedia|Certificate Authority}}. In order for your [[Second Life Viewer|client]] to validate the server certificate, you will need to download and install our CA certificate and add it to the CA store on your system: you can download it from https://raw.githubusercontent.com/secondlife/llca/master/LindenLab.crt<ref>Note that Linden Lab has moved from the old BitBucket repository to GitHub; the link is to the [https://github.com/secondlife/llca new official repository].</ref>
* As of Spring 2025, new certificate handling is being rolled out. This might change the whole process. See https://community.secondlife.com/forums/topic/521090-grid-ssl-cert-updates-coming-soon/
|constants
|examples=
{{LSL Tip|Never ever forget to release a URL again which you have requested! URLs are region resources just like prims. If you take them all you can get into big trouble with the [[Private Region|region owner]] and/or [[Estate Manager|estate managers]].}}
Requesting a secure URL:
<syntaxhighlight lang="lsl2">
string secureUrl;
key urlRequestId;
key selfCheckRequestId;

request_secure_url()
{
llReleaseURL(secureUrl);
secureUrl = "";

urlRequestId = llRequestSecureURL();
}

throw_exception(string inputString)
{
key owner = llGetOwner();
llInstantMessage(owner, inputString);

// yeah, bad way to handle exceptions by restarting.
// However this is just a demo script...

llResetScript();
}

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

changed(integer change)
{
if (change & (CHANGED_OWNER | CHANGED_INVENTORY))
{
llReleaseURL(secureUrl);
secureUrl = "";

llResetScript();
}

if (change & (CHANGED_REGION | CHANGED_REGION_START | CHANGED_TELEPORT))
request_secure_url();
}

state_entry()
{
request_secure_url();
}

http_request(key id, string method, string body)
{
integer responseStatus = 400;
string responseBody = "Unsupported method";

if (method == URL_REQUEST_DENIED)
throw_exception("The following error occurred while attempting to get a free URL for this device:\n \n" + body);

else if (method == URL_REQUEST_GRANTED)
{
secureUrl = body;
key owner = llGetOwner();
llLoadURL(owner, "Click to visit my URL!", secureUrl);

// check every 5 mins for dropped URL
llSetTimerEvent(300.0);
}
else if (method == "GET")
{
responseStatus = 200;
responseBody = "Hello world!";
}
// else if (method == "POST") ...;
// else if (method == "PUT") ...;
// else if (method == "DELETE") { responseStatus = 403; responseBody = "forbidden"; }

llHTTPResponse(id, responseStatus, responseBody);
}

http_response(key id, integer status, list metaData, string body)
{
if (id == selfCheckRequestId)
{
// If you're not usually doing this,
// now is a good time to get used to doing it!
selfCheckRequestId = NULL_KEY;

if (status != 200)
request_secure_url();
}

else if (id == NULL_KEY)
throw_exception("Too many HTTP requests too fast!");
}

timer()
{
selfCheckRequestId = llHTTPRequest(secureUrl,
[HTTP_METHOD, "GET",
HTTP_VERBOSE_THROTTLE, FALSE,
HTTP_BODY_MAXLENGTH, 16384],
"");
}
}
</syntaxhighlight>
|helpers
|mode=
|also_functions=
{{LSL DefineRow||[[llRequestURL]]}}
{{LSL DefineRow||[[llGetFreeURLs]]}}
{{LSL DefineRow||[[llReleaseURL]]}}
{{LSL DefineRow||[[llHTTPResponse]]}}
{{LSL DefineRow||[[llGetHTTPHeader]]}}
|also_tests
|also_events
|also_articles=
{{LSL DefineRow||[[LSL http server]]}}
|notes
|deepnotes=
|history=
*{{SVN|1836|rev=112899 |trunk=*|anchor=file22|ver=|ser=}}
|cat1=HTTP
|cat2=HTTP/Server
|cat3
|cat4
}}

LlGiveInventoryList

2025-04-06T10:39:38Z

Peter Stindberg: Added llGiveAgentInventory to see-also

{{LSL_Function
|inject-2={{Issues/SVC-868}}
{{LSL_Function/give|target|inventory|sim=*|uuid=false|insert=list of items}}
|func_id=231|func_sleep=3.0|func_energy=10.0
|func=llGiveInventoryList
|p1_type=key|p1_name=target|p1_desc
|p2_type=string|p2_name=folder|p2_desc=folder name to use
|p3_type=list|p3_name=inventory
|func_footnote
|return_text
|func_desc=Gives '''inventory''' items to '''target''', creating a new '''folder''' to put them in.
|spec=
===target types===
Depending upon the type of '''target''' this function works differently.
* Avatar
** Must be in or able to see into the same Region as the sending object, or recently have been so. [[#SVC-868|SVC-868]]
** Places the inventory items in a newly created folder in the avatars inventory (even if there is a folder by the same name, a new one is created).
* Prim / Object
** The prim ''must'' be in the same region.
** Does ''not'' create a folder.
|caveats=
|examples=
<source lang="lsl2">
default
{
touch_start(integer n)
{
key toucher = llDetectedKey(0);
string folder = "Item Folder";
list inventory = ["item", "another item"];
llGiveInventoryList(toucher, folder, inventory);
}
}
</source>
<source lang="lsl2">
// when the prim is touched, the script checks all other inventory items whether or not they're copiable
// copiable items are added to a list, if the list is not empty when all items have been checked
// the prim gives them to the touching avatar within a single folder

default
{
touch_start(integer num_detected)
{
string thisScript = llGetScriptName();
list inventoryItems;
integer inventoryNumber = llGetInventoryNumber(INVENTORY_ALL);

integer index;
for ( ; index < inventoryNumber; ++index )
{
string itemName = llGetInventoryName(INVENTORY_ALL, index);

if (itemName != thisScript)
{
if (llGetInventoryPermMask(itemName, MASK_OWNER) & PERM_COPY)
{
inventoryItems += itemName;
}
else
{
llSay(0, "Unable to copy the item named '" + itemName + "'.");
}
}
}

if (inventoryItems == [] )
{
llSay(0, "No copiable items found, sorry.");
}
else
{
llGiveInventoryList(llDetectedKey(0), llGetObjectName(), inventoryItems); // 3.0 seconds delay
}
}
}
</source>
<source lang="lsl2">
// script gives items to owner only
// all copiable items are given within a single folder
// all no-copy items are transferred separately (only one time, right? right!)

default
{
touch_start(integer num_detected)
{
key owner = llGetOwner();
if (llDetectedKey(0) != owner)
return;

list inventoryItems;
integer inventoryNumber = llGetInventoryNumber(INVENTORY_ALL);

integer index;
for ( ; index < inventoryNumber; ++index )
{
string itemName = llGetInventoryName(INVENTORY_ALL, index);
if (itemName != llGetScriptName() )
{
if (llGetInventoryPermMask(itemName, MASK_OWNER) & PERM_COPY)
{
inventoryItems += itemName;
}
else
{
llGiveInventory(owner, itemName); // 2.0 seconds delay
}
}
}

if (inventoryItems != [] )
llGiveInventoryList(owner, llGetObjectName(), inventoryItems); // 3.0 seconds delay
}
}
</source>
|helpers
|also_functions={{LSL DefineRow||[[llGiveInventory]]}}
{{LSL DefineRow||[[llGiveAgentInventory]]}}
|also_events={{LSL DefineRow||[[changed]]}}
|also_tests
|also_articles
|notes|cat1=Inventory
|cat2
|cat3
|cat4
}}

LlGiveInventory

2025-04-06T10:38:38Z

Peter Stindberg: Added llGiveAgentInventory to see-also

{{LSL_Function
|inject-2={{LSL_Function/give|destination|inventory|uuid=false|copyok=*}}{{Issues/SVC-7631}}{{Issues/BUG-5656}}
|func_id=150|func_sleep=0.0|func_energy=10.0
|func_sleep_hover=If 'destination' is an avatar the script sleeps for 2.0 seconds. (Giving to objects or attachments has no delay)
|func_sleep_note=If {{LSLP|destination}} is an avatar the script sleeps for 2.0 seconds. (Giving to objects or attachments has no delay)
|func=llGiveInventory
|p1_type=key|p1_name=destination|p1_desc
|p2_type=string|p2_name=inventory
|func_footnote=If {{LSLP|destination}} is an object then it must be in the same [[region]]. If {{LSLP|destination}} is an avatar they do not have to be in the same region.
|func_desc=Give {{LSLP|inventory}} to {{LSLP|destination}}.
|return_text
|spec
|caveats=
* There is no way to know if the transaction failed. Unless you send a message when inventory is given to a prim and prim's script checks its inventory and sends a message back using llRegionSay.
* Scripts reach {{LSLP|destination}} disabled (not running, and cannot be made to run unless the destination object is taken to inventory and rezzed again, or the script is recompiled). To send a running script to a prim use [[llSetRemoteScriptAccessPin]] and [[llRemoteLoadScriptPin]].
* If {{LSLP|destination}} is locked then {{LSLP|inventory}} is not transferred and a '''Blocked by permissions''' error is shouted on the [[DEBUG_CHANNEL]].
* If {{LSLP|destination}} object is not modifiable then {{LSLP|inventory}} is not transferred and a '''Blocked by permissions''' error is shouted on the [[DEBUG_CHANNEL]].
* If {{LSLP|inventory}} is no-copy it is transfered to {{LSLP|destination}} without copying it. Since it is no-copy the only copy is given to {{LSLP|destination}}; removing it from the source prim's inventory.
** To avoid this problem use [[llGetInventoryPermMask]] to check the permissions of {{LSLP|inventory}}.
* {{HoverLink|Attachment|Attachment - Any object that is currently attached to an avatar|Attachments}} cannot give or receive no-copy inventory. When attempted an error is shouted on [[DEBUG_CHANNEL]].
* When giving to an attachment that is not owned by the script owner, the receiving attachment must have [[llAllowInventoryDrop]] set to TRUE.
* If {{LSLP|destination}} is an avatar that refuses to accept it (by manual decline or muting), is in busy mode, or is offline with instant messages capped, it is not returned to the prim's inventory; it is deleted.
** It is not returned to the owner. It does not show up in their lost and found or any other inventory folder.
** It is not put in the target's trash folder.
* A successful send to an offline avatar by means of llGiveInventory() counts as an IM against that avatar’s IM cap.
* As of 31th January 2012, llGiveInventory now has similar throttle to instant messages. A throttle of 5k per hour per owner per region; with a maximum burst of 2.5k. This throttle only affects gives to agents, not to non-agents.
** "With 3k subscribers you will want to send slow enough that it takes ~45 minutes to send 1 item to each subscriber. A general safe way would be to send ~2k as fast as you can, then wait 31 minutes and send another 2k." [https://jira.secondlife.com/browse/SVC-7631?focusedCommentId=308665&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-308665 Kelly Linden on SVC-7631]
** Be aware that while you script a system to handle the top of these limits that other busy scripted objects can be adding up to the throttle as well, such as vendors.
|constants
|examples=
<source lang="lsl2">default
{
touch_start(integer n)
{
//Gives this script to whoever touches the object.
llGiveInventory(llDetectedKey(0), llGetScriptName());
}
}</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llGiveInventoryList]]}}
{{LSL DefineRow||[[llGiveAgentInventory]]}}
{{LSL DefineRow||[[llRemoteLoadScriptPin]]}}
{{LSL DefineRow||[[llSetRemoteScriptAccessPin]]}}
{{LSL DefineRow||[[llMapDestination]]}}
|also_events=
{{LSL DefineRow||[[changed]]}}
|also_tests=
{{LSL DefineRow||[[llGiveInventory Test]]}}
|also_articles
|notes
|permission
|negative_index
|sort=GiveInventory
|cat1=Inventory
|cat2=Avatar
|cat3
|cat4
}}

User talk:WolfGang Senizen

2025-04-04T05:30:49Z

Peter Stindberg: Created page with "Welcome to the wiki! --~~~~"

Welcome to the wiki!

--[[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 22:30, 3 April 2025 (PDT)

Limits

2025-02-21T07:47:22Z

Peter Stindberg: /* Avatar */ New animesh attachment limits for PPlus members

<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]] and body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Edit My Outfit'''.
** 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.
** With the introduction of the Bento armature, there are 47 attachment points available.
** With the introduction of Animesh, there is a limit of 1 Animesh attachment for Basic & Plus members, 2 for Premium members, and 3 for Premium Plus members.
* '''Max. attachment position''' - 3.5m in a sphere around <0, 0, 0>.
* '''Max. # of clothing layers''' - 60 including alpha, tattoo, shoe base, physics, socks, gloves, undershirt, underpants, shirt, pants, jacket, skirt
** On viewers before Second Life Release 3.7.29.301305, the potential total was still 60, but limited to 5 items of each type.
** In any case, only one each of shape, skin, eyes and hair base may be worn. These 4 basic body parts are in addition to the 60 clothing layers.
* '''Max Clothing Texture''' - 1024x1024 px (except 128x128 px for eyes) - Server Side Appearance (and legacy baking on outside grids) will downsize larger textures*. (Support for 2K textures & Bakes on Mesh is in development but not yet supported)
* '''Max. unassisted fly height''' - Stable hover at current ground elevation ''plus'' 5020m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Traditionally, most women's shoes were designed for a size 0 (zero) foot. Men's generally scale up to 14. Newer items (mesh and some sculpted) replace the system feet or conform to the avatar's shape, so adjustments may be necessary.
** 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''' - 6 teleports per minute

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Length of animation
| n/a
| {{no|60.0 seconds}}
| Limited by length or Size, whichever is reached first
| n/a
|-
||Size of Animation
| n/a
| {{no|{{HoverText|250,000 bytes|250 KB (decimal), 244 KB (binary)}}}}
| Limited by length or Size, whichever is reached first. Size is after conversion to [[Internal Animation Format|.anim]]. {{KBtip|custom=Tip for Blender users:|1=You can use a built-in function called "''Decimate''" to simplify your animation. See [https://www.youtube.com/watch?v=lScwEYJZy1M this tutorial]}}
| [[Internal Animation Format]]
|-
||Distance an Animation Can Travel
| {{no|-5 meters (per axis)}}
| {{no|+5 meters (per axis)}}
| 10 meters per axis cumulatively (travelling from -5 to +5).
| n/a

|-
||animation priority
| {{no|0}}
| {{no|.bvh: 4, [[Internal Animation Format|.anim]]: 6}}
| [[Internal Animation Format|.anim]] uses per-joint priorities, meaning it's possible to have a mix of joint priorities in the same animation.
| [[Animation_Priority|Animation Priority]]
|-
||Number of unique joints per animation
| n/a
| {{no|216}}
| [[Internal Animation Format|.anim]], unlike .bvh, uses a flat structure, meaning that only the bones animated are stored, and bones which would otherwise be kept by .bvh (to keep hierarchy structure) are deleted.
| n/a
|-
||Number of simultaneous animations playing
| n/a
| {{no|30}}
| n/a
| n/a
|}

== [http://community.secondlife.com/t5/English-Knowledge-Base/Build-Tools/ta-p/700039 Building] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Prim]] dimensions
| {{no|<0.01, 0.01, 0.01>}}
| {{no|<64.0, 64.0, 64.0>}}
| Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770
| [[llSetScale]], [[PRIM_SIZE]] and [[Megaprim]]
|-
||Number of prims in a linkset
| n/a
| {{no|256 prims}}
| Used to be 255 prior to Second Life Server version 1.26
| n/a
|-
||Linking distance
| n/a
| {{no|64 meters}}
| distance has changed on [https://community.secondlife.com/blogs/entry/13626-coming-soon-server-release-202306/ 2023.06 update]. The old max distance was 54 meters.
| n/a
|-
||Local offset (avatars)
| n/a
| {{no|1000 meters per axis}}
| Unlike regular [[Linkability_Rules|Linkability Rules]] for linksets, an avatar sitting on an object may be moved significantly further by scripts.
| [[llSetLinkPrimitiveParams]] with [[PRIM_POS_LOCAL]]
|-
||[[Mesh/Mesh_physics#Physics_Resource_Cost|Physics cost]] for a physical object
| n/a
| {{no|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.
| [[OBJECT_PHYSICS_COST]]
|-
||Build or rez height
| n/a
| {{no|4096.0 meters}}
| 768.0 meters for Viewers prior to version 1.20
| n/a
|-
||Prim name length
| n/a
| {{no|63 bytes UTF-8 [[String|string]]}}
| same limit for {{LSLGC|Avatar/Name|avatar names}}, although the character set for avatar names is significantly limited.
| n/a
|-
||Prim description length
| n/a
| {{no|127 bytes UTF-8 [[String|string]]}}
| n/a
| n/a
|-
||Temporary prims' lifetime
| n/a
| {{no|up to around 60 seconds}}
| depends upon when the next garbage collector cycle is
| n/a
|-
||Number of temporary prims
| n/a
| {{no|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| n/a
| n/a
|-
||Length of hovertext
| n/a
| {{no|254 bytes UTF-8 [[String|string]]}}
| n/a
| [[llSetText]] and [[PRIM_TEXT]]
|}

== [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/ Lighting] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of projectors rendered at full detail
| n/a
| {{no|2}}
| Only the 2 projectors closest to an object will cause it to cast shadows.
| [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/#Projectors Knowledge Base > Lighting > Projectors]
|-
||Number of lights rendered on Alpha Blended surfaces
| n/a
| {{no|8}}
| 8 including the Sun and Moon. The viewer will attempt to select the "most significant" lights to render, however these blended surfaces will look different as a result of these lighting limitations.
| [[Alpha Modes Do's and Don'ts#Alpha_blending|Alpha Blending]]

|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Whisper distance
| n/a
| {{no|10 meters}}
| <code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Chat distance
| n/a
| {{no|20 meters}}
| text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered. /whisper and /shout ''can'' be used in the "Replace with" field.
| n/a
|-
||Shout distance
| n/a
| {{no|100 meters}}
| <code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Length of a chat message and whether or not it is truncated
| {{no|1 byte or single-byte character}}
| {{no|1024 bytes or single-byte characters}}
| Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1023 bytes or single-byte characters.
The viewer-to-server communication on ''negative'' channels is truncated to 254 bytes, and on ''positive'' channels, to 1023 bytes. These limits do not affect communication between scripts.
| [[llInstantMessage]]
|-
||Maximum events
| n/a
| {{no|64 events}}
| Events are stored in a 64 bit bitmap. Events happening when the bitmap is full, will get discarded.
| n/a
|-
||Number of offline messages
| n/a
| {{no|Capped at 30 messages for Basic members, 40 for Plus members, 120 for Premium members, and 240 for Premium Plus members.}}
| Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped. Note: If autoAcceptNewInventory (debug setting) is set to TRUE (the default is FALSE), then all inventory offers, even above the cap allowed by membership, go directly to inventory and do not count against the cap on offline messages.
| [[IM]] - [https://community.secondlife.com/blogs/entry/2559-group-limits-update-no-changes-for-basic-members/ Blog Post]
|-
||Length of a properly delivered email reply to an [[IM]]
| n/a
| {{no|1023 bytes or single-byte characters}}
| n/a
| n/a
|-
||Time after which a reply to an [[IM]] can be sent via email.
| {{no|when receiving the IM via email.}}
| {{no|5 days after receiving the offline IM via email.}}
| n/a
| [https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]
|-
||Time period for which [[IM|IMs]] are stored within Second Life.
| n/a
| {{no|31 days after receiving the [[IM]]}}
| [[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]
| n/a
|-
||Number of [[IM|IMs]] sent by an object within an hour
| n/a
| {{no|5000 per hour}}
| n/a
| n/a
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Shortcut key mappings
| n/a
| {{no|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| n/a
| [[All_keyboard_shortcut_keys]] and [http://community.secondlife.com/t5/English-Knowledge-Base/Keyboard-shortcuts/ta-p/1086557 the knowledge base]
|-
||Chat step length
| n/a
| {{no|127 bytes or single-byte characters}}
| n/a
| n/a
|-
||Wait time
| n/a
| {{no|3600 seconds (which is one hour)}}
| n/a
| n/a
|-
| Maximum steps data
| n/a
| {{no|1000 bytes}} of packed data; saving with more data returns the message "Gesture save failed. This gesture has too many steps. Try removing some steps, then save again." Shorter text, for example, will allow more steps.
| n/a
| n/a
|-
||Length of included assets
| n/a
| see sections for [[#Animation|animation]], [[#Sound|sound]]
| n/a
| n/a
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 50 for Basic members, 55 for Plus members, 80 for Premium members, 150 for Premium Plus members.
** After downgrading from a higher limit membership to a lower one, you may not join any new groups until you are a member of fewer than your current subscriptions's group limit. For example, if you downgrade from Premium (70 groups allowed) to Basic (42 groups allowed), you can't join any new groups until you're a member of fewer than 42 groups.
** 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.
* '''Maximum Age of a Group Notice:''' 14 days.

== [[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 number of accounts that an inventory item can be shared with at once:''' The limit is unknown, but tests show that it is more than 35. No documentation has been found. One third-party viewer developer says that the code doesn't seem to look for a limit. It just builds the list and sends it to each avatar individually.
* '''Maximum number of inventory items that can be contained in a prim:''' 10,000
* '''Maximum characters in an inventory item name:''' 63
* '''Maximum notecard line:''' None, but scripts can only read the first 1024 bytes (was 255 bytes before server version [https://releasenotes.secondlife.com/simulator/2021-10-25.565008.html 2021-10-25.565008]).
* '''Maximum notecard size:''' 65,536 bytes

* '''Number of items in the Library:''' 3,500 as of 2019-08-10
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.
* '''Maximum number of inventory items displayed in a single inventory folder:''' Several thousand. 
** This was discussed during [http://wiki.secondlife.com/wiki/Simulator_User_Group/Transcripts/2011.03.08] "the folder will load up to the limit number of items, and remaining ones won't show up in the viewer. you still own them, they aren't lost, but they will be hidden until the folder size is reduced."
** There is no specified limit for total avatar inventory, very large folders can be split.
** There was discussion in the Third Party Developers' UG (4/10/2015) meeting about new inventory and login problems from having large numbers of items in a single folder. AISv3 ''removed'' server-side limits on the number of items in a folder. Flat inventories are bad. No one is certain at what number of items in a folder cause a login problem. The fix is to clear the inventory cache (not the viewer cache) and log into a deserted, empty region then move inventory items into folders and sub-folders. - The problem appears at different a number of items depending on your computer and connection speed. Hopefully being on an empty region will give one enough edge to get logged in and do some corrective work before being dropped. If not, you will need to contact support for help. They will divide large folders into smaller groups so you can log in.

== [[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:''' Linden Concierge policy states a 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]]. However, the technical maximum limit is 35 characters, and exceptions to the concierge policy do exist (e.g [http://maps.secondlife.com/secondlife/Sandbox%20-%20Weapons%20testing%20%28no%20damag/128/128/2 Sandbox - Weapons testing (no damag] and [http://slurl.com/secondlife/X/128/128/24 X])
* '''Ban line height for "no entry" or "pay to access"''' (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation ''plus'' 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is '''explicitly banned by name''', the height is the parcel's ground elevation ''plus'' 5000 meters. On current viewers this is visible to the full extent.
* '''Maximum prims in a [[Land#Region|region]]:'''
** "Mainland / Full Region" and "Linden Homes / Full Region": 22,500
** Full Regions in private estates: 20,000 with an [https://community.secondlife.com/t5/Featured-News/Upgrade-Your-Full-Private-Region-to-30-000-Land-Impact-Today/ba-p/3086162 option for 30,000]
** Homestead: 5,000
** Openspace : 1,000
:: To check a region's capacity, use <tt>[[llGetEnv]]("region_max_prims")</tt>.
::''(Region types are as found in the General tab of World > About Land, or returned by ''<tt>llGetEnv("region_product_name")</tt>'')''
* '''Maximum auto return value''': Besides {{code|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 regions cannot be terraformed, including: Bay City regions, Boardman, Brown, De Haro, Horizons, Kama City regions, Nautilus City regions, Nova Albion regions, and Shermerville regions.
** [http://community.secondlife.com/t5/English-Knowledge-Base/Linden-Homes/ta-p/700103 Linden Homes] do not allow terraforming.
** 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, 255 meters by using a {{code|*.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 {{code|*.raw}} file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 20 estate managers, 500 allowed Residents, 63 allowed groups, and 750 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Maximum number of agents'''
** [https://second.life/eventregions Event Regions]: 175 agents
** Full region: 100 basic account users plus 10 additional available to premium accounts. (Typically set to 40 on mainland, 55 on Linden Homes regions, 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 (plus 5 additional available to premium accounts)
** [[Land#Openspace|Openspace]]: 10 (plus 2 additional available to premium accounts)
* '''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

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of vertices
| n/a
| {{no|65536 vertices per LOD}}
| per [[mesh]] - See [[Talk:Limits#Mesh_Limits|discussion page]]
| n/a
|-
||COLLADA file size
| n/a
| {{no|8 MB}}
| Maximum mesh asset size after compression, roughly equivalent to a 256 MB Raw COLLADA file.
| n/a
|-
||Bone influence weights per vertex
| n/a
| {{no|4}}
| n/a
| n/a
|-
||Bone influence weights per mesh
| n/a
| {{no|110}}
| some folk have reported needing to go as low as about 99 in rare cases
| n/a
|-
||Number of materials per mesh
| n/a
| {{no|8}}
| n/a
| n/a
|-
||Number of materials per face
| n/a
| {{no|1}}
| n/a
| n/a
|-
||Physics weight for a vehicle
| n/a
| {{no|32.0}}
| n/a
| n/a
|-
||Maximum number of triangles for Animesh
| n/a
| {{no|100,000}}
| Server uses estimated triangles (streaming cost calculated), not visual triangles.
| [[Animesh User Guide|Animesh_User_Guide]]
|}

===User Found Temporary Mesh Limits:===
''Because of an apparent bug in the importer stay within these limits.''
* 174,752 triangles, beyond which additional triangles will appear as holes.
* The 64k vertices per material is pre-empted by a limit of 21,844 triangles per material, which is presently reported as {{Jira|BUG-1001}}. (4/2014 - See [[Talk:Limits#Mesh_Limits|discussion page]])

:: The import process will continue making new materials beyond 8 x 21,844 (=174,752) triangles, but the extra triangles then get dropped by the limitation to 8 materials, causing holes in the resulting object. Over the 21,844-triangle limit, the vertex count will start to climb steeply, even with smooth shading, because the materials get highly interspersed. So the same vertices have to appear in multiple material lists. So, the moral of the story is to stay below 21,844 triangles per material, for now, if you want to avoid some unexpected effects.

::Since viewer release 3.8.4, processing of meshes in the Collada file that have faces assigned to more than 8 materials has changed. Instead of simply dropping the extra material faces, the uploader now creates a new object to accommodate them. The result is that the single mesh is divided into multiple objects (prims) in a linkset. Thus, the limitation to 8 materials is removed as far as input is concerned, but still applies to each of the resulting linked objects actually uploaded. As a consequence, it is now possible to upload a mesh with more than 174,752 triangles, although it will be divided into multiple objects.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.

== 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] = 231 − 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:''' 4096
** This used to be much higher, but is clamped in late model viewers.

== [[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

== [[Lag|Performance]] ==

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

'''*''' Only until your framerate reaches your monitor's refresh rate, after this point there will be very little benefit.

== [[Scripting]] == 

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls will keep running when you fly down or enter a no-script parcel. (If scripts are disabled in the region debug panel, they will not run at any height.)
* '''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 (that's a viewer limit and can be changed in the config file 'panel_script_ed.xml').
* '''Maximum script memory size (LSO)''' - 16384 bytes.
* '''Maximum script memory size ([[Mono]])''' - 65536 bytes (the maximum memory available to Mono scripts can be constrained via [[llSetMemoryLimit]]).
* '''Maximum memory for [[:Category:LSL LinksetData|Linkset data]]''' key/value pairs - 128 KiB
* '''Maximum memory for [[:Category:Experience Tools|Experience]]''' key/value pairs- 128 MiB
* '''Maximum active [[llListen|listeners]] per script''' - 65.
** '''Usable channel for each listener''' - ''min.'' -2147483648, ''max.'' 2147483647, including the following special channels: [[PUBLIC_CHANNEL]] ''and'' [[DEBUG_CHANNEL]].
* '''Maximum number of scripts that can be rezzed at once''' – 1,000. (Refer to [https://community.secondlife.com/knowledgebase/english/building-tips-r13/ Building Tips, by Jeremy Linden].)
* For specific scripting limits, look up calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==



{{KBtip|Second Life will accept sounds that are encoded following "[https://en.wikipedia.org/wiki/Compact_Disc_Digital_Audio CD Quality]" encoding presets present in many {{Abbr|DAW|Digital Audio Workstation}}s.}}

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Sound length
| n/a
| {{no|less than 30 seconds or precisely 1,323,000 samples}}
| The advice is typically to upload sounds less than 30.0 and that 29.99 seconds is fine. However if you do wish to be able upload sounds that are 30 seconds precisely then the .WAV file must have exactly 1,323,000 samples (44,100Hz * 30 seconds). Specifically anything above 1,323,000 samples fails to upload.
| '''[https://community.secondlife.com/knowledgebase/english/uploading-assets-r75/ Uploading Assets]'''
|-
||Bit depth
| n/a
| {{no|16 bit}}
| n/a
| n/a
|-
||Sample rate
| n/a
| {{no|44.100 kHz}}
| n/a
| n/a
|-
||Audio channels
| n/a
| {{no|1 channel (mono)}}
| Channels will be '''merged''' at upload time for dual-channel (stereo) audio.
| 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:

=== Second Life Viewer 3.6 ===

* '''Search > Classifieds thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (159×120 pixels)
* '''Search > Classifieds expanded > More Info''' - native aspect ratio
* '''Search > Destination Guide thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Destination Guide expanded''' - ~4:3 (159×120 pixels)
* '''Search > People''' - 1:1 (100×100 pixels)
* '''Search > Places expanded''' ~4:3 (159×120 pixels)
* '''Place Profile''' - ~3:2 (290×197 pixels)
* '''About Land > Options tab''' - ~4:3 (195×150 pixels)
* '''Profile > Picture''' - native aspect ratio; thumbnail cropped to 72×72 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Real world picture''' - native aspect ratio; thumbnail cropped to 45×45 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Picks thumbnail''' - ~16:9 (~516×~270 pixels as measured on screen; the ratio seems closer to 16:8.5)
* '''Profile > Pick expanded''' - Unknown as of 2022-11-13 (viewer 6.6.7.576223); the Pick image does not expand.

=== 1.x Series Viewers ===
(official Viewer up to 1.23.5, still used by some [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pixels)<ref>As of {{#time: r|2024-02-26T18:00:00}}, this seems to be one of the very few sizes supported by the [[Picture Service]].</ref>
* '''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.]]

=== All Viewers ===

* '''Maximum texture size''' - 2048×2048 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** 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 2048×2048.

* '''Minimum texture size''' - 4×4 pixels
** This means that there are ten possible image dimensions: 4, 8, 16, 32, 64, 128, 256, 512, 1024 & 2048 pixels, either horizontal or vertical.

* '''Texture resizing'''
** Uploaded textures will be resized to the dimensions above.
** Each dimension is resized independently (for instance, a 1024 x 999 image will be resized to 1024 x 1024).
** A dimension that is already a power of two will not be resized.
** The uploader “prefers” to round down rather than up. The threshold for rounding down/up is .75 of the distance between powers of two.
*** For example, given a dimension of x, if x / 512 is larger than 1.75, x will be resized to 1024, else 512.
*** Another example: If x / 256 is larger than 1.75, x will be resized to 512.

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

=== Notes ===
In general, 1 byte is enough to contain one character.<ref>Except in .NET-based applications, and those related to .NET development — which is the case of the SL viewer — which essentially use UTF-16 everywhere, i.e., every character is encoded in ''two'' bytes, not just one.</ref>

----
{{References}}

Limits

2025-02-21T07:45:42Z

Peter Stindberg: /* Communication */ New offline IM limits as of February 2025

<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]] and body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Edit My Outfit'''.
** 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.
** With the introduction of the Bento armature, there are 47 attachment points available.
** With the introduction of Animesh, there is a limit of 1 Animesh attachment for Basic & Plus members, 2 if the resident has Premium or Premium Plus.
* '''Max. attachment position''' - 3.5m in a sphere around <0, 0, 0>.
* '''Max. # of clothing layers''' - 60 including alpha, tattoo, shoe base, physics, socks, gloves, undershirt, underpants, shirt, pants, jacket, skirt
** On viewers before Second Life Release 3.7.29.301305, the potential total was still 60, but limited to 5 items of each type.
** In any case, only one each of shape, skin, eyes and hair base may be worn. These 4 basic body parts are in addition to the 60 clothing layers.
* '''Max Clothing Texture''' - 1024x1024 px (except 128x128 px for eyes) - Server Side Appearance (and legacy baking on outside grids) will downsize larger textures*. (Support for 2K textures & Bakes on Mesh is in development but not yet supported)
* '''Max. unassisted fly height''' - Stable hover at current ground elevation ''plus'' 5020m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Traditionally, most women's shoes were designed for a size 0 (zero) foot. Men's generally scale up to 14. Newer items (mesh and some sculpted) replace the system feet or conform to the avatar's shape, so adjustments may be necessary.
** 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''' - 6 teleports per minute

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Length of animation
| n/a
| {{no|60.0 seconds}}
| Limited by length or Size, whichever is reached first
| n/a
|-
||Size of Animation
| n/a
| {{no|{{HoverText|250,000 bytes|250 KB (decimal), 244 KB (binary)}}}}
| Limited by length or Size, whichever is reached first. Size is after conversion to [[Internal Animation Format|.anim]]. {{KBtip|custom=Tip for Blender users:|1=You can use a built-in function called "''Decimate''" to simplify your animation. See [https://www.youtube.com/watch?v=lScwEYJZy1M this tutorial]}}
| [[Internal Animation Format]]
|-
||Distance an Animation Can Travel
| {{no|-5 meters (per axis)}}
| {{no|+5 meters (per axis)}}
| 10 meters per axis cumulatively (travelling from -5 to +5).
| n/a

|-
||animation priority
| {{no|0}}
| {{no|.bvh: 4, [[Internal Animation Format|.anim]]: 6}}
| [[Internal Animation Format|.anim]] uses per-joint priorities, meaning it's possible to have a mix of joint priorities in the same animation.
| [[Animation_Priority|Animation Priority]]
|-
||Number of unique joints per animation
| n/a
| {{no|216}}
| [[Internal Animation Format|.anim]], unlike .bvh, uses a flat structure, meaning that only the bones animated are stored, and bones which would otherwise be kept by .bvh (to keep hierarchy structure) are deleted.
| n/a
|-
||Number of simultaneous animations playing
| n/a
| {{no|30}}
| n/a
| n/a
|}

== [http://community.secondlife.com/t5/English-Knowledge-Base/Build-Tools/ta-p/700039 Building] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Prim]] dimensions
| {{no|<0.01, 0.01, 0.01>}}
| {{no|<64.0, 64.0, 64.0>}}
| Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770
| [[llSetScale]], [[PRIM_SIZE]] and [[Megaprim]]
|-
||Number of prims in a linkset
| n/a
| {{no|256 prims}}
| Used to be 255 prior to Second Life Server version 1.26
| n/a
|-
||Linking distance
| n/a
| {{no|64 meters}}
| distance has changed on [https://community.secondlife.com/blogs/entry/13626-coming-soon-server-release-202306/ 2023.06 update]. The old max distance was 54 meters.
| n/a
|-
||Local offset (avatars)
| n/a
| {{no|1000 meters per axis}}
| Unlike regular [[Linkability_Rules|Linkability Rules]] for linksets, an avatar sitting on an object may be moved significantly further by scripts.
| [[llSetLinkPrimitiveParams]] with [[PRIM_POS_LOCAL]]
|-
||[[Mesh/Mesh_physics#Physics_Resource_Cost|Physics cost]] for a physical object
| n/a
| {{no|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.
| [[OBJECT_PHYSICS_COST]]
|-
||Build or rez height
| n/a
| {{no|4096.0 meters}}
| 768.0 meters for Viewers prior to version 1.20
| n/a
|-
||Prim name length
| n/a
| {{no|63 bytes UTF-8 [[String|string]]}}
| same limit for {{LSLGC|Avatar/Name|avatar names}}, although the character set for avatar names is significantly limited.
| n/a
|-
||Prim description length
| n/a
| {{no|127 bytes UTF-8 [[String|string]]}}
| n/a
| n/a
|-
||Temporary prims' lifetime
| n/a
| {{no|up to around 60 seconds}}
| depends upon when the next garbage collector cycle is
| n/a
|-
||Number of temporary prims
| n/a
| {{no|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| n/a
| n/a
|-
||Length of hovertext
| n/a
| {{no|254 bytes UTF-8 [[String|string]]}}
| n/a
| [[llSetText]] and [[PRIM_TEXT]]
|}

== [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/ Lighting] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of projectors rendered at full detail
| n/a
| {{no|2}}
| Only the 2 projectors closest to an object will cause it to cast shadows.
| [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/#Projectors Knowledge Base > Lighting > Projectors]
|-
||Number of lights rendered on Alpha Blended surfaces
| n/a
| {{no|8}}
| 8 including the Sun and Moon. The viewer will attempt to select the "most significant" lights to render, however these blended surfaces will look different as a result of these lighting limitations.
| [[Alpha Modes Do's and Don'ts#Alpha_blending|Alpha Blending]]

|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Whisper distance
| n/a
| {{no|10 meters}}
| <code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Chat distance
| n/a
| {{no|20 meters}}
| text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered. /whisper and /shout ''can'' be used in the "Replace with" field.
| n/a
|-
||Shout distance
| n/a
| {{no|100 meters}}
| <code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Length of a chat message and whether or not it is truncated
| {{no|1 byte or single-byte character}}
| {{no|1024 bytes or single-byte characters}}
| Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1023 bytes or single-byte characters.
The viewer-to-server communication on ''negative'' channels is truncated to 254 bytes, and on ''positive'' channels, to 1023 bytes. These limits do not affect communication between scripts.
| [[llInstantMessage]]
|-
||Maximum events
| n/a
| {{no|64 events}}
| Events are stored in a 64 bit bitmap. Events happening when the bitmap is full, will get discarded.
| n/a
|-
||Number of offline messages
| n/a
| {{no|Capped at 30 messages for Basic members, 40 for Plus members, 120 for Premium members, and 240 for Premium Plus members.}}
| Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped. Note: If autoAcceptNewInventory (debug setting) is set to TRUE (the default is FALSE), then all inventory offers, even above the cap allowed by membership, go directly to inventory and do not count against the cap on offline messages.
| [[IM]] - [https://community.secondlife.com/blogs/entry/2559-group-limits-update-no-changes-for-basic-members/ Blog Post]
|-
||Length of a properly delivered email reply to an [[IM]]
| n/a
| {{no|1023 bytes or single-byte characters}}
| n/a
| n/a
|-
||Time after which a reply to an [[IM]] can be sent via email.
| {{no|when receiving the IM via email.}}
| {{no|5 days after receiving the offline IM via email.}}
| n/a
| [https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]
|-
||Time period for which [[IM|IMs]] are stored within Second Life.
| n/a
| {{no|31 days after receiving the [[IM]]}}
| [[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]
| n/a
|-
||Number of [[IM|IMs]] sent by an object within an hour
| n/a
| {{no|5000 per hour}}
| n/a
| n/a
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Shortcut key mappings
| n/a
| {{no|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| n/a
| [[All_keyboard_shortcut_keys]] and [http://community.secondlife.com/t5/English-Knowledge-Base/Keyboard-shortcuts/ta-p/1086557 the knowledge base]
|-
||Chat step length
| n/a
| {{no|127 bytes or single-byte characters}}
| n/a
| n/a
|-
||Wait time
| n/a
| {{no|3600 seconds (which is one hour)}}
| n/a
| n/a
|-
| Maximum steps data
| n/a
| {{no|1000 bytes}} of packed data; saving with more data returns the message "Gesture save failed. This gesture has too many steps. Try removing some steps, then save again." Shorter text, for example, will allow more steps.
| n/a
| n/a
|-
||Length of included assets
| n/a
| see sections for [[#Animation|animation]], [[#Sound|sound]]
| n/a
| n/a
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 50 for Basic members, 55 for Plus members, 80 for Premium members, 150 for Premium Plus members.
** After downgrading from a higher limit membership to a lower one, you may not join any new groups until you are a member of fewer than your current subscriptions's group limit. For example, if you downgrade from Premium (70 groups allowed) to Basic (42 groups allowed), you can't join any new groups until you're a member of fewer than 42 groups.
** 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.
* '''Maximum Age of a Group Notice:''' 14 days.

== [[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 number of accounts that an inventory item can be shared with at once:''' The limit is unknown, but tests show that it is more than 35. No documentation has been found. One third-party viewer developer says that the code doesn't seem to look for a limit. It just builds the list and sends it to each avatar individually.
* '''Maximum number of inventory items that can be contained in a prim:''' 10,000
* '''Maximum characters in an inventory item name:''' 63
* '''Maximum notecard line:''' None, but scripts can only read the first 1024 bytes (was 255 bytes before server version [https://releasenotes.secondlife.com/simulator/2021-10-25.565008.html 2021-10-25.565008]).
* '''Maximum notecard size:''' 65,536 bytes

* '''Number of items in the Library:''' 3,500 as of 2019-08-10
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.
* '''Maximum number of inventory items displayed in a single inventory folder:''' Several thousand. 
** This was discussed during [http://wiki.secondlife.com/wiki/Simulator_User_Group/Transcripts/2011.03.08] "the folder will load up to the limit number of items, and remaining ones won't show up in the viewer. you still own them, they aren't lost, but they will be hidden until the folder size is reduced."
** There is no specified limit for total avatar inventory, very large folders can be split.
** There was discussion in the Third Party Developers' UG (4/10/2015) meeting about new inventory and login problems from having large numbers of items in a single folder. AISv3 ''removed'' server-side limits on the number of items in a folder. Flat inventories are bad. No one is certain at what number of items in a folder cause a login problem. The fix is to clear the inventory cache (not the viewer cache) and log into a deserted, empty region then move inventory items into folders and sub-folders. - The problem appears at different a number of items depending on your computer and connection speed. Hopefully being on an empty region will give one enough edge to get logged in and do some corrective work before being dropped. If not, you will need to contact support for help. They will divide large folders into smaller groups so you can log in.

== [[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:''' Linden Concierge policy states a 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]]. However, the technical maximum limit is 35 characters, and exceptions to the concierge policy do exist (e.g [http://maps.secondlife.com/secondlife/Sandbox%20-%20Weapons%20testing%20%28no%20damag/128/128/2 Sandbox - Weapons testing (no damag] and [http://slurl.com/secondlife/X/128/128/24 X])
* '''Ban line height for "no entry" or "pay to access"''' (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation ''plus'' 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is '''explicitly banned by name''', the height is the parcel's ground elevation ''plus'' 5000 meters. On current viewers this is visible to the full extent.
* '''Maximum prims in a [[Land#Region|region]]:'''
** "Mainland / Full Region" and "Linden Homes / Full Region": 22,500
** Full Regions in private estates: 20,000 with an [https://community.secondlife.com/t5/Featured-News/Upgrade-Your-Full-Private-Region-to-30-000-Land-Impact-Today/ba-p/3086162 option for 30,000]
** Homestead: 5,000
** Openspace : 1,000
:: To check a region's capacity, use <tt>[[llGetEnv]]("region_max_prims")</tt>.
::''(Region types are as found in the General tab of World > About Land, or returned by ''<tt>llGetEnv("region_product_name")</tt>'')''
* '''Maximum auto return value''': Besides {{code|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 regions cannot be terraformed, including: Bay City regions, Boardman, Brown, De Haro, Horizons, Kama City regions, Nautilus City regions, Nova Albion regions, and Shermerville regions.
** [http://community.secondlife.com/t5/English-Knowledge-Base/Linden-Homes/ta-p/700103 Linden Homes] do not allow terraforming.
** 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, 255 meters by using a {{code|*.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 {{code|*.raw}} file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 20 estate managers, 500 allowed Residents, 63 allowed groups, and 750 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Maximum number of agents'''
** [https://second.life/eventregions Event Regions]: 175 agents
** Full region: 100 basic account users plus 10 additional available to premium accounts. (Typically set to 40 on mainland, 55 on Linden Homes regions, 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 (plus 5 additional available to premium accounts)
** [[Land#Openspace|Openspace]]: 10 (plus 2 additional available to premium accounts)
* '''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

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of vertices
| n/a
| {{no|65536 vertices per LOD}}
| per [[mesh]] - See [[Talk:Limits#Mesh_Limits|discussion page]]
| n/a
|-
||COLLADA file size
| n/a
| {{no|8 MB}}
| Maximum mesh asset size after compression, roughly equivalent to a 256 MB Raw COLLADA file.
| n/a
|-
||Bone influence weights per vertex
| n/a
| {{no|4}}
| n/a
| n/a
|-
||Bone influence weights per mesh
| n/a
| {{no|110}}
| some folk have reported needing to go as low as about 99 in rare cases
| n/a
|-
||Number of materials per mesh
| n/a
| {{no|8}}
| n/a
| n/a
|-
||Number of materials per face
| n/a
| {{no|1}}
| n/a
| n/a
|-
||Physics weight for a vehicle
| n/a
| {{no|32.0}}
| n/a
| n/a
|-
||Maximum number of triangles for Animesh
| n/a
| {{no|100,000}}
| Server uses estimated triangles (streaming cost calculated), not visual triangles.
| [[Animesh User Guide|Animesh_User_Guide]]
|}

===User Found Temporary Mesh Limits:===
''Because of an apparent bug in the importer stay within these limits.''
* 174,752 triangles, beyond which additional triangles will appear as holes.
* The 64k vertices per material is pre-empted by a limit of 21,844 triangles per material, which is presently reported as {{Jira|BUG-1001}}. (4/2014 - See [[Talk:Limits#Mesh_Limits|discussion page]])

:: The import process will continue making new materials beyond 8 x 21,844 (=174,752) triangles, but the extra triangles then get dropped by the limitation to 8 materials, causing holes in the resulting object. Over the 21,844-triangle limit, the vertex count will start to climb steeply, even with smooth shading, because the materials get highly interspersed. So the same vertices have to appear in multiple material lists. So, the moral of the story is to stay below 21,844 triangles per material, for now, if you want to avoid some unexpected effects.

::Since viewer release 3.8.4, processing of meshes in the Collada file that have faces assigned to more than 8 materials has changed. Instead of simply dropping the extra material faces, the uploader now creates a new object to accommodate them. The result is that the single mesh is divided into multiple objects (prims) in a linkset. Thus, the limitation to 8 materials is removed as far as input is concerned, but still applies to each of the resulting linked objects actually uploaded. As a consequence, it is now possible to upload a mesh with more than 174,752 triangles, although it will be divided into multiple objects.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.

== 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] = 231 − 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:''' 4096
** This used to be much higher, but is clamped in late model viewers.

== [[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

== [[Lag|Performance]] ==

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

'''*''' Only until your framerate reaches your monitor's refresh rate, after this point there will be very little benefit.

== [[Scripting]] == 

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls will keep running when you fly down or enter a no-script parcel. (If scripts are disabled in the region debug panel, they will not run at any height.)
* '''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 (that's a viewer limit and can be changed in the config file 'panel_script_ed.xml').
* '''Maximum script memory size (LSO)''' - 16384 bytes.
* '''Maximum script memory size ([[Mono]])''' - 65536 bytes (the maximum memory available to Mono scripts can be constrained via [[llSetMemoryLimit]]).
* '''Maximum memory for [[:Category:LSL LinksetData|Linkset data]]''' key/value pairs - 128 KiB
* '''Maximum memory for [[:Category:Experience Tools|Experience]]''' key/value pairs- 128 MiB
* '''Maximum active [[llListen|listeners]] per script''' - 65.
** '''Usable channel for each listener''' - ''min.'' -2147483648, ''max.'' 2147483647, including the following special channels: [[PUBLIC_CHANNEL]] ''and'' [[DEBUG_CHANNEL]].
* '''Maximum number of scripts that can be rezzed at once''' – 1,000. (Refer to [https://community.secondlife.com/knowledgebase/english/building-tips-r13/ Building Tips, by Jeremy Linden].)
* For specific scripting limits, look up calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==



{{KBtip|Second Life will accept sounds that are encoded following "[https://en.wikipedia.org/wiki/Compact_Disc_Digital_Audio CD Quality]" encoding presets present in many {{Abbr|DAW|Digital Audio Workstation}}s.}}

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Sound length
| n/a
| {{no|less than 30 seconds or precisely 1,323,000 samples}}
| The advice is typically to upload sounds less than 30.0 and that 29.99 seconds is fine. However if you do wish to be able upload sounds that are 30 seconds precisely then the .WAV file must have exactly 1,323,000 samples (44,100Hz * 30 seconds). Specifically anything above 1,323,000 samples fails to upload.
| '''[https://community.secondlife.com/knowledgebase/english/uploading-assets-r75/ Uploading Assets]'''
|-
||Bit depth
| n/a
| {{no|16 bit}}
| n/a
| n/a
|-
||Sample rate
| n/a
| {{no|44.100 kHz}}
| n/a
| n/a
|-
||Audio channels
| n/a
| {{no|1 channel (mono)}}
| Channels will be '''merged''' at upload time for dual-channel (stereo) audio.
| 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:

=== Second Life Viewer 3.6 ===

* '''Search > Classifieds thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (159×120 pixels)
* '''Search > Classifieds expanded > More Info''' - native aspect ratio
* '''Search > Destination Guide thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Destination Guide expanded''' - ~4:3 (159×120 pixels)
* '''Search > People''' - 1:1 (100×100 pixels)
* '''Search > Places expanded''' ~4:3 (159×120 pixels)
* '''Place Profile''' - ~3:2 (290×197 pixels)
* '''About Land > Options tab''' - ~4:3 (195×150 pixels)
* '''Profile > Picture''' - native aspect ratio; thumbnail cropped to 72×72 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Real world picture''' - native aspect ratio; thumbnail cropped to 45×45 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Picks thumbnail''' - ~16:9 (~516×~270 pixels as measured on screen; the ratio seems closer to 16:8.5)
* '''Profile > Pick expanded''' - Unknown as of 2022-11-13 (viewer 6.6.7.576223); the Pick image does not expand.

=== 1.x Series Viewers ===
(official Viewer up to 1.23.5, still used by some [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pixels)<ref>As of {{#time: r|2024-02-26T18:00:00}}, this seems to be one of the very few sizes supported by the [[Picture Service]].</ref>
* '''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.]]

=== All Viewers ===

* '''Maximum texture size''' - 2048×2048 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** 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 2048×2048.

* '''Minimum texture size''' - 4×4 pixels
** This means that there are ten possible image dimensions: 4, 8, 16, 32, 64, 128, 256, 512, 1024 & 2048 pixels, either horizontal or vertical.

* '''Texture resizing'''
** Uploaded textures will be resized to the dimensions above.
** Each dimension is resized independently (for instance, a 1024 x 999 image will be resized to 1024 x 1024).
** A dimension that is already a power of two will not be resized.
** The uploader “prefers” to round down rather than up. The threshold for rounding down/up is .75 of the distance between powers of two.
*** For example, given a dimension of x, if x / 512 is larger than 1.75, x will be resized to 1024, else 512.
*** Another example: If x / 256 is larger than 1.75, x will be resized to 512.

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

=== Notes ===
In general, 1 byte is enough to contain one character.<ref>Except in .NET-based applications, and those related to .NET development — which is the case of the SL viewer — which essentially use UTF-16 everywhere, i.e., every character is encoded in ''two'' bytes, not just one.</ref>

----
{{References}}

Limits

2025-02-21T07:41:48Z

Peter Stindberg: /* Groups */ New limits as of February 2025

<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]] and body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Edit My Outfit'''.
** 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.
** With the introduction of the Bento armature, there are 47 attachment points available.
** With the introduction of Animesh, there is a limit of 1 Animesh attachment for Basic & Plus members, 2 if the resident has Premium or Premium Plus.
* '''Max. attachment position''' - 3.5m in a sphere around <0, 0, 0>.
* '''Max. # of clothing layers''' - 60 including alpha, tattoo, shoe base, physics, socks, gloves, undershirt, underpants, shirt, pants, jacket, skirt
** On viewers before Second Life Release 3.7.29.301305, the potential total was still 60, but limited to 5 items of each type.
** In any case, only one each of shape, skin, eyes and hair base may be worn. These 4 basic body parts are in addition to the 60 clothing layers.
* '''Max Clothing Texture''' - 1024x1024 px (except 128x128 px for eyes) - Server Side Appearance (and legacy baking on outside grids) will downsize larger textures*. (Support for 2K textures & Bakes on Mesh is in development but not yet supported)
* '''Max. unassisted fly height''' - Stable hover at current ground elevation ''plus'' 5020m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Traditionally, most women's shoes were designed for a size 0 (zero) foot. Men's generally scale up to 14. Newer items (mesh and some sculpted) replace the system feet or conform to the avatar's shape, so adjustments may be necessary.
** 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''' - 6 teleports per minute

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Length of animation
| n/a
| {{no|60.0 seconds}}
| Limited by length or Size, whichever is reached first
| n/a
|-
||Size of Animation
| n/a
| {{no|{{HoverText|250,000 bytes|250 KB (decimal), 244 KB (binary)}}}}
| Limited by length or Size, whichever is reached first. Size is after conversion to [[Internal Animation Format|.anim]]. {{KBtip|custom=Tip for Blender users:|1=You can use a built-in function called "''Decimate''" to simplify your animation. See [https://www.youtube.com/watch?v=lScwEYJZy1M this tutorial]}}
| [[Internal Animation Format]]
|-
||Distance an Animation Can Travel
| {{no|-5 meters (per axis)}}
| {{no|+5 meters (per axis)}}
| 10 meters per axis cumulatively (travelling from -5 to +5).
| n/a

|-
||animation priority
| {{no|0}}
| {{no|.bvh: 4, [[Internal Animation Format|.anim]]: 6}}
| [[Internal Animation Format|.anim]] uses per-joint priorities, meaning it's possible to have a mix of joint priorities in the same animation.
| [[Animation_Priority|Animation Priority]]
|-
||Number of unique joints per animation
| n/a
| {{no|216}}
| [[Internal Animation Format|.anim]], unlike .bvh, uses a flat structure, meaning that only the bones animated are stored, and bones which would otherwise be kept by .bvh (to keep hierarchy structure) are deleted.
| n/a
|-
||Number of simultaneous animations playing
| n/a
| {{no|30}}
| n/a
| n/a
|}

== [http://community.secondlife.com/t5/English-Knowledge-Base/Build-Tools/ta-p/700039 Building] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Prim]] dimensions
| {{no|<0.01, 0.01, 0.01>}}
| {{no|<64.0, 64.0, 64.0>}}
| Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770
| [[llSetScale]], [[PRIM_SIZE]] and [[Megaprim]]
|-
||Number of prims in a linkset
| n/a
| {{no|256 prims}}
| Used to be 255 prior to Second Life Server version 1.26
| n/a
|-
||Linking distance
| n/a
| {{no|64 meters}}
| distance has changed on [https://community.secondlife.com/blogs/entry/13626-coming-soon-server-release-202306/ 2023.06 update]. The old max distance was 54 meters.
| n/a
|-
||Local offset (avatars)
| n/a
| {{no|1000 meters per axis}}
| Unlike regular [[Linkability_Rules|Linkability Rules]] for linksets, an avatar sitting on an object may be moved significantly further by scripts.
| [[llSetLinkPrimitiveParams]] with [[PRIM_POS_LOCAL]]
|-
||[[Mesh/Mesh_physics#Physics_Resource_Cost|Physics cost]] for a physical object
| n/a
| {{no|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.
| [[OBJECT_PHYSICS_COST]]
|-
||Build or rez height
| n/a
| {{no|4096.0 meters}}
| 768.0 meters for Viewers prior to version 1.20
| n/a
|-
||Prim name length
| n/a
| {{no|63 bytes UTF-8 [[String|string]]}}
| same limit for {{LSLGC|Avatar/Name|avatar names}}, although the character set for avatar names is significantly limited.
| n/a
|-
||Prim description length
| n/a
| {{no|127 bytes UTF-8 [[String|string]]}}
| n/a
| n/a
|-
||Temporary prims' lifetime
| n/a
| {{no|up to around 60 seconds}}
| depends upon when the next garbage collector cycle is
| n/a
|-
||Number of temporary prims
| n/a
| {{no|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| n/a
| n/a
|-
||Length of hovertext
| n/a
| {{no|254 bytes UTF-8 [[String|string]]}}
| n/a
| [[llSetText]] and [[PRIM_TEXT]]
|}

== [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/ Lighting] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of projectors rendered at full detail
| n/a
| {{no|2}}
| Only the 2 projectors closest to an object will cause it to cast shadows.
| [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/#Projectors Knowledge Base > Lighting > Projectors]
|-
||Number of lights rendered on Alpha Blended surfaces
| n/a
| {{no|8}}
| 8 including the Sun and Moon. The viewer will attempt to select the "most significant" lights to render, however these blended surfaces will look different as a result of these lighting limitations.
| [[Alpha Modes Do's and Don'ts#Alpha_blending|Alpha Blending]]

|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Whisper distance
| n/a
| {{no|10 meters}}
| <code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Chat distance
| n/a
| {{no|20 meters}}
| text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered. /whisper and /shout ''can'' be used in the "Replace with" field.
| n/a
|-
||Shout distance
| n/a
| {{no|100 meters}}
| <code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Length of a chat message and whether or not it is truncated
| {{no|1 byte or single-byte character}}
| {{no|1024 bytes or single-byte characters}}
| Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1023 bytes or single-byte characters.
The viewer-to-server communication on ''negative'' channels is truncated to 254 bytes, and on ''positive'' channels, to 1023 bytes. These limits do not affect communication between scripts.
| [[llInstantMessage]]
|-
||Maximum events
| n/a
| {{no|64 events}}
| Events are stored in a 64 bit bitmap. Events happening when the bitmap is full, will get discarded.
| n/a
|-
||Number of offline messages
| n/a
| {{no|Capped at 15 messages for Basic & Plus members, 80 for Premium members, and 160 for Premium Plus members.}}
| Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped. Note: If autoAcceptNewInventory (debug setting) is set to TRUE (the default is FALSE), then all inventory offers, even above the cap allowed by membership, go directly to inventory and do not count against the cap on offline messages.
| [[IM]] - [https://community.secondlife.com/blogs/entry/2559-group-limits-update-no-changes-for-basic-members/ Blog Post]
|-
||Length of a properly delivered email reply to an [[IM]]
| n/a
| {{no|1023 bytes or single-byte characters}}
| n/a
| n/a
|-
||Time after which a reply to an [[IM]] can be sent via email.
| {{no|when receiving the IM via email.}}
| {{no|5 days after receiving the offline IM via email.}}
| n/a
| [https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]
|-
||Time period for which [[IM|IMs]] are stored within Second Life.
| n/a
| {{no|31 days after receiving the [[IM]]}}
| [[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]
| n/a
|-
||Number of [[IM|IMs]] sent by an object within an hour
| n/a
| {{no|5000 per hour}}
| n/a
| n/a
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Shortcut key mappings
| n/a
| {{no|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| n/a
| [[All_keyboard_shortcut_keys]] and [http://community.secondlife.com/t5/English-Knowledge-Base/Keyboard-shortcuts/ta-p/1086557 the knowledge base]
|-
||Chat step length
| n/a
| {{no|127 bytes or single-byte characters}}
| n/a
| n/a
|-
||Wait time
| n/a
| {{no|3600 seconds (which is one hour)}}
| n/a
| n/a
|-
| Maximum steps data
| n/a
| {{no|1000 bytes}} of packed data; saving with more data returns the message "Gesture save failed. This gesture has too many steps. Try removing some steps, then save again." Shorter text, for example, will allow more steps.
| n/a
| n/a
|-
||Length of included assets
| n/a
| see sections for [[#Animation|animation]], [[#Sound|sound]]
| n/a
| n/a
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 50 for Basic members, 55 for Plus members, 80 for Premium members, 150 for Premium Plus members.
** After downgrading from a higher limit membership to a lower one, you may not join any new groups until you are a member of fewer than your current subscriptions's group limit. For example, if you downgrade from Premium (70 groups allowed) to Basic (42 groups allowed), you can't join any new groups until you're a member of fewer than 42 groups.
** 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.
* '''Maximum Age of a Group Notice:''' 14 days.

== [[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 number of accounts that an inventory item can be shared with at once:''' The limit is unknown, but tests show that it is more than 35. No documentation has been found. One third-party viewer developer says that the code doesn't seem to look for a limit. It just builds the list and sends it to each avatar individually.
* '''Maximum number of inventory items that can be contained in a prim:''' 10,000
* '''Maximum characters in an inventory item name:''' 63
* '''Maximum notecard line:''' None, but scripts can only read the first 1024 bytes (was 255 bytes before server version [https://releasenotes.secondlife.com/simulator/2021-10-25.565008.html 2021-10-25.565008]).
* '''Maximum notecard size:''' 65,536 bytes

* '''Number of items in the Library:''' 3,500 as of 2019-08-10
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.
* '''Maximum number of inventory items displayed in a single inventory folder:''' Several thousand. 
** This was discussed during [http://wiki.secondlife.com/wiki/Simulator_User_Group/Transcripts/2011.03.08] "the folder will load up to the limit number of items, and remaining ones won't show up in the viewer. you still own them, they aren't lost, but they will be hidden until the folder size is reduced."
** There is no specified limit for total avatar inventory, very large folders can be split.
** There was discussion in the Third Party Developers' UG (4/10/2015) meeting about new inventory and login problems from having large numbers of items in a single folder. AISv3 ''removed'' server-side limits on the number of items in a folder. Flat inventories are bad. No one is certain at what number of items in a folder cause a login problem. The fix is to clear the inventory cache (not the viewer cache) and log into a deserted, empty region then move inventory items into folders and sub-folders. - The problem appears at different a number of items depending on your computer and connection speed. Hopefully being on an empty region will give one enough edge to get logged in and do some corrective work before being dropped. If not, you will need to contact support for help. They will divide large folders into smaller groups so you can log in.

== [[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:''' Linden Concierge policy states a 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]]. However, the technical maximum limit is 35 characters, and exceptions to the concierge policy do exist (e.g [http://maps.secondlife.com/secondlife/Sandbox%20-%20Weapons%20testing%20%28no%20damag/128/128/2 Sandbox - Weapons testing (no damag] and [http://slurl.com/secondlife/X/128/128/24 X])
* '''Ban line height for "no entry" or "pay to access"''' (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation ''plus'' 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is '''explicitly banned by name''', the height is the parcel's ground elevation ''plus'' 5000 meters. On current viewers this is visible to the full extent.
* '''Maximum prims in a [[Land#Region|region]]:'''
** "Mainland / Full Region" and "Linden Homes / Full Region": 22,500
** Full Regions in private estates: 20,000 with an [https://community.secondlife.com/t5/Featured-News/Upgrade-Your-Full-Private-Region-to-30-000-Land-Impact-Today/ba-p/3086162 option for 30,000]
** Homestead: 5,000
** Openspace : 1,000
:: To check a region's capacity, use <tt>[[llGetEnv]]("region_max_prims")</tt>.
::''(Region types are as found in the General tab of World > About Land, or returned by ''<tt>llGetEnv("region_product_name")</tt>'')''
* '''Maximum auto return value''': Besides {{code|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 regions cannot be terraformed, including: Bay City regions, Boardman, Brown, De Haro, Horizons, Kama City regions, Nautilus City regions, Nova Albion regions, and Shermerville regions.
** [http://community.secondlife.com/t5/English-Knowledge-Base/Linden-Homes/ta-p/700103 Linden Homes] do not allow terraforming.
** 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, 255 meters by using a {{code|*.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 {{code|*.raw}} file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 20 estate managers, 500 allowed Residents, 63 allowed groups, and 750 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Maximum number of agents'''
** [https://second.life/eventregions Event Regions]: 175 agents
** Full region: 100 basic account users plus 10 additional available to premium accounts. (Typically set to 40 on mainland, 55 on Linden Homes regions, 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 (plus 5 additional available to premium accounts)
** [[Land#Openspace|Openspace]]: 10 (plus 2 additional available to premium accounts)
* '''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

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of vertices
| n/a
| {{no|65536 vertices per LOD}}
| per [[mesh]] - See [[Talk:Limits#Mesh_Limits|discussion page]]
| n/a
|-
||COLLADA file size
| n/a
| {{no|8 MB}}
| Maximum mesh asset size after compression, roughly equivalent to a 256 MB Raw COLLADA file.
| n/a
|-
||Bone influence weights per vertex
| n/a
| {{no|4}}
| n/a
| n/a
|-
||Bone influence weights per mesh
| n/a
| {{no|110}}
| some folk have reported needing to go as low as about 99 in rare cases
| n/a
|-
||Number of materials per mesh
| n/a
| {{no|8}}
| n/a
| n/a
|-
||Number of materials per face
| n/a
| {{no|1}}
| n/a
| n/a
|-
||Physics weight for a vehicle
| n/a
| {{no|32.0}}
| n/a
| n/a
|-
||Maximum number of triangles for Animesh
| n/a
| {{no|100,000}}
| Server uses estimated triangles (streaming cost calculated), not visual triangles.
| [[Animesh User Guide|Animesh_User_Guide]]
|}

===User Found Temporary Mesh Limits:===
''Because of an apparent bug in the importer stay within these limits.''
* 174,752 triangles, beyond which additional triangles will appear as holes.
* The 64k vertices per material is pre-empted by a limit of 21,844 triangles per material, which is presently reported as {{Jira|BUG-1001}}. (4/2014 - See [[Talk:Limits#Mesh_Limits|discussion page]])

:: The import process will continue making new materials beyond 8 x 21,844 (=174,752) triangles, but the extra triangles then get dropped by the limitation to 8 materials, causing holes in the resulting object. Over the 21,844-triangle limit, the vertex count will start to climb steeply, even with smooth shading, because the materials get highly interspersed. So the same vertices have to appear in multiple material lists. So, the moral of the story is to stay below 21,844 triangles per material, for now, if you want to avoid some unexpected effects.

::Since viewer release 3.8.4, processing of meshes in the Collada file that have faces assigned to more than 8 materials has changed. Instead of simply dropping the extra material faces, the uploader now creates a new object to accommodate them. The result is that the single mesh is divided into multiple objects (prims) in a linkset. Thus, the limitation to 8 materials is removed as far as input is concerned, but still applies to each of the resulting linked objects actually uploaded. As a consequence, it is now possible to upload a mesh with more than 174,752 triangles, although it will be divided into multiple objects.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.

== 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] = 231 − 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:''' 4096
** This used to be much higher, but is clamped in late model viewers.

== [[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

== [[Lag|Performance]] ==

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

'''*''' Only until your framerate reaches your monitor's refresh rate, after this point there will be very little benefit.

== [[Scripting]] == 

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls will keep running when you fly down or enter a no-script parcel. (If scripts are disabled in the region debug panel, they will not run at any height.)
* '''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 (that's a viewer limit and can be changed in the config file 'panel_script_ed.xml').
* '''Maximum script memory size (LSO)''' - 16384 bytes.
* '''Maximum script memory size ([[Mono]])''' - 65536 bytes (the maximum memory available to Mono scripts can be constrained via [[llSetMemoryLimit]]).
* '''Maximum memory for [[:Category:LSL LinksetData|Linkset data]]''' key/value pairs - 128 KiB
* '''Maximum memory for [[:Category:Experience Tools|Experience]]''' key/value pairs- 128 MiB
* '''Maximum active [[llListen|listeners]] per script''' - 65.
** '''Usable channel for each listener''' - ''min.'' -2147483648, ''max.'' 2147483647, including the following special channels: [[PUBLIC_CHANNEL]] ''and'' [[DEBUG_CHANNEL]].
* '''Maximum number of scripts that can be rezzed at once''' – 1,000. (Refer to [https://community.secondlife.com/knowledgebase/english/building-tips-r13/ Building Tips, by Jeremy Linden].)
* For specific scripting limits, look up calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==



{{KBtip|Second Life will accept sounds that are encoded following "[https://en.wikipedia.org/wiki/Compact_Disc_Digital_Audio CD Quality]" encoding presets present in many {{Abbr|DAW|Digital Audio Workstation}}s.}}

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Sound length
| n/a
| {{no|less than 30 seconds or precisely 1,323,000 samples}}
| The advice is typically to upload sounds less than 30.0 and that 29.99 seconds is fine. However if you do wish to be able upload sounds that are 30 seconds precisely then the .WAV file must have exactly 1,323,000 samples (44,100Hz * 30 seconds). Specifically anything above 1,323,000 samples fails to upload.
| '''[https://community.secondlife.com/knowledgebase/english/uploading-assets-r75/ Uploading Assets]'''
|-
||Bit depth
| n/a
| {{no|16 bit}}
| n/a
| n/a
|-
||Sample rate
| n/a
| {{no|44.100 kHz}}
| n/a
| n/a
|-
||Audio channels
| n/a
| {{no|1 channel (mono)}}
| Channels will be '''merged''' at upload time for dual-channel (stereo) audio.
| 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:

=== Second Life Viewer 3.6 ===

* '''Search > Classifieds thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (159×120 pixels)
* '''Search > Classifieds expanded > More Info''' - native aspect ratio
* '''Search > Destination Guide thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Destination Guide expanded''' - ~4:3 (159×120 pixels)
* '''Search > People''' - 1:1 (100×100 pixels)
* '''Search > Places expanded''' ~4:3 (159×120 pixels)
* '''Place Profile''' - ~3:2 (290×197 pixels)
* '''About Land > Options tab''' - ~4:3 (195×150 pixels)
* '''Profile > Picture''' - native aspect ratio; thumbnail cropped to 72×72 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Real world picture''' - native aspect ratio; thumbnail cropped to 45×45 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Picks thumbnail''' - ~16:9 (~516×~270 pixels as measured on screen; the ratio seems closer to 16:8.5)
* '''Profile > Pick expanded''' - Unknown as of 2022-11-13 (viewer 6.6.7.576223); the Pick image does not expand.

=== 1.x Series Viewers ===
(official Viewer up to 1.23.5, still used by some [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pixels)<ref>As of {{#time: r|2024-02-26T18:00:00}}, this seems to be one of the very few sizes supported by the [[Picture Service]].</ref>
* '''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.]]

=== All Viewers ===

* '''Maximum texture size''' - 2048×2048 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** 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 2048×2048.

* '''Minimum texture size''' - 4×4 pixels
** This means that there are ten possible image dimensions: 4, 8, 16, 32, 64, 128, 256, 512, 1024 & 2048 pixels, either horizontal or vertical.

* '''Texture resizing'''
** Uploaded textures will be resized to the dimensions above.
** Each dimension is resized independently (for instance, a 1024 x 999 image will be resized to 1024 x 1024).
** A dimension that is already a power of two will not be resized.
** The uploader “prefers” to round down rather than up. The threshold for rounding down/up is .75 of the distance between powers of two.
*** For example, given a dimension of x, if x / 512 is larger than 1.75, x will be resized to 1024, else 512.
*** Another example: If x / 256 is larger than 1.75, x will be resized to 512.

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

=== Notes ===
In general, 1 byte is enough to contain one character.<ref>Except in .NET-based applications, and those related to .NET development — which is the case of the SL viewer — which essentially use UTF-16 everywhere, i.e., every character is encoded in ''two'' bytes, not just one.</ref>

----
{{References}}

LlSetObjectMass

2025-01-07T17:34:27Z

Peter Stindberg: Changed source tag

'''llSetObjectMass()''' doesn't exist, however it is possible to adjust the mass of an object to what you want by adjusting the density of one large prim. Unfortunately it is a little tricky for multi-prim objects. Here is an example script which tries to adjust the total mass of a potentially multi-prim object plus a sitting avatar to a standard mass, no matter the avatar's size.
<syntaxhighlight lang="lsl2">
// adjust_root_density_to_hit_target_mass.lsl
//
// Put this script on the root prim of an object. When an avatar sits on it
// this script will try to adjust the mass of the root prim to make the total
// final mass of the object+avatar an known quantity no matter the avatar's mass.
//
// Note: this will only work of the root prim has more mass than the largest
// avatar expected to sit.
//

float DEBUG = FALSE;
float EXPECTED_AVATAR_MASS = 1.6; // mass of an "average" avatar
float prim_density = 1000.0;
float prim_volume = 1.0;
float obj_mass = 1.0;
float target_mass_with_sitter = 1.0;
float mass_of_other_parts = 1.0;
integer obj_num_prims = 1;
key prim_key;

measure_prim_volume()
{
// In order to do the adjustment math we need to know the effective volume
// of the root prim. Unfortunately this is not exposed in LSL, however we
// can measure it by adjusting the root prim's density and doing some math.
list material = llGetPhysicsMaterial();
prim_density = llList2Float(material, 3);
obj_mass = llGetObjectMass(llGetKey());
target_mass_with_sitter = obj_mass + EXPECTED_AVATAR_MASS;

float test_density = 2.0 * prim_density;
llSetPhysicsMaterial(DENSITY, 0.0, 0.0, 0.0, test_density);

// check to make sure our density setting took effect (it can fail if the prim is
// already near max density).
material = llGetPhysicsMaterial();
float actual_test_density = llList2Float(material, 3);
if (actual_test_density != test_density)
{
// density setting failed --> try a lower density instead
test_density = 0.5 * prim_density;
llSetPhysicsMaterial(DENSITY, 0.0, 0.0, 0.0, test_density);
}

// we can now compute prim_volume
float test_mass = llGetObjectMass(llGetKey());
prim_volume = (test_mass - obj_mass) / (test_density - prim_density);
if (DEBUG)
{
llOwnerSay("prim_volume=" + (string)(prim_volume));
}

// we also need to know the total mass of the non-root prims of the original object
mass_of_other_parts = test_mass - (prim_volume * test_density);

// restore original density
llSetPhysicsMaterial(DENSITY, 0.0, 0.0, 0.0, prim_density);
}

adjust_prim_density()
{
llSleep(1.0);
// When an avatar sits down the formula for mass becomes:
//
// obj_mass = avatar_mass + mass_of_other_parts + prim_density * prim_volume
//
// Let obj_mass equal target_mass_with_sitter and solve for density:
//
// prim_density = (target_mass_with_sitter - avatar_mass - mass_of_other_parts) / prim_volume
//

// adjust density to achieve target_mass_with_sitter
float mass = llGetObjectMass(prim_key);
float avatar_mass = mass - obj_mass;;
float target_density = (target_mass_with_sitter - (avatar_mass + mass_of_other_parts)) / prim_volume;
float MIN_DENSITY = 1.0;
if (target_density < MIN_DENSITY)
{
if (DEBUG)
{
llOwnerSay("extra_mass is too heavy");
}
target_density = MIN_DENSITY;
}
llSetPhysicsMaterial(DENSITY, 0.0, 0.0, 0.0, target_density);

// check to see how well we succeeded
if (DEBUG)
{
llOwnerSay( "original_mass=" + (string)(obj_mass) + " sit_mass=" + (string)(mass) + " avatar_mass=" + (string)(avatar_mass));
float final_mass = llGetObjectMass(prim_key);
float mass_error = target_mass_with_sitter - final_mass;
llOwnerSay("target_mass=" + (string)(target_mass_with_sitter) + ", after density adjustment: mass_error=" + (string)(mass_error));
}
}

reset_prim_density()
{
llSetPhysicsMaterial(DENSITY, 0.0, 0.0, 0.0, prim_density);
list materials = llGetPhysicsMaterial();
prim_density = llList2Float(materials, 3);
if (DEBUG)
{
float mass = llGetObjectMass(prim_key);
llOwnerSay("prim_density=" + (string)(prim_density) + " mass=" + (string)(mass));
}
}

default
{
state_entry()
{
// measure the object's initial properties
prim_key = llGetKey();
obj_num_prims = llGetNumberOfPrims();
obj_mass = llGetObjectMass(prim_key);
list material = llGetPhysicsMaterial();
prim_density = llList2Float(material, 3);

measure_prim_volume();
}

changed(integer change)
{
if (change & CHANGED_LINK)
{
integer num_prims = llGetNumberOfPrims();
if (num_prims != obj_num_prims)
{
if (DEBUG)
{
float mass = llGetObjectMass(prim_key);
float extra_mass = mass - obj_mass;
llOwnerSay("extra_mass=" + (string)(extra_mass));
}
adjust_prim_density();
}
else
{
reset_prim_density();
}
}
}
}
</syntaxhighlight>

Talk:LlReplaceSubString

2025-01-06T07:01:09Z

Peter Stindberg: /* About time! */

= About time! =
It's not rolled out fully yet. You can start using it in your code already now though, using Firestom's conditional compiles:

<syntaxhighlight lang="lsl">
#define no577942

#ifdef no577942
string llReplaceSubString(string str, string search, string replace, integer count) {
return llDumpList2String(llParseStringKeepNulls((str = "") + str, [search], []), replace);
}
#endif
</syntaxhighlight>

Once it's rolled out in your region, simply remove the #define statement.

— [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 08:31, 01 February 2023 (PDT)

: {{Mention|Peter Stindberg|p=,}} I had no idea this took 20 years to be implemented! I just learned his week that it existed, by 'naturally' using it — I cannot even remember what we used before this! — [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 14:41, 5 January 2025 (PST)

:: You still find code galore - even on this wiki - that uses user-defined functions for this. I have changed a few occurances, but there are certainly more. The Linden Lab implementation goes nicely beyond the most popular udf by providing the count variable, which is VERY useful!

:: — [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 23:01, 5 January 2025 (PST)

Talk:SLetanque

2025-01-04T15:43:27Z

Peter Stindberg: /* So, what exactly does this pair of scripts do? How to use them? */

== So, what exactly does this pair of scripts do? How to use them? ==

I'm well aware that {{Mention|Babbage Linden|p=}} is not part of LL any longer, and he left some of his legacy scripts around for us to interpret, but... what exactly is a ''SLetanque'' and how do we assemble it?

It seems that it's something that will launch an avatar (?) pushed with some force, but how does it work? Is the first script for an avatar attachment? (in that case, why does it only check for touching)?

Baffled. Puzzled.

— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 03:55, 4 January 2025 (PST)

: https://en.wikipedia.org/wiki/P%C3%A9tanque

: — [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 07:43, 4 January 2025 (PST)

LSL HTTP server

2024-12-24T22:29:58Z

Peter Stindberg: XMP-RPC is discontinued

{{LSL Header|ml=*}}

= Introduction =

This is the counterpart to [[llHTTPRequest]]. While [[llHTTPRequest]] enables [[Script|LSL scripts]] to request data from HTTP-accessible sources, HTTP-in enables outside sources to request data from [[Script|LSL scripts]] in Second Life. The key difference is that [[llHTTPRequest]] exchanges data when the script in SL wants; HTTP-in allows outside sources to determine when they need to communicate with [[Script|LSL scripts]] in SL.

Prior to HTTP-in, similar functionality could be achieved by [[HTTP Polling|polling]] with [[llHTTPRequest]], [[llEmail]] and [[:Category:LSL_XML-RPC|XML-RPC]]. All three are cumbersome and the latter two have serious scalability bottlenecks, with XML-RPC being discontinued altogether since June 2023.

It is important to note that [[LSL HTTP server|LSL HTTP servers]] cannot use [[llSetContentType]] with [[CONTENT_TYPE_HTML]] for an [[llHTTPResponse]] except in very limited circumstances. See [[#Other_Limitations|Other Limitations]] for details.

'''This section forms the [[:Category:LSL HTTP#Understanding_LSL_HTTP_Communications | Incoming]] HTTP pipeline.'''

= Uses =

* Easily get data from [[Script|LSL scripts]] to outside viewers, [[Script|LSL scripts]] or servers.
** Web front end for a visitor counter or other statistics accumulator.
* Easily get data into [[Script|LSL scripts]] from outside viewers, [[Script|LSL scripts]] or servers.
** A store with a web front end that communicates to an in-world object to exchange L$ and inventory items.
** Inworld game for which an external program handles the primary game logic that needs to manipulate inworld items.
* HUD UI when used with [[llSetContentType]]. See [[HTML HUD Demo]].
Gory Technical Details follow. Or jump straight to the [[LSL_http_server/examples | Script Examples]].

= Script API =

== Events ==
* '''[[http_request|http_request(key id, string method, string body)]]'''
: Event triggered when an URL is hit:
:* id is unique to this request
:* Supported methods are <code>"GET"</code>, <code>"POST"</code>, <code>"PUT"</code>, <code>"DELETE"</code>
:* body: The body of the request.
: Event also triggered with response to [[llRequestURL]] and [[llRequestSecureURL]]
:* id matches the key returned by [[llRequestURL]] or [[llRequestSecureURL]]
:* method == [[URL_REQUEST_GRANTED]] for success, [[URL_REQUEST_DENIED]] for failure to get an URL
:* body is the public URL. If unable to get a public URL body will be empty.
* '''[[Changed|changed(integer change)]]'''
:* [[CHANGED_REGION_START]]: New [[changed]] [[event]] triggered on region startup.
:* [[CHANGED_REGION]]: New [[changed]] [[event]] triggered when crossing regions or teleporting. Please read [[CHANGED_REGION]] for more info.
:* [[CHANGED_TELEPORT]]: New [[changed]] [[event]] triggered when the avatar teleports. Please read [[CHANGED_TELEPORT]] for more info.

== Functions ==
{{LSL Function/Head
|func_id=345|func_sleep=0.0|func_energy=10.0
|func=llRequestURL
|func_desc=Requests one HTTP:// url for use by the script. The [[http_request]] [[event]] is triggered with the result of the request. HTTP-in uses port 12046.
|return_type=key|return_text=that is the handle used for identifying the result in the [[http_request]] [[event]].
|func_footer
|caveats=none
}}
{{LSL Function/Head
|func_id=346|func_sleep=0.0|func_energy=10.0
|func=llRequestSecureURL
|func_desc=Requests one HTTPS:// (SSL) url for use by the script. The [[http_request]] [[event]] is triggered with the result of the request. HTTPS-in uses port 12043.
|return_type=key|return_text=that is the handle used for identifying the result in the [[http_request]] [[event]].
|func_footer
|caveats=none
}}
{{LSL Function/Head
|func_id=347|func_sleep=0.0|func_energy=10.0
|func=llReleaseURL
|p1_type=string|p1_name=url|p1_desc=URL to release
|func_desc=Releases the specified URL, it will no longer be usable.
|func_footer
|caveats=none
}}
{{LSL Function/Head
|func_id=348|func_sleep=0.0|func_energy=10.0
|func=llHTTPResponse
|p1_type=key|p1_name=request_id|p1_desc=A valid HTTP request key
|p2_type=integer|p2_name=status|p2_desc=[http://en.wikipedia.org/wiki/List_of_HTTP_status_codes HTTP_Status] (200, 400, 404, etc)
|p3_type=string|p3_name=body|p3_desc=Contents of the response.
|func_desc=Responds to {{LSLP|request_id}} with {{LSLP|status}} and {{LSLP|body}}.
|func_footer=The response need not be made inside the [[http_request]] [[event]] but if it does not happen in a timely fashion the request will time out (within 25 seconds).
|caveats=none
}}
{{LSL Function/Head
|func_id=344|func_sleep=0.0|func_energy=10.0
|func=llGetFreeURLs
|return_type=integer|return_text=that is the number of available URLs.
|caveats=none
}}
{{LSL Function/Head
|func_id=349|func_sleep=0.0|func_energy=10.0
|func=llGetHTTPHeader
|p1_type=key|p1_name=request_id|p1_desc=A valid HTTP request key
|p2_type=string|p2_name=header|p2_desc=Lower case header value name
|return_type=string|return_text=that is the value for {{LSLP|header}} for {{LSLP|request_id}}.
|func_footer=Returns an empty [[string]] if the {{LSLP|header}} is not found or if the headers can no longer be accessed. Headers can only be accessed before [[llHTTPResponse]] is called and with-in the first 30 seconds after the [[http_request]] [[event]] is queued.

====Generated Headers====
These headers are automatically generated by the simulator, they were not actually sent by the requesting client. They supply information about the request to make parsing easier.

Sample URL: [https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/foo/bar?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;|/foo/bar|2={{String|x-path-info}} = {{String|/foo/bar}}}}?{{HoverTextStyle|style=color:red;|1=arg=gra|2={{String|x-query-string}} = {{String|1=arg=gra}}}}]

{{{!}} class="lltable" border="1"
! header
! description
! example
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-script-url"
{{!}} The base url, as originally received from [[llRequestURL]]/[[llRequestSecureURL]]
{{!}} <nowiki>https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322</nowiki>
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-path-info"
{{!}} Any trailing path information from the requested url
{{!}} /foo/bar
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-query-string"
{{!}} Any query arguments, the text past the first "?" in the url
{{!}} arg=gra
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "x-remote-ip"
{{!}} IP address of the host that made the request
{{!}}
{{!}}}

====Common Headers====

{{{!}} class="lltable" border="1"
! header
! description
! example
{{!}}-
{{!}} style="white-space: nowrap;" {{!}} "user-agent"
{{!}} The user-agent header as reported by the requester
{{!}}
{{!}}}

====[[llHTTPRequest]] Headers====
{{LSL_Constants/HTTP_Headers|lower-case=*}}
|caveats=none
}}

= URL Lifetime Limitations =
* URLs are '''temporary'''!
* URLs will be lost in the following cases, all detectable by the script events listed with them.
** On object derez/rez: [[on_rez]]
** On script save/reset: ''[[default]] [[state_entry]] (trickier in multi-state [[Script|LSL scripts]])
** On region cross or TP(attachments): [[changed]] {{LSLGC|Events|event}}, [[CHANGED_REGION]] and [[CHANGED_TELEPORT]]. Testing the latter event, it has been found that teleports within a region DO NOT cause a URL to be lost, therefore you do not need to request a new URL on [[CHANGED_TELEPORT]], because [[CHANGED_REGION]] will handle a teleport to a different region. If you choose to request a URL after a teleport, it is recommended to release the old URL to be sure you don't have too many used. (Stone Tremont Aug 8th 2010)
** On region restart: [[changed]] [[event]], flag [[CHANGED_REGION_START]]
* When urls are 'lost' it means that all public urls for that script are gone, new ones will need to be requested and the new urls will '''not''' resemble the old ones.
* Maintaining persistent URLs will require building or using an external service similar to how [http://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] services work for tying domain names to dynamic IP addresses.

Contributed HTTP-in URL mapping implementations and services:
* A Dynamic DNS service running on Google App Engine (contributed as an example) can be found in the forums [http://wiki.secondlife.com/wiki/User:Darien_Caldwell/HTTP-DNS here].
* Yet another one, running on GAE, with password protected and private domains. http://wiki.secondlife.com/wiki/Public_Object_DNS
* The [http://www.silverday.net/sqndns SilverDay ObjectDNS] is an easy to use dns-mapping-service with many configurable options (password protection, write protection, etc.) and an optional web-interface. The [[Script|LSL scripts]] are available here on the wiki (LSL-Script Library/[[Silverday ObjectDNS]]).

= Resource Limitations =
* There are a limited number of URLs available in each [[region]], split by land ownership exactly like prim limits.
** Use [[llGetFreeURLs]] to get the exact number of available URLs for the script.
** The number of allowed URLs is the same as the number of allowed [[prim|prims]] on the [[Land#Parcel|parcel]] the [[object]] is over.
**: ''Object owner does not matter, all objects over a [[Land#Parcel|parcel]] will use the resource pool for that [[Land#Parcel|parcel]].''
**: ''Like [[prim|prims]], all the [[Land#Parcel|parcels]] owned by the same owner and in the same [[region]] share the same pool of resources.''
**: ''If you have two [[Land#Parcel|parcels]] in a [[region]] that each support 100 URLs, then you could use all 200 in object(s) on a single [[Land#Parcel|parcel]].''
** The [[region]]'s [[object]] bonus factor does not apply to available URLs.
**: ''If a [[Land#Parcel|parcel]] has a max of 300 [[prim|prims]] in a [[region]] with a 2x bonus factor there will only be 150 urls allowed.''
* Each resident has their own unique pool of available URLs with a max of 38 URLs per resident.
** This is 1 per attachment point, but all 38 could be used by a single attachment for example.
* Vehicles are special and lazily moved to resident pools by the following logic:
** Any [[object]] that has a resident sitting on it is a 'vehicle'
** Vehicles will use the url resources from the [[Land#Parcel|parcel]] they are over until the cross a [[Land#Parcel|parcel]] border.
**: ''Specifically this prevents anyone from breaking your vending machine by sitting on it and making it a 'vehicle'.''
** When any [[object]] using URL resources with a resident sitting on it crosses a [[Land#Parcel|parcel]] boundary the resources will switch to the first sitting resident with enough resources. If no sitting agents have enough resources then the resources from the [[Land#Parcel|parcel]] being moved onto will be used. If even then there are not enough resources to use then the vehicle will be blocked from moving.
**: ''In short we do everything we can to find a pool to host the resources needed by the vehicle, but will block movement if we can't.''
* Parcel Sale: When a [[Land#Parcel|parcel]] is sold such that it changes the total available URLs in the [[region]] for either resident (seller or buyer) such that more URLs are being used than are available some objects will be returned.
** The objects returned will be from youngest [[object]] to oldest [[object]] of those using URLs in each category in order of [[object]] category: Temporary, Other, Group, Owner, Selected/Sat upon.
**: ''The '''only''' time objects are possibly returned is when [[Land#Parcel|parcels]] change owner, and only if more resources are being used than allowed.''
**: ''We return youngest temporary objects before older temporary objects before younger 'other' (owned by non-group, non-[[Land#Parcel|parcel]]-owner) objects etc.''

= Other Limitations =
* Size of the body of requests on the '''[[:Category:LSL HTTP#Understanding_LSL_HTTP_Communications | Incoming pipeline]]''' will be [[limit]]ed to 2k [[bytes]], and cannot currently be changed.
* Size of headers of requests will be limited to 255 bytes per header, not total.
* The size of responses to requests is not currently limited, but this is subject to review during testing.
* By default the content type of the returned data is always <code>"text/plain; charset=utf-8"</code>, this however can be changed via [[llSetContentType]] for all subsequent responses via [[llHTTPResponse]].
* There is a cap of 64 in flight requests per script. This is based on the maximum number of pending [[event|events]] in LSL. After hitting the 64 request limit, the simulator cap server returns <code>{{String|503 Service Unavailable}}</code> to the inbound request.
* ''We may throttle the rate we accept hits at the CAP server level as well. This is possible, but has not yet been decided.''
* HTML can be used to in-client browser, including media on a prim, with some restrictions. See [[llSetContentType]] and [[CONTENT_TYPE_HTML]] for further details.
* If making a parser, remember that you should probably restrict access to only Linden Lab HTML URLs as to not have your bandwith stolen. See [[Simulator_IP_Addresses]] for details.
* It is important to note that 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.

= Links =
* [[LSL_http_server/examples | Script Examples]]
* [[LSL_http_server/design | Design Document]]
* Design Jira:{{jira|SVC-1086}}

{{LSLC|HTTP}}
{{LSLC|Communications}}

LlGiveAgentInventory

2024-12-19T16:04:29Z

Peter Stindberg: Added example after testing it on ADITI

{{LSL_Function
|inject-2=
{{LSL_Function/give|target|inventory|sim=*|uuid=false|insert=list of items}}
|func_id=|func_sleep=3.0|func_energy=10.0|return_type=integer
|func=llGiveAgentInventory
|p1_type=key|p1_name=agent|p1_desc=agent to receive inventory offer.
|p2_type=string|p2_name=folder|p2_desc=destination folder name to use.
|p3_type=list|p3_name=inventory|p3_desc=list of inventory items to give to the agent
|p4_type=list|p4_name=options|p4_desc=list of options for inventory transfer.
|func_footnote
|return_text
|func_desc=Gives '''inventory''' items to '''target''', creating a new '''folder''' to put them in.
|spec=
* The target must be an avatar in the same region as the sending object, or must have recently been in the region.
* Places the inventory items in a newly created folder in the avatar's inventory (even if there is a folder by the same name, a new one is created).
* If a path of root folders has been specified, the function will ensure that those folders exist but will not recreate them if they already exist.
|constants={{LSL Constants/Transfer Inventory}}

{{LSL Constants/Transfer Errors}}

|caveats
|examples=
In this example, the object inventory needs to contain two objects named ''Item 1'' and ''Item 2''. The destination folder will be named ''Destination Folder'' and will be created under the main folder ''Objects'', in the sub-folder ''Subfolder''. If ''Subfolder'' does not exist, it will be created.

If the object gets touched for a second time, the sub-folder ''Subfolder'' will '''not''' be duplicated, however the destination folder ''Destination Folder'' '''will''' be duplicated.

If ''Item 1'' and/or ''Item 2'' do not exist, the transfer will silently fail partially or completely.
<syntaxhighlight lang="lsl2">default
{
touch_start(integer total_number)
{
llGiveAgentInventory(llDetectedKey(0), "Destination Folder", ["Item 1","Item 2"], [0, "Objects|Subfolder"] );
}
}</syntaxhighlight>
|helpers
|also_functions={{LSL DefineRow||[[llGiveInventory]]}}
{{LSL DefineRow||[[llGiveInventoryList]]}}
|also_events={{LSL DefineRow||[[changed]]}}
|also_tests
|also_articles
|notes|cat1=Inventory
|cat2
|cat3
|cat4
}}

Breedables Guide For Second Life

2024-12-07T09:42:13Z

Peter Stindberg: Keep the headline structure clean please.

{{help|Misc=*}}

'''NOTE:''' This is a wiki. Everyone can add to it. The information below comes from volunteers as well as developers and enthusiasts of a specific system. The information provided should best be regarded as advertisement and is '''not''' routinely fact-checked. Fact-checks happen more or less randomly and are done by volunteers.

= Breedable Animals Guide For Second Life =

One of the most popular{{Citation needed|reason=Source needed for this statement.|date=March 2024}} pastimes in Second Life is the caring for, feeding and breeding of virtual animals in Second Life. Over the years these animals have developed and a whole community of breeders and traders has emerged. Some players become so good at breeding animals that they are able to earn linden dollar profits from the buying and selling of them.

= Breedables List =

== ADS Company ==

====Snuffles====

[[File:Snuffles_site_promo.png|thumb|alt=breedable animal second life|[http://www.goldtokens.net/index.php?title=Snuffles Snuffles] is an example of another breedable animal in Second Life.]]

Most aptly described as squirrel type creatures, [http://www.snufflesbreedables.com Snuffles] are a breedable animal in Second Life with a thriving secondary market for the breeding and trading of Snuffle Burrows.

====Shubbies====

[http://www.goldtokens.net/index.php?title=Shubbies Shubbies] are a breedable pet that act as companions in the [http://www.goldtokens.net/index.php?title=Fish_Hunt Fish Hunt]

== AEON PETS ==

offer a variety of breedable pets for all ages.
Happy Hamster,
Happy Elephants,
Exotics,
E-Cats,
Silly Ghost,
Amazing Spiders,
Patchworx,
Crazy Eggs,
Silly Mice,
Pengi,
and much more.

Visit the [http://maps.secondlife.com/secondlife/Fama/42/79/1001 AEON Pets Mainstore]

== Amaretto Breedables==
[[File:AmarettoLogo.jpg|300px|right]]
====Amaretto Horses====
Amaretto Ranch Breedables released Amaretto Breedable Horses in Second Life in September of 2010 and very quickly became a leader in the breedables industry. Amaretto Breedable Horses are an interactive breedable that you can pet, ride, race and breed based on genetics. Amaretto Breedable Horses have a large secondary market for breeding, studding, racing, selling, trading and much more. The Amaretto Horses Main Store is located here

[http://maps.secondlife.com/secondlife/Horses%20and%20Ponie%20Pals/247/32/21 Horse Main Store]

====Amaretto K-9s====
Amaretto Ranch Breedables released its 2nd breedable, Amaretto Breedable K-9s in Second Life in August of 2011. Amaretto Breedable K-9s are an interactive breedable that you can walk, play with and breed based on genetics. Amaretto Breedable K-9s also have a secondary market for breeding, studding, selling and trading.
The Amaretto K-9s Main Store is located here.

[http://maps.secondlife.com/secondlife/K9s%20and%20Birds/16/19/23 K-9 Main Store]

====Amaretto Barnyard Birds====
Amaretto Ranch Breedables released its 3rd breedable, Amaretto Barnyard Birds in Second Life in May of 2012. Amaretto Barnyard Birds are an interactive breedable that you can hold and breed based on genetics. Amaretto Barnyard Birds have a secondary market for breeding, studding, selling and trading.
The Amaretto Barnyard Bird Store is located here.
[http://maps.secondlife.com/secondlife/K9s%20and%20Birds/16/19/23 Amaretto Ranch Breedables Barnyard Bird Main Store]
[http://amarettobreedables.com/ Amaretto Ranch Breedables Main Website]

== BattleBeast Breedables ==
* Website: [http://www.battlebeastbreedables.com]

==== BattleBeast Dragons ====

BattleBeast Breedables Dragons were released in Spring of 2012, as the first breedable in Second Life where battle (aka combat) can affect the dragons' genetic offspring. BattleBeast Breedables dragons have enjoyed a wide following in Second Life with people who like to breed, collect, fly, ride, and Role-Play (RP) with them.
* Dragons Main Store: [http://maps.secondlife.com/secondlife/Dragons/226/167/23]

==== BattleBeast Kitsune ====

BattleBeast Breedables Kitsune are a new project from BattleBeast Breedables, which was released in Spring of 2017, bringing the mythical and magical Japanese fox ("kitsune") to Second Life. In their many-tailed forms, and steeped in mythos, lore and legend, the Kitsune can be your guides in Questing to earn Wisdom and other rewards throughout SL.
* Kitsune Main Store: [http://maps.secondlife.com/secondlife/Dragons/26/65/37]

== BioBreeds ==
[[File:BioBreeds_Logo.jpg|300px|right]]
* Website: [http://BioBreeds.com]
* BioBreeds Main Store: [http://maps.secondlife.com/secondlife/BioBreeds/75/179/32]

==== BioBreeds Dogs ====

BioBreeds Dogs are realistically created breedable dogs in Second Life. BioBreeds launched in February of 2011 and prides itself on being a leader in innovation in the breedable community. The dogs respond to commands, breed, hunt and interact with BioBreeds horses. The Biobreeds genetic system mirrors real life. BioBreeds also provides a system for the owners to create unique attachments. BioBreeds users have built a strong secondary market, selling not only their dogs with unique traits, but also attachments, snacks, pets and other dog related items. You can view the existing traits on the website: [http://biobreeds.com/Traitopia.aspx]

==== BioBreeds Pal Ponies ====

BioBreeds Ponies were released in November of 2011. BioBreeds Ponies are a realistic looking ridable pony that follows commands, breeds and interacts with its owners and BioBreeds Dogs. Like the BioBreeds Dogs, an owner can create their own unique attachments. Its genetic system, and the rare traits that it produces, has spawned a strong secondary market for its breeders. You can view the existing traits on the website: [http://www.biobreeds.com/Traitopia.aspx?breed=Pony]

==== BioBreeds Exotics ====

BioBreeds Exotics introduced fantasy into the BioBreeds line of breedables. The ridable Exotics follow commands, breed, interact with their owners and also with Biobreeds Dogs. Like the BioBreeds Dogs, an owner can create their own unique attachments. Using the same genetic system as the BioBreeds Ponies, an owner can choose to crossbreed the Exotics with BioBreeds Ponies, infusing the Ponies traits into the genetic system of the Exotics, and vice versa. You can view the existing traits on the website: [http://biobreeds.com/Traitopia.aspx?breed=Exotic]

==== BioBreeds Wild Ones ====

BioBreeds continued its expansion of available types of animals in February 2014 releasing "Wild Ones." The Wild Ones are realistic versions of a wolf, fox, coyote and tiger. Like the BioBreeds Dogs, an owner can create their own unique attachments. The Wild Ones also have unique and applicable animations, poses and user commands. As with other BioBreeds products, they can be bred for specific traits. You can view the existing known traits here: [http://biobreeds.com/Traitopia.aspx?breed=Wolf]

== Buildables (Robots)==

[http://mybuildables.com/ Buildables]Those of you that have taken part in the old form of breedables, will LOVE what the Buildables system is capable of! This is the ONLY system on SL that has the ability to "breed"(build) DIFFERENT styles of "Buildables" (bots) with over 50 types of bots and too many variants to count! At the time of this posting there are almost 600 kinds of bots! And with the HIGH QUALITY designs and amazing textures that make the bots come to life, there is a bot for ANY genre!

Another very attractive point is their AFFORDABILITY. This is one of the most affordable breedable to maintain. Unlike other breedables that require food to keep them alive, if you get the unlimited power and unlimited oil (1000L each, so 2000L investment) that's all you need to fuel/"feed" your bots. A small investment that fuels/feeds your all your bots. You can have 1 or a million bots and if you get the unlimited power and oil it will feed/fuel all your bots FOREVER. After that the only other expenses you will incur are the building pods (the mega pod is 499L for up to 25 builds) for the bots to build new bots and crates (25 crates for 100L) to crate up rezzed bots.

[https://buildablesblog.wordpress.com/ Buildables Blog]

Official Buildables Vendor [http://maps.secondlife.com/secondlife/Light%20Heaven/196/16/23 here].

== Digital Farm System (DFS) ==

[[File:DFS Logo -With Bevel.png|thumb|alt=breedables second life|[https://www.digitalfarmsystem.com] [http://maps.secondlife.com/secondlife/DFS/126/149/24 Official Digital Farming System (DFS) Sim]]]

[https://www.digitalfarmsystem.com] Digital Farm System (DFS), established October 3rd, 2016, is a farming simulation system, which allows players to experience the depths of farming life by planning their farming goals, breeding different types of farm animals, and grow their own crops, plants and trees. The DFS community uses the system in various ways to further enhance their (SL) experiences.

Many DFS users conduct trades with other farmers and users in marketplaces and roles playing structures. This further supports the role-playing experience and their individual or group goals for DFS. DFS creators offer a wide range of content, from Mayan farmers to post-apocalyptic earth.

DFS has resizable equipment to fit avatars of any sizes. Several of the equipment is sold in regular and tiny size, which is intended for [[ToddleeDoos]], but can also be used to accommodate smaller space or multiple equipment needs.

The system is constantly being developed and promises timely updates and fix system issues quickly to guarantee everything runs smoothly.

Your avatar must be at least 30 days old to use the Digital Farm System and to visit the DFS Main store.

More information can be found on the [[DFS - Digital Farm System]] promotional wiki page, and at the [http://maps.secondlife.com/secondlife/DFS/126/149/24 Official Digital Farming System (DFS) Sim].

== EVO Breeding Co ==

[http://Evosl.com EVO Portal]
Come check EVO Breeding CO at our mainstore SIM Remood United - http://maps.secondlife.com/secondlife/REMOOD%20UNITED/92/226/25

===GOFishin===

Fishing system, with contests and different rarities of fishes and other prizes. You can also win breedable fishes.

===GoFishin Breedables===

Some of the fishes you catch on GoFishin game, can be bred to get other fishes.

===Fairies===

Fairies are one of our most know pet, they have pretty buildings, they fly and feed, give prizes, and lay eggs to give you new faes. At the moment we have around 500 different faes, and we are in a constant production of new ones.

===Arborea===

Arborea is for all the botanics of second life. You drop the seed on the vase, you water them and wait for them to bloom and polynise each other.

===Shoals===

Shoals came as an addition to the "sea" department of pets. They have their own clam lab which you can have in your living room filled with water, or you can empty it and have it on the water. They grow and reproduce, but sometimes they are closed and you will need to play, and open them in order to get prizes.

===Hammies===

Hammies are cute little rodents, they were updated to a mesh shape, and rescripted recently (April 2016) they hop around their stump, eating their petmix. There's different colour coats, ears, eyes and tails.

===Yukas===

Yukas are our most recent project, they are not yet out, but will be pretty soon. Yukas are little mamoths which you'll have the opurtunity to unfroze and care for. They will be super fun. Keep tuned.

== Fawns ==

[http://www.fawns.org/ Fawns Breedables] feature dueling, racing, hand-painted unique coats and so much more. You can walk around with your Fawns, hold them in your arms, at your side, etc.

Online market for Fawns: [http://www.fawns.org/market Fawns Market].

Visit the [http://maps.secondlife.com/secondlife/PayHUD/150/134/23 Fawns Official SLURL].

[[File:Fennux-and-Fawns.jpg]]

== Fennux ==

The [http://www.fennux.com/ Fennux] are breedable pets that feature dueling, crafting of adapted Fennux with rare coats, community events and more. You can walk your Fennux, wear them on your shoulder, carry them around, feed them, breed them, and even duel your friends (or enemies). Come see The Fennux in-world by visiting the main sim location today!

Online market for Fennux: [http://www.fennux.com/market Fennux Market].

Visit the [http://maps.secondlife.com/secondlife/PayHUD/115/163/23 Fennux Official SLURL].

== JingJings ==

[[File:JINGJING Breedables powered by Teulu Breedables 512.jpg|thumb|alt=breedables second life|[http://jingjing.info] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/42/183/27 Official JingJing's powered by Teulu Breedables Main Sim]are JingJings first landed on the grid for sale to public on October 1st, 2012 owned by 亗ღ Twstd ღ亗™ (twstd.ruggles). Change of Ownership happened on September 24, 2023 to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs are the first Animesh breedable on Second Life Grid Currently with many more to come.)]]

[http://jingjing.info] First landed on Second Life Grid on October 1st, 2012 owned by 亗ღ Twstd ღ亗™ (twstd.ruggles) who now sold the company to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) who owns Teulu Breedables. First animesh breedables on grid in March 2020 followed by Teulu Horses in November 2022 then our latest Teulu Dogs in April 2023. Teulu Breedables can be attached to avatar center to be worn on avatar as a pets or to ride them!

Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/42/183/27].

== KittyCatS ==

[[File:Square_kitty.png|thumb]]

[https://www.kittycats.ws/forum/ KittyCatS] are highly interactive cats that can be petted, cuddled and held. Owners and non-owners alike can interact with the adorable cats. KittyCatS are the first{{fact}} to take breeding OUTSIDE of SL with their [https://kittycats.ws/online/ KittyCatS Cattery]. The Cattery is is a section of their website thus making breeding available to internet browsing devices, such as iPads.

KittyCatS won the Avi Choice Award 2012 for Favorite Breedable in Second Life.

== Krafties ==

[http://krafties.com Krafties] are fantasy based creatures with an interesting backstory. They are the center of a free, in depth MMORPG type game in which the players can battle creatures and other players, catch new creatures and then combine them with many varieties of elemental souls, craft and enchant powerful items, and much much more. There are many species of creatures to choose from, all with different strengths and weaknesses. Visit the Krafties Island to start the journey for free.

[[File:Krafties-Screenshot2.jpg]]

== Kreatures ==

[[File:Kreatures_Breedable_Pets_498x444.jpg|thumb|alt=breedables second life|[http://www.kreatures.net/ Kreatures] are one of many varieties of breedable pets in Second life. (Fennux and Fawns are also featured in this image.)]]

[http://www.kreatures.net/ Kreatures] is a breedable pet game that officially launched April 2022. The creators of this also produced The Fennux and Fawns. Kreatures feature bear cubs, lion cubs and wolf pups. The different species can be crossbred so you can pass, for example, a tiger striped coat from a lion onto a bear or a wolf. Kreatures will require food to breed, just like The Fennux. Kreatures can be attached to various attachment points to enable holdable pets, running pets, rideable pets and more!

Visit the [http://slurl.com/secondlife/Kreatures/ Official Kreatures Sim].

[[File:Kreatures-Limited-Editions.jpg]]

== Meeroos ==

[http://www.worldofmeeroos.com/ Meeroos] are a fantasy animal somewhat resembling a meerkat, with an elaborate backstory of their mythological origins. The first chapter of the story introduced the ground-based diurnal Meeroos, the second chapter introduces nocturnal Meeroos who emerged from caverns.

== Mossms ==

[[File:Mossm.jpg|text-top|frame|200px]]

[http://mossms.com/ Mossms] are fun and zany space creatures that have come to our world to gather certain resources that appear to be in short supply or no longer exist in their space communities.

In order to mate, Mossms must return to space. Of course, space travel and the courting ritual both require resources. In other words, your Mossms will need to work for a living into a [http://www.infosafe.fr security safe]!

Mossms are incredibly interactive. Mossms know when an avatar is near and will respond to the avatar's presence. In addition, Mossms interact with other Mossms as well as their surroundings.

Mossms have a complex DNA system. Each newly born Mossm possesses genetics from its earliest ancestors. In addition, space exploration can cause genetic anomalies. The end result is an extensive array of possible breeds just waiting to be discovered.

Mossms are new to SL, arriving on scene in mid 2013 and are the first breedable to make use of several new SL technologies including: mesh, static pathfinding, keyframe movement and ray cast.

== oYo Breedables ==

oYo started in 2014 to bring their breedables to SL from InWorldz.

Main shop: http://maps.secondlife.com/secondlife/Majestic%20Paradise/154/129/23
Web Page: http://oyobreedables.org/

They are offerering 3 types of breeds at the moment:

====Dodos====

[http://oyobreedables.org/index.php/dodo The dodos] were the first breed oYo offered. You can attach them for riding if they are grown up or sit on them.

====Fuzzy Buzzies====

[http://oyobreedables.org/index.php/fuzzy These little pets] look like a mix of gremlins and teddy bears. They are sweet and love to play and eat sweets. A set of toys is available for them to play and collect happiness poynts to get more toys.

====Pigs====

[http://oyobreedables.org/index.php/pig Pigs] complete the list of breeds. Female pigs send out a free food after 30 days.

== Ozimals ==

====Bunnies====
Ozimals' flagship Bunny product was officially released on Jan 9 2010. The product was the first successful breedable product to rely upon real genetic principles as part of its gameplay.

====Pufflings====
Pufflings are small stylized birds which can be raised and bred for rare traits using similar genetic breeding principles as the other Ozimals product, bunnies.

== Papillon Breedables ==

[http://papillon.wikidot.com Papillons] are a collection of breedable butterflies, dragonflies, fireflies and plants. All the various insects and plants interact, along with accessories, to create an interdependent ecosystem. There is also an optional Adventure Game that can be played with the flutters.

==Pet Peddlers==

[http://petpeddlersl.com/ Pet Peddlers] was released in Dec. 2010 as the first shape changing breedable{{Fact}}. All of Pet Peddles fish and seahorses (released Spring 2013) look like the real life version of that species. Pet Peddlers uses a unique predator system that allows you to load a food bowl and feed your predators with unwanted or breed out fish and seahorses. At present there are over 150 current fish breeds and 26 current seahorses. Pet Peddlers also has fishing game in beta now that will be released in the near future.

== Stray Cats Breedable ==

[http://slstraycats.com/ Stray Cats] are breedable cats in Second Life. They come in many shapes, features, breeds and colors, including a fantasy line of 'cats'. Animations include pathfinding. Once they are finished with their breedings, they automatically become permanent pets and do not require feedings anymore. They are safe to keep in inventory too at any time. They never die.

Visit our home sim sometime and learn more: http://maps.secondlife.com/secondlife/Bast/180/40/3500

== Teulu Breedables ==

[[File:Teulu Breedables Logo.jpg|thumb|alt=breedables second life|[https://portal7.teulubreedables.com] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/75/70/27 Official Teulu Breedables Sim]are The First Animesh Breedables in Second Life. (Furbs, Teulu Horses and Teulu Dogs are available on the Second Life Grid Currently with many more to come.)]]

[https://portal7.teulubreedables.com] are the first{{Citation needed|reason=Source for statement required.|date=March 2024}} Animesh Breedable on second life grid. Furbs was first released in March 2020 followed by Teulu Horses in November 2022 then followed by Teulu Dogs in April 2023. Teulu Breedables can be attached to the avatar center and be worn, or are rideable.

Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/75/70/27 Official Teulu Breedables Sim].

===Ludens powered by Teulu Breedables===

[[File:Ludens powered by Teulu Breedables 512.jpg|thumb|alt=breedables second life|https://ludens.world/] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/208/213/27 Official Ludens powered by Teulu Breedables Main Sim]are Ludens first landed on the grid for Beta June 26th 2023 sale to the public on September 28th, 2023 owned by Mystia (mystery.doge). Change of Ownership happened on March 15, 2024, to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs & JingJings (not Animesh) the first Animesh breedable on Second Life Grid Currently with many more to come.)]]

[https://ludens.world/] is an Animesh Breedable on the second life grid. Ludens first landed on the grid for Beta June 26th 2023 sale to the public on September 28th, 2023 owned by Mystia (mystery.doge). Change of Ownership happened on March 15, 2024, to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs & JingJings (not Animesh) the first Animesh breedable on Second Life Grid Currently with many more to come.)
Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/208/213/27 Official Teulu Breedables Sim].

== Unique Breedables ==

[[File:Unique_breedables.jpg|thumb|]]

[http://www.ub-monkeys.de Unique Breedables] is a company dedicated to creating breedables that are fun and unique, with a fresh approach to how breeding in Second Life works. They listen to their customers and staff and welcome input on how they can improve the overall experience of breeding animals. Their goal is to innovate and improve upon the breeding and the community in order to foster a more enjoyable environment for anyone to join.
So if you are a breeding pro, or a new breeder just looking to get into the game, they have what you need.

= External Articles & Sites =

Lawsuits between Ozimals and Amaretto have been in progress since 2010. Wikipedia has an article on [http://en.wikipedia.org/wiki/Amaretto_Ranch_Breedables,_LLC_v._Ozimals,_Inc. Amaretto Ranch Breedables, LLC v. Ozimals, Inc.]

Talk:Resident

2024-11-30T15:01:45Z

Peter Stindberg:

== Fun after-the-fact fact ==

One thing I just realised today was that 'resident' includes the sound 'rez' in it.

In other words: 'resident' is ''someone who '[[:Category:LSL_Rez|rezzes]]' objects in-world'' (or whose avatar gets rezzed in-world, which is also common jargon in SL).

This is purely coincidental, of course, but nevertheless fun — especially 20 years after the designation was created!

Technically speaking, with an American English twist, we ought to be called 're'''zz'''idents' (two 'zz' to make the analogy more obvious), which, of course, is a homophone of 'resident'.

— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 06:48, 30 November 2024 (PST)

: 😲

: --[[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 07:01, 30 November 2024 (PST)

Breedables Guide For Second Life

2024-11-26T08:10:58Z

Peter Stindberg: /* DFS - Digital Farm System */ The wiki is neither a brochure nor a SEO text. Aged 8 years it is not really "new" anymore either. Removed the hyperbole, and stripped it to info only.

{{help|Misc=*}}

'''NOTE:''' This is a wiki. Everyone can add to it. The information below comes from volunteers as well as developers and enthusiasts of a specific system. The information provided should best be regarded as advertisement and is '''not''' routinely fact-checked. Fact-checks happen more or less randomly and are done by volunteers.

= Breedable Animals Guide For Second Life =

One of the most popular{{Citation needed|reason=Source needed for this statement.|date=March 2024}} pastimes in Second Life is the caring for, feeding and breeding of virtual animals in Second Life. Over the years these animals have developed and a whole community of breeders and traders has emerged. Some players become so good at breeding animals that they are able to earn linden dollar profits from the buying and selling of them.

= Breedables List =

== ADS Company ==

====Snuffles====

[[File:Snuffles_site_promo.png|thumb|alt=breedable animal second life|[http://www.goldtokens.net/index.php?title=Snuffles Snuffles] is an example of another breedable animal in Second Life.]]

Most aptly described as squirrel type creatures, [http://www.snufflesbreedables.com Snuffles] are a breedable animal in Second Life with a thriving secondary market for the breeding and trading of Snuffle Burrows.

====Shubbies====

[http://www.goldtokens.net/index.php?title=Shubbies Shubbies] are a breedable pet that act as companions in the [http://www.goldtokens.net/index.php?title=Fish_Hunt Fish Hunt]

== AEON PETS ==

offer a variety of breedable pets for all ages.
Happy Hamster,
Happy Elephants,
Exotics,
E-Cats,
Silly Ghost,
Amazing Spiders,
Patchworx,
Crazy Eggs,
Silly Mice,
Pengi,
and much more.

Visit the [http://maps.secondlife.com/secondlife/Fama/42/79/1001 AEON Pets Mainstore]

== Amaretto Breedables==
[[File:AmarettoLogo.jpg|300px|right]]
====Amaretto Horses====
Amaretto Ranch Breedables released Amaretto Breedable Horses in Second Life in September of 2010 and very quickly became a leader in the breedables industry. Amaretto Breedable Horses are an interactive breedable that you can pet, ride, race and breed based on genetics. Amaretto Breedable Horses have a large secondary market for breeding, studding, racing, selling, trading and much more. The Amaretto Horses Main Store is located here

[http://maps.secondlife.com/secondlife/Horses%20and%20Ponie%20Pals/247/32/21 Horse Main Store]

====Amaretto K-9s====
Amaretto Ranch Breedables released its 2nd breedable, Amaretto Breedable K-9s in Second Life in August of 2011. Amaretto Breedable K-9s are an interactive breedable that you can walk, play with and breed based on genetics. Amaretto Breedable K-9s also have a secondary market for breeding, studding, selling and trading.
The Amaretto K-9s Main Store is located here.

[http://maps.secondlife.com/secondlife/K9s%20and%20Birds/16/19/23 K-9 Main Store]

====Amaretto Barnyard Birds====
Amaretto Ranch Breedables released its 3rd breedable, Amaretto Barnyard Birds in Second Life in May of 2012. Amaretto Barnyard Birds are an interactive breedable that you can hold and breed based on genetics. Amaretto Barnyard Birds have a secondary market for breeding, studding, selling and trading.
The Amaretto Barnyard Bird Store is located here.
[http://maps.secondlife.com/secondlife/K9s%20and%20Birds/16/19/23 Amaretto Ranch Breedables Barnyard Bird Main Store]
[http://amarettobreedables.com/ Amaretto Ranch Breedables Main Website]

== BattleBeast Breedables ==
* Website: [http://www.battlebeastbreedables.com]

==== BattleBeast Dragons ====

BattleBeast Breedables Dragons were released in Spring of 2012, as the first breedable in Second Life where battle (aka combat) can affect the dragons' genetic offspring. BattleBeast Breedables dragons have enjoyed a wide following in Second Life with people who like to breed, collect, fly, ride, and Role-Play (RP) with them.
* Dragons Main Store: [http://maps.secondlife.com/secondlife/Dragons/226/167/23]

==== BattleBeast Kitsune ====

BattleBeast Breedables Kitsune are a new project from BattleBeast Breedables, which was released in Spring of 2017, bringing the mythical and magical Japanese fox ("kitsune") to Second Life. In their many-tailed forms, and steeped in mythos, lore and legend, the Kitsune can be your guides in Questing to earn Wisdom and other rewards throughout SL.
* Kitsune Main Store: [http://maps.secondlife.com/secondlife/Dragons/26/65/37]

== BioBreeds ==
[[File:BioBreeds_Logo.jpg|300px|right]]
* Website: [http://BioBreeds.com]
* BioBreeds Main Store: [http://maps.secondlife.com/secondlife/BioBreeds/75/179/32]

==== BioBreeds Dogs ====

BioBreeds Dogs are realistically created breedable dogs in Second Life. BioBreeds launched in February of 2011 and prides itself on being a leader in innovation in the breedable community. The dogs respond to commands, breed, hunt and interact with BioBreeds horses. The Biobreeds genetic system mirrors real life. BioBreeds also provides a system for the owners to create unique attachments. BioBreeds users have built a strong secondary market, selling not only their dogs with unique traits, but also attachments, snacks, pets and other dog related items. You can view the existing traits on the website: [http://biobreeds.com/Traitopia.aspx]

==== BioBreeds Pal Ponies ====

BioBreeds Ponies were released in November of 2011. BioBreeds Ponies are a realistic looking ridable pony that follows commands, breeds and interacts with its owners and BioBreeds Dogs. Like the BioBreeds Dogs, an owner can create their own unique attachments. Its genetic system, and the rare traits that it produces, has spawned a strong secondary market for its breeders. You can view the existing traits on the website: [http://www.biobreeds.com/Traitopia.aspx?breed=Pony]

==== BioBreeds Exotics ====

BioBreeds Exotics introduced fantasy into the BioBreeds line of breedables. The ridable Exotics follow commands, breed, interact with their owners and also with Biobreeds Dogs. Like the BioBreeds Dogs, an owner can create their own unique attachments. Using the same genetic system as the BioBreeds Ponies, an owner can choose to crossbreed the Exotics with BioBreeds Ponies, infusing the Ponies traits into the genetic system of the Exotics, and vice versa. You can view the existing traits on the website: [http://biobreeds.com/Traitopia.aspx?breed=Exotic]

==== BioBreeds Wild Ones ====

BioBreeds continued its expansion of available types of animals in February 2014 releasing "Wild Ones." The Wild Ones are realistic versions of a wolf, fox, coyote and tiger. Like the BioBreeds Dogs, an owner can create their own unique attachments. The Wild Ones also have unique and applicable animations, poses and user commands. As with other BioBreeds products, they can be bred for specific traits. You can view the existing known traits here: [http://biobreeds.com/Traitopia.aspx?breed=Wolf]

== Buildables (Robots)==

[http://mybuildables.com/ Buildables]Those of you that have taken part in the old form of breedables, will LOVE what the Buildables system is capable of! This is the ONLY system on SL that has the ability to "breed"(build) DIFFERENT styles of "Buildables" (bots) with over 50 types of bots and too many variants to count! At the time of this posting there are almost 600 kinds of bots! And with the HIGH QUALITY designs and amazing textures that make the bots come to life, there is a bot for ANY genre!

Another very attractive point is their AFFORDABILITY. This is one of the most affordable breedable to maintain. Unlike other breedables that require food to keep them alive, if you get the unlimited power and unlimited oil (1000L each, so 2000L investment) that's all you need to fuel/"feed" your bots. A small investment that fuels/feeds your all your bots. You can have 1 or a million bots and if you get the unlimited power and oil it will feed/fuel all your bots FOREVER. After that the only other expenses you will incur are the building pods (the mega pod is 499L for up to 25 builds) for the bots to build new bots and crates (25 crates for 100L) to crate up rezzed bots.

[https://buildablesblog.wordpress.com/ Buildables Blog]

Official Buildables Vendor [http://maps.secondlife.com/secondlife/Light%20Heaven/196/16/23 here].

== [[DFS - Digital Farm System]] ==

[[File:DFS Logo -With Bevel.png|thumb|alt=breedables second life|[https://www.digitalfarmsystem.com] [http://maps.secondlife.com/secondlife/DFS/126/149/24 Official Digital Farming System (DFS) Sim]]]

[https://www.digitalfarmsystem.com] Digital Farm System (DFS), established October 3rd, 2016, is a farming simulation system, which allows players to experience the depths of farming life by planning their farming goals, breeding different types of farm animals, and grow their own crops, plants and trees. The DFS community uses the system in various ways to further enhance their (SL) experiences.

Many DFS users conduct trades with other farmers and users in marketplaces and roles playing structures. This further supports the role-playing experience and their individual or group goals for DFS. DFS creators offer a wide range of content, from Mayan farmers to post-apocalyptic earth.

DFS has resizable equipment to fit avatars of any sizes. Several of the equipment is sold in regular and tiny size, which is intended for [[ToddleeDoos]], but can also be used to accommodate smaller space or multiple equipment needs.

The system is constantly being developed and promises timely updates and fix system issues quickly to guarantee everything runs smoothly.

Your avatar must be at least 30 days old to use the Digital Farm System and to visit the DFS Main store.

Visit the [http://maps.secondlife.com/secondlife/DFS/126/149/24 Official Digital Farming System (DFS) Sim].

== EVO Breeding Co ==

[http://Evosl.com EVO Portal]
Come check EVO Breeding CO at our mainstore SIM Remood United - http://maps.secondlife.com/secondlife/REMOOD%20UNITED/92/226/25

===GOFishin===

Fishing system, with contests and different rarities of fishes and other prizes. You can also win breedable fishes.

===GoFishin Breedables===

Some of the fishes you catch on GoFishin game, can be bred to get other fishes.

===Fairies===

Fairies are one of our most know pet, they have pretty buildings, they fly and feed, give prizes, and lay eggs to give you new faes. At the moment we have around 500 different faes, and we are in a constant production of new ones.

===Arborea===

Arborea is for all the botanics of second life. You drop the seed on the vase, you water them and wait for them to bloom and polynise each other.

===Shoals===

Shoals came as an addition to the "sea" department of pets. They have their own clam lab which you can have in your living room filled with water, or you can empty it and have it on the water. They grow and reproduce, but sometimes they are closed and you will need to play, and open them in order to get prizes.

===Hammies===

Hammies are cute little rodents, they were updated to a mesh shape, and rescripted recently (April 2016) they hop around their stump, eating their petmix. There's different colour coats, ears, eyes and tails.

===Yukas===

Yukas are our most recent project, they are not yet out, but will be pretty soon. Yukas are little mamoths which you'll have the opurtunity to unfroze and care for. They will be super fun. Keep tuned.

== Fawns ==

[http://www.fawns.org/ Fawns Breedables] feature dueling, racing, hand-painted unique coats and so much more. You can walk around with your Fawns, hold them in your arms, at your side, etc.

Online market for Fawns: [http://www.fawns.org/market Fawns Market].

Visit the [http://maps.secondlife.com/secondlife/PayHUD/150/134/23 Fawns Official SLURL].

[[File:Fennux-and-Fawns.jpg]]

== Fennux ==

The [http://www.fennux.com/ Fennux] are breedable pets that feature dueling, crafting of adapted Fennux with rare coats, community events and more. You can walk your Fennux, wear them on your shoulder, carry them around, feed them, breed them, and even duel your friends (or enemies). Come see The Fennux in-world by visiting the main sim location today!

Online market for Fennux: [http://www.fennux.com/market Fennux Market].

Visit the [http://maps.secondlife.com/secondlife/PayHUD/115/163/23 Fennux Official SLURL].

== JingJings ==

[[File:JINGJING Breedables powered by Teulu Breedables 512.jpg|thumb|alt=breedables second life|[http://jingjing.info] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/42/183/27 Official JingJing's powered by Teulu Breedables Main Sim]are JingJings first landed on the grid for sale to public on October 1st, 2012 owned by 亗ღ Twstd ღ亗™ (twstd.ruggles). Change of Ownership happened on September 24, 2023 to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs are the first Animesh breedable on Second Life Grid Currently with many more to come.)]]

[http://jingjing.info] First landed on Second Life Grid on October 1st, 2012 owned by 亗ღ Twstd ღ亗™ (twstd.ruggles) who now sold the company to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) who owns Teulu Breedables. First animesh breedables on grid in March 2020 followed by Teulu Horses in November 2022 then our latest Teulu Dogs in April 2023. Teulu Breedables can be attached to avatar center to be worn on avatar as a pets or to ride them!

Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/42/183/27].

== KittyCatS ==

[[File:Square_kitty.png|thumb]]

[https://www.kittycats.ws/forum/ KittyCatS] are highly interactive cats that can be petted, cuddled and held. Owners and non-owners alike can interact with the adorable cats. KittyCatS are the first{{fact}} to take breeding OUTSIDE of SL with their [https://kittycats.ws/online/ KittyCatS Cattery]. The Cattery is is a section of their website thus making breeding available to internet browsing devices, such as iPads.

KittyCatS won the Avi Choice Award 2012 for Favorite Breedable in Second Life.

== Krafties ==

[http://krafties.com Krafties] are fantasy based creatures with an interesting backstory. They are the center of a free, in depth MMORPG type game in which the players can battle creatures and other players, catch new creatures and then combine them with many varieties of elemental souls, craft and enchant powerful items, and much much more. There are many species of creatures to choose from, all with different strengths and weaknesses. Visit the Krafties Island to start the journey for free.

[[File:Krafties-Screenshot2.jpg]]

== Kreatures ==

[[File:Kreatures_Breedable_Pets_498x444.jpg|thumb|alt=breedables second life|[http://www.kreatures.net/ Kreatures] are one of many varieties of breedable pets in Second life. (Fennux and Fawns are also featured in this image.)]]

[http://www.kreatures.net/ Kreatures] is a breedable pet game that officially launched April 2022. The creators of this also produced The Fennux and Fawns. Kreatures feature bear cubs, lion cubs and wolf pups. The different species can be crossbred so you can pass, for example, a tiger striped coat from a lion onto a bear or a wolf. Kreatures will require food to breed, just like The Fennux. Kreatures can be attached to various attachment points to enable holdable pets, running pets, rideable pets and more!

Visit the [http://slurl.com/secondlife/Kreatures/ Official Kreatures Sim].

[[File:Kreatures-Limited-Editions.jpg]]

== Meeroos ==

[http://www.worldofmeeroos.com/ Meeroos] are a fantasy animal somewhat resembling a meerkat, with an elaborate backstory of their mythological origins. The first chapter of the story introduced the ground-based diurnal Meeroos, the second chapter introduces nocturnal Meeroos who emerged from caverns.

== Mossms ==

[[File:Mossm.jpg|text-top|frame|200px]]

[http://mossms.com/ Mossms] are fun and zany space creatures that have come to our world to gather certain resources that appear to be in short supply or no longer exist in their space communities.

In order to mate, Mossms must return to space. Of course, space travel and the courting ritual both require resources. In other words, your Mossms will need to work for a living into a [http://www.infosafe.fr security safe]!

Mossms are incredibly interactive. Mossms know when an avatar is near and will respond to the avatar's presence. In addition, Mossms interact with other Mossms as well as their surroundings.

Mossms have a complex DNA system. Each newly born Mossm possesses genetics from its earliest ancestors. In addition, space exploration can cause genetic anomalies. The end result is an extensive array of possible breeds just waiting to be discovered.

Mossms are new to SL, arriving on scene in mid 2013 and are the first breedable to make use of several new SL technologies including: mesh, static pathfinding, keyframe movement and ray cast.

== oYo Breedables ==

oYo started in 2014 to bring their breedables to SL from InWorldz.

Main shop: http://maps.secondlife.com/secondlife/Majestic%20Paradise/154/129/23
Web Page: http://oyobreedables.org/

They are offerering 3 types of breeds at the moment:

====Dodos====

[http://oyobreedables.org/index.php/dodo The dodos] were the first breed oYo offered. You can attach them for riding if they are grown up or sit on them.

====Fuzzy Buzzies====

[http://oyobreedables.org/index.php/fuzzy These little pets] look like a mix of gremlins and teddy bears. They are sweet and love to play and eat sweets. A set of toys is available for them to play and collect happiness poynts to get more toys.

====Pigs====

[http://oyobreedables.org/index.php/pig Pigs] complete the list of breeds. Female pigs send out a free food after 30 days.

== Ozimals ==

====Bunnies====
Ozimals' flagship Bunny product was officially released on Jan 9 2010. The product was the first successful breedable product to rely upon real genetic principles as part of its gameplay.

====Pufflings====
Pufflings are small stylized birds which can be raised and bred for rare traits using similar genetic breeding principles as the other Ozimals product, bunnies.

== Papillon Breedables ==

[http://papillon.wikidot.com Papillons] are a collection of breedable butterflies, dragonflies, fireflies and plants. All the various insects and plants interact, along with accessories, to create an interdependent ecosystem. There is also an optional Adventure Game that can be played with the flutters.

==Pet Peddlers==

[http://petpeddlersl.com/ Pet Peddlers] was released in Dec. 2010 as the first shape changing breedable{{Fact}}. All of Pet Peddles fish and seahorses (released Spring 2013) look like the real life version of that species. Pet Peddlers uses a unique predator system that allows you to load a food bowl and feed your predators with unwanted or breed out fish and seahorses. At present there are over 150 current fish breeds and 26 current seahorses. Pet Peddlers also has fishing game in beta now that will be released in the near future.

== Stray Cats Breedable ==

[http://slstraycats.com/ Stray Cats] are breedable cats in Second Life. They come in many shapes, features, breeds and colors, including a fantasy line of 'cats'. Animations include pathfinding. Once they are finished with their breedings, they automatically become permanent pets and do not require feedings anymore. They are safe to keep in inventory too at any time. They never die.

Visit our home sim sometime and learn more: http://maps.secondlife.com/secondlife/Bast/180/40/3500

== Teulu Breedables ==

[[File:Teulu Breedables Logo.jpg|thumb|alt=breedables second life|[https://portal7.teulubreedables.com] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/75/70/27 Official Teulu Breedables Sim]are The First Animesh Breedables in Second Life. (Furbs, Teulu Horses and Teulu Dogs are available on the Second Life Grid Currently with many more to come.)]]

[https://portal7.teulubreedables.com] are the first{{Citation needed|reason=Source for statement required.|date=March 2024}} Animesh Breedable on second life grid. Furbs was first released in March 2020 followed by Teulu Horses in November 2022 then followed by Teulu Dogs in April 2023. Teulu Breedables can be attached to the avatar center and be worn, or are rideable.

Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/75/70/27 Official Teulu Breedables Sim].

===Ludens powered by Teulu Breedables===

[[File:Ludens powered by Teulu Breedables 512.jpg|thumb|alt=breedables second life|https://ludens.world/] Visit us at the [http://maps.secondlife.com/secondlife/Urban%20Paradise/208/213/27 Official Ludens powered by Teulu Breedables Main Sim]are Ludens first landed on the grid for Beta June 26th 2023 sale to the public on September 28th, 2023 owned by Mystia (mystery.doge). Change of Ownership happened on March 15, 2024, to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs & JingJings (not Animesh) the first Animesh breedable on Second Life Grid Currently with many more to come.)]]

[https://ludens.world/] is an Animesh Breedable on the second life grid. Ludens first landed on the grid for Beta June 26th 2023 sale to the public on September 28th, 2023 owned by Mystia (mystery.doge). Change of Ownership happened on March 15, 2024, to Siâи ĐaяΚƑµƦץ тєµℓµ (welshgoddess) to add to her Teulu Breedables business. (Furbs, Teulu Horses, and Teulu Dogs & JingJings (not Animesh) the first Animesh breedable on Second Life Grid Currently with many more to come.)
Visit the [http://maps.secondlife.com/secondlife/Urban%20Paradise/208/213/27 Official Teulu Breedables Sim].

== Unique Breedables ==

[[File:Unique_breedables.jpg|thumb|]]

[http://www.ub-monkeys.de Unique Breedables] is a company dedicated to creating breedables that are fun and unique, with a fresh approach to how breeding in Second Life works. They listen to their customers and staff and welcome input on how they can improve the overall experience of breeding animals. Their goal is to innovate and improve upon the breeding and the community in order to foster a more enjoyable environment for anyone to join.
So if you are a breeding pro, or a new breeder just looking to get into the game, they have what you need.

= External Articles & Sites =

Lawsuits between Ozimals and Amaretto have been in progress since 2010. Wikipedia has an article on [http://en.wikipedia.org/wiki/Amaretto_Ranch_Breedables,_LLC_v._Ozimals,_Inc. Amaretto Ranch Breedables, LLC v. Ozimals, Inc.]

User talk:Soap Frenzy

2024-11-19T18:49:20Z

Peter Stindberg: Created page with "Welcome to the wiki. -- ~~~~"

Welcome to the wiki.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 10:49, 19 November 2024 (PST)

LlIsFriend

2024-11-15T18:03:20Z

Peter Stindberg: Bugfix in 2024-11-12.11802108395

{{LSL Function
|inject-2={{LSL Function/uuid|uuid|sim=*}}
|func=llIsFriend
|sort=IsFriend
|func_id=0|func_sleep=0.0|func_energy=10.0
|return_type=integer
|return_subtype=boolean
|p1_type=key|p1_name=agent_id
|func_desc=
|return_text=that is [[TRUE]] if {{LSLP|agent_id}} and the owner of the [[prim]] the [[script]] is in are friends, otherwise [[FALSE]].
|func_footnote
|spec=

* If the prim is owned by a group this function behaves identically to [[llSameGroup]]
* This function will return [[FALSE]] under the following edge cases:
** If neither the owner, nor the target agent are in the region.
** If the agent_id does not specify an agent.

|caveats=
* You are not your own friend.
* <s>Currently a faulty result is given if the owner of the object the script resides in has moved to an adjacant region shortly before the query (see [https://feedback.secondlife.com/scripting-bugs/p/llisfriend-fails-if-owner-is-not-present-on-region llIsFriend fails if owner is not present on region] on Canny). First noticed on server version 2024-01-19.7590161929, last checked (and still not fixed) in server version 2024-09-13.10853867644.</s> Fixed in server version 2024-11-12.11802108395.

|constants
|examples=
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT, 95, PI, 10);
}

sensor(integer count)
{
integer index;
for (index = 0; index < count; ++index)
{
string is_is_not = " is NOT ";
if (llIsFriend(llDetectedKey(index)))
{
is_is_not = " is ";
}
llSay(0, llDetectedName(index) + is_is_not + "a friend.");
}
}
}

</syntaxhighlight>
|helpers
|also_functions=
{{LSL DefineRow||[[llDetectedGroup]]}}
{{LSL DefineRow||[[llSameGroup]]}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Avatar
|cat2=Group
|haiku
|cat3
|cat4
}}

User talk:Coffee Pancake

2024-11-04T19:26:05Z

Peter Stindberg: Created page with "Welcome! --~~~~"

Welcome!

--[[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 11:26, 4 November 2024 (PST)

User talk:Quinn Elara

2024-10-08T04:41:13Z

Peter Stindberg: Created page with "Welcome! So the wiki does not allow for a name change? How peculiar. -- ~~~~"

Welcome! So the wiki does not allow for a name change? How peculiar.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 21:41, 7 October 2024 (PDT)

Talk:LlSetRemoteScriptAccessPin

2024-10-07T10:14:45Z

Peter Stindberg: /* The PIN is a characteristic of the primitive, right? */

== The PIN is a characteristic of the primitive, right? ==

I have a few questions —

# The PIN is one of the many properties assigned to the prim where the script runs, is that correct? (like hover text set via [[llSetText]]) In other words, you can reset every script you wish inside the prim, or remove them, or give the prim away, restart the current region, whatever, so long as no script changes the PIN again (or sets it to zero), it will remain forever set to the original value?
## Yes, but it is instanced. It will not survive shift-drag, but will survive Take Copy, re-rezzing, transfer, etc. It appears to be the same rules as texture animations or particles as a prim property.
# When making a copy of a prim which had its PIN set (but assume that its inventory is now empty), the PIN persists?
##Taking a copy yes, shift-drag no.
# What if the original creator changes permissions and/or ownership (i.e., sells or transfers the original prim without retaining the right to copy it), will the PIN also persist? Again, I'm not considering the many levels of checks required for [[LlRemoteLoadScriptPin]] to actually ''work'', just what happens with the PIN in those edge cases.
##The use-case of this function is updating scripts externally, after transfer to another. While I don't have underlying knowledge of the pin in no-modify situations, I do know because product updaters exist and work, that the pin survives transfer to another.
# When another script does a [[LlRemoteLoadScriptPin]], will it affect scripts in child prims as well, or only those on the root prims?
##Pins are not inherited, a child prim needs its own pin set.
# What happens when two prims, each with their own PIN, are linked together? Will the PIN of the new root prim prevail, while the other prims will get their PINs reset? Or will each prim retain their individual PINs?
##Rearranging link orders has no effect on pins. Each link has its own settable pin. This includes when it becomes unlinked, and when it becomes the link/root of another linkset with different pins.
Well, there are more questions like these, and I have in mind several different scenarios, all of which have the same assumption: that the PIN is really a property of the prim, not something somehow written to the script's "memory" (or state, or whatever).

I suppose that one might be able to save the PIN in the KVP store, these days, and thus provide a way to guarantee that a prim has persistent PIN storage. A script ''expecting'' the PIN to be set might be able to check first if the PIN is not zero, but, if it is, attempt to load it from a well-known key/value pair on the KVP store, and set it using [[LlSetRemoteScriptAccessPin]], if needed.
#It may be wiser to just set the pin after getting a handshake, must like a chat channel tends to be, if you fear the pin may have been reset.
— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 23:38, 22 September 2024 (PDT)

:Added responses after testing these myself. I do wish they'd survive shift-drag, but for products I can avoid this by putting a no copy item in my copyable products so they cant shift-drag. -Paz

::Interweaving your answers with Gwyneth's the way you did is considered bad practice in a wiki environment.
::-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 03:14, 7 October 2024 (PDT)

Talk:LlSetRemoteScriptAccessPin

2024-10-07T10:14:10Z

Peter Stindberg: /* The PIN is a characteristic of the primitive, right? */

== The PIN is a characteristic of the primitive, right? ==

I have a few questions —

# The PIN is one of the many properties assigned to the prim where the script runs, is that correct? (like hover text set via [[llSetText]]) In other words, you can reset every script you wish inside the prim, or remove them, or give the prim away, restart the current region, whatever, so long as no script changes the PIN again (or sets it to zero), it will remain forever set to the original value?
## Yes, but it is instanced. It will not survive shift-drag, but will survive Take Copy, re-rezzing, transfer, etc. It appears to be the same rules as texture animations or particles as a prim property.
# When making a copy of a prim which had its PIN set (but assume that its inventory is now empty), the PIN persists?
##Taking a copy yes, shift-drag no.
# What if the original creator changes permissions and/or ownership (i.e., sells or transfers the original prim without retaining the right to copy it), will the PIN also persist? Again, I'm not considering the many levels of checks required for [[LlRemoteLoadScriptPin]] to actually ''work'', just what happens with the PIN in those edge cases.
##The use-case of this function is updating scripts externally, after transfer to another. While I don't have underlying knowledge of the pin in no-modify situations, I do know because product updaters exist and work, that the pin survives transfer to another.
# When another script does a [[LlRemoteLoadScriptPin]], will it affect scripts in child prims as well, or only those on the root prims?
##Pins are not inherited, a child prim needs its own pin set.
# What happens when two prims, each with their own PIN, are linked together? Will the PIN of the new root prim prevail, while the other prims will get their PINs reset? Or will each prim retain their individual PINs?
##Rearranging link orders has no effect on pins. Each link has its own settable pin. This includes when it becomes unlinked, and when it becomes the link/root of another linkset with different pins.
Well, there are more questions like these, and I have in mind several different scenarios, all of which have the same assumption: that the PIN is really a property of the prim, not something somehow written to the script's "memory" (or state, or whatever).

I suppose that one might be able to save the PIN in the KVP store, these days, and thus provide a way to guarantee that a prim has persistent PIN storage. A script ''expecting'' the PIN to be set might be able to check first if the PIN is not zero, but, if it is, attempt to load it from a well-known key/value pair on the KVP store, and set it using [[LlSetRemoteScriptAccessPin]], if needed.
#It may be wiser to just set the pin after getting a handshake, must like a chat channel tends to be, if you fear the pin may have been reset.
— [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 23:38, 22 September 2024 (PDT)

Added responses after testing these myself. I do wish they'd survive shift-drag, but for products I can avoid this by putting a no copy item in my copyable products so they cant shift-drag. -Paz

:Interweaving your answers with Gwyneth's the way you did is considered bad practice in a wiki environment.
:-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 03:14, 7 October 2024 (PDT)

LlSetRemoteScriptAccessPin

2024-10-07T10:12:23Z

Peter Stindberg: Added caveat about not being able to find out of a script pin has been set (aka as "The day I broke the CasperLet Updates of a customer")

{{LSL Function
|func_id=252|func_sleep=0.2|func_energy=10.0
|func=llSetRemoteScriptAccessPin
|p1_type=integer|p1_name=pin|p1_desc=zero disables (ie [[llRemoteLoadScriptPin]] will fail), non-zero enables.
|func_desc=Allows a prim to have scripts remotely loaded via [[llRemoteLoadScriptPin]] when it is passed the correct pin and the prim is set mod.
|func_footnote
|spec
|caveats=*A prim has only one pin for remotely loading scripts.
**By changing the pin, a script can deny other scripts the ability to load scripts into the prim.
***This could result in unintentionally breaking a products ability to be updated by an upstream creator.
***This can be used to intentionally stop an upstream creator from updating a product.
***There is no way to find out wether a script pin has been set by another script in the prim. If the prim contains scripts from other developers, the safe approach is to assume a script pin has been set by an upstream creator.
|constants
|examples
|helpers
|also_functions={{LSL DefineRow||[[llRemoteLoadScriptPin]]|Used to load a script into a remote prim}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Script
|cat2
|cat3
|cat4
|}}

LlIsFriend

2024-10-03T08:22:34Z

Peter Stindberg: Caveat about a bug in the function as confirmed by Maestro Linden in March

{{LSL Function
|inject-2={{LSL Function/uuid|uuid|sim=*}}
|func=llIsFriend
|sort=IsFriend
|func_id=0|func_sleep=0.0|func_energy=10.0
|return_type=integer
|return_subtype=boolean
|p1_type=key|p1_name=agent_id
|func_desc=
|return_text=that is [[TRUE]] if {{LSLP|agent_id}} and the owner of the [[prim]] the [[script]] is in are friends, otherwise [[FALSE]].
|func_footnote
|spec=

* If the prim is owned by a group this function behaves identically to [[llSameGroup]]
* This function will return [[FALSE]] under the following edge cases:
** If neither the owner, nor the target agent are in the region.
** If the agent_id does not specify an agent.

|caveats=
* You are not your own friend.
* Currently a faulty result is given if the owner of the object the script resides in has moved to an adjacant region shortly before the query (see [https://feedback.secondlife.com/scripting-bugs/p/llisfriend-fails-if-owner-is-not-present-on-region llIsFriend fails if owner is not present on region] on Canny). First noticed on server version 2024-01-19.7590161929, last checked (and still not fixed) in server version 2024-09-13.10853867644.

|constants
|examples=
<syntaxhighlight lang="lsl2">
default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT, 95, PI, 10);
}

sensor(integer count)
{
integer index;
for (index = 0; index < count; ++index)
{
string is_is_not = " is NOT ";
if (llIsFriend(llDetectedKey(index)))
{
is_is_not = " is ";
}
llSay(0, llDetectedName(index) + is_is_not + "a friend.");
}
}
}

</syntaxhighlight>
|helpers
|also_functions=
{{LSL DefineRow||[[llDetectedGroup]]}}
{{LSL DefineRow||[[llSameGroup]]}}
|also_tests
|also_events
|also_articles
|notes
|cat1=Avatar
|cat2=Group
|haiku
|cat3
|cat4
}}

LlGetAttached

2024-09-11T21:15:19Z

Peter Stindberg: Replaced source with syntaxhighlight

{{LSL_Function
|func_id=224|func_sleep=0.0|func_energy=10.0
|func=llGetAttached|return_type=integer|return_subtype=attach_point
|func_footnote
|func_desc
|Return_text=the object is attached to or {{HoverText|zero|0}} if it is either not attached or is pending detachment.
|spec
|caveats
|constants={{LSL_Constants_Attachment}}
|examples=
<syntaxhighlight lang="lsl2">default
{
attach(key id)
{
if(id)//it's attached
{
if(llGetAttached() != ATTACH_LHAND)
{
llOwnerSay("Please attach me only to the left hand");
llRequestPermissions(id, PERMISSION_ATTACH);
}
}
}
run_time_permissions(integer a)
{
if(a & PERMISSION_ATTACH)
llDetachFromAvatar();
}
}</syntaxhighlight>
This snippet will make a prim invisible when attached, but visible when rezzed unattached
<syntaxhighlight lang="lsl2">
on_rez(integer p)
{
// !llGetAttached() has the value 0 when attached, and 1 when unattached
llSetAlpha( !llGetAttached(), ALL_SIDES);
}
</syntaxhighlight>
|helpers
|also_functions={{LSL DefineRow||[[llAttachToAvatar]]}}
{{LSL DefineRow||[[llDetachFromAvatar]]}}
{{LSL DefineRow||[[llGetAttachedList]]}}
{{LSL DefineRow||[[llGetObjectDetails]]|[[OBJECT_ATTACHED_POINT]]}}
|also_events={{LSL DefineRow||[[attach]]}}
|also_tests
|also_articles
|notes
|permission
|negative_index
|cat1=Attachment
|cat2
|cat3
|cat4
}}

Project talk:About

2024-09-07T18:45:06Z

Peter Stindberg: /* How to: Get write access to the wiki */

I don't understand why there are so many wikis. What was wrong with the original one? Why did LL decide to completely scrap that one and start a new one so that all us scripters would have to scrounge through several sources for relevant data?{{unsigned|Nynthan Folsom|10:38, 26 May 2007}}
: {{reply to|Nynthan Folsom}} Now there is only one :-) — [[User:Gwyneth Llewelyn|Gwyneth Llewelyn]] ([[User talk:Gwyneth Llewelyn|talk]]) 08:56, 23 August 2022 (PDT)

If this is like real life, why is there not a death area. I have had my heart ripped out by my boyfriend and i want my avatar to die and all of sl to get the article of the death. Why is there not a place for death. That way for people that do die there real life people can come here and let us know this has really happened to. Thank you[[User:Nini Danitz|Nini Danitz]] 19:24, 30 October 2010 (UTC)

== multi-lang ==

Eu acho que falta colocar na página a predefinição ou o gabarito: <nowiki>{{multi-lang}}</nowiki>. I think missing template <nowiki>{{multi-lang}}</nowiki> on the page: --[[User:Gianinni_Babenco|Gianinni Babenco]]([[User talk:Gianinni_Babenco|talk]]|[[Special:Contributions/Gianinni_Babenco|contribs]]) 15:40, 2 September 2011 (PDT)

I just started on SecondLife and i dont know how to get out of the place you are put when you get on for the first time evar. I would appreciate some help.{{Unsigned|NuttyHorseLuver Resident}}

== How to: Get write access to the wiki ==

Since the page is locked, this will need to suffice: If you want to contribute to the wiki, you need to [https://lindenlab.freshdesk.com/support/tickets/new file a ticket] and request write access.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 14:56, 10 May 2024 (PDT)

: Check here: https://wiki.secondlife.com/wiki/Project:Editing_Guidelines#How_can_I_contribute.3F
: -- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 11:45, 7 September 2024 (PDT)

LSL Alternate Editors

2024-08-29T19:55:01Z

Peter Stindberg: /* Visual Studio Code */ added another LSL plugin

{{LSL Header|ml=*}}

There are several off-world editors available for free or to purchase. Some have syntax highlighting for LSL that will make your code easier to follow. At least two will compile and execute a large subset of LSL. Below are some of the more popular editors for use with LSL.

If you have a favorite that is missing from the list, '''please''' feel free to add it.

==Opening scripts in another editor directly from the viewer:==

* Enable: Preferences > Advanced > Show [[Advanced_menu]].
* Go to: Advanced > Show [[Debug_Settings]].
* Edit: "ExternalEditor".

As the description tells you, enter 3 params:
* Path to editor (enclose in quotes, if path has spaces).
* Optional command line params (you can ignore these if you like).
* <code>"%s"</code> will paste script path automatically (dont change this).

Examples:
* Linux (opens script in new window if already open): <code>/usr/bin/gedit --new-window "%s"</code>
* Windows (path has spaces > enclosed in quotes): <code>"C:\Users\FirstName LastName\Notepad\notepad++.exe" "%s"</code>

Then click the <code>"Edit..."</code> button in the script edit window. Save and close editor when done.

==Making your own files for syntax highlighting and autocompletion:==

Please refer to the page [[Making_your_own_LSL_syntax_and_autocompletion_files]] for a list of colors used by Linden Labs for the editor in their viewer as well as a list with current keywords.

== Online LSL Generators ==
Online LSL generators create and edit LSL scripts via a website, some may have syntax highlighting for better reading.
Sites are multi-platform editors without downloads:
*[http://conwylie.co.uk/ScriptGenerator/ Con Wylie's LSL Script Generator]

== Syntax Highlighting Files ==
These projects may have more current LSL highlighting files:
*[http://hilitelsl.googlecode.com HiLiteLSL.GoogleCode.com]

== Syntax highlighting, autocompletion and snippet files by the [http://www.buildersbrewery.com Builder's Brewery]: ==

{| class="wikitable" style="font-size: 85%; text-align: center; width: auto; border=1px;"
|-
! '''Software:'''
! '''URL for download:'''
! '''Issue tracker:'''
! '''Commercial:'''
! '''Windows:'''
! '''Mac:'''
! '''Linux:'''
! '''Browser'''
! '''Syntax:'''
! '''Autocompletion:'''
! '''Snippets:'''
! '''Tooltips:'''
|-
| [http://ace.c9.io Ace]
| rowspan="19" | [https://github.com/buildersbrewery/linden-scripting-language/ Download files]
| rowspan="19" | [https://github.com/buildersbrewery/linden-scripting-language/issues/ Issue tracker]
| {{no}}
| colspan="3" {{maybe|requires a browser}}
| {{yes}}
| {{maybe|LL viewer theme not included}}
| colspan="2" {{yes}}
| {{no}}
|-
| [http://www.atom.io/ AtomEditor]
| {{no}}
| colspan="3" {{yes}}
| {{yes|Atom is built upon Chrome}}
| colspan="3" {{yes}}
| {{no}}
|-
| [http://www.contexteditor.org/ ConTEXT]
| {{no}}
| {{yes}}
| colspan="2" {{no}}
| {{no}}
| colspan="2" {{yes}}
| {{no}}
| {{no}}
|-
| [http://www.gnu.org/software/emacs/ Emacs]
| {{no}}
| colspan="3" {{yes}}
| {{no}}
| {{maybe|Work in progress}}
| {{no}}
| {{maybe|included for [https://github.com/capitaomorte/yasnippet YASnippet]}}
| {{no}}
|-
| [http://projects.gnome.org/gedit/ gedit]
| {{no}}
| colspan="2" {{yes}}
| {{maybe|for GNOME}}
| {{no}}
| colspan="2" {{yes}}
| colspan="2" {{no}}
|-
| [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi GeSHi - wikimedia extension]
| {{no}}
| colspan="3" {{maybe|requires a browser}}
| colspan="2" {{yes}}
| colspan="3" {{no}}
|-
| [http://www.highlightjs.org/ Highlight.js]
| {{no}}
| colspan="3" {{maybe|requires a browser}}
| colspan="2" {{yes}}
| colspan="3" {{no}}
|-
| [http://www.jedit.org/ jEdit]
| {{no}}
| colspan="3" {{maybe|requires JavaVM}}
| {{no}}
| {{maybe|LL viewer theme not included}}
| {{yes}}
| colspan="2" {{no}}
|-
| [http://www.kate-editor.org/ Kate]
| {{no}}
| {{maybe|via KDE for Windows}}
| {{maybe|via KDE for Mac}}
| {{yes}}
| {{no}}
| colspan="2" {{yes}}
| colspan="2" {{no}}
|-
| [http://www.nano-editor.org/ Nano]
| {{no}}
| colspan="2" {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| colspan="3" {{no}}
|-
| [http://www.notepad-plus-plus.org/ Notepad++]
| {{no}}
| {{yes}}
| colspan="2" {{no}}
| {{no}}
| colspan="2" {{yes}}
| {{maybe|included for [https://github.com/erinata/FingerText FingerText]}}
| {{no}}
|-
| [http://www.pygments.org/ Pygments]
| {{no}}
| colspan="3" {{maybe|requires a browser}}
| colspan="2" {{yes}}
| colspan="3" {{no}}
|-
| [http://www.codingmonkeys.de/subethaedit/ SubEthaEdit]
| {{yes}}
| {{no}}
| {{yes}}
| colspan="2" {{no}}
| colspan="2" {{yes}}
| colspan="2" {{no}}
|-
| Sublime Text [http://www.sublimetext.com/2 ST 2 stable], [http://www.sublimetext.com/dev ST 2 dev], [http://www.sublimetext.com/3 ST 3 stable], [http://www.sublimetext.com/3dev ST 3 dev]
| {{yes}}
| colspan="3" {{yes}}
| {{no}}
| colspan="3" {{yes}}
| {{yes}}
|-
| [http://www.textasticapp.com/ Textastic]
| {{yes}}
| {{no}}
| {{yes|Supports Mac OS and iOS versions of Textastic}}
| colspan="2" {{no}}
| colspan="3" {{yes}}
| {{no}}
|-
| [https://www.smilesoftware.com/TextExpander/ TextExpander] and [https://www.smilesoftware.com/TextExpander/touch/ TextExpander touch]
| {{yes}}
| {{no}}
| {{yes}}
| colspan="2" {{no}}
| colspan="2" {{no}}
| {{yes}}
| {{no}}
|-
| [http://www.ultraedit.com/ UltraEdit]
| {{yes}}
| colspan="3" {{yes}}
| {{no}}
| colspan="3" {{yes}}
| {{no}}
|-
| [http://www.vim.org/ Vim]
| {{no}}
| colspan="3" {{yes}}
| {{no}}
| {{maybe|LL viewer theme not included}}
| {{yes}}
| {{maybe|included for [https://github.com/garbas/vim-snipmate Snipmate] and [https://github.com/SirVer/ultisnips Ultisnips]}}
| {{no}}
|-
| [https://code.visualstudio.com/ Visual Studio Code]
| {{no}}
| colspan="3" {{yes}}
| {{no}}
| colspan="3" {{yes}}
| {{no}}
|}

==LSL Integrated Development Environments (coding and testing environments) ==

===[[Con-Wylies-Script-Generator]]===

*[http://conwylie.co.uk/ScriptGenerator/ Con Wylie's LSL Script Generator] has been ported from a website into a free downloadable program, anyone can use the program as it is very easy to use.

Con Wylie's LSL program is multi-platform on Windows, Linux and Mac. The generator, editor and compiler have been built from the ground up to give the user ease of use.

===[[LslPre]]===
* <s>[http://lsl.dreamjammers.net http://lsl.dreamjammers.net]</s>{{dead link}}
[[LslPre]] is a full featured LSL script editor, preprocessor and optimiser for windows.

===[[LSL Editor Community Edition]]===

LSL Editor Community Edition '''for Windows''' is a standalone LSL script '''editor, compiler and debugger'''. Binary and Source as of 2013-03-14.

Its compiler and debugger are already now reasonably accurate. Please blog any LSL-Editor bugs you find into such places as our [[LSLEditorBugs|LSL-Editor Bugs]] article or via the project's SourceForge bug tracker located at: [http://sourceforge.net/tracker/?group_id=319248 Bug Tracker].

* Alphons van der Heijden, author of LSLEditor, the great off-line editor and debugging tool for scripting in Second Life, has donated his opus magnum to the free and open source community where it can grow and keep pace with the SL platform!

*Details, executable and source can be found at [http://sourceforge.net/projects/lsleditor/ http://sourceforge.net/projects/lsleditor/]

Development of LSL-Editor was originally done by Alphons van der Heijden at [http://www.lsleditor.org/ http://www.lsleditor.org/].

=== [[LSL-Plus]] ===

[http://lslplus.sourceforge.net/ LSL PLus Eclipse Plugin]

'''For Windows, Mac, and Linux''', the LSL Plus Eclipse plugin is a Editor/Unit Test environment for LSL implemented in Eclipse. It is a FLOSS project (Free/Libre Open Source Software). The latest release (0.13.0 - 2010-01-06) features multi-script execution with '''source level debugging''' (setting breakpoints, single stepping through code, examining variables on the call stack, etc.), making it unique among LSL IDEs. It now supports both multi-script execution in a simulated environment (with avatars, prims, inventory, (limited) physics, etc.) and '''unit''' testing - allowing you to test individual handlers and functions by precisely controlling the setup/teardown and interaction with the execution environment (including support for 'mocking' the LL function call that interact with the script environment). It also has some additional code management features that encourage code re-use without having to cut-and-paste, as well as code '''optimization''' (inlining, constant folding).

By using the Eclipse IDE you get features such as integration with source code control systems like CVS or Subversion, task management, integration with 3rd party bug tracking software, and so on. It supports development on Windows, Mac, and Linux platforms.
* Missing bracket matching and certain highlighting features.

=== [[LSLForge]] ===

'''LSLForge Eclipse for Windows/Linux/OS X''', is a derivative of [[LSL-Plus]], forked in September 2011. LSLForge aims to further advance and mature the LSL-Plus project and support the Eclipse LSL developer community.

This project was initially maintained [https://github.com/elnewfie/lslforge here], but is abandoned/orphaned. The currently most active (as of 04/2024) fork can be found [https://github.com/KoolLSL/lslforge here].

=== [[MiceOnABeam Visual Scripting Tool]] [{{HoverText|''C''|Commercial Software}}]===

* [http://www.miceonabeam.com/ MiceOnABeam Visual Scripting Tool]
MiceOnABeam is a visual programming tool (for Windows only) that generates LSL scripts for SL. You choose among graphical modelling components to specify the program flow of your script in terms of states and the events that transition between the states. You can then use the built-in LSL Action Wizard or insert your own LSL code to specify what happens when an event occurs. The program then generates the LSL code for the model to form a complete script for the SL environment. Check out the demo video '''[https://bit.ly/ihCqyf here]''' or on '''[https://www.youtube.com/watch?v=LBA8wvoA9EI YouTube]'''. A Free version can be downloaded from '''[http://www.miceonabeam.com here]'''.

{{warning|This project was unfortunately abandoned ''circa'' 2016, but you can still download v1.0.5 as well as a professional license for free from the original developers.}}

=== [[LSL plugin for JetBrains IDEs]] ===

[https://plugins.jetbrains.com/plugin/21002-linden-script-lsl- LSL plugin] for [https://www.jetbrains.com/ JetBrains IDEs] (IntelliJ IDEA, PyCharm, Android Studio etc.)

Supports syntax highlighting, code style formatting, autocompletion, hints, references, plus everything that provides IDE itself.

The plugin is in early access and any contain bugs.

==A build system that uses cpp and make==

A build system for LSL scripts is described [[How_to_make_writing_LSL_scripts_easier|here.]] Sources are available from [https://github.com/Ratany/lsl-repo here].

[[User:Ratany Resident|Ratany Resident]] 09:38, 13 January 2014 (PST)

==Off-world syntax checker==
You can build a syntax checker yourself and hook it into whatever editor you fancy if you have the viewer source installed and compiled on your machine. The C++ source to build one yourself is [[User:JB_Kraft#Offline_LSL_Syntax_Checker|here (JB Kraft)]].

==Multi-platform Editors==

===ByronStar SL===
Based on [http://eclipse.org Eclipse], the [http://byronstar-sl.sourceforge.net/ ByronStar SL IDE] includes most modern program editor features. It also includes custom features for LSL, such as variable checking, error markers, and code formatting. Eclipse is available for Macintosh, Linux, Windows, and many UNIX flavors.
* No longer maintained.

===Emacs===
There is an [[Emacs LSL Mode]] available on this wiki, which provides syntax highlighting and indentation features. For tips on writing LSL in emacs, read [http://xahlee.org/sl/ls-emacs.html Xah Lee's page]. Emacs is available for many Unix flavors, Macintosh and Windows.

You may come across (and attempt to use) Gary Evan's '''LSL major mode'''. It won't work with the Linden Scripting Language, as Gary wrote it for the [http://www.cs.cmu.edu/afs/cs/usr/wing/www/publications/LarchBook.pdf Larch Shared Language].
* Last updated 5 January 2014

===vim===
[http://www.vim.org/ vim:] vi improved. A multi-platform evolution of the most classical of the editors: vi. GPL code.
 [http://www.secondlifelab.it/index.php?option=com_remository&Itemid=77&func=select&id=7 Plugins for VIM] for install the syntax, autocompletion, autoident for LSL script into vim
* Plugin link is dead

===JOE===
[http://joe-editor.sourceforge.net/ Joe's Own Editor (a.k.a. Joe)] is a comand line editor for unixoid systems. See [[User:Zai Lynch/LSL highlighting in Joe]] for a manual and syntax file download.

===SciTE===
Easy to use, features syntax highlighting, folding, auto complete, help that opens the appropriate wiki page, and is setup to use the c preprocessor, and [[lslint]]. 
Windows only [https://sdfjkl.org/hack/scite-ez/] 

Files for Linux or Windows [http://forums.secondlife.com/showthread.php?t=209219 Forum thread] [http://dimension128.homelinux.net/scite_lsl.tar.gz scite_lsl.tar.gz]
* LSL file links are dead

===jEdit===
Developed in Java, this mature, cross-platform editor runs on any operating system with a Java 2 version 1.3 or higher virtual machine. It has all the features you'd expect from a full-GUI text editor. Syntax highlighting and tailored editing behavior is supported through "modes." (You can get the LSL 'modes' file [https://gist.github.com/GitSkunk/5327522 here] .) The editor supports a rich plug-in API; many third-party plug-ins exist to facility editing, formatting, communications, etc. 
You can find jEdit [http://www.jedit.org/ here].
*LSL Files last updated june 2013

===Midnight Commander===
[http://www.midnight-commander.org/ GNU Midnight Commander (mc)] is a free cross-platform orthodox file manager and a clone of Norton Commander. 
Midnight Commander is a console application with a text user interface. 
OS: Unix-like, Microsoft Windows 
For Linux see [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/mc]] for a manual and syntax file download.
*LSL files last updated in 2009

===UltraEdit-32/UEStudio [{{HoverText|''C''|Commercial Software}}]===
Very outdated
[http://www.ultraedit.com/ UltraEdit-32/UEStudio] is a powerful text, HTML, and HEX editor. This is a commercial editor with a 30 day trial version available at the website. Important features:
* column/block mode editing
* brackets/braces matching
* code-folding
* configurable syntax highlighting via custom [http://www.ultraedit.com/index.php?name=Content&pa=showpage&pid=40#wordfiles wordfiles]
* autocomplete (using keywords defined in the wordfile)
* bookmarks, incremental searching, CTAG support
* automatic conversion between Unix/Dos/MAC/UTF-8, etc
* built-in FTP/SFTP client

OS: Linux, Mac and Windows.

The following syntax files are available for UltraEdit
* [[User:Lum Pfohl/LSL Syntax Highlighting For UltraEdit]]
* Last updated 28 November 2007.

===Sublime Text [{{HoverText|''C''|Commercial Software}}]===
[http://www.sublimetext.com/ Sublime Text] is a sophisticated text editor for code, markup and prose.
You'll love the slick user interface, extraordinary features and amazing performance. Key Bindings, Menus, Snippets, Macros, Completions and more - just about everything in Sublime Text is customizable with simple JSON files. This system gives you flexibility as settings can be specified on a per-file type and per-project basis. Sublime Text uses a custom UI toolkit, optimized for speed and beauty, while taking advantage of native functionality on each platform.

Sublime Text is available for OS X, Windows and Linux.

Sublime Text may be downloaded and evaluated for free, however a license must be purchased for continued use. There is no enforced time limit for the evaluation.

The following syntax highlighting files are available for Sublime Text.
* [https://github.com/JKolya/sublime-text-2-lsl Sublime Text 2 LSL Syntex] Last updated October 28, 2012.

What you will get via Package Control is the following. Simply go "Package Control: Install Package" and search for "LSL". (including not only syntax highlighting, but also smooth LSL functions/events/constants completions, [[lslint]] as build system, and inworld editor look-and-feel theme)
* [https://github.com/Makopo/sublime-text-lsl LSL Bundle for Sublime Text 2]
*Active as of 27 September 2015

===Visual Studio Code===
[https://code.visualstudio.com/ Visual Studio Code] - sometimes called VS Code - is the free editor component of the otherwise commercial Visual Studio package by Microsoft. Visual Studio Code is a full editing environment with projects support, syntax highlighting, editing timeline, autocomplete, GitHub connection, diff, etc.

Visual Studio Code can be extended with a wide range of extension. There are a handful of extensions for LSL, in various stages of actuality. The most recently maintained ones being [https://marketplace.visualstudio.com/items?itemName=MinuitFerina.lsl-tools LSL Tools] and [https://marketplace.visualstudio.com/items?itemName=DalGhost.lsl-fp LSL-FP], or the realtively new [https://marketplace.visualstudio.com/items?itemName=jyaoma.lsl-lsp LSL Language Server], all available for free via the [https://marketplace.visualstudio.com/search?term=lsl&target=VSCode&category=All%20categories&sortBy=Relevance VS Code Marketplace].

Visual Studio Code has built-in provisions for make and build workflows, so tools like an external linter, prrprocessor or optimizer can be included into the development workflow.
* Active as of 11 September 2023

==Windows Editors==

===e===
The [https://github.com/etexteditor/e e Editor] is a port of TextMate to Windows, and can use the TextMate LSL bundle listed below.

===Notepad++===
[http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] is probably one of the best Windows editor around. Packed with features, extremely powerful and easy to use for beginners too. Best of all, it is GPL code.

Shan Bright's Notepad++ LSL syntax file 'BrightLSL' is at the Bright Corporation website: [http://www.brightcorporation.net/brightlsl BrightLSL] (Updated December 10, 2010)

Nexii Malthus's Notepad++ LSL syntax file, includes latest functions and constants [http://c438644.r44.cf2.rackcdn.com/userDefineLang.xml] (3rd December, 2011)

WhiteStar Magic's Notepad++ LSL syntax file is being updated regularly, and is available on Github: [https://github.com/WhiteStar-Magic/NotePad---userdef/archives/master NotePad---userdef] (Last Update: May.03.2012)

Gwen Setzer's Notepad++ (6.3 and above) LSL Syntax Files: (Generated from Firestorm 4.4.0)
Language description: [http://pastebin.com/2AsRuKjh lslLanguage.xml] (Language->Define your Language->Import)
Autocompletion support: [http://pastebin.com/FcjNVDyb lsl.xml] (Copy the file lsl.xml in the API plugin directory of Notepad++. ex: C:\Program Files\Notepad++\plugins\APIs, I also recommend enabling Settings->Preferences->Autocompletion->Function parameters hint on input)

Dari's Better Highlighting for Notepad++ (6.3 and above): [http://home.comcast.net/~volfin/LSL.XML LSL.XML] (updated 11/22/2013) [[User:Darien Caldwell|Darien Caldwell]] 12:11, 9 July 2013 (PDT)

Hint: to ensure code folding works properly, change line endings to Windows style if they are not already set as such. (Edit / EOL conversion / Windows format)

===ConTEXT===
[http://www.context.cx/component/option,com_frontpage/Itemid,1/ ConTEXT] is a small, fast and powerful freeware text editor, developed mainly to serve as secondary tool for software developers.

The following syntax files are available for ConTEXT.
* [http://blogic14.blogspot.com/ Last Activity] July 2012
* [http://archive.is/Wm3B Last Announcement by developer of ConTEXT] Friday, 07 September 2007
* [http://www.contexteditor.org/ Site and Newsletter Sign Up - '''DOWNLOAD'''] September 2007
* [http://forum.context.cx/index.php?action=dlattach;topic=1775.0;id=359 Shyan Graves] Last updated March 01, 2007.
* [http://adammarker.org/shill/context/lsl.chl Sir.Grelling] Last updated July 10, 2006.

===Crimson Editor===
[http://www.crimsoneditor.com/ Crimson Editor] is a professional source code editor for Windows.
The following syntax files are available for Crimson Editor.

* Aakanaar - Last updated September 10, 2006 for Second Life version 1.10.0.
* [http://sourceforge.net/projects/emeraldeditor/files/crimsoneditor/ Emerald Editor] '''2011''' Open Source version of Crimson Editor

===[[LSL-Editor]]===

* This project is no longer maintained. Instead, consider LSL Editor Community Edition. See below.

===LSL Editor Community Edition===

* [http://sourceforge.net/projects/lsleditor/ Source Forge: LSL Editor]

[[LSL-Editor]] is the '''frequently''' updated version of the LSL Editor with editing, compiling, and debugging abilities.
When the path to the editor is added to the viewer's Debug Setting: ''ExternalEditor'' one can have a nice round trip external editor. See the LSL-Editor entry just above, or see above in the Integrated section, or the wiki page [[LSL-Editor]] for more information.

===TextPad [{{HoverText|''C''|Commercial Software}}]===
[http://www.textpad.com/products/textpad/index.html TextPad] is a powerful, but easy to use general purpose text editor. It is a commercial product, but there is a 30 day trial version available for free on the website.

The following syntax files are available for TextPad.
* [[LSL_Editor_TextPad_ClipBook_Events | Events ClipBook]] Last updated March 5, 2007. Based on the LSL Portal event entries.
* [[LSL_Editor_TextPad_Syntax | Prodigal Maeterlinck & Patrick2 Chama]] Last updated February 20, 2007. Extracted from the Second Life viewer source code.
* [http://www.textpad.com/add-ons/files/syntax/lsl_.zip Ben Gray] Last updated August 23, 2006. As of version 1.12.0, with the deprecated functions in a separate keyword list.
* [http://www.textpad.com/add-ons/files/syntax/lsl.zip Matthias Huber] Last updated September 23, 2004.

===EditPad Pro [{{HoverText|''C''|Commercial Software}}]===
[http://www.editpadpro.com/ EditPad Pro] is a text editor with many great features for programming. It is a commercial program, with a demo version available. There is also a Lite version, but that has no syntax-highlighting support.

There is an LSL syntax file available for download from inside the program. However, it is from October 2006 so some new features may not be available.

===LSLCCEditor===

[https://github.com/Teriks/LibLSLCC/releases LSLCCEditor] is an open-source LSL editor for Windows with autocomplete, off world syntax checking, common code analysis warnings, and code formatting. It was built as part of an improved OpenSim compiler project, and is also able to compile LSL into OpenSim compatible C# code. The editor is released along side a cross platform C# library (LibLSLCC), which implements a reusable LSL compiler frontend and OpenSim compatible transpiler.

Library Data (highlighting data) is provided for both Linden LSL, and OpenSim LSL + OpenSim LSL extensions.
The dialect of LSL is configurable via the editor menu. Some editor usage information is provided on the project's [https://github.com/Teriks/LibLSLCC/wiki Wiki].

==Macintosh Editors==
===TextMate [{{HoverText|''C''|Commercial Software}}]===

TextMate is a commercial text/program editor from [http://macromates.com/ Macromates] (30 day trial available). You can find details about Piero Padar's well-maintained LSL bundle in the [http://forums-archive.secondlife.com/54/ae/89389/1.html Scripting Tips forum archive].

===SubEthaEdit [{{HoverText|''C''|Commercial Software}}]===
This a great text editor with extensible language support. It also happens to be an incredible collaborative editor. Info at: http://www.subethaedit.net/

There is a contributed LSL mode by Zarf Vantongerloo. The mode is a little out of date and could use some love. But in general works great, doing syntax hilighting of LSL funcitons and adding a pop-up menu of all functions, states and event handlers to the top of the window.

An updated LSL mode by Mark Lentczner is available now from the SubEthaEditor [http://www.subethaedit.net/modes.html User contributed modes Repository].

An updated (but still out of date) version of Mark Lentczner's mode is available on Solo Mornington's Github: https://github.com/SoloMornington/LSL_mode Note that this mode was developed for Coda 1.

===Coda [{{HoverText|''C''|Commercial Software}}]===

Coda is 'one-window web development,' but it's a very pleasing text editor for a wide variety of uses. You can set up 'sites' which are web sites, but can represent any remote filesystem, which is echoed locally through ftp and/or subversion.

Coda can use SubEthaEdit syntax coloring 'modes,' so LSL is supported. Also available is a plug-in editor which lets you run arbitrary scripts on the selection or document.

https://library.panic.com/coda/

''Note: Coda was [https://library.panic.com/coda/purchase-faq/ discontinued] as of September 16th, 2020. However, it's still available for download for customers with a valid license who are running ancient versions of macOS. It was replaced by Nova; see below.''

===Nova [{{HoverText|''C''|Commercial Software}}]===

[https://nova.app/ Nova] is Panic Inc.'s next generation code editor. It has been rewritten from scratch, and, except for allowing importing old Coda 2 projects (what it used to be called 'sites'), it's not compatible with Coda plugins or themes. By contrast, it's a far more sophisticated code editor (tenderly referred to as 'a lightweight IDE' by its fans), aiming to directly compete with VS Code on the macOS platform, offering much more.

Because the old SubEthaEdit syntax colouring modes used by Coda aren't supported any longer (the new syntax highlighting engine uses Panic's own variant of a [https://markdown-all-in-one.github.io/docs/contributing/textmate-language-grammar.html#introduction TextMate grammar]), Nova requires the development of new 'language extensions' from scratch by volunteers; starting with Nova 10, it also supports grammars written with [https://docs.nova.app/syntax-reference/tree-sitter/ Tree-sitter Extensions], but [https://tree-sitter.github.io/tree-sitter/ there isn't yet a Tree-sitter grammar for LSL].

There is an [https://extensions.panic.com/extensions/gwynethllewelyn/gwynethllewelyn.LindenScriptingLanguage/ LSL language extension on the Nova Extension Library] which features not just syntax highlighting/colouring, but also auto-completion, scope context and tooltips, although many features are still under development. The colours used for actual syntax highlighting are '''not''' the [[Making your own LSL syntax and autocompletion files|official ones]], but they're specified by whatever is set to the current ''theme'', not by the language extension itself; there is, at the time of writing, no LSL-specific theme for Nova (but it's not too hard to do one).

Nova is a fully commercial code editor with a 30-day trial period and a license fee that gets you one year of updates, after which you can just keep the copy you've got forever without paying anything else (or, alternatively, buy another year of updates, at a discount).

===BBEdit and TextWrangler ===

You can get an LSL language plugin for all versions of BBEdit and TextWrangler at [http://blog.elitecoderz.net/lsl-linden-script-language-plugin-for-bbedit/2008/12/ Erik Scholtz' Blog]

For older versions of BBEdit (7.0 or less) and TextWrangler (1.0 only), there is a module available at [http://adammarker.org/bbedit http://adammarker.org/bbedit]

==Linux Editors==
===Kate===
[http://kate-editor.org/ Kate] is an advanced text editor for KDE. Usually included in all KDE based distributions. 
A [[Kate LSL Mode]] is available on this wiki.
===Gedit===
[http://www.gnome.org/projects/gedit/ Gedit] is an advanced text editor for GNOME. 
See [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/gedit]] for a manual, syntax file and Color Theme download.
===Nano===
Nano is a curses-based text editor for Unix and Unix-like systems. 
Nano has been an official part of the GNU Project since February 2001. 
See [[User:Kuraiko_Yoshikawa/sandbox/LSL_Goodies/nano]] for a manual and syntax file download.
===Vim===
Based on the vi editor common to Unix-like systems, [http://vim.sourceforge.net/ Vim] is designed for use both from a command line interface and as a standalone application in a graphical user interface. 
Vim comes standard with LSL highlighting support.

== Features Table ==

{| class="wikitable sortable" style="font-size: 85%; text-align: center; width: auto; border=1px;"
|-
! Name
! Integrated development environment
! Windows
! Mac OS
! Linux
! Code Completion
! Highlighting
! Actively Maintained
|-
! [[LSL_Alternate_Editors#Con-Wylies-Script-Generator|Con-Wylies-Script-Generator]]
| {{yes}}
| {{yes}}
| colspan="2" {{no|No since 2.x}}
| {{yes}}
| {{yes}}
| {{Yes}}
|-
|-
! [[LSL_Alternate_Editors#LSL-Plus|LSL-Plus]]
| {{yes}}
| colspan="3" {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
|-
! [[LSL_Alternate_Editors#LSLForge|LSLForge]]
| {{yes}}
| colspan="3" {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
|-
|-
! [[LSL_Alternate_Editors#LSL Editor Community Edition|LSL Editor Community Edition]]
| {{yes}}
| {{yes}}
| colspan="2" {{no}}
| {{yes | Custom Vars and Functions also}}
| {{yes}}
| {{yes}}
|-
|-
! [[LSL_Alternate_Editors#LslPre|LslPre]]
| {{yes}}
| {{maybe|Windows (.NET)}}
| colspan="2" {{no}}
| {{yes}}
| {{yes}}
| {{maybe|All links and references down as of 2023}}
|-
|-
! [[LSL_Alternate_Editors#MiceOnABeam Visual Scripting Tool|MiceOnABeam Visual Scripting Tool]]
| {{yes}}
| {{maybe|Windows (.NET)}}
| colspan="2" {{no}}
| {{yes | Custom Vars and Functions also}}
| {{yes}}
| {{no|Old licensees can still download code}}
|-
! [[LSL_Alternate_Editors#LSLCCEditor|LSLCCEditor]]
| {{yes}}
| {{maybe|Windows (.NET)}}
| colspan="2" {{no}}
| {{yes | Custom Vars and Functions also}}
| {{yes}}
| {{yes}}
|-
|-
! [[LSL_Alternate_Editors#LSL_plugin_for_JetBrains_IDEs|LSL plugin for JetBrains IDEs]]
| {{yes}}
| colspan="3" {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
|}

LlLinksetDataWrite

2024-08-14T18:57:00Z

Peter Stindberg:

{{LSL Function/Headless
|default={{{default|}}}
|inject-2=
|summary=The '''llLinksetDataWrite''' and '''llLinksetDataWriteProtected''' functions create or update a '''name:value''' pair in the linkset datastore. The linkset datastore is a semi-permanent key-value store that is retained as a prim property regardless of whether the script is deleted or reset (via manual reset, [[llResetScript]], [[llResetOtherScript]], or cloning the object). If {{LSLP|value}} is an empty string, the pair is deleted.

This function returns 0 on success or an error code on failure.

When these functions are called, the [[linkset_data]] event is triggered in all scripts running in the linkset with an action of [[Template:LSL_Constants_Linkset_Data|LINKSETDATA_UPDATE]], or [[Template:LSL_Constants_Linkset_Data|LINKSETDATA_DELETE]] if the pair is deleted.

The linkset datastore can contain up to 131072 bytes (128 KiB) of data and has no impact on script memory usage aside from the functions and events used to interact with it. Every pair written to the datastore consumes a number of bytes in the datastore equal to the length of {{LSLP|name}} plus the length of {{LSLP|value}}, plus an additional 32 bytes if written using '''llLinksetDataWriteProtected'''.

|constants={{LSL Constants Linkset_Data Returns}}

|func=llLinksetDataWrite|sort={{{sort|LinksetDataWrite}}}
|head={{LSL Function/Head
|func_id=|func_sleep=0|func_energy=10.0
|func=llLinksetDataWrite
|return_type=integer
|return_text=success or failure code.
|p1_type=string|p1_name=name|p1_desc=The key of the '''name:value''' pair in the datastore to be updated or created.
|p2_type=string|p2_name=value|p2_desc=The '''value''' of the '''name:value''' pair.
|func_desc=Creates or updates an unprotected '''name:value''' pair from the linkset's datastore.
}}{{LSL_Function/Head
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataWriteProtected
|p1_type=string|p1_name=name|p1_desc=
|p2_type=string|p2_name=value|p2_desc=
|p3_type=string|p3_name=pass|p3_desc=A pass phrase used to protect the '''name:value''' pair.
|return_type=integer
|return_text=success or failure code.
|func_footnote
|func_desc=Creates or updates a protected '''name:value''' pair from the linkset's datastore. Further attempts to read, write or update the '''name:value''' pair must use the protected versions of those functions and must supply the same string that was used in {{LSLP|pass}}.
|func_footnote
|caveats=
* Protecting a '''name:value''' pair adds an additional 32 bytes to its size in the datastore regardless of the length of {{LSLP|pass}}. The length of {{LSLP|pass}} itself is not counted against the data storage limit.
* When writing a protected name, the [[linkset_data]] event fires as normal, however the value parameter will be an empty string.
}}
|caveats=
* Events are only fired if the linkset's datastore is changed.
** Rewriting an existing value to a '''name:value''' pair returns LINKSETDATA_NOUPDATE.
** Writing an empty string to a nonexistent name in the datastore returns LINKSETDATA_NOTFOUND.
* There is currently no way to write to or read from a linkset datastore from another linkset.
* The datastore is accessible from the entire linkset but acts as a property of the root prim alone. Therefore, linking and unlinking prims produces the following results:
** When linking one linkset to another linkset, the combined linkset datastore includes all pairs from both datastores.
*** If any pairs have conflicting {{LSLP|name}}s, the combined linkset datastore will keep the pair from the original linkset and will silently drop conflicting pairs from newly added prim(s).
*** If the combined linkset datastore would exceed 131072 bytes, pairs from the newly linked prim(s) will be added to the combined linkset datastore up to the limit. It is not currently clear in what order pairs are added, so there is no way to predict which will be dropped.
** When unlinking a child prim from a linkset, the datastore remains in the original linkset and the child prim (now its own root prim) has an empty datastore.
*** If the datastore is too large to cache in a script to be rewritten after unlinking, you may need to devise a custom method of porting the datastore from the original linkset to the child prim, if necessary.
** When unlinking a root prim from a linkset, the datastore remains in the newly-unlinked root prim and the remaining prims in the original linkset have an empty datastore.
* There is no limit on the size of {{LSLP|value}} aside from the total datastore limit, so care should be taken when writing very large values that could crash other scripts in the linkset via [[linkset_data]].
** If a script does not define a [[linkset_data]] event, it will not load any event parameters into its memory when the datastore is written to, so the script should not crash from another script in the linkset writing to the datastore.
** If this is a possible risk, consider using '''llLinksetDataWriteProtected''', which does not send {{LSLP|value}} in [[linkset_data]], with a static {{LSLP|pass}}.
* It is possible for data to be rolled back to a previous state if the datastore is stored in an object that is restored via a simulator rollback, or in an attachment that is not properly saved back to the server on logout.
** Viewer crashes can cause attachment states to not be saved, so care should be taken when using these functions in attachments, because datastore rollbacks are likely to occur on occasion for attachments.
|examples=
<syntaxhighlight lang="lsl2">
default
{
touch_start(integer num_detected)
{
llLinksetDataWrite("test-name", "See you on the other side!");
llResetScript();
}
state_entry()
{
llOwnerSay(llLinksetDataRead("test-name")); // Should print "See you on the other side!" to the owner
}
}
</syntaxhighlight>
|helpers=
=== Securing Against Tampering ===
<syntaxhighlight lang="lsl2">
// While there is no "standard" for names, it's a good idea to take some steps to prevent against other scripts accidentally overwriting your data.
// Since the datastore is shared among the entire linkset, one way to avoid name conflicts is to include the prim's UUID in the data pair's name.
// This example also monitors for llLinksetDataReset/unlinks and refreshes the datastore in response, which is usually good practice if you want to keep your data!

key this_uuid;
string lsd_data;

default
{
state_entry()
{
this_uuid = llGetKey(); // Save the current key into this_uuid for checking later
lsd_data = "bar"; // Store the data locally so it can be rewritten if the datastore gets erased for whatever reason
llLinksetDataWrite((string)llGetKey() + "-foo", lsd_data); // Write the data
}
on_rez(integer start_param)
{
if (llGetKey() != this_uuid)
{
// Prim UUID has changed!
// This should always be the case when on_rez is called, but is included here for clarity.
llLinksetDataWrite((string)llGetKey() + "-foo", llLinksetDataRead((string)this_uuid + "-foo")); // Read the data from the last prim UUID's pair and write it into this prim UUID's pair
// Note that you could also just write the lsd_data string instead of calling llLinksetDataRead, but this method is theoretically a little more robust if you expect other scripts to manipulate the data.
llLinksetDataDelete((string)this_uuid + "-foo"); // Erase the original data to free up memory
this_uuid = llGetKey(); // Update the UUID variable to the new UUID
}
}
linkset_data(integer action, string name, string value)
{
if (action == LINKSETDATA_UPDATE || action == LINKSETDATA_DELETE)
{
if (name == (string)llGetKey() + "-foo")
{
// Somebody else wrote to our pair - we'll just save it in case we need it later, but you could re-write the original data instead if desired.
lsd_data = value; // Note that in the case of LINKSETDATA_DELETE, value will be an empty string (""), which may or may not be how you want to handle that case
}
}
else if (action == LINKSETDATA_RESET)
{
// Linkset datastore has been reset!
llLinksetDataWrite((string)llGetKey() + "-foo", lsd_data); // Write the lsd_data string into this prim UUID's pair - in this case we can't use llLinksetDataRead because the datastore is empty
}
}
changed(integer change)
{
if (change & CHANGED_LINK)
{
// Linkset has changed!
// Generally, this can happen for a few reasons (see Caveats above), including when an avatar sits on the object. In certain circumstances, this resets the datastore.
// However, since the linkset data functions are very quick, it is easier to just write the data on every change to be safe for this example whether or not the datastore was reset.
llLinksetDataWrite((string)llGetKey() + "-foo", lsd_data); // Write the lsd_data string into this prim UUID's pair - in this case we can't use llLinksetDataRead because the datastore might be empty
}
}
}
</syntaxhighlight>
=== Simple blacklist management ===
<syntaxhighlight lang="lsl2">integer gDialogChannel;
integer gDialogHandle;
integer gManagingBlocks;

startDialog(key person)
{
gManagingBlocks = 0;
gDialogHandle = llListen(gDialogChannel, "", person, "");
llDialog(person, "\nSelect action", ["List blocks", "Add block", "Remove block"], gDialogChannel);
llSetTimerEvent(60);
}

stopDialog()
{
llSetTimerEvent(0);
llListenRemove(gDialogHandle);
}

default
{

on_rez(integer sp)
{
llResetScript();
}

state_entry()
{
gDialogChannel = (integer)(llFrand(-10000000)-10000000);
llListen(PUBLIC_CHANNEL, "", NULL_KEY, "");;
}

timer()
{
stopDialog();
}

touch_start(integer nd)
{
key toucherKey = llDetectedKey(0);
if (toucherKey == llGetOwner())
{
startDialog(toucherKey);
}
}

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

if (llGetAgentSize(id) == ZERO_VECTOR)
{
return;
}

if (channel == gDialogChannel)
{
stopDialog();
if (gManagingBlocks)
{
message = llStringTrim(message, STRING_TRIM);
if ((key)message)
{
if (gManagingBlocks == 1)
{
llOwnerSay("Addition request has been sent to the blacklist storage");
llLinksetDataWrite("blocklist:" + message, "1");
}
else
{
llOwnerSay("Removal request has been sent to the blacklist storage.");
llLinksetDataDelete("blocklist:" + message);
}
}
else
{
llOwnerSay("The UUID '" + message + "' appears to be invalid.");
}
startDialog(id);
}
else if (message == "List blocks")
{
list blocks = llLinksetDataFindKeys("^blocklist:", 0, 0);
integer listLength = llGetListLength(blocks);
llOwnerSay("Blacklist items: " + (string)listLength);
integer i;
while (i < listLength)
{
string record = llGetSubString(llList2String(blocks, i), 10, -1);
llOwnerSay("- secondlife:///app/agent/" + record + "/about" + " - " + record);
++i;
}
blocks = [];
startDialog(id);
}
else if (message == "Add block" || message == "Remove block")
{
string label = "add to";
gManagingBlocks = 1;
if (message == "Remove block")
{
gManagingBlocks = 2;
label = "remove from";
}
gDialogHandle = llListen(gDialogChannel, "", id, "");
llTextBox(id, "\nPlease specify one single avatar UUID you'd like to " + label + " the blacklist storage.", gDialogChannel);
llSetTimerEvent(60);
}
return;
}

if (llGetListLength(llLinksetDataFindKeys("blocklist:" + (string)id, 0, 1)) > 0)
{
llRegionSayTo(id, 0, "You're blacklisted.");
return;
}

llRegionSayTo(id, 0, "Hello there, secondlife:///app/agent/" + (string)id + "/about - your message: " + message);

}

linkset_data(integer action, string name, string value)
{
if (action == LINKSETDATA_RESET || action == LINKSETDATA_DELETE || action == LINKSETDATA_UPDATE)
{
llOwnerSay("Blacklist storage modified.");
}
}

}</syntaxhighlight>
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteProtected]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReadProtected]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
|also_events=
{{LSL DefineRow||[[linkset_data]]}}
|also_tests
|also_articles
|notes=
* Linkset datastore operations are synchronous and are usually processed within one server frame. Therefore, it is possible to synchronize variables between multiple scripts using the datastore alone without resorting to [[llMessageLinked]], or to use the datastore directly as extended memory for specific workloads that need to work with extremely large datasets.
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataReset

2024-08-14T18:56:33Z

Peter Stindberg:

{{LSL_Function
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataReset
|func_footnote
|func_desc=The '''llLinksetDataReset''' function erases all '''name:value''' pairs stored in the linkset's datastore. When this function is called the [[linkset_data]] event is triggered in all scripts running in the linkset with an action of [[Template:LSL_Constants_Linkset_Data|LINKSETDATA_RESET]].
|func_footnote
|spec
|caveats=
llLinksetDataReset removes all keys. Even those that were created by llLinksetDataWriteProtected.
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
|also_events=
{{LSL DefineRow||[[linkset_data]]}}
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataRead

2024-08-14T18:56:07Z

Peter Stindberg:

{{LSL Function/Headless
|default={{{default|}}}
|inject-2=
|summary=The '''llLinksetDataRead''' and '''llLinksetDataReadProtected''' functions return the '''value''' in the linkset's datastore for the provided {{LSLP|name}}. If {{LSLP|name}} is not found, these functions return an empty string.
|func=llLinksetDataRead|sort={{{sort|LinksetDataRead}}}
|head={{LSL Function/Head
|func_id=|func_sleep=0|func_energy=10.0
|func=llLinksetDataRead
|p1_type=string|p1_name=name|p1_desc=The key of the linkset '''name:value''' pair to be read.
|return_type=string
|return_text='''value''' corresponding to {{LSLP|name}}
|func_desc=Reads an unprotected '''name:value''' pair from the linkset's datastore.
|caveats=If the {{LSLP|name}} is an empty string, or the '''name:value''' pair was created with [[llLinksetDataWriteProtected]] this function returns an empty string.
}}{{LSL_Function/Head
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataReadProtected
|p1_type=string|p1_name=name|p1_desc=The '''key''' of the '''name:value''' pair to be read.
|p2_type=string|p2_name=pass|p2_desc=The pass phrase protecting the '''name:value''' pair.
|return_type=string
|return_text='''value''' corresponding to {{LSLP|name}}
|func_footnote
|func_desc=Reads a protected '''name:value''' pair from the datastore.
|func_footnote
|caveats=If the {{LSLP|pass}} parameter does not match, this function returns an empty string.
|spec
}}
|caveats
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteProtected]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
{{LSL DefineRow||[[llLinksetDataWriteProtected]]|}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataListKeys

2024-08-14T18:55:51Z

Peter Stindberg:

{{LSL_Function
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataListKeys
|p1_type=integer|p1_name=start|p1_desc=The first key to return.
|p2_type=integer|p2_name=count|p2_desc=The number of keys to return.
|return_type=list
|return_text=of the keys in the datastore, ordered alphabetically.
|func_footnote
|func_desc=The '''llLinksetDataListKeys''' function returns a list of up to {{LSLP|count}} keys in the datastore, starting at the one indicated by {{LSLP|start}}. If {{LSLP|count}} is less than 1, then all keys between {{LSLP|start}} and the end are returned. If {{LSLP|count}} minus {{LSLP|start}} exceeds the total number of keys, the returned list will be shorter than {{LSLP|count}}, down to a zero-length list if {{LSLP|start}} equals or exceeds the total number of keys.
|func_footnote
|spec
|caveats
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataDelete

2024-08-14T18:55:08Z

Peter Stindberg:

{{LSL Function/Headless
|default={{{default|}}}
|inject-2=
|summary=The '''llLinksetDataDelete''' and '''llLinksetDataDeleteProtected''' functions erases a '''name:value''' pair from the linkset's datastore.

When this function successfully removes a '''name:value''' pair a [[linkset_data]] event is triggered in all scripts running in the linkset with an action of [[Template:LSL_Constants_Linkset_Data|LINKSETDATA_DELETE]] and the '''name''' parameter set to the {{LSLP|name}} that was removed. The '''value''' parameter in the event is set to an empty string.

|func=llLinksetDataDelete|sort={{{sort|LinksetDataDelete}}}
|head={{LSL Function/Head
|func_id=|func_sleep=0|func_energy=10.0
|func=llLinksetDataDelete
|return_type=integer
|return_text=success or failure code.
|p1_type=string|p1_name=name|p1_desc=The key of the linkset '''name:value''' pair to be deleted.
|func_desc=Removes an unprotected '''name:value''' pair from the linkset's datastore. If the pair was created
}}{{LSL_Function/Head
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataDeleteProtected
|func_footnote
|func_desc=The '''llLinksetDataDeleteProtected''' function erases a protected '''name:value''' pair from the linkset's datastore.

|func_footnote
|return_type=integer
|return_text=success or failure code.
|p1_type=string|p1_name=name|p1_desc=The key of the linkset '''name:value''' pair to be deleted.
|p2_type=string|p2_name=pass|p2_desc=A pass phrase previously used to protect the '''name:value''' pair.
|spec
}}
|caveats=
* If the {{LSLP|name}} does not exist or the {{LSLP|pass}} does not match, no event is triggered.
|constants={{LSL Constants Linkset_Data Returns}}
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReadProtected]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
{{LSL DefineRow||[[llLinksetDataWriteProtected]]|}}
|also_events=
{{LSL DefineRow||[[linkset_data]]}}
|also_tests
|also_articles
|notes
|examples=<source lang="lsl2">// Simple blacklist management.

integer gDialogChannel;
integer gDialogHandle;
integer gManagingBlocks;

startDialog(key person)
{
gManagingBlocks = 0;
gDialogHandle = llListen(gDialogChannel, "", person, "");
llDialog(person, "\nSelect action", ["List blocks", "Add block", "Remove block"], gDialogChannel);
llSetTimerEvent(60);
}

stopDialog()
{
llSetTimerEvent(0);
llListenRemove(gDialogHandle);
}

default
{

on_rez(integer sp)
{
llResetScript();
}

state_entry()
{
gDialogChannel = (integer)(llFrand(-10000000)-10000000);
llListen(PUBLIC_CHANNEL, "", NULL_KEY, "");;
}

timer()
{
stopDialog();
}

touch_start(integer nd)
{
key toucherKey = llDetectedKey(0);
if (toucherKey == llGetOwner())
{
startDialog(toucherKey);
}
}

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

if (llGetAgentSize(id) == ZERO_VECTOR)
{
return;
}

if (channel == gDialogChannel)
{
stopDialog();
if (gManagingBlocks)
{
message = llStringTrim(message, STRING_TRIM);
if ((key)message)
{
if (gManagingBlocks == 1)
{
llOwnerSay("Addition request has been sent to the blacklist storage");
llLinksetDataWrite("blocklist:" + message, "1");
}
else
{
llOwnerSay("Removal request has been sent to the blacklist storage.");
llLinksetDataDelete("blocklist:" + message);
}
}
else
{
llOwnerSay("The UUID '" + message + "' appears to be invalid.");
}
startDialog(id);
}
else if (message == "List blocks")
{
list blocks = llLinksetDataFindKeys("^blocklist:", 0, 0);
integer listLength = llGetListLength(blocks);
llOwnerSay("Blacklist items: " + (string)listLength);
integer i;
while (i < listLength)
{
string record = llGetSubString(llList2String(blocks, i), 10, -1);
llOwnerSay("- secondlife:///app/agent/" + record + "/about" + " - " + record);
++i;
}
blocks = [];
startDialog(id);
}
else if (message == "Add block" || message == "Remove block")
{
string label = "add to";
gManagingBlocks = 1;
if (message == "Remove block")
{
gManagingBlocks = 2;
label = "remove from";
}
gDialogHandle = llListen(gDialogChannel, "", id, "");
llTextBox(id, "\nPlease specify one single avatar UUID you'd like to " + label + " the blacklist storage.", gDialogChannel);
llSetTimerEvent(60);
}
return;
}

if (llGetListLength(llLinksetDataFindKeys("blocklist:" + (string)id, 0, 1)) > 0)
{
llRegionSayTo(id, 0, "You're blacklisted.");
return;
}

llRegionSayTo(id, 0, "Hello there, secondlife:///app/agent/" + (string)id + "/about - your message: " + message);

}

linkset_data(integer action, string name, string value)
{
if (action == LINKSETDATA_RESET || action == LINKSETDATA_DELETE || action == LINKSETDATA_UPDATE)
{
llOwnerSay("Blacklist storage modified.");
}
}

}</source>
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataCountKeys

2024-08-14T18:54:29Z

Peter Stindberg:

{{LSL_Function
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataCountKeys
|return_type=integer
|return_text=number of keys used in the linkset store.
|func_footnote
|func_desc=The '''llLinksetDataCountKeys''' returns the number of unique keys that have been stored in the linkset's datastore.
|func_footnote
|spec
|caveats
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataAvailable]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

LlLinksetDataAvailable

2024-08-14T18:54:17Z

Peter Stindberg:

{{LSL_Function
|func_sleep=0.0|func_energy=10.0
|func=llLinksetDataAvailable
|return_type=integer
|return_text=number of bytes available in the linkset store.
|func_footnote
|func_desc=The '''llLinksetDataAvailable''' returns the number of bytes available in the linkset's datastore.
|func_footnote
|spec
|caveats
|helpers
|also_functions=
{{LSL DefineRow||[[llLinksetDataCountKeys]]|}}
{{LSL DefineRow||[[llLinksetDataDelete]]|}}
{{LSL DefineRow||[[llLinksetDataDeleteFound]]|}}
{{LSL DefineRow||[[llLinksetDataFindKeys]]|}}
{{LSL DefineRow||[[llLinksetDataListKeys]]|}}
{{LSL DefineRow||[[llLinksetDataRead]]|}}
{{LSL DefineRow||[[llLinksetDataReset]]|}}
{{LSL DefineRow||[[llLinksetDataWrite]]|}}
|also_events
|also_tests
|also_articles
|notes
|cat1=Script
|cat2=LinksetData
|cat3
|cat4
}}

User talk:Rhet0rica Resident/RLVa Protocol

2024-07-25T14:54:18Z

Peter Stindberg: Created page with "Awesome, thank you! -- ~~~~"

Awesome, thank you!

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 07:54, 25 July 2024 (PDT)

User talk:GoSpeed Racer

2024-07-22T15:52:49Z

Peter Stindberg: Created page with "Welcome to the wiki, neighbor. -- ~~~~"

Welcome to the wiki, neighbor.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 08:52, 22 July 2024 (PDT)

Talk:How to Earn Linden Dollars in Second Life

2024-07-20T08:35:03Z

Peter Stindberg: Pointing out the page is a blatant promotion page for traffic tools.

Is it just me, or is this whole page primarily geared at promoting traffic tools for SL? The topic is so wide, it deserves a structural in-depth approach. Instead, this page uses exactly TWO sentences on saying that you can work a job or start your own business, yet paragraph after paragraph are used to mention games (traffic tools).

Not to mention an edit history where the majority of editors did not even bother to create their own "about" page and whose edits solely focus on this page (or traffic related pages). This seems all rather fishy to me.

Yes, I know, I can change it. Probably will, if I get annoyed enough. For now some feedback would be welcome.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 01:35, 20 July 2024 (PDT)

User talk:Thunder Rahja

2024-07-19T19:08:16Z

Peter Stindberg: Created page with "Welcome to the wiki! -- ~~~~"

Welcome to the wiki!

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 12:08, 19 July 2024 (PDT)

Talk:LlFindNotecardTextSync

2024-07-01T20:32:08Z

Peter Stindberg: Created page with "Oh, fancy. We're getting slowly to the point where we can sensibly use notecards as ROM. -- ~~~~"

Oh, fancy. We're getting slowly to the point where we can sensibly use notecards as ROM.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 13:32, 1 July 2024 (PDT)

Limits

2024-06-12T16:12:05Z

Peter Stindberg: Added LSD and Experience memory limits

<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 '''Edit My Outfit'''.
** 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.
** With the introduction of the Bento armature, there are 47 attachment points available.
** With the introduction of Animesh, there is a limit of 1 Animesh attachment for Basic & Plus members, 2 if the resident has Premium or Premium Plus.
* '''Max. attachment position''' - 3.5m in a sphere around <0, 0, 0>.
* '''Max. # of clothing layers''' - 60 including alpha, tattoo, shoe base, physics, socks, gloves, undershirt, underpants, shirt, pants, jacket, skirt
** On viewers before Second Life Release 3.7.29.301305, the potential total was still 60, but limited to 5 items of each type.
** In any case, only one each of shape, skin, eyes and hair base may be worn. These 4 basic body parts are in addition to the 60 clothing layers.
* '''Max Clothing Texture''' - 1024x1024 px (except 128x128 px for eyes) - Server Side Appearance (and legacy baking on outside grids) will downsize larger textures*. (Support for 2K textures & Bakes on Mesh is in development but not yet supported)
* '''Max. unassisted fly height''' - Stable hover at current ground elevation ''plus'' 5020m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Traditionally, most women's shoes were designed for a size 0 (zero) foot. Men's generally scale up to 14. Newer items (mesh and some sculpted) replace the system feet or conform to the avatar's shape, so adjustments may be necessary.
** 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''' - 6 teleports per minute

== [[Animation]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Length of animation
| n/a
| {{no|60.0 seconds}}
| Limited by length or Size, whichever is reached first
| n/a
|-
||Size of Animation
| n/a
| {{no|{{HoverText|250,000 bytes|250 KB (decimal), 244 KB (binary)}}}}
| Limited by length or Size, whichever is reached first. Size is after conversion to [[Internal Animation Format|.anim]]. {{KBtip|custom=Tip for Blender users:|1=You can use a built-in function called "''Decimate''" to simplify your animation. See [https://www.youtube.com/watch?v=lScwEYJZy1M this tutorial]}}
| [[Internal Animation Format]]
|-
||Distance an Animation Can Travel
| {{no|-5 meters (per axis)}}
| {{no|+5 meters (per axis)}}
| 10 meters per axis cumulatively (travelling from -5 to +5).
| n/a

|-
||animation priority
| {{no|0}}
| {{no|.bvh: 4, [[Internal Animation Format|.anim]]: 6}}
| [[Internal Animation Format|.anim]] uses per-joint priorities, meaning it's possible to have a mix of joint priorities in the same animation.
| [[Animation_Priority|Animation Priority]]
|-
||Number of unique joints per animation
| n/a
| {{no|216}}
| [[Internal Animation Format|.anim]], unlike .bvh, uses a flat structure, meaning that only the bones animated are stored, and bones which would otherwise be kept by .bvh (to keep hierarchy structure) are deleted.
| n/a
|-
||Number of simultaneous animations playing
| n/a
| {{no|30}}
| n/a
| n/a
|}

== [http://community.secondlife.com/t5/English-Knowledge-Base/Build-Tools/ta-p/700039 Building] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||[[Prim]] dimensions
| {{no|<0.01, 0.01, 0.01>}}
| {{no|<64.0, 64.0, 64.0>}}
| Used to be <10.0, 10.0, 10.0> prior to Second Life Server version 11.08.17.238770
| [[llSetScale]], [[PRIM_SIZE]] and [[Megaprim]]
|-
||Number of prims in a linkset
| n/a
| {{no|256 prims}}
| Used to be 255 prior to Second Life Server version 1.26
| n/a
|-
||Linking distance
| n/a
| {{no|64 meters}}
| distance has changed on [https://community.secondlife.com/blogs/entry/13626-coming-soon-server-release-202306/ 2023.06 update]. The old max distance was 54 meters.
| n/a
|-
||Local offset (avatars)
| n/a
| {{no|1000 meters per axis}}
| Unlike regular [[Linkability_Rules|Linkability Rules]] for linksets, an avatar sitting on an object may be moved significantly further by scripts.
| [[llSetLinkPrimitiveParams]] with [[PRIM_POS_LOCAL]]
|-
||[[Mesh/Mesh_physics#Physics_Resource_Cost|Physics cost]] for a physical object
| n/a
| {{no|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.
| [[OBJECT_PHYSICS_COST]]
|-
||Build or rez height
| n/a
| {{no|4096.0 meters}}
| 768.0 meters for Viewers prior to version 1.20
| n/a
|-
||Prim name length
| n/a
| {{no|63 bytes UTF-8 [[String|string]]}}
| same limit for {{LSLGC|Avatar/Name|avatar names}}, although the character set for avatar names is significantly limited.
| n/a
|-
||Prim description length
| n/a
| {{no|127 bytes UTF-8 [[String|string]]}}
| n/a
| n/a
|-
||Temporary prims' lifetime
| n/a
| {{no|up to around 60 seconds}}
| depends upon when the next garbage collector cycle is
| n/a
|-
||Number of temporary prims
| n/a
| {{no|RegionPrimLimit - NumberOfPrimsInRegion + Minimum(0.5*RegionPrimLimit, 1000)}}
| n/a
| n/a
|-
||Length of hovertext
| n/a
| {{no|254 bytes UTF-8 [[String|string]]}}
| n/a
| [[llSetText]] and [[PRIM_TEXT]]
|}

== [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/ Lighting] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of projectors rendered at full detail
| n/a
| {{no|2}}
| Only the 2 projectors closest to an object will cause it to cast shadows.
| [https://community.secondlife.com/knowledgebase/english/lighting-and-shadows-r331/#Projectors Knowledge Base > Lighting > Projectors]
|-
||Number of lights rendered on Alpha Blended surfaces
| n/a
| {{no|8}}
| 8 including the Sun and Moon. The viewer will attempt to select the "most significant" lights to render, however these blended surfaces will look different as a result of these lighting limitations.
| [[Alpha Modes Do's and Don'ts#Alpha_blending|Alpha Blending]]

|}

== [[Communication]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Whisper distance
| n/a
| {{no|10 meters}}
| <code>/whisper</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Chat distance
| n/a
| {{no|20 meters}}
| text spoken as a "chat" step '''within gestures''' cannot be shouted or whispered. /whisper and /shout ''can'' be used in the "Replace with" field.
| n/a
|-
||Shout distance
| n/a
| {{no|100 meters}}
| <code>/shout</code> as the first few characters in a message can be used in viewer-2-code based viewers in local chat.
| n/a
|-
||Length of a chat message and whether or not it is truncated
| {{no|1 byte or single-byte character}}
| {{no|1024 bytes or single-byte characters}}
| Limit does not apply to instant messages via [[llInstantMessage]] and communication between IM and email, the limit there is 1023 bytes or single-byte characters.
The viewer-to-server communication on ''negative'' channels is truncated to 254 bytes, and on ''positive'' channels, to 1023 bytes. These limits do not affect communication between scripts.
| [[llInstantMessage]]
|-
||Maximum events
| n/a
| {{no|64 events}}
| Events are stored in a 64 bit bitmap. Events happening when the bitmap is full, will get discarded.
| n/a
|-
||Number of offline messages
| n/a
| {{no|Capped at 15 messages for Basic & Plus members, 80 for Premium members, and 160 for Premium Plus members.}}
| Number of offline messages (involving [[IM|IMs]], inventory offers, group notices, group invitations) received before messages get capped. Note: If autoAcceptNewInventory (debug setting) is set to TRUE (the default is FALSE), then all inventory offers, even above the cap allowed by membership, go directly to inventory and do not count against the cap on offline messages.
| [[IM]] - [https://community.secondlife.com/blogs/entry/2559-group-limits-update-no-changes-for-basic-members/ Blog Post]
|-
||Length of a properly delivered email reply to an [[IM]]
| n/a
| {{no|1023 bytes or single-byte characters}}
| n/a
| n/a
|-
||Time after which a reply to an [[IM]] can be sent via email.
| {{no|when receiving the IM via email.}}
| {{no|5 days after receiving the offline IM via email.}}
| n/a
| [https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing Second Life Blogs]
|-
||Time period for which [[IM|IMs]] are stored within Second Life.
| n/a
| {{no|31 days after receiving the [[IM]]}}
| [[User:Torley_Linden|Torley Linden]] confirmed this with [[User:Kelly_Linden|Kelly Linden]]
| n/a
|-
||Number of [[IM|IMs]] sent by an object within an hour
| n/a
| {{no|5000 per hour}}
| n/a
| n/a
|}

== [[Gesture]]s ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Shortcut key mappings
| n/a
| {{no|33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.}}
| n/a
| [[All_keyboard_shortcut_keys]] and [http://community.secondlife.com/t5/English-Knowledge-Base/Keyboard-shortcuts/ta-p/1086557 the knowledge base]
|-
||Chat step length
| n/a
| {{no|127 bytes or single-byte characters}}
| n/a
| n/a
|-
||Wait time
| n/a
| {{no|3600 seconds (which is one hour)}}
| n/a
| n/a
|-
| Maximum steps data
| n/a
| {{no|1000 bytes}} of packed data; saving with more data returns the message "Gesture save failed. This gesture has too many steps. Try removing some steps, then save again." Shorter text, for example, will allow more steps.
| n/a
| n/a
|-
||Length of included assets
| n/a
| see sections for [[#Animation|animation]], [[#Sound|sound]]
| n/a
| n/a
|}

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42 for Basic members, 50 for Plus members, 70 for Premium members, 140 for Premium Plus members.
** After downgrading from a higher limit membership to a lower one, you may not join any new groups until you are a member of fewer than your current subscriptions's group limit. For example, if you downgrade from Premium (70 groups allowed) to Basic (42 groups allowed), you can't join any new groups until you're a member of fewer than 42 groups.
** 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.
* '''Maximum Age of a Group Notice:''' 14 days.

== [[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 number of accounts that an inventory item can be shared with at once:''' The limit is unknown, but tests show that it is more than 35. No documentation has been found. One third-party viewer developer says that the code doesn't seem to look for a limit. It just builds the list and sends it to each avatar individually.
* '''Maximum number of inventory items that can be contained in a prim:''' 10,000
* '''Maximum characters in an inventory item name:''' 63
* '''Maximum notecard line:''' None, but scripts can only read the first 1024 bytes (was 255 bytes before server version [https://releasenotes.secondlife.com/simulator/2021-10-25.565008.html 2021-10-25.565008]).
* '''Maximum notecard size:''' 65,536 bytes

* '''Number of items in the Library:''' 3,500 as of 2019-08-10
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.
* '''Maximum number of inventory items displayed in a single inventory folder:''' Several thousand. 
** This was discussed during [http://wiki.secondlife.com/wiki/Simulator_User_Group/Transcripts/2011.03.08] "the folder will load up to the limit number of items, and remaining ones won't show up in the viewer. you still own them, they aren't lost, but they will be hidden until the folder size is reduced."
** There is no specified limit for total avatar inventory, very large folders can be split.
** There was discussion in the Third Party Developers' UG (4/10/2015) meeting about new inventory and login problems from having large numbers of items in a single folder. AISv3 ''removed'' server-side limits on the number of items in a folder. Flat inventories are bad. No one is certain at what number of items in a folder cause a login problem. The fix is to clear the inventory cache (not the viewer cache) and log into a deserted, empty region then move inventory items into folders and sub-folders. - The problem appears at different a number of items depending on your computer and connection speed. Hopefully being on an empty region will give one enough edge to get logged in and do some corrective work before being dropped. If not, you will need to contact support for help. They will divide large folders into smaller groups so you can log in.

== [[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:''' Linden Concierge policy states a 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]]. However, the technical maximum limit is 35 characters, and exceptions to the concierge policy do exist (e.g [http://maps.secondlife.com/secondlife/Sandbox%20-%20Weapons%20testing%20%28no%20damag/128/128/2 Sandbox - Weapons testing (no damag] and [http://slurl.com/secondlife/X/128/128/24 X])
* '''Ban line height for "no entry" or "pay to access"''' (in other words, "allow public access" is turned off, or "allow group access" is turned on, in the parcel options) is the parcel's ground elevation ''plus'' 50 meters (except, if the region has been set to "Block Parcel Fly Over" in which case the access controls extend to at least 4096 meters). If a user is '''explicitly banned by name''', the height is the parcel's ground elevation ''plus'' 5000 meters. On current viewers this is visible to the full extent.
* '''Maximum prims in a [[Land#Region|region]]:'''
** "Mainland / Full Region" and "Linden Homes / Full Region": 22,500
** Full Regions in private estates: 20,000 with an [https://community.secondlife.com/t5/Featured-News/Upgrade-Your-Full-Private-Region-to-30-000-Land-Impact-Today/ba-p/3086162 option for 30,000]
** Homestead: 5,000
** Openspace : 1,000
:: To check a region's capacity, use <tt>[[llGetEnv]]("region_max_prims")</tt>.
::''(Region types are as found in the General tab of World > About Land, or returned by ''<tt>llGetEnv("region_product_name")</tt>'')''
* '''Maximum auto return value''': Besides {{code|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 regions cannot be terraformed, including: Bay City regions, Boardman, Brown, De Haro, Horizons, Kama City regions, Nautilus City regions, Nova Albion regions, and Shermerville regions.
** [http://community.secondlife.com/t5/English-Knowledge-Base/Linden-Homes/ta-p/700103 Linden Homes] do not allow terraforming.
** 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, 255 meters by using a {{code|*.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 {{code|*.raw}} file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 20 estate managers, 500 allowed Residents, 63 allowed groups, and 750 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Maximum number of agents'''
** [https://second.life/eventregions Event Regions]: 175 agents
** Full region: 100 basic account users plus 10 additional available to premium accounts. (Typically set to 40 on mainland, 55 on Linden Homes regions, 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 (plus 5 additional available to premium accounts)
** [[Land#Openspace|Openspace]]: 10 (plus 2 additional available to premium accounts)
* '''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

== [[Mesh]] ==

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Number of vertices
| n/a
| {{no|65536 vertices per LOD}}
| per [[mesh]] - See [[Talk:Limits#Mesh_Limits|discussion page]]
| n/a
|-
||COLLADA file size
| n/a
| {{no|8 MB}}
| Maximum mesh asset size after compression, roughly equivalent to a 256 MB Raw COLLADA file.
| n/a
|-
||Bone influence weights per vertex
| n/a
| {{no|4}}
| n/a
| n/a
|-
||Bone influence weights per mesh
| n/a
| {{no|110}}
| some folk have reported needing to go as low as about 99 in rare cases
| n/a
|-
||Number of materials per mesh
| n/a
| {{no|8}}
| n/a
| n/a
|-
||Number of materials per face
| n/a
| {{no|1}}
| n/a
| n/a
|-
||Physics weight for a vehicle
| n/a
| {{no|32.0}}
| n/a
| n/a
|-
||Maximum number of triangles for Animesh
| n/a
| {{no|100,000}}
| Server uses estimated triangles (streaming cost calculated), not visual triangles.
| [[Animesh User Guide|Animesh_User_Guide]]
|}

===User Found Temporary Mesh Limits:===
''Because of an apparent bug in the importer stay within these limits.''
* 174,752 triangles, beyond which additional triangles will appear as holes.
* The 64k vertices per material is pre-empted by a limit of 21,844 triangles per material, which is presently reported as {{Jira|BUG-1001}}. (4/2014 - See [[Talk:Limits#Mesh_Limits|discussion page]])

:: The import process will continue making new materials beyond 8 x 21,844 (=174,752) triangles, but the extra triangles then get dropped by the limitation to 8 materials, causing holes in the resulting object. Over the 21,844-triangle limit, the vertex count will start to climb steeply, even with smooth shading, because the materials get highly interspersed. So the same vertices have to appear in multiple material lists. So, the moral of the story is to stay below 21,844 triangles per material, for now, if you want to avoid some unexpected effects.

::Since viewer release 3.8.4, processing of meshes in the Collada file that have faces assigned to more than 8 materials has changed. Instead of simply dropping the extra material faces, the uploader now creates a new object to accommodate them. The result is that the single mesh is divided into multiple objects (prims) in a linkset. Thus, the limitation to 8 materials is removed as far as input is concerned, but still applies to each of the resulting linked objects actually uploaded. As a consequence, it is now possible to upload a mesh with more than 174,752 triangles, although it will be divided into multiple objects.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.

== 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] = 231 − 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:''' 4096
** This used to be much higher, but is clamped in late model viewers.

== [[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

== [[Lag|Performance]] ==

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

'''*''' Only until your framerate reaches your monitor's refresh rate, after this point there will be very little benefit.

== [[Scripting]] == 

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls will keep running when you fly down or enter a no-script parcel. (If scripts are disabled in the region debug panel, they will not run at any height.)
* '''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 (that's a viewer limit and can be changed in the config file 'panel_script_ed.xml').
* '''Maximum script memory size (LSO)''' - 16384 bytes.
* '''Maximum script memory size ([[Mono]])''' - 65536 bytes (the maximum memory available to Mono scripts can be constrained via [[llSetMemoryLimit]]).
* '''Maximum memory for [[:Category:LSL LinksetData|Linkset data]]''' key/value pairs - 128 KiB
* '''Maximum memory for [[:Category:Experience Tools|Experience]]''' key/value pairs- 128 MiB
* '''Maximum active [[llListen|listeners]] per script''' - 65.
** '''Usable channel for each listener''' - ''min.'' -2147483648, ''max.'' 2147483647, including the following special channels: [[PUBLIC_CHANNEL]] ''and'' [[DEBUG_CHANNEL]].
* '''Maximum number of scripts that can be rezzed at once''' – 1,000. (Refer to [https://community.secondlife.com/knowledgebase/english/building-tips-r13/)|Building Tips, by Jeremy Linden].)
* For specific scripting limits, look up calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==



{{KBtip|Second Life will accept sounds that are encoded following "[https://en.wikipedia.org/wiki/Compact_Disc_Digital_Audio CD Quality]" encoding presets present in many {{Abbr|DAW|Digital Audio Workstation}}s.}}

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Limit affects'''
! '''Lower limit'''
! '''Upper limit'''
! '''Comment'''
! '''More coverage'''
|-
||Sound length
| n/a
| {{no|less than 30 seconds}}
| 29.99 seconds is fine, but 30.0 will fail to upload. See the knowledge base article.
| '''[https://community.secondlife.com/knowledgebase/english/uploading-assets-r75/ Uploading Assets]'''
|-
||Bit depth
| n/a
| {{no|16 bit}}
| n/a
| n/a
|-
||Sample rate
| n/a
| {{no|44.100 kHz}}
| n/a
| n/a
|-
||Audio channels
| n/a
| {{no|1 channel (mono)}}
| Channels will be '''merged''' at upload time for dual-channel (stereo) audio.
| 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:

=== Second Life Viewer 3.6 ===

* '''Search > Classifieds thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (159×120 pixels)
* '''Search > Classifieds expanded > More Info''' - native aspect ratio
* '''Search > Destination Guide thumbnail''' - ~3:2 (101×69 pixels)
* '''Search > Destination Guide expanded''' - ~4:3 (159×120 pixels)
* '''Search > People''' - 1:1 (100×100 pixels)
* '''Search > Places expanded''' ~4:3 (159×120 pixels)
* '''Place Profile''' - ~3:2 (290×197 pixels)
* '''About Land > Options tab''' - ~4:3 (195×150 pixels)
* '''Profile > Picture''' - native aspect ratio; thumbnail cropped to 72×72 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Real world picture''' - native aspect ratio; thumbnail cropped to 45×45 pixels; zoomed uncropped up to 300×300 pixels
* '''Profile > Picks thumbnail''' - ~16:9 (~516×~270 pixels as measured on screen; the ratio seems closer to 16:8.5)
* '''Profile > Pick expanded''' - Unknown as of 2022-11-13 (viewer 6.6.7.576223); the Pick image does not expand.

=== 1.x Series Viewers ===
(official Viewer up to 1.23.5, still used by some [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pixels)<ref>As of {{#time: r|2024-02-26T18:00:00}}, this seems to be one of the very few sizes supported by the [[Picture Service]].</ref>
* '''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.]]

=== All Viewers ===

* '''Maximum texture size''' - 2048×2048 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** 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 2048×2048.

* '''Minimum texture size''' - 4×4 pixels
** This means that there are ten possible image dimensions: 4, 8, 16, 32, 64, 128, 256, 512, 1024 & 2048 pixels, either horizontal or vertical.

* '''Texture resizing'''
** Uploaded textures will be resized to the dimensions above.
** Each dimension is resized independently (for instance, a 1024 x 999 image will be resized to 1024 x 1024).
** A dimension that is already a power of two will not be resized.
** The uploader “prefers” to round down rather than up. The threshold for rounding down/up is .75 of the distance between powers of two.
*** For example, given a dimension of x, if x / 512 is larger than 1.75, x will be resized to 1024, else 512.
*** Another example: If x / 256 is larger than 1.75, x will be resized to 512.

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

=== Notes ===
In general, 1 byte is enough to contain one character.<ref>Except in .NET-based applications, and those related to .NET development — which is the case of the SL viewer — which essentially use UTF-16 everywhere, i.e., every character is encoded in ''two'' bytes, not just one.</ref>

----
{{References}}

LlDerezObject

2024-06-08T06:28:14Z

Peter Stindberg: Copy/paste error by Rider :p

{{LSL_Function
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llDerezObject|return_type=integer
|p1_type=key|p1_name=id|p1_desc=The ID of an object in the region.
|p2_type=integer|p2_name=flag|p2_desc=Deletion options.
|func_desc=Derezzes an object previously rezzed from within the object containing the script.
|return_text=Returns success or failure.
|spec=
Deletes, or marks temp, an object that was previously rezzed by this script. The object must have been previously rezzed from a script within this object.
If the object is successfully deleted this function returns TRUE, if it fails for any reason it returns false.
|caveats=
* The targeted object's rezzer must be the same as the object hosting this script
* The target must not be an attachment
* The target must be copyable
* The target's owner must be the same as the script's owner.
* When marking an object as temporary, the object must not contribute to the navmesh.
|examples
|helpers
|constants=
{{{!}} class="sortable" {{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! Constant
! Value
! class="unsortable" {{!}}Description
{{!}}-
{{!}} [[DEREZ_DIE]]
{{!}} 0
{{!}} Immediately delete the object.
{{!}}-
{{!}} [[DEREZ_MAKE_TEMP]]
{{!}} 1
{{!}} Mark the object as temporary so that the simulator will remove the object at a later time.
{{!}}}

|also_functions
|also
|notes
|cat1=Script
|cat2
|cat3
|cat4
}}

User talk:Ivanova Shostakovich

2024-06-06T17:18:17Z

Peter Stindberg:

== Collision Caveat ==

You added "Will not detect collisions between the [[avatar]] sitting on the task." but it doesn't make sense. Do you mean: "Will not detect collisions while an [[avatar]] is sitting on the task." or "Will not detect collisions between the [[avatar]] sitting on the task and the task." or something else altogether? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 17:59, 21 January 2010 (UTC)

== Welcome back to the wiki ==

It's been a while! Glad to see you back on the wiki.

-- [[User:Peter Stindberg|Peter Stindberg]] ([[User talk:Peter Stindberg|talk]]) 10:18, 6 June 2024 (PDT)

Project talk:About

2024-05-10T21:56:21Z

Peter Stindberg: How to get write access for the wiki.