Disabling whispering

Does anyone have a solution to disable whispering in an object or set of objects? I know that they can be muted but I am looking for something scripted where I can say 'whipser off' and 'whisper on' So that the object(s) will obey.

=)

That would have to be some feature in the script.

If programmed for llWhisper, then it will do that, but if script have the ability to turn off that whisper then you could, so if you can modify the script you can turn it off, other wise only way is to mute it

Got it michael. I figured it out! =)

That's what I am asking. For a solution or procedure to use in a script that will enable MY SCRIPT to turn whisper off and on.

If anyone has a solution, idea, or script that would be useful. Please post! =) Smiles

I wrote this directly here in the forum, and have not tested it in-world. But it should work.

integer iWhisperEnabled = TRUE;

MyWhisper( string msg )
{
    if( iWhisperEnabled )
    {
        llWhisper(0,msg);
    }
}

default
{
    state_entry()
    {
        llListen(1, "", llGetOwner(), "");
    }

    listen(integer channel, string name, key id, string message)
    {
        if( message == "whisper" )
        {
            if( iWhisperEnabled )
            {
                iWhisperEnabled = FALSE;
                llOwnerSay("Whisper Disabled");
            } else {
                iWhisperEnabled = TRUE;
                llOwnerSay("Whisper Enabled");
            }
        }
    }

    touched( integer num )
    {
        MyWhisper( "I've been touched!" );
    }
}

Yes, that looks pretty much like what I was thinking. Replace all llWhisper calls with MyWhisper calls and you're set.

touched( integer num ) 
    { 
        MyWhisper( "I've been touched!" ); 
    } 

I think you meant:

touch_start( integer num_detected ) 
    { 
        MyWhisper( "I've been touched!" ); 
                    }
          } 

num vs num_detected makes no difference

It's just a variable name. In my own scripts, I usually just use touched( integer num_agents )

<shrug>

no, 'cos that's got one too many }s

I think Exile was referring to using 'touch_start' instead of 'touched'. It's funny how 3 people look at the same thing and see 3 different things

Oh, heh... ya, "touched" won't work.

But:

touch_start( integer num )
touch( integer num )
touch_end( integer num )

Should all work in this case.

Oh yeah, fair enough (though it still has too many }s)

Lol, okay. w/e. =p