Fix llSetScriptState!

For us scripters, having llSetScriptState actually turn scripts on and off is a huge plus! Right now it seems completely random as to when it works, with it failing most of the time.

I understand the security issues behind not having one script be able to enable/disable another within the same object, but maybe check the owner and allow it only if the owner of the object also owns the scripts (script ownership is another feature I'd love to see).

PLEASE consider fixing the current implementation, or at the very least, let us know why it is not working consistently and show us some workarounds. Thanks!

I'm getting stuck on this bug too...

I have a bunch of parts to a build and I want them all to have the same script. When I change it, I have to go around to each and every object (some of them not too easy to get to when it's all together) and open it up, delete the old script, and drag in the new script. A pain.

(Being able to add a script by KEY so that they all point to the same source file... THAT would be WONDERFUL. But that's feature request, and this is a bug report/query.)

What I thought I could do is have them all handshake with a tool object that tells them there is a new version available. The outdated script requests the new version and deletes itself. The tool then gives it the new script with llGiveInventory, but it comes in un-running. So each of the objects also has a simple script that watches for changes to the inventory that will kick the new script running again with llSetScriptState...

...But llSetScriptState doesn't do anything.

All my objets have the same owner, permissions, and what-not. There should be nothing preventing this from working.

Lindens, can we have an update on what's going on here? Is it broken, or is there something aspect of this command that we just don't know about?

Help me Obi-wan, I've crashed, and I can't reboot.