Big News in Scripting and Animation Overriding

[Nalates Urriah]

Today news broke on significant changes that are coing to Second Life. These changes affect those that make scripted products, like animation overriders (AO). But, the changes affect more than just AO's.

Plus, we are getting ribbon particles.

See the details here: Second Life Scripting Changes - AO & Particles

[Rolig Loon]

Fascinating, especially the AO functions.  On quick reading, though, there's one part that isn't quite clear to me.

"Once the script is run, the attachment that sets the animations can be detached. As best I can tell at this point it does not HAVE TO be attached. It could be run from any prim that has your permission."

So, suppose you attach something that requests PERMISSION_OVERRIDE_ANIMATIONS, and then changes your default walking animation.  Does this really say that permission is not released once the scripted object is detached?  That's different from all other permissions. I can see all sorts of potential confusion if that's true.  If it's true for objects that you link to as well --- seats and poseballs -- it could be a nasty griefer tool.  Or maybe I'm just not understanding.......

[Ela Talaj]

My only excitement is that advertised changes do not appear "significant". This is very good because the word "significant" usually scares the living daylights out of ppl in engineering world as it inevitably means that something that has worked before will quit working and usually in a totally different part of the system. But as long as Lindens add parameters to the particle system and make a few animation wrapper functions I suppose we would be safe... Yet I've been wrong before

[Helium Loon]

Rollig, I read it differently.

 

I think (note, this is not tested, of course) that what it is saying is that since these are server side settings, the calls to change them persist.

 

Much like setting the texture on a prim via llSetTexture(), once it's set, the script could simply be deleted.....the texture stays.  When you alter the animation override via these scripts, it 'sticks' for the session.

 

Now, unlike llSetTexture() and such, it doesn't persist between sessions.  So the next time you login, your avatar is back to the normal default animations on the server.

 

So an object could request permissions, change the AO settings, then simply delete itself.  The settings would hold until something else changed them, or the avatar logged out.