Who said that???

Yesterday, I was hanging out with some friends, when someone started to tease me, by using an "emoter" to make various folks say various outlandish things. [about me]

Now this was all in good fun, but I am a bit frustrated because I cannot figure out just exactly *who* was using the d&*% thing. (How can I get even if I don't know???)

Can anyone tell me? When I hear a disembodied voice, claiming to be me, how can I tell "who said that?"

Al

I'm curious too. Were the things said into chat? Was the text green or white?

You need a script that listens on the open chat channel, zero. Each time the script hears chat, it will know the key of the object emitting the chat. You can then use various methods to locate the object with the same key... such as a particle pointer which targets the key.

The script below begins to listen to all chat when rezzed, and assigns the key of the chatting object. Only the owner (you) will see the key and repeated chat. When you see offensive chat, you can click your object to stop the script. Then, copy/paste the key associated with the offensive chat into your handy particle pointer script and hopefully you'll find the source of the emoting.

integer handle;

default {
     on_rez(integer start_param) {
          handle = llListen(0, "", "", "");
     }
     listen(integer ch, string n, key id, string msg) {
          llOwnerSay((string)id + "<--SAID-->" + msg);
     }
     touch_start(integer num_detected) {
          if (llDetectedKey(0) == llGetOwner()) llListenRemove(handle);
     }
}

Getting a type mismatch error.......................dote

Thanks, I added a (string)id typecast. For whatever reason, sometimes keys typecast to strings automatically, and sometimes they don't. Anyway, thanks for testing, and can you try it again please. I'm at work, bored and drowning in American Idol-aholics.

Edit: It passes compile test with or without the typecast using lslint. Hmm?

HHEHEHE you need help dote hehe

Thank you for the fix
Usagi

I can soooo relate to that. My posting to this forum tends to cluster around break time, server down time and lunch.