Scripting Features

Ability for a seated avatar to stay relative to the prim they are sitting on when it moves / rotates. E.g default { state_entry() { llLinkSitTarget(2,<0,0,1>,ZERO_ROTATION); llSetLinkSitFlag(2, SIT_FLAG_MAINTAIN_RELATIVE); llSetTimerEvent(0.1); } timer() { llSetLinkPrimitiveParamsFast( 2, [ PRIM_POS_LOCAL,<0,1.5 + llCos(llGetTime()),0>, PRIM_ROT_LOCAL, llEuler2Rot(<0,0,llGetTime()>) ] ); } } An avatar sitting on prim 2 should move back and forth and rotate along with the prim.

This feature request relies on https://feedback.secondlife.com/feature-requests/p/store-material-names-as-metadata-for-meshes-exposing-them-to-scripts being implemented. If the above feature is implemented, and if we could have a feature to retrieve the material names (not names of Material Assets!) for each "side" or "face" with a script, it'll be easier to implement scripts for controling textures and other "face" related features for several objects at once, without having to first create mappings between face / side number and intended material face. See the provided images for two objects that are intended to share some materials, while they differ in other ones. I envision having those material names, listed to the right in the pictures, retrievable by for example llGetObjectDetails(OBJECT_SIDE_NAMES), which could return a list like so: ["Floor", "OuterWalls", "Roof", "Underside", "WallEdges", "WindowPanes"] Which means that "side 0 is named Floor", corresponding to the index. An object not having this information should return an empty string for each unnamed side. This makes it possible for a script to automatically map side numbers with intended materials for them. A viewer such as Firestorm with a scripted "bridge" could also potentially retrieve the information to show in the UI.

Summary: Enhance llGiveAgentInventory to provide better folder management and allow deeper inventory hierarchy, enabling more complex inventory structures for scripted outfit and appearance management systems. Proposed Enhancements: New Flag for Folder Reuse - Introduce an additional flag ( TRANSFER_REUSE_FOLDER ) that, when set, will place items in an existing destination folder if it already exists, rather than creating a duplicate. - This will prevent unnecessary clutter in a user’s inventory when updating or managing scripted items. Increase Maximum Folder Depth - Expand the allowable inventory path depth from 4 levels to 8 levels when using TRANSFER_DEST . - This allows for more granular organization, which is particularly useful for modular outfit management systems where users need to organize appearance layers and accessories effectively. Use Case: A scripted outfit management system needs to store various items in a structured way, such as: #RLV | Product/Region | Outfits | Sci-Fi | Armor | Chest | V1 #RLV | Product/Region | Outfits | Sci-Fi | Armor | Chest | V2 #RLV | Product/Region | Outfits | Fantasy | Robes | Mage | Red #RLV | Product/Region | Outfits | Fantasy | Robes | Mage | Blue The current depth limitation (4 levels) makes this approach unworkable. By increasing the depth to 8, systems that manage avatar appearances dynamically can maintain organization without workarounds like splitting folders into separate deliveries and having the user manually move them. Additionally, without TRANSFER_REUSE_FOLDER , every time a scripted system attempts to add to an outfit folder, it creates duplicates, making inventory organization difficult for users. This flag would ensure updates and additions go into the existing folder seamlessly. Expected Benefits: Improved Inventory Organization – Prevents unnecessary duplicate folders when updating outfits or items. Greater Flexibility for Outfit Management – Allows deeper categorization, benefiting modular and layered appearance systems. Better User Experience – Reduces clutter and streamlines scripted inventory transfers. These enhancements will significantly improve usability for content creators and users relying on automated inventory systems. Thank you for considering this feature request!

Currently the function rotates the avatar and camera, I think it would be useful if we had a flag to enable or disable the camera being rotated with the function. llSetAgentRot(rotation rot, ROTATE_CAMERA); I Believe this would add useful functionality

Now that AI is here, many people of different experience are using AI to generate scripts. Given the low footprint of LSL (and SLua) there are not a lot of sources for AI to get patterns and good practices from, so AI frequently hallucinates. Now that MCP is booming, is it possible that we can get an MCP server for LSL and/or SLUa so that we can use agentic coding (I hate the term vibe coding) in IDEs to generate better scripts? That way, less experienced scripters can produce higher quality scripts and experienced scripters can create content more efficiently. When is comes to SLua, having an MCP that tames the AI agent into using good practices will also help the learning curve for people that are adopting SLua, now and in the future.

Simple one this. Add a new flag to the llGiveAgentInventory command: [TRANSFER_IMG,key] This would allow a folder to be given with a pre-determined folder image. That would be great for unpacker huds as typically used in clothes purchases. Shops that used this would be giving a useful service to customers and the servers wouldn't have to store a unique image for each person updating that folder with their own folder images.

Hard coding link numbers into scripts is usually bad practice. So it's often best to search for something more concrete like the name of a linked prim and assign it to an integer using a loop by using llGetLinkName and comparing it to the link name you want to find. This isn't very friendly to new scripters who want to work with linked prims. A function that checks all of the prims in a linkset and finds the first instance of a specified link name would make scripts like this much easier. If I wanted to find the first instance of 'door left' in a linkset this could look like; llFindLinkNumber("door left");

We noticed that the SIT_FLAG_INVISIBLE flag was not implemented as proposed by Signal on https://feedback.secondlife.com/scripting-features/p/add-llsetsitflags-sitflaginvisible-et-al . We were hoping to have this implemented to make the avatar invisible so it would not require detaching all objects and wearing an alpha layer so you would not be rendered in smaller vehicles. It affects interacting with vehicles in a FPS setting when multiple avatars are on the objects. (For example, Avatars in the Commander Seat, Gunner Seat, and Driver Seat) This would also allow us to scale down vehicles without considering avatars rendering and ruining the immersion.

I feel this has to have been discussed before.... but can we get a version of llGetTimestamp() that returns SLT so we're not reduced to adding 70+ lines of code and the associated overhead just to get the same timestamp that's showing up in every viewer?

Add the ability to receive input from game controllers such as joysticks, Xbox controllers, etc. This will allow the creation ofhHelicopters and planes that use analog input from console controllers, attachments that control drones, arcade games, cranes, machinima puppetry, etc. This new feature will be implemented by adding a LSL event game_control(...) which script authors can use to capture and respond to input from users. For further details, see https://wiki.secondlife.com/wiki/Game_control