Scripting Features

Pertains to SIT_FLAG_NO_DAMAGE in https://wiki.secondlife.com/wiki/LlSetLinkSitFlags Currently, when an object with SIT_FLAG_NO_DAMAGE is shot whilst an avatar is on it, a combat log event is still generated and broadcasted on the combat log channel. This can lead to false positives and confusion when other avatars are using a form of hit marker/hit confirmation huds. While verbose logging is very welcome in the case of llAdjustDamage and the like, we can discard these in this use case as damage to avatars on this object is going to be either not possible, or processed in a scripted manner via on_damage/final_damage or other scripted means.

I'm not familiar with the internals of how the physics engine works but it would be great for many applications, vehicles in particular, if you could get additional physics information at that moment in time. Particularly vehicles need to understand if the vehicle is "grounded" or free falling. Currently this is done through llCastRay at the locations of the wheels downwards, but for some vehicles that are track based such as tanks that have a larger surface area this becomes bit more tricky to raycast when dealing with uneven and complicated surface environments like rubble or offroad. It would be great if a Linden could investigate additional useful physics info that could be surfaced to scripts if the Havok physics engine is already aware of certain information about objects. I do know that Havok physics has a 'sleep' state for objects which could be useful to know, likewise the script also enter a sleepier state by slowing down timer events if it's not actively moving for example. Gotcha is that this is stuff perhaps specific to Havok engine behaviour, so switching to a modern, multi-threaded engine like Jolt ( https://github.com/jrouwe/JoltPhysics ) which might not have this info could break this functionality. There might be also something from the linden vehicle code that could be surfaced, as VEHICLE_FLAG_LIMIT_MOTOR_UP requires the sim to know if a vehicle is airborne or not.

Right now, LSL has a bunch of one-way hash functions and an llSignRSA/llVerifyRSA function. What I am not yet seeing (and would like to have in case communications need more security) are functions to encode and decode a string (aside things like llXORBase64 which, let's face it, is not the pinnacle of security). Therefore I am proposing the following functions string llRSAEncrypt(string plain_text, string hash_algorithm, string rsa_private_key); string llRSADecrypt(string cipher, string hash_algorithm, string rsa_public_key); Since the RSA architecture is clearly in place for the sign/verify functionality, code-wise this might hopefully not be insurmountable. I don't know if such a protocol might be too much for current LSL limitations, but it would make quite a difference in creating more secure communication if the phrases sent/received are not fixed and therefore might not be known in advance. Thank you for your consideration.

Currently, I can get a list of all the objects attached to an AVI, and with the correct permissions, I can detach them. I would like the same capabilities for clothing layers. Obviously, there are a few things that you don't want to remove, but since most clothing is already Mesh objects, don't see why clothing layers shouldn't get the same treatment.