Search results
Jump to navigation
Jump to search
- ...|p3_desc=can consists of any number of [[#options|option flag]]s and their parameters. *[[llCastRay]] will not detect prims having no physics shape ([[PRIM_PHYSICS_SHAPE_TYPE]] = [[PRIM_PHYSICS15 KB (2,230 words) - 09:48, 5 November 2023
- ...|p3_desc=can consists of any number of [[#options|option flag]]s and their parameters. ===={{LSL Param|status_code}}====15 KB (1,085 words) - 11:32, 22 November 2023
- {{LSL Function ...pt within the object itself can detect this by reading the [[PRIM_OMEGA]] parameters.6 KB (936 words) - 14:24, 18 April 2024
- ** Ability to chat radar info (keys) to boost lsl radars ** Ability to set all prim parameters without changing shape (easy prim torture)4 KB (527 words) - 13:27, 14 January 2013
- Persons who wish to demonstrate competence in intermediate LSL scripting. # RGB definition of a color vector in LSL and how it is different from the editor window.18 KB (2,980 words) - 09:01, 6 September 2010
- ...has been created because there doesn´t seem to be any sort of standard to detect devices. Devices can be leashing posts, furniture, collars, cuffs and chas ...of a token. The token may be followed by a parameter. Multiple tokens and parameters may be sent in a single message. However, a single message should not cont32 KB (4,547 words) - 10:54, 30 December 2015
- {{LSL Header}} ...To understand the logic, it is best to pull the code apart but be wary of LSL's strict order of operations.27 KB (3,241 words) - 01:42, 6 February 2023
- * New LSL function: integer [[llManageEstateAccess]](integer action, key id) ...as [[llGetMass]]() or [[llGetPos]]()) but don't actually change any object parameters, since most of those calls have built-in delays that automatically throttle36 KB (5,126 words) - 00:14, 14 December 2011
- ...Linden</b><nowiki>: The interesting new stuff in that release is a set of LSL functions to process JSON data</nowiki></font> ...<font color=#c50000><b>Fadeout Razorfen</b><nowiki>: it randomly fails to detect stuff</nowiki></font>32 KB (5,087 words) - 16:35, 17 May 2013
- ...<font color=#b500b5><b>Johan Laurasia</b><nowiki>: well, the server would detect the mobile device and upload a previously made, lower rez version, or scale ...viewers to get the graphics they want ... the viewer sends up it's camera parameters (distance, etc), the region sends down object information based on that, an46 KB (7,344 words) - 14:31, 31 January 2012
- ...ng:0 3px;"|ic, well, im glad you still keep a secret meeting for the worst LSL addicts ^^ |width=100% style=" padding:0 3px;"|Kelly, is the a hold on new lsl functions?67 KB (8,493 words) - 16:46, 22 March 2011
- ** New LSL function: key [[llTransferLindenDollars]](key id, integer amount) ** New LSL event: [[transaction_result]](key id, integer success, string data)47 KB (6,673 words) - 15:46, 19 January 2012
- ...days copybots are easily available and very user frieendly. I dont see the LSL way to copy items very big threat. Not worth ruining the item by making it ...z (kelly.linden)</b><nowiki>: land-scanning-bots end up being heavy on the LSL system.</nowiki></font>33 KB (4,991 words) - 15:37, 9 January 2012
- ...=#00c530><b>Mona Eberhardt</b><nowiki>: Simon, remember when I asked about LSL functionality to control materials? I was pointed to a JIRA on this matter. ...be on Firestorm and were you building at the time using copy/paste object parameters? Theres a really bizarre bug on FS that can cause you to see all sculpts as33 KB (5,275 words) - 19:15, 17 December 2013
- ...days copybots are easily available and very user frieendly. I dont see the LSL way to copy items very big threat. Not worth ruining the item by making it ...z (kelly.linden)</b><nowiki>: land-scanning-bots end up being heavy on the LSL system.</nowiki></font>33 KB (5,003 words) - 10:51, 10 January 2012
- [12:33] <font color=#5ab500><b>Kitto Flora</b><nowiki>: Nah - have to detect failure to cross then hammer the object sith multiple llSetPus() to get it ...a prim from LSL scripts has decent interaction with the world (back to the LSL script). The transparency part is a problem, but I don't think it is unsolv30 KB (4,675 words) - 18:24, 29 November 2011
- ...g. autocomplete for event and function arguments, as well as arguments for parameters to [[llSetPrimitiveParams]], etc. | style="white-space:normal;"|yeah I mean gadgets as in clientside code not LSL71 KB (9,294 words) - 18:49, 20 August 2009
- ...because he opted-in to the new accounting by changing some of the physics parameters - but not enough of them to optimize the content.</nowiki></font> ...30] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: For legacy LSL - the events are registered in a unsigned-64 bit integer.</nowiki></font>52 KB (8,024 words) - 10:55, 10 January 2012
- [16:09] <font color=#b50000><b>Ima Mechanique</b><nowiki>: how final are the LSL functions for that?</nowiki></font> [16:09] <font color=#440044><b>Andrew Linden</b><nowiki>: Ima, those LSL functions are not necessarily final -- we can change them if there is good57 KB (8,961 words) - 09:01, 28 February 2012
- ...4><b>Andrew Linden</b><nowiki>: as for the latter report, I wasn't able to detect any lost items (items in inventory that were not in valid folders)</nowiki> ...i>: I also did some viewer work recently for scripting that will paste the LSL tooltip into your scripts</nowiki></font>49 KB (7,674 words) - 19:10, 20 July 2012