Four questions about bling

For anyone who was wondering, the following features are all persistent to a prim... i.e. removing/stopping the script DOESN'T remove the effect and the scrubber script or similar is necessary.

Floating text
Sit text (the label that appears instead of 'Sit Here' in the pie menu)
Texture animations
Bling and other particles
Sit position
Client side rotation
Looped sounds

All of these can be sources of confusion to newbie scripters. There may be others I'm not aware of waiting to trip me up

Thanks, Beezle! I often get Alexin's help in editing the script to remove the bling, but this is much easier and I don't need to bother him.



Ditto! I never purchase no mod items if they have bling. With very very few exceptions, I can't stand bling.



And the goodness keeps coming! Thank you, Qie!



I agree wholeheartedly! If creators followed this recommendation, Ann, I might actually consider purchasing a no mod bling item.

angel

I found one other way based on the excellent responses here. Though I'm sure the scrubber works more efficiently, I was too impatient to learn it yesterday. I found a bling script in a pendant, opened it, had no clue what I was looking at, but found something about transparency. I set it all the way to full transparent with a little experimentation, then removed the script. No more bling.

That was probably the hard way. I'll keep the scrubber for the next time I have bling I can't turn off.

The bling is still being created and the client is still being required to make updates, but it is just not visible.

This is a pretty inefficient way of doing things, tbh. You still swallow the bandwidth that the particles create but get none of the benefit of the visual effect.

Not recommended as a "solution"

Uh, well. This isn't Scripting Tips, but if the script might need to listen to a different agent (like a different owner) when it's rezzed, the llListen belongs somewhere other than state_entry (such as on_rez itself). For really simple scripts, yeah, it's fine to just llResetScript and start afresh each time, but a lot of beginning scripters do this as a kind of magical incantation--which makes them extra confused when they try to do anything more complex--e.g., preserving state between attachment events. (This confusion has even given rise to a totally specious rumor of a bug in llGetOwner!)

Really, though, there are only a very few scripts that should listen for agent input not generated by llDialog, anyway. Some, of course, but really very few.

/me points to post #33, which has a script that removes bling and hovertext without requiring any interaction/listens. Just remove the original blingy/hovertext script (if the prim creator left it in), drop in the script in the prim, and forget it. It deletes itself.
.

most HUD's use lllisten as well so they don't help the bling lag /listen problem

I actually have a suite of 'Scrub' scripts:
"Scrub Particles",
"Scrub Hover Text",
"Scrub Physics",
"Scrub Sound",
"Scrub Texture Anim",
"Scrub TargetOmega" ... etc.

each of which are simply something very like:

  default { state_entry() {llParticleSystem( [ ] );
  llRemoveInventory( llGetScriptName() ); }}
  
CODE

 
 So when I need to clear any one, I just type: "Scrub" in my inventory search and drag/drop the desired script into the offending prim.  No menu to deal with. =)
 
 Sadly, I'm a hovertext monster, and until we get the ability to render HTML or a Notecard on the side of a prim am likely to polute the air with it.  So I've also got a set of "SetText()" do-and-die scripts that will grab an object's description and turn it into hover text in different colors.
 
 Be creative with llRemoveInventory( llGetScriptName() ); and you can create an entire set of useful utilities of your own.  Name them well so you can find them and use them as needed! =)

Look at any script in an animal avatar. They all do pretty much the same thing: Listen to the owner on a channel, and reset when rezzed. Only a handful reset some other way. The point of the reset is because these scripts are meant to change owners - they're used in for sale objects. Take away the reset or the listen itself, and you lose most of the interesting features like moving ears and color changing eyes. llDialog also requires a listen for it to actually do anything, because when you click a button on the dialog, the button's name is said in chat by the person, not an object. You can use link messages to communicate with scripts in the same link set, but to control things in other objects you need listens. You just have to be careful not to use too many of them, and filter them very strictly.