Scripting Bugs

If one person takes a copy of another person's object, the object left in-world loses PERMISSION_DEBIT . I didn't test other permissions Rez an object and insert this script: default { state_entry() { llRequestPermissions(llGetOwner(), PERMISSION_DEBIT); } touch_start(integer count) { llOwnerSay("Permissions: " + (string)llGetPermissionsKey() + ": " + (string)llGetPermissions()); } } Grant debit permission Click to make sure it has permission Sign onto an alt that has object edit permissions On the Alt, right click > Take Copy Click the object still rezzed in world. It no longer has debit permission

As the title says, touch_start() won't fire until the second click if the object is already being touched. Here's some quick demo code: default { touch_start(integer num) { llOwnerSay("touch_start(): " + (string)num); } touch(integer num) { llSetText("touch(): " + (string)num, <1.0, 1.0, 1.0>, 1.0); } } Detailed scenario: User#1 clicks the prim and keeps their mouse button held, touch_start() outputs the correct number of 1 new touches, touch() outputs the correct number of 1 continuous touches, User#2 clicks the prim and keeps their mouse button held, touch_start() does not output anything. touch() outputs 2 continuous touches, User#2 releases their mouse button and clicks again touch_start() now outputs 1 new touches, touch() outputs 2 continuous touches. I discovered this while coding authentication for a touchable object. The alternative is to do authentication directly in touch() which will cripple performance as it will needlessly be validating unauthenticated users' access over and over whilst touched.

SIT_FLAG_NO_COLLIDE (applied with llSetLinkSitFlags()) disables collision shapes on seated avatars but avatar mass is still contributed to the object. This shifts the physical object's center of mass and interferes with the function of particularly small vehicles. Avatar mass contributions should be simply be disabled entirely when SIT_FLAG_NO_COLLIDE is applied to match the behavior of linked objects not contributing to a linkset's mass when PRIM_PHYSICS_SHAPE_TYPE is set to PRIM_PHYSICS_SHAPE_NONE with llSetLinkPrimitiveParams(). Alternatively, a sit flag, e.g. 'SIT_FLAGS_NO_MASS', that disables mass contribution from seated avatars is proposed.

https://wiki.secondlife.com/wiki/LlListFindListNext llListFindListNext(haystack, needle, instance); Returns the index for the Nth instance of needle . instance is zero-based. Returns -1 when there aren't enough instances. Error: Returns last index + 1 when needle is the last element of the list. integer index; list haystack = ["A", "B", "C"]; index = llListFindListNext(haystack, ["C"], 0); // OK llSay(PUBLIC_CHANNEL, "Expect 2: " + (string)index); index = llListFindListNext(haystack, ["B"], 1); // OK llSay(PUBLIC_CHANNEL, "Expect -1: " + (string)index); index = llListFindListNext(haystack, ["C"], 1); llSay(PUBLIC_CHANNEL, "Expect -1: " + (string)index); index = llListFindListNext(haystack, ["C"], 23); llSay(PUBLIC_CHANNEL, "Expect -1: " + (string)index);

Please see https://i.gyazo.com/9458091243cd7f38b5bd858165a59508.mp4 to see what's happening. The script is put inside a root link that is the swivel bar, the mesh door is the second link in the linkset. The function is called as: llSetKeyframedMotion(lKeyFramesOpening, [ KFM_DATA, KFM_ROTATION, KFM_MODE, KFM_FORWARD ]); Where lKeyFramesOpening is a list generated like so: // Rotation for most keyframes rotation rRotation = llEuler2Rot(<0.0, 0.0, 15.0> * DEG_TO_RAD); // First keyframe lKeyFramesOpening += [ llEuler2Rot(<0.0, 0.0, 15.0> * DEG_TO_RAD), 3.0 ]; // Generating in-between keyframes integer i = 1; for(; i < 5; i++) { lKeyFramesOpening += [ rRotation, i * .2 ]; } // Ending keyframe lKeyFramesOpening += [ llEuler2Rot(<0.0, 0.0, 15.0> * DEG_TO_RAD), 0.6 ]; Object and full script can be sent upon request. See comments in the thread here for more info.

SL Regex {} counts bytes instead of characters if test string contains multi-byte characters.

Hello, I wanted to find a way to give an object to a new owner from a script, the object being no-copy I used the flag "TRANSFER_FLAG_TAKE" but after receiving said object, the new owner has a "Locked" version of the object. It wasn't locked before. So if they rez it, they are unable to take it back as it's also no-mod.

The PRIM_PROJECTOR flag in llGetPrimitiveParams() returns the following script error: llGetPrimitiveParams error: Param 1 error, unknown parameter. The Wiki indicates this is to protect the UUID of the returned texture parameter from bypassing object permissions. However, by turning this entire function off we can not request other useful parameters such as FOV, Focus, and Ambiance. These have become more important with PBR. Please just have the flag return NULL_KEY for texture so we can at least get the other settings?

When a person sits on an objects which he/she owns and the person gets ejected by the llEjectFromLand function, it will also eject the object from the land and sends it back to the "lost and found" folder. This happens several times with an professional scripted skybox security system. I suggest to have a look at this function and make sure the objects won't be removed again.

According to https://wiki.secondlife.com/wiki/LlSetLinkGLTFOverrides , "Passing an empty string ("") as the override value will clear that override." This is true as far as I have tested except for OVERRIDE_GLTF_BASE_ALPHA, where setting to "" seems to simply do nothing. To Reproduce: Rez a prim, add a PBR material to it, and put the following script into it: default { touch_start(integer total_number) { toggle=!toggle; if(toggle) llSetLinkGLTFOverrides(LINK_THIS,ALL_SIDES,[OVERRIDE_GLTF_BASE_ALPHA_MODE,PRIM_GLTF_ALPHA_MODE_BLEND,OVERRIDE_GLTF_BASE_ALPHA,0]); else llSetLinkGLTFOverrides(LINK_THIS,ALL_SIDES,[OVERRIDE_GLTF_BASE_ALPHA_MODE,"",OVERRIDE_GLTF_BASE_ALPHA,""]); } } You will see that the alpha will set to 0 on the first click, but will not return to its previous value on the second click. The alpha mode WILL revert as intended if you use a PBR material which is not in blend mode, but the prim remains invisible if the material is not opaque. The wiki page provides a toggle alpha on/off function, but this simply toggles the alpha value between 0 and 1 rather than setting and then removing an override. Where the base alpha value of a material is not 1, this will fail as it will set the alpha to 1 rather than the correct value.