📃 SLua Alpha

Slua viewer has a linux build: https://github.com/secondlife/viewer/releases/tag/Second_Life_Project%231bcae36f-SLua But it isn't listed on the release page: https://releasenotes.secondlife.com/viewer/26.1.0.21525310258.html

This appears to be related to highlighting. It is also influenced by the amount of code in the script and by the amount of comment text. However, commenting out all preceding code, or turning it all into a very long string, can make the problem vanish. The affected scripts compile and run without unexpected errors, but it becomes difficult to edit certain lines within the editor: Steps to reproduce: In an SLua Enabled Sim, rez a new prim. Create a new script, open it, and replace the contents with the attached script. Note that "LLEvents" in line 14 is highlighted in green. Attempt to select the line. Observe that only the word "function" is highlighted. Copy the line and paste at the bottom of the script. Observe that the whole line is pasted. Place the cursor at the left edge of the line and move right one character at a time with the arrow keys. Observe that the characters "s.touch_e" are skipped as a group. Attempt to select or erase "_end". Depending on your method, various failures will occur. Press End to move to the end of the line. Observe that the visible cursor is well past the end of the line, but that backspace deletes the last character. Note that when the line no longer represents a proper event that the line becomes normally editable. Comment out line 12. Observe that "LLEvents" becomes blue and the line is normally editable. Reenable line 12 and delete line 13. Observe the same. So far, I have only observed this with LLEvents.touch... All 3 are affected. In-Editor WORKAROUND: When editing an affected line, change the first keyword by adding an extra character at the beginning, such as making "LLEvents" into "xLLEvents". Edit the line as needed, then remove the extra character.

The following code snippet generates a one and a zero for my "vis" value shown in the DBG_MSG0 call (is_visible is an argument to the function declared as integer): // force into a boolean 0/1 value integer b4 = is_visible; is_visible = is_visible != 0; DBG_MSG0(["S1: change_piece_vis", full_piece_id, "vis", is_visible, b4, "link_num", link_num]); b4 is printing out as zero, while is_visible ends up being one. The "skid marks" that are the result of this action in my scripts look like this: set_body_flags 8 0 NEW body_vis_flags 7 S1: change_piece_vis 25 vis 1 0 link_num 57 The first skid mark is shows that body flags was indeed updated to have a zero at the relevant position confirming that the change_piece_vis code should be getting a zero value which is what b4 has stored. So the "is_visible != 0" clause is not generating the right value.

lljson.empty_array decodes to an empty table: local t = { lljson.null, lljson.empty_array } print(t[1], t[2]) -- > lljson_constant: 0x0000000000000003 lljson_constant: 0x0000000000000005 local s = lljson.slencode(t) print(s) -- > [null,[]] local ts = lljson.sldecode(s) print(ts[1], ts[2]) -- > lljson_constant: 0x0000000000000003 table: 0x0000000011ef6718 lljson.slencode()/sldecode() should be able to recover the exact same table.

Running on server: Luau 2026-01-06.20757451310 In successive calls of string.match, I often get a fatal error if I don't wrap string.match in a pcall: runtime error lua_script:3: String pattern too complex, timed out [C] function match The problem is that the only thing repeatable is that I may or may not get errors when running the code. local function getStringMatch(s) local status, k, v repeat status, k, v = pcall(string.match, s, "(%g+)%s*=%s*(%g+)") if not status then print(k) end until status end local keys = {} for i = 1, 10 do table.insert(keys, tostring(ll.GenerateKey())) end for k, v in keys do print(k) getStringMatch(v) end This is basically a useless example, except to trigger the issue. gmatch should return the captures, the original string if no captures, or nil. This example will never find a match, but I don't believe string complexity is the issue, and I don't believe its timing out because it happens very fast. But, if a failure is triggered, I can recall the very same match again and get success, without providing any delays in the code.

While this caveat behavior is known and possibly relied upon by lsl scripts. Nobody should be writing a slua script expecting this security issue to exist. So if possible could a ll.HTTPRequest from slua, only trigger the http_response event in the slua script making the request. Or a dataserver request also respond only to the requesting script. Not in any other, script regardless of their platform runtime. This might be a slight pain to implement to keep the behavior for lsl on luau scripts, but I think worth it for slua Test Place 2 scripts in a prim save them with the following content ll.HTTPRequest("https://secondlife.com",{},"") function http_response(id,stat,meta,body) ll.OwnerSay(`{ll.GetScriptName()} = {stat}`) end Note that on saving of the second script you get 2 owner says, one from each script stating the response status. Ideally this behavior should be avoided for slua. Alternate suggestion It was suggested it may be possible to instead add a new HTTP_* flag Something like ll.HTTPRequest( "https://secondlife.com", { HTTP_PRIVATE_REQUEST, TRUE }, "" ) This would not work for dataserver events though

Possibly related to [ https://feedback.secondlife.com/scripting-bugs/p/script-suddently-losing-connetion-with-the-server-on-save ] A few times I've gotten the above error. Fixing the syntax error does not eliminate the message — it's as if the script inventory instance is permanently disabled. My workaround has been to copy the script text to a new inventory instance. I was able to reproduce this on SLua Tombolo. 1) Create a block and add a new SLua script to it. 2) Change line 1 to: `` xxx ll.Say(0, "Hello, Avatar!") `` 3) Save. See an expected, normal error message. 4) Clone the object. Edit the script in the clone. 5) Notice the cloned script is marked not-running. 6) Use the external editor button to edit the cloned script. See the dreaded (0,0) error. (I am using BBEdit as my external editor: /usr/bin/open -a bbedit "%s" ) --- Second Life Project lua editor 7.1.12.13973830462 (64bit) Release Notes You are at 194.7, 250.2, 23.1 in SLua Tombolo located at simhost-0766603a88e3665d6.aditi SLURL: secondlife://Aditi/secondlife/SLua%20Tombolo/195/250/23 (global coordinates 41154.7, 23802.2, 23.1) Luau 2025-03-27.14115520293 Release Notes CPU: Apple M2 Max (2400 MHz) Memory: 32768 MB OS Version: macOS 15.3.2 Darwin 24.3.0 Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6020 x86_64 Graphics Card Vendor: Apple Graphics Card: Apple M2 Max OpenGL Version: 4.1 Metal - 89.3 Window size: 2602x2102 Font Size Adjustment: 96pt UI Scaling: 1 Draw distance: 512m Bandwidth: 3000kbit/s LOD factor: 1.25 Render quality: 2 Texture memory: 21845MB Disk cache: Max size 1638.4 MB (99.9% used) HiDPI display mode: true J2C Decoder Version: KDU v7.10.4 Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.23.1 / OpenAL Community / OpenAL Soft: OpenAL Soft Dullahan: 1.14.0.202408091638 CEF: 118.4.1+g3dd6078+chromium-118.0.5993.54 Chromium: 118.0.5993.54 LibVLC Version: 3.0.21 Voice Server Version: Not Connected Packets Lost: 13/10384 (0.1%) March 30 2025 06:20:01

Using strict type checking doesn't display warnings in the Script Warning/Error window --!strict local function add(a: number, b: number): number return a + b end local result1: number = add(3, 4) -- Should work fine local result2: number = add("3", 4) -- Should trigger a type error in strict mode This code in Luau/Roblox displays this warning: Type Error: (8,29) Type 'string' could not be converted into 'number'

The SLua code below demonstrates the problem. Two vectors, multiplied, results in a vector answer rather than a number. v1 = vector(9, 2, 7) v2 = vector(4,8,10) v3 = v1 * v2 ll.OwnerSay(typeof(v3) .. ": " .. tostring(v3)) Program output: vector: <36.00000, 16.00000, 70.00000> Reason for identifying as a bug: The SL Wiki indicates that the dot product should return the sum of the products of the vector elements. In this case, the expected result should be 122.0. What is returned instead is simply the vector of the products of each element.

Very, very minor bug. Currently "goto" highlights as a keyword in the script editor, and gives the helper text, "Lua goto statement: jumps to a specified label" goto is not implemented in Luau, and this is not me asking for it to be implemented. But right now the script editor is implying that goto will work, and it doesn't. Perhaps there are some other functions from Lua that aren't implemented in Luau where this is also an issue? I couldn't find anything else, but it's possible.