Misplaced Pages

Linden Scripting Language: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 04:38, 23 March 2015 edit1.220.41.12 (talk) →Default LSL script← Previous edit Latest revision as of 16:39, 13 June 2024 edit undoMika1h (talk | contribs)Autopatrolled, Extended confirmed users, File movers, New page reviewers, Rollbackers119,574 edits ←Changed redirect target from Second Life to Second Life#ContentTag: Redirect target changed 
(14 intermediate revisions by 11 users not shown)
Line 1: Line 1:
#redirect ]
{{Primary sources|date=December 2011}}
{{infobox programming language
| name = Linden Scripting Language (LSL)
| paradigm =
| year =
| influenced by = ]
| developer =
| latest release version =
| latest release date =
| latest preview version =
| latest preview date =
| typing = ]
| operating system = ]
| file ext =
| license =
| website = {{URL|https://wiki.secondlife.com/LSL_Portal}}
}}
'''Linden Scripting Language''', or LSL, is the ] used by residents of ] ('''SL'''), a ] by ]<ref>. Wiki.secondlife.com (2013-07-01). Retrieved on 2013-09-21.</ref> and similar virtual worlds.


{{Rwh}}
LSL has a ] similar to ] and allows objects to control the behavior of in-world objects of Second Life from the Internet via email, ], and most recently, ] requests.
{{R to section}}

==LSL design==
Linden Scripting Language is a state-] ], in the sense of a ].<ref>. Wiki.secondlife.com (2011-08-08). Retrieved on 2013-09-21.</ref>
A script consists of variables, function definitions, and one or more named states. Each state contains a description of how to react to events that occur while the program is within that state. The system sends to the script, such as timers, movement, chat (from other agents), email, and collisions (with objects in the virtual world). Scripts can change most aspects of the state of the object and communicate with other objects and agents. As soon as a script is added to an object, and turned on, it begins to execute.

A script is tightly bound to the concept of virtual-world '']'' (in the 3D modeling sense rather than in the ] sense) called ''primitives''. An object in Second Life represents something like a chair or a wall, or possibly something invisible. Multiple scripts may be placed inside an object, where they all execute simultaneously.

There are over 300 library ]s available.<ref>. Wiki.secondlife.com (2012-09-08). Retrieved on 2013-09-21.</ref> Users can also define additional functions. LSL is a ]<ref>. Wiki.secondlife.com (2012-04-27). Retrieved on 2013-09-21.</ref> that is compiled to ] before runtime execution in a ] ('''VM''') on one of Linden Lab's servers.

LSL's native ]s includes ],<ref>. Wiki.secondlife.com (2012-12-22). Retrieved on 2013-09-21.</ref> ],<ref>https://wiki.secondlife.com/Category:LSL_Float</ref> ],<ref>. Wiki.secondlife.com (2013-05-19). Retrieved on 2013-09-21.</ref> keys(]),<ref>. Wiki.secondlife.com (2013-09-11). Retrieved on 2013-09-21.</ref> ] (used for 3D coordinates and ] color expression),<ref>. Wiki.secondlife.com (2011-10-05). Retrieved on 2013-09-21.</ref> and ]s (]s).<ref>. Wiki.secondlife.com (2008-10-24). Retrieved on 2013-09-21.</ref> There are also heterogeneous lists. There are no arrays; multiple list functions are used to adapt programs requiring array structures.<ref>. Wiki.secondlife.com. Retrieved on 2013-09-21.</ref> There is no built-in persistent data storage, such as a file or database (though users have found various workarounds for this like storing data in various data fields of the items containing scripts). On the other hand, scripts continue to run even when a user is not logged in, and if an object is saved (taken into inventory), and then re-introduced into the World later, it still maintains its previous state. In addition, the mechanisms for communicating via HTTP can be used to store a state externally.

Some functions in LSL have built-in delays, which range from a 0.1-second delay when (for example) requesting string data from a notecard;<ref>https://wiki.secondlife.com/Category:LSL_Notecard An ] data storage medium mainly used for text.</ref> to a 20-second script pause after sending an ]. The delays help prevent developers from writing LSL scripts that could overtax system resources. Memory available to LSL scripts (when compiled as ]) is capped at about 64 ], which places a practical limit on how much a single script can do, however the ability to use multiple scripts and to call scripts from another script allows the user to pragmatically work around this 64 KiB cap.

==Permission system==
Certain actions in LSL require permissions:
* take money from agent's account
* take agent's controls
* start or stop Animations on agent
* attach/detach from agent
* change links
* track the agent's camera position and rotation
* control the agent's camera

The permission system, however, is an issue for scripts owned by the land owner: those scripts can modify the parcel settings without requiring permissions. A malicious script can unsit avatars, ban and unban avatars, destroy the terrain that includes returning of objects by letting them fall out of the World, and gather the ip addresses of avatars by manipulating the media settings for that avatar.

==Default LSL script==
The default script, "Hello, Avatar",<ref>. Wiki.secondlife.com (2012-10-06). Retrieved on 2013-09-21.</ref> a ] that speaks (streams message to local chat ("heard" (printed) by all viewers (]s) within 20 meters <sup>(3D virtual environment)</sup> of the task)) when the script is first saved, initialized or reset (in this case, since the command is in the default "state", the first to be run on initialization) or 'touched' (a simple user interaction usually initiated using a mouse click), looks like:

<source lang="lsl2">
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
}
touch_start(integer total_number)
{
llSay(0, "Touched BB.");
}
}
</source>

==Mono==
The revised version of Second Life's scripting virtual machine is based on ], the open source implementation of the Microsoft.NET framework. The Mono '''VM''' was introduced to several ] ('''sims''') on the Second Life ] ] for compatibility testing on 29 January 2008 and later that year on 20 August 2008 Linden Lab started deploying it on the production grid<ref>. Blog.secondlife.com. Retrieved on 2013-09-21.</ref> - with the entire production grid updated to use it on 29 August 2008.

While the LSL scripting language remained the same, scripts executed on the Mono underpinnings were up to 220<ref>https://jira.secondlife.com/browse/SVC-1341</ref> times faster in execution, but at the cost of a somewhat higher overhead when creating (rezzing) scripted objects and moving them from '''sim''' to '''sim'''.<ref>https://jira.secondlife.com/browse/SVC-3895</ref>

==More complex example script==

Below is an example of a relatively simple LSL script, that when placed in a '''primitive''' along with a selection of ], users may select the sound files to be played in series. This scripting is required to play full length songs in Second Life, as the sound file length is limited to a maximum of 10 seconds per clip at upload to '''SL'''.

<small><source lang="lsl2">
// This list is all you need to edit. List the names of the songs (each collection of sound files that makes one song)
// followed by the length of those sound clips (each song should contain clips of equal length)
// The list should be structured like so -
// list songs = ;
// The names of the songs must be identical to some part of the sound files used for that song like so -
// In the prim inventory (along with this script) -
// Box_Of_Rain_wav_1
// Box_Of_Rain_wav_2
// Box_Of_Rain_wav_3
// Servant 1
// Servant 2
// Servant 3
// In the script -
// list songs = ;
// The script will play the clips in alpha/numerical order so name them wisely.
list songs = ; // YUP! EDIT THIS BIT ;-)

//////////// No editing is required below here ////////////

// Global variables must be declared above any functions created and above the first "default" state.
integer volume = 10; // All variables (global or local) must have their type declared on creation
integer lis_count;
integer playing;
integer busy; // Values need not be applied to variable at creation
integer part;
integer lis;
integer sl;
float delay;
list cancel = ;
list playlist;
list waiting;
list song;
string vol_str = "Volume";
string song_str = "Songs";
string song_name;

// Variable names (as well as function names and state names) must begin with a letter (upper or lower case) or any number of underscores.
// Variable names cannot begin with a numeral, but they may contain numerals as any other character.

// User created functions can be created by simply naming the function.
// Functions that return a value, must have the value type declared as the type for the function.
// Arguments passed to the function must have their types declared. the type of data passed to the function must match the argument type.
list StrideOfList(list src, integer stride, integer start, integer end)
{
list l = ;
integer ll = llGetListLength(src);
if(start < 0)start += ll;
if(end < 0)end += ll;
if(end < start) return llList2List(src, start, start);
while(start <= end)
{
l += llList2List(src, start, start);
start += stride;
}
return l;
}
list Volumes(integer vol)
{
integer v = 0;
list l = ;
do
{
if(v != vol)
l += ;
}
while((++v) <= 10);
return l;
}
PageOne(key k, integer c)
{
llDialog(k, "\nAdjust the volume or select a song to play?", + cancel, c);
}
PlaySong(string n)
{
song = ;
integer c = -1;
string name = "";
do
{ // Functions may be nested and used inline where values are returned (the values need not be stored to a variable for use).
if(llSubStringIndex((name = llGetInventoryName(INVENTORY_SOUND, (++c))), n) != -1)
song += ;
}
while(name);
delay = llList2Float(songs, (llListFindList(songs, ) + 1));
if((sl = llGetListLength(song)))
{
llPreloadSound(llList2String(song, (part = 0)));
if(sl > 1)
llPreloadSound(llList2String(song, 1));
playing = FALSE;
llSetTimerEvent(0.01);
}
}
integer Chan()
{
return llRound((llFrand(-5000000.0) + -500000.0));
}
float ScaleVol(integer v)
{
return (v * 0.1);
}
Listen(integer c, key a)
{
lis = llListen(c, "", a, "");
}
RemoveListen(integer b)
{
llListenRemove(lis);
lis_count = 0;
if(b)
busy = FALSE;
lis = 0;
}
SetListenTimer(integer p)
{
if(p)
while(((++lis_count) * llRound(delay)) < 30);
else
{
lis_count = 1;
llSetTimerEvent(30.0);
}
}
integer CheckWaitingRoom(integer c)
{
if(waiting)
{
key a = llList2Key(waiting, 0);
if(!c)
{
RemoveListen(0);
Listen((c = Chan()), a);
SetListenTimer(playing);
}
PageOne(a, c);
waiting = llDeleteSubList(waiting, 0, 0);
return 1;
}
return 0;
}

// All scripts must have a default state.
// However many other states a script may have, the default state must be uppermost in the script (below global vars and functions).
default
{
on_rez(integer param) // Event names are written in all lower case letters. Some contain underscores.
{ // If an event is passed any values as it is triggered, those values will be of specific types.
// Writers can choose the name for the variable, but not the type.
// Even if the data contained in the variables passed to the event are not used, the event must contain reference to that data.
llStopSound();
llResetScript();
}
changed(integer change)
{
if(change & CHANGED_INVENTORY)
llResetScript();
}
touch_start(integer nd)
{
while(nd)
{
key agent = llDetectedKey(--nd);
if(!busy)
{
busy = TRUE;
integer channel = Chan();
SetListenTimer(playing);
Listen(channel, agent);
PageOne(agent, channel);
}
else
{
list a = ;
if(llListFindList(waiting, a) == -1)
waiting += a;
}
}
}
listen(integer chan, string name, key id, string msg)
{
if(msg != llList2String(cancel, 0))
{
SetListenTimer(playing);
if(msg == vol_str)
{
llDialog(id, "\nChange the volume?\nThe current volume is set at \"" + ((string)volume) +
"\"", cancel + Volumes(volume), chan);
return;
}
if(msg == song_str)
{
string current = "";
if(playlist)
{
current = "\n\nThe songs currently queued are\n\"" + llList2String(playlist, 0) +
"\" (currently playing)";
if(llGetListLength(playlist) > 1)
current += "\n\"" + llDumpList2String(llList2List(playlist, 1, -1), "\"\n\"") + "\"";
}
llDialog(id, llGetSubString(("\nSelect a song to play?" + current), 0, 500), cancel +
StrideOfList(songs, 2, 0, -1), chan);
return;
}
if(llListFindList(Volumes(volume), ) != -1)
{
llAdjustSoundVolume(ScaleVol((volume = ((integer)msg))));
PageOne(id, chan);
return;
}
if(llGetListLength((playlist += )) == 1)
PlaySong((song_name = msg));
}
if(CheckWaitingRoom(chan))
return;
RemoveListen(1);
}
timer()
{
if(playlist)
{
if(!playing)
{
llSetTimerEvent(delay);
playing = TRUE;
}
llPlaySound(llList2String(song, part), ScaleVol(volume));
if((++part) == sl)
{
if(llGetListLength(playlist) > 1)
{
song_name = llList2String((playlist = llDeleteSubList(playlist, 0, 0)), 0);
llSleep(delay);
PlaySong(song_name);
}
else
{
llSetTimerEvent(0.0);
song_name = "";
playing = FALSE;
playlist = ;
}
}
else if(part == (sl - 1))
llPreloadSound(llList2String(song, 0));
else
llPreloadSound(llList2String(song, (part + 1)));
}
if(lis && (!(--lis_count)))
{
if(!(CheckWaitingRoom(0)))
RemoveListen(1);
}
}
}
</source></small>

==References==
{{reflist}}

==External links==
* &mdash;Second Life LSL forum
* &mdash;Dr. Dobb's
* &mdash;A community effort to supplement the available LSL documentation
* &mdash;A new Wiki hosted by Second Life
* &ndash; Information regarding the move to Mono
* Criticism by Xah Lee
* - Privately maintained library of LSL Scripts.

<!-- navboxen -->
{{Second Life}}
{{Vector graphics markup languages}}


] ]

Latest revision as of 16:39, 13 June 2024

Redirect to:

  • With history: This is a redirect from a page containing substantive page history. This page is kept as a redirect to preserve its former content and attributions. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated), nor delete this page.
    • This template should not be used for redirects having some edit history but no meaningful content in their previous versions, nor for redirects created as a result of a page merge (use {{R from merge}} instead), nor for redirects from a title that forms a historic part of Misplaced Pages (use {{R with old history}} instead).
Categories: