The Ghost of Scriptmas Past..

I'm posting this in here because it really seems to be an issue with the way SL handles scripted prims rather than an actual building issue.

What I've observed is if I take a prim, plop a script into it (I make jewelry so lets say a particle script), then later remove the script (stopping it first), take a copy, when I rerez the scriptless copy days later, the new empty prim will behave as if it's a scripted prim, spewing particles from some mystery phantom source.

I've tried stopping running scripts, replacing the scripts, etc., and nothing seems to make the prim stop burping out particles.

Other than recreating every buggy prim in my inventory is there a way to work around this?

Add the following script, and it will turn the particles off. Particles are the same thing as setting a texture on a prim. Once set, you have to change the texture. Just removing a script that sets a texture is not enough, you have to actually change the texture.

What this script will do is to set the particles to nothing, thereby turning the old ones off.

  default
  {
  	state_entry()
  	{
  		llParticleSystem([]);
  	}
  }
  

yup its the same with hovering text
just drop a stop particles script in it
then delete the script.
it has something to do with the way
its saved in the prim parameters i think.
-LW

Thank both of you very very much.

I was wondering if it was a persistent state that got associated with the prim itself and indeed it is. Now I'm back to work.

For good measure, a version to remove floating text:

default {
     state_entry() {
          llSetText("", <0,0,0>, 0.0);
          llRemoveInventory(llGetScriptName());
     }
}

and a version to remove animated textures:

default {
     state_entry() {
          llSetTextureAnim(FALSE, ALL_SIDES, 1, 1, 0, 0, 0.5);
          llRemoveInventory(llGetScriptName());
     }
}

These two scripts do their thing, then delete themselves. They're handy as quick and easy utility scripts to use again and again.

Just for completeness looped sounds also become a property of the prim and replacing the various kill lines with llStopSound(); will stop that.

Any other scripted starts that need a scripted stop rather than removing the script people have come across? I actually have a little set of scripts to do all of those mentioned so far.

The offset and rotation vectors associated with where you sit when you sit on a prim, which we use to write within-sim teleporters, is a prim property. Write a teleport script, use it once, delete the script, then sit on the prim, and you'll find yourself sitting at the same offset and rotation called for by the teleport script.

I believe llTargetOmega (for constant client-side rotation) is another one. The kill line for that would be:

llTargetOmega(<0,0,0>, 0, 0);