Second Life Wiki - User contributions [en]

LlGetNotecardLine

2010-05-31T21:33:57Z

Randur Source: Code sample snippet to read multiple notecards in sequence

{{LSL_Function/negative_index|false|line}}{{LSL_Function/notecard|name|uuid=true}}{{LSL_Function
|func_id=217|func_sleep=0.1|func_energy=10.0
|sort=GetNotecardLine
|func=llGetNotecardLine
|return_type=key
|p1_type=string|p1_name=name
|p2_type=integer|p2_name=line|p2_desc=Line number in a notecard (the index starts at zero).
|func_desc=Requests the line '''line''' of the notecard '''name''' from the dataserver.
|return_text=that is the handle for a [[dataserver]] event response.
|func_footnote=If '''line''' is past the end of the notecard [[EOF]] is returned by the [[dataserver]].
|spec
|caveats=* If notecard contains embedded inventory items (such as textures and landmarks), [[EOF]] will be returned, regardless of the line requested.
*If the requested line is longer then 255 bytes the [[dataserver]] will return the first 255 bytes of the line.
|constants
|examples=<lsl>
key kQuery;
integer iLine = 0;
default {

state_entry() {
llSay(0, "Reading notecard...");
kQuery = llGetNotecardLine("My Notecard", iLine); // read in "My Notecard" when you can
}

dataserver(key query_id, string data) {

if (query_id == kQuery) { // were we called to work on "My Notecard"?
// this is a line of our notecard
if (data == EOF) {

llSay(0, "No more lines in notecard, read " + (string)iLine + " lines.");

} else {

llSay(0, "Line " + (string)iLine + ": " + data); // data has the current line from this notecard

//request next line
iLine++; // increment line count
kQuery = llGetNotecardLine("My Notecard", iLine); // read another line when you can

}
}
}
}
</lsl>
|helpers=
<lsl>
/////
// Generic Multi Notecard reader by Brangus Weir
// Given freely and published on wiki.secondlife.com
//
// This script will read three note cards and store the results into three lists.
// It can be modified and extended to as many (or few) cards as you'd like to read.
//

list gOneCard; // All the lines from from the first card
list gTwoCard; // All the lines from from the second card
list gThreeCard; // All the lines from from the third card

string gsCardOneName = "One"; //Set these to the name of the invetory item.
string gsCardTwoName = "Two";
string gsCardThreeName = "Three";

//Temporary variables for processing
string g_sNoteCardName; // Name of the card to be read.
list g_lTempLines; // The resulting data pushed into a list
integer g_iLine; // The line count for the card reader
key g_kQuery; // The key of the card being read

initialize(string _action) {
// Due to the execution order when using dataserver, this function sets the first card to
// be read, and the excetuion finishes when called again with the _action set to "finish".
if (_action == "") {
loadNoteCard(gsCardOneName);
} else if (_action == "finish") {
// All cards have been read into the lists... now you can do any kind of string
// manipulations to get the data you need to set your script.
// But here we will prove that the cards have been read with a loop

g_lTempLines = []; // lets not forget to delete this global, or it will be dead weight.

integer len = llGetListLength(gOneCard); //Always evaluate this once, don't do it
//INSIDE the for loop like noob programers will.
//Reduce lag, THINK ABOUT MACHINE CYCLES!
integer i = 0;
for (; i< len; ++i)
llSay(0, llList2String(gOneCard,i));

len = llGetListLength(gTwoCard);
for (i = 0; i< len; ++i)
llSay(0, llList2String(gTwoCard,i));

len = llGetListLength(gThreeCard);
for (i = 0; i< len; ++i)
llSay(0, llList2String(gThreeCard,i));
}

}

loadNoteCard( string _notecard ) {
g_lTempLines = []; //clear the temp lines
g_sNoteCardName = _notecard;
g_iLine = 0;
g_kQuery = llGetNotecardLine(g_sNoteCardName, g_iLine);

}

notecardFinished(string _notecard){
// Called at the end of each notecard as it is read. The temp results are stored
// and the next card is commanded to be read.
if (_notecard == gsCardOneName) {
gOneCard = g_lTempLines;
loadNoteCard(gsCardTwoName);
} else if (_notecard == gsCardTwoName) {
gTwoCard = g_lTempLines;
loadNoteCard(gsCardThreeName);
} else if (_notecard == gsCardThreeName) {
gThreeCard = g_lTempLines;
initialize("finish"); // Finally pass execution to finish the initialization.
}
}

default
{
state_entry()
{
}

touch_start(integer _num_det){
initialize("");
}

dataserver(key _query_id, string _data)
{
if (_query_id == g_kQuery) {
// this is a line of our notecard
if (_data != EOF) {
g_lTempLines += _data;
//request a next line
++g_iLine; // increment line count
g_kQuery = llGetNotecardLine(g_sNoteCardName, g_iLine);
} else {
//The notecard has been read
//notify end of read
notecardFinished(g_sNoteCardName);
}
}
}
}
</lsl>

<lsl>
/////
// Generic Multi Notecard reader by Randur Source
// Given freely and published on wiki.secondlife.com
//
// This script will read all note cards in sequence and dump the results into chat as an example.
// It can be modified and extended to do other things to the data.
//

integer inventorycnt;
integer notecardlinecnt;
integer notecardlinenumber;
string notecardname;
key linenumberid;
key lineid;

getnextnotecardlinenumber()
{
// first get the number of lines from the notecard
inventorycnt++;
if (inventorycnt < llGetInventoryNumber(INVENTORY_NOTECARD))
{
notecardname = llGetInventoryName(INVENTORY_NOTECARD,inventorycnt);
linenumberid = llGetNumberOfNotecardLines(notecardname);
}
else
llOwnerSay("Done.");
}

getnextnotecardline()
{
// get the next line from the notecard or skip to the next notecard
notecardlinecnt++;
if (notecardlinecnt < notecardlinenumber)
lineid = llGetNotecardLine(notecardname,notecardlinecnt);
else
getnextnotecardlinenumber();
}

default
{
touch_start(integer total_number)
{
if (llDetectedKey(0) != llGetOwner()) return; // allow owner only

inventorycnt = -1;
getnextnotecardlinenumber();
}

dataserver(key queryid,string data)
{
if (queryid == linenumberid) // this was a line number lookup
{
linenumberid = NULL_KEY;
notecardlinenumber = (integer)data;
if (notecardlinenumber == 0)
getnextnotecardlinenumber();
else
{
notecardlinecnt = -1;
getnextnotecardline();
}
}
else if (queryid == lineid) // this was a data line lookup
{
lineid = NULL_KEY;

// Example of what to do with the data:
// Test for valid avatar names, possibly multiple names on each line, separated by ,
// and say them in chat to the owner
list names = llParseString2List(data,[","],[]); // split lines on ,
integer len = llGetListLength(names); // I wouldn't dare to put this inside the for loop
integer cnt;
for (cnt = 0; cnt < len; cnt++)
{
string name = llDumpList2String(llParseString2List(llList2String(names,cnt),[" "],[])," "); // remove extra spaces
if (llGetListLength(llParseString2List(name,[" "],[])) == 2) // check for first + lastname
llOwnerSay(notecardname + ": " + name);
}

getnextnotecardline();
}
}
}

</lsl>
|also_functions={{LSL DefineRow||[[llGetNumberOfNotecardLines]]|}}
|also_events={{LSL DefineRow||[[dataserver]]|}}
|also_articles
|also_tests
|notes=The notecard read can be no modify, or no modify/no copy.
|permission
|cat1=Notecard
|cat2=Dataserver
|cat3=
|cat4=
}}

LlStartAnimation

2009-08-14T12:02:25Z

Randur Source: added sit animate example

{{LSL_Function/permission|PERMISSION_TRIGGER_ANIMATION}}{{LSL_Function/inventory|anim|uuid=false|type}}{{LSL_Function
|func_id=129|func_sleep=0.0|func_energy=10.0
|func=llStartAnimation|sort=StartAnimation
|p1_type=string|p1_name=anim
|func_footnote
|func_desc=Start animation '''anim''' for agent that granted [[PERMISSION_TRIGGER_ANIMATION]] if the permission has not been revoked.
|return_text
|spec
|caveats=* Prior to 1.25.3 of the server code, an essentially unlimited number of animations could be played at once. In 1.25.3, a limit of 15 simultaneous animations was imposed; in 1.25.4, that limit was (will be) raised to 30.
|constants
|examples=
<lsl>
default
{
touch_start(integer detected)
{
llRequestPermissions(llDetectedKey(0), PERMISSION_TRIGGER_ANIMATION);
}
run_time_permissions(integer perm)
{
if (perm & PERMISSION_TRIGGER_ANIMATION)
{
llStartAnimation("sit");
llOwnerSay("animation will end in 5 seconds");
llSetTimerEvent(5.0);
}
}
timer()
{
llSetTimerEvent(0.0);
llStopAnimation("sit");
}
}
</lsl>
Add an animation or pose inside the same object as this script:
<lsl>
string animation; // the first animation in inventory will automatically be used
// the animation name must be stored globally to be able to stop the animation when standing up

default
{
state_entry()
{
// set sit target, otherwise this will not work
llSitTarget(<0.0, 0.0, 0.1>, ZERO_ROTATION);
}

changed(integer change)
{
if (change & CHANGED_LINK)
{
key av = llAvatarOnSitTarget();
if (av) //evaluated as true if not NULL_KEY or invalid
llRequestPermissions(av, PERMISSION_TRIGGER_ANIMATION);
else // avatar is standing up
{
if (animation)
llStopAnimation(animation); // stop the started animation
llResetScript(); // release the avatar animation permissions
}
}
}

run_time_permissions(integer perm)
{
if (perm & PERMISSION_TRIGGER_ANIMATION)
{
animation = llGetInventoryName(INVENTORY_ANIMATION,0); // get the first animation from inventory
if (animation)
{
llStopAnimation("sit"); // stop the default sit animation
llStartAnimation(animation);
}
}
}
}
</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llStopAnimation]]|}}
|also_tests
|also_events
|also_articles={{LSL DefineRow||[[Internal_Animations]]|lists internal Animations always available}}
|notes
|cat1=Animation
|cat2
|cat3
|cat4
}}

LlGetObjectDetails

2009-07-03T09:26:47Z

Randur Source: Added a script example: Group join inviter

{{LSL_Function/limits}}{{LSL_Function/uuid|id|sim=*}}
{{LSL_Function
|func_id=332|func_sleep=0.0|func_energy=10.0
|func=llGetObjectDetails
|p1_type=key|p1_name=id
|p2_type=list|p2_name=params|p2_desc=OBJECT_* flags
|return_type=list|return_text=of the details specified in '''params''' for the object with key '''id'''.
|func_footnote={{LSL Const|OBJECT_UNKNOWN_DETAIL|integer|-1|c=}} is returned when passed an invalid integer parameter.
|caveats=
*Items in '''params''' that are not integers are silently ignored, {{LSL Const|OBJECT_UNKNOWN_DETAIL|integer|-1|c=}} is not returned.
*If an object represented by '''id''' is not in the sim an empty list is returned.
*An empty list is also returned if the key given was an item in inventory (object or agent).
*If '''id''' represents an agent, this function will continue to return information for approximately 45 seconds after they have left the sim (but the information is not updated).
*[[llTargetOmega]] will only effect the return of [[OBJECT_ROT]] if the object is [[STATUS_PHYSICS|physical]]. If the object is not physical then the original start rotation is returned, [[llTargetOmega]] is a {{LSLGC|Effects|client side effect}}.
|examples=
<lsl>default
{
collision_start(integer i)
{
list a = llGetObjectDetails(llDetectedKey(0), ([OBJECT_NAME,
OBJECT_DESC, OBJECT_POS, OBJECT_ROT, OBJECT_VELOCITY,
OBJECT_OWNER, OBJECT_GROUP, OBJECT_CREATOR]));
llWhisper(0,"UUID: " + (string)llDetectedKey(0) +
"\nName: \"" + llList2String(a,0) + "\"" +
"\nDescription: \"" + llList2String(a,1) + "\"" +
"\nPosition: " + llList2String(a,2) +
"\nRotation: " + llList2String(a,3) +
"\nVelocity: " + llList2String(a,4) +
"\nOwner: " + llList2String(a,5) +
"\nGroup: " + llList2String(a,6) +
"\nCreator: " + llList2String(a,7));
}
}</lsl>
<lsl>// Group join inviter
default
{
touch_start(integer num_detected)
{
llInstantMessage(llDetectedKey(0),"Click on Join in my group profile:\n" +
" secondlife:///app/group/" + llList2String(llGetObjectDetails(llGetKey(), [OBJECT_GROUP]), 0) + "/about ");
}
}</lsl>

|spec
|constants={{LSL Constants/Object Details}}
|helpers=See {{LSLGC|Link/Get}} for some {{LSLGC|Link|link}} related helper functions. Since there is no function to get linked prim parameters, this can be useful if you need to get the position and rotation of a linked prim.
|also_functions={{LSL DefineRow||[[llKey2Name]]}}
{{LSL DefineRow||[[llGetPrimitiveParams]]}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]}}
{{LSL DefineRow||[[llSetPrimitiveParams]]}}
{{LSL DefineRow||[[llGetParcelDetails]]}}
|also_tests
|also_events
|also_articles={{LSL DefineRow||{{LSLGC|Detected}}}}
{{LSL DefineRow||[[Prim Attribute Overloading]]}}
|notes
|history=Introduced in SL 1.18.3(2)
|cat1=Object
|cat2=Prim
|cat3=Avatar
|cat4=Owner
|cat5=Creator
|cat6=Group
|cat7=Link
|cat8
}}

LlDialog

2009-07-03T08:49:18Z

Randur Source: Self defined Ignore button will not give a chat result either

{{LSL_Function/avatar|avatar|sim=*}}{{LSL_Function/chat|chat_channel}}{{LSL_Function|sort=Dialog|func_id=247|func_sleep=1.0|func_energy=10.0|func=llDialog
|p1_type=key|p1_name=avatar|p1_desc
|p2_type=string|p2_name=message|p2_desc=message to be displayed
|p3_type=list|p3_name=buttons|p3_desc=button labels
|p4_type=integer|p4_name=chat_channel|p4_desc
|func_desc=Shows a blue dialog box in the upper right corner of the '''avatar's''' screen with a '''message''' and choice '''buttons''', as well as an ignore button. This has many uses ranging from simple message delivery to complex menu systems.
|func_footnote=When a button is pressed, the '''avatar''' says the text of the button label on '''chat_channel'''. The position where the chat is generated is where the root prim of the dialog generating object was when the dialog button was pressed.
|spec
|caveats=
*There is no way by script to kill a dialog box.
*There is no way for the script to detect if the user clicked the small "Ignore" button (no chat is generated as a result of pressing this button).
*If you create a button yourself with the name "Ignore" (case sensitive) there is also no chat generated as a result of pressing this button.
*There is no way to distinguish the input from a dialog box and regular chat made by the same user.
**It is important to expect that the response may not be one of the buttons.
*If the distance between the root prim of the [[listen]]ing object and the dialog generating prim is greater than 20 meters when a button is pressed, the response will not be heard. See [[#Limits]].
**This limitation affects attachments too if the wearer moves more than 20 meters from where the listener is located. See [[#Limits]].

===<tt>message</tt> limits===
*'''message''' must be fewer than 512 bytes in length and be not empty. If it is empty, llDialog will shout "llDialog: must supply a message" on the [[DEBUG_CHANNEL]]. If it is greater than or equal to 512 bytes, it shouts (again on the [[DEBUG_CHANNEL|debug channel]]): "llDialog: message too long, must be less than 512 characters"; in both instances, the dialog box will not be created for '''avatar'''.
*The client only displays 8 lines of '''message''' if it is longer the dialog has a scroll bar. See [[#Appearance]].

===<tt>buttons</tt> limits===
*If '''buttons''' is an empty list, it will default to as if it were ["OK"]
*An error will be shouted on [[DEBUG_CHANNEL]], if...
**there are more than 12 buttons.
**any list item is not a string.
**any list item string length (in bytes) is zero or greater than 24.
***In other words, a button's text cannot be longer than 24 bytes or a empty string.
*The client will not display all the characters of a button if the text is wider then the text space of the button. See [[#Appearance]].
|examples=<lsl>integer channel = 1000;

default
{
state_entry()
{
llListen(channel,"", "","");
}

touch_start(integer count)
{
llDialog(llDetectedKey(0), "This is a test dialog.\n\nPlease choose one of the below options.",
["Yes", "No", "0", "1"], channel);
}

listen(integer chan, string name, key id, string mes)
{
if(id == llGetOwnerKey(id))//won't listen to objects unless they aren't in the region.
llSay(0,name + " (" + (string)llGetObjectDetails(id, (list)OBJECT_POS) + ") chose option " + mes);
}
}</lsl>
|helpers=<lsl>//Compact function to put buttons in "correct" human-readable order
integer channel;

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

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

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

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

listen(integer _chan, string _name, key _id, string _option)
{
llSay(0, _name + " chose option " + _option);
}
}</lsl>
|constants={{#vardefine:constants_nb}}
{{{!}}
{{!}}- valign="top"
{{!}}
{{{!}}{{Prettytable|style=margin-top:0;}}
{{!}}-{{Hl2}}
! colspan="4" {{!}} Button Order
{{!}}-
{{!}}9  
{{!}}10
{{!}}11
{{!}}-
{{!}}6
{{!}}7
{{!}}8  
{{!}}-
{{!}}3
{{!}}4
{{!}}5
{{!}}-
{{!}}0
{{!}}1
{{!}}2
{{!}}}
{{!}}
{{!}}}
|helpers
|related
|notes=
To use dialog boxes to make menu systems, see [[Dialog Menus|Dialog Menus: A step by step guide]] (aimed at learners).

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

llDialog(llDetectedKey(0), "Please choose one of the below options:",
["Yes", "No", "0", "1"], channel);</lsl>
Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to [[llTextBox]] was to use [[llDialog]] which was limited to 24 bytes.

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

<lsl>integer dialog_channel; // top of script in variables

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

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

===Appearance===

If '''message''' requires more than 8 lines, a vertical scroll bar will appear in the dialog.

The message text can be formatted somewhat using "\n" (for newline) and "\t" (for tab). You can do nothing though to influence the font face, size or weight.

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

The number of characters that can be displayed in a button depends upon the width of the characters.

===Limits===

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

|also_events=
{{LSL DefineRow||[[listen]]|}}
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llTextBox]]|}}
{{LSL DefineRow||[[llRegionSay]]|}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to the specified user}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only}}
|also_tests
|also_articles=
{{LSL DefineRow||[[Dialog Menus|Dialog Menus: A step by step guide]]|A walk through of the entire dialog menu process (aimed at learners).}}
|issues=
{{Issue|SVC-1815|llDialog menus can fail when an object is deeded to a group|type=bug}}
|cat1=Chat
|cat2=Communications
|cat3=Dialog
|cat4}}

Category:LSL Color

2009-07-02T12:33:22Z

Randur Source: fixed typo reasone

{{LSL Header|ml=*}}
{{#if:

{{#vardefine:header_title|Color in LSL}}
{{#vardefine:header_text|LSL has its own special format for color. LSL uses a [[vector]] to store color. Unlike traditional RGB where each channel is 0 -> 255, LSL's color channels are 0 -> 1. 
===Format: {{LSL VR|'''R'''|'''G'''|'''B'''}}===
{{{!}}
{{LSL DefineRow|float|x|Red value|[0, 1]}}
{{LSL DefineRow|float|y|Green value|[0, 1]}}
{{LSL DefineRow|float|z|Blue value|[0, 1]}}
{{!}}}
}}

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

vector RGBAtoColor(integer rgba) {
return < (rgba >> 16) & 0xFF, (rgba >> 8) & 0xFF, (rgba & 0xFF) > / 255.0; // for some reason parentheses are needed around the Z part
}

float RGBAtoAlpha(integer rgba) {
return ((rgba >> 24) & 0xFF) / 255.0;
}</lsl>
}}

{{#vardefine:examples|
<lsl>vector white = <1.0, 1.0, 1.0>;
vector grey = <0.5, 0.5, 0.5>;
vector black = <0.0, 0.0, 0.0>;
vector red = <1.0, 0.0, 0.0>;
vector green = <0.0, 1.0, 0.0>;
vector blue = <0.0, 0.0, 1.0>;
vector yellow = <1.0, 1.0, 0.0>;
vector cyan = <0.0, 1.0, 1.0>;
vector magenta = <1.0, 0.0, 1.0>;</lsl>
}}

}}{{LSL Generic}}{{LSLC|Face|Color}}
{{LSLC|}}{{LSLC|FixMe}}

Category:LSL Color

2009-07-02T12:32:52Z

Randur Source: parentheses needed are around the Z part of the RGBAtoColor return value

{{LSL Header|ml=*}}
{{#if:

{{#vardefine:header_title|Color in LSL}}
{{#vardefine:header_text|LSL has its own special format for color. LSL uses a [[vector]] to store color. Unlike traditional RGB where each channel is 0 -> 255, LSL's color channels are 0 -> 1. 
===Format: {{LSL VR|'''R'''|'''G'''|'''B'''}}===
{{{!}}
{{LSL DefineRow|float|x|Red value|[0, 1]}}
{{LSL DefineRow|float|y|Green value|[0, 1]}}
{{LSL DefineRow|float|z|Blue value|[0, 1]}}
{{!}}}
}}

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

vector RGBAtoColor(integer rgba) {
return < (rgba >> 16) & 0xFF, (rgba >> 8) & 0xFF, (rgba & 0xFF) > / 255.0; // for some reasone parentheses are needed around the Z part
}

float RGBAtoAlpha(integer rgba) {
return ((rgba >> 24) & 0xFF) / 255.0;
}</lsl>
}}

{{#vardefine:examples|
<lsl>vector white = <1.0, 1.0, 1.0>;
vector grey = <0.5, 0.5, 0.5>;
vector black = <0.0, 0.0, 0.0>;
vector red = <1.0, 0.0, 0.0>;
vector green = <0.0, 1.0, 0.0>;
vector blue = <0.0, 0.0, 1.0>;
vector yellow = <1.0, 1.0, 0.0>;
vector cyan = <0.0, 1.0, 1.0>;
vector magenta = <1.0, 0.0, 1.0>;</lsl>
}}

}}{{LSL Generic}}{{LSLC|Face|Color}}
{{LSLC|}}{{LSLC|FixMe}}

LlDie

2009-04-08T13:37:57Z

Randur Source: Added some handy Q&A from http://lslwiki.net/lslwiki/wakka.php?wakka=lldie

{{LSL_Function
|func=llDie
|sort=Die
|func_id=41|func_sleep=0.0|func_energy=0.0
|func_footnote=If called in any prim in the {{LSLG|link set}} the result will be the deletion of the entire object. To remove a single prim from an object use [[llBreakLink]] first.
|func_desc=Deletes the object. The object does not go to the owners Inventory:Trash.
|return_text
|spec
|caveats=*After this function is called there is no way to undo the deletion of the object.
*Has no effect if called from within an {{LSLGC|Attachment|attachment}}; there is no way to delete an attachment.
**To detach an object from the avatar call [[llDetachFromAvatar]]
|constants
|examples=
<lsl>//Counts down from 5 to 1, then dies
default
{
state_entry()
{
integer olf;
for(olf = 5; olf > 0; --olf)
llSay(0, (string)olf);
llDie();
}
}</lsl>
|helpers=
[[llRemoveInventory]] of [[llGetScriptName]] deletes just the calling script, rather than all of the object that the calling script contains. For instance, you can write a script that chats a little when dragged on to an object from inventory and then politely disappears itself, such as:
<lsl>
// http://wiki.secondlife.com/wiki/llDie
default
{
state_entry()
{
llOwnerSay("llGetRegionTimeDilation()");
llOwnerSay((string) llGetRegionTimeDilation());
llRemoveInventory(llGetScriptName());
}
}
</lsl>

Q: How do I delete another object? 
A: You can't. Your best option is to place a script inside the object you wish to delete and then use chat to tell it when to do so. 
Alternatively, llGiveInventory can be used to give a copy of a script to another object, but the script will always be turned off within the recipient object. Scripts can only be turned on by manually activating them. 
[[llRemoteLoadScriptPin]] may be useful, but if you can already get into the object that way, you can likely put a script containing [[llDie]] in it already. 
 
Q: How do I make my object delete itself if it goes off my land? 
A: Use a [[timer]] and [[llGetLandOwnerAt]]([[llGetPos]]()). 
 
Q: How do I make my object delete or return itself when it leaves the sim? 
A: See [[llSetStatus]] and the [[STATUS_DIE_AT_EDGE]] and [[STATUS_RETURN_AT_EDGE]] constants.
|also_functions={{LSL DefineRow||[[llDetachFromAvatar]]|}}
{{LSL DefineRow||[[llBreakLink]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||{{LSLGC|Attachment}}|}}
|notes
|permission
|negative_index
|cat1=Object
|cat2
|cat3
|cat4
}}

User:Randur Source

2008-08-08T10:36:04Z

Randur Source:

Randur's SL reSource

I can offer you any kind of scripted solution for SecondLife. I create HUD gadgets and also inworld rezzable objects. You can also use some of my SL scripts to apply to your own builds. I can make custom solutions by request.

I also make new sound samples and gestures, as well as new textures for clothing and tattoes. I create new animations and some sculpted objects as well.

Use my vending machines and look at slexchange.com
I even give away some full perm scripts.

Join my group in SL: Randur's SL reSource (secondlife:///app/group/f975bd4c-f126-b6b6-4063-aa351a4d1bf3/about)

User:Randur Source

2008-08-08T10:17:01Z

Randur Source: New page: Randur's SL reSource I can offer you any kind of scripted solution for SecondLife. I create HUD gadgets and also inworld rezzable objects. You can also use some of my SL scripts to apply ...

LlSetText

2008-08-08T10:13:18Z

Randur Source: Multiple linebreaks with empty lines solution

{{LSL Function/color|color}} {{LSL Function/alpha|alpha}}{{LSL_Function
|func_id=152
|func_sleep=0.0
|func_energy=10.0
|func=llSetText
|sort=SetText
|p1_type=string|p1_name=text|p1_desc=text to display
|p2_type=vector|p2_name=color
|p3_type=float|p3_name=alpha
|func_desc=Displays '''text''' that hovers over the prim with specific '''color''' and translucency (specified with '''alpha''').
|return_text
|spec=
|caveats=
*'''text''' is limited to 254 bytes, if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
*Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.
*There is no way for a script to determine the prims current floating text or detect when it is changed.
**There is no [[llGetText]] function or [[CHANGED_TEXT]] [[changed]] event flag.
*Removing the script or deactivating it will not remove the prims floating text.
**Floating text is a prim property and not dependent or changed to a script to continue to exist.
*To remove floating text, use the following:
<lsl>llSetText("", <1.0, 1.0, 1.0>, 1.0);</lsl>
*Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
*Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip [[User:Randur Source]]:
<lsl>llSetText("Monkeys\n\n\n\n\n", <1.0, 1.0, 1.0>, 1.0);//Bad
llSetText("Monkeys\n\n\n\n\n ", <1.0, 1.0, 1.0>, 1.0);//Good - no, bad, see next line:
llSetText("Monkeys\n \n \n \n \n ", <1.0, 1.0, 1.0>, 1.0);//Good</lsl>
|examples=
Example of how llSetText could be included in default code to show object's name in green text:
<lsl>default
{
state_entry()
{
llSay(0, "Hello, Avatar!");
llSetText(llGetObjectName(), <0.0, 1.0, 0.0>, 1.0); // Display the object's current name in green
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}</lsl>
By default the floating text will appear on a single line. However, the floating text can be spread over multiple lines by using a line break "\n" (read [[SplitLine]] in section 'See Also').
===Color & Alpha===
{{{!}} class="sortable" {{Prettytable|style=float:right; margin-top:0;}}
{{!}}- {{Hl2}}
! Color
! Code
{{!}}- style="background:white"
{{!}}White
{{!}}<1.0, 1.0, 1.0>
{{!}}- style="background:grey"
{{!}}Grey
{{!}}<0.5, 0.5, 0.5>
{{!}}- style="background:black; color:white;"
{{!}}{{!}}Black
{{!}}<0.0, 0.0, 0.0>
{{!}}- style="background:red; color:white;"
{{!}}Red
{{!}}<1.0, 0.0, 0.0>
{{!}}- style="background:green; color:white;"
{{!}}Green
{{!}}<0.0, 1.0, 0.0>
{{!}}- style="background:blue; color:white;"
{{!}}Blue
{{!}}<0.0, 0.0, 1.0>
{{!}}}
The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different then traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black":
<lsl>llSetText("I am on", <1.0, 1.0, 1.0>, 1.0);//white text</lsl>
<lsl>llSetText("I am off", <0.0, 0.0, 0.0>, 1.0);//black text</lsl>
The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible):
<lsl>llSetText("alpha", <0.0, 1.0, 0.0>, 0.5);//50% translucent green text</lsl>
===Multiple lines===
<lsl>llSetText("I am \n on two lines!", <0.0, 1.0, 0.0>, 1.0);//two lines of green text</lsl>
|helpers=
Drag this script out of inventory onto an object to erase its set text:
<lsl>// http://wiki.secondlife.com/wiki/llSetText
default
{
state_entry()
{
llSetText("", <1.0, 1.0, 1.0>, 1.0);
llRemoveInventory(llGetScriptName());
}
}</lsl>
|also
|also_functions
|also_articles=
{{LSL DefineRow||[[:Category:LSL Examples|Examples]]: [[SplitLine]]|Insert 'new line' escape codes at certain positions of a string}}
{{LSL DefineRow||Useful snippet: [[llGetObjectPermMask]]|Label an object with text and newlines to give away or sell}}
|notes=To actually display text on a prim, see [[XyzzyText]], or consider using parcel prim [[:Category:LSL_Media|Media]] options (useful only you have control over the land's media settings.)
|cat1=Effects
|cat2=Prim
|cat3
|cat4
}}

Talk:LlSitTarget

2008-08-01T13:45:39Z

Randur Source: Using llSetLinkPrimitiveParams for skydiving: why limited to 5m in a linked set?

== Unsitting on wrong side or camera rotation ==

Hi, i am getting frustrated with this. I create a board and set the sit target with
llSitTarget(<0.4, 0.0, 0.0>, ZERO_ROTATION);
and an animation which for "standing". So while the person technical sits, she stands in front of the board.
But I have a problem with that: If the board stand freely, the person unsits right through it towards the other side. I can put the board with the back facing a large wall. In the case the unsitting is correctly in front of it. But on sit down the camera rotates, so that it is behind the avatar again; on the other side of the wall.

If anyone has an idea how to fix, please tell me (even if it is just an idea where to look for more information). --[[User:Maike Short|Maike Short]] 12:41, 24 February 2008 (PST)

:You could position the camera with the {{LSLGC|Camera}} functions. -- [[User:Strife Onizuka|Strife Onizuka]] 04:46, 25 February 2008 (PST)

==Optimization==
<pre>
list GetSitTarget(integer prim, key av)
{//WARNING: llGetObjectDetails can introduce an error that goes as far as the 5th decimal place.
vector tp = llGetAgentSize(av);
if(tp)
{
if(prim == LINK_THIS)//llGetLinkKey doesn't like LINK_THIS
prim = llGetLinkNumber();

list details = OBJECT_POS + (list)OBJECT_ROT;
rotation f = llList2Rot(details = (llGetObjectDetails(llGetLinkKey(prim), details) + llGetObjectDetails(av, details)), 1);

return [(llRot2Up(f = (llList2Rot(details, 3) / f)) * tp.z * 0.02638) + ((llList2Vector(details, 2) - llList2Vector(details, 0)) / f) - <0.0, 0.0, 0.4>, f];
}
return [];
}//Written by Strife Onizuka
</pre>

==Using llSetLinkPrimitiveParams for skydiving: why limited to 5m in a linked set?==
llSetLinkPrimitiveParams can be used as a handy tool to adjust an avatar's position and rotation.
This works perfectly when the object consists of 1 prim, with a range for setting the avatar position away to 500m easily!
When there are more prims linked, this offset seems to be limited to 5m (measured with llVecDist). This is an awfull sideeffect!

Put this next script inside a prim and sit on the prim, it will bring you to 1000.0 higher then the prim.
Next link this prim to another prim and try again. You will notice you are limited to 5m. My Question: why is this limited?
<pre>
// by Randur Source

integer heightcnt = 0;
list heights = [0.0, 1.0, 5.0, 6.0, 10.0, 100.0, 300.0, 500.0, 800.0, 1000.0];

default
{
state_entry()
{
llSitTarget(ZERO_VECTOR,ZERO_ROTATION); // Clear the current sittarget for a clear test
llSetRot(ZERO_ROTATION); // set the prim to no rotation, for simple z axis movement
}

changed(integer change)
{
if (change & CHANGED_LINK) // detect linked prims and avatars
{
integer primnum = llGetNumberOfPrims(); // the avatar is the last linked prim
if (primnum <= 1) // stop if there is only 1 prim
return;

key avatar = llGetLinkKey(primnum);
if (llGetAgentSize(avatar) == ZERO_VECTOR) // stop if this is not an avatar
return;

// loop through the list of test heights:
for (heightcnt = 0; heightcnt < llGetListLength(heights); heightcnt++)
{
float height = llList2Float(heights,heightcnt);
llSetLinkPrimitiveParams(primnum,[PRIM_POSITION,<0.0,0.0,height>]); // set this to the wanted height using a vector z axis

vector avatarpos = llList2Vector(llGetObjectDetails(avatar,[OBJECT_POS]),0); // detect the avatar position within the sim
float distance = llVecDist(llGetPos(),avatarpos);
llOwnerSay("Attempt to move " + llKey2Name(llGetLinkKey(primnum)) + " to " + (string)height + "m high resulting to " + (string)distance + "m");

llSleep(1.0);
}
llUnSit(avatar);
}
}
}
</pre>