Odd open channel + linkmessage

Ok, I'm testing the open channel behavior.
sample1

default
{
    state_entry()
    {
        llListen(0, "", "", "");
    }

    listen(integer channel, string name, key id, string message)
    {
        llSay(0, message);
    }
}

This is no problem. But if you linked two objects and...
sample2(sender)

default
{
    state_entry()
    {
        llListen(0, "", "", "");
    }

    listen(integer channel, string name, key id, string message)
    {
        llMessageLinked(LINK_SET, 0, message, "");
    }
}

sample2(receiver)

default
{
    link_message(integer sender_num, integer num, string str, key id)
    {
        llSay(0, str);
    }
}

What do you think this happens?
It repeats my saying forever. I'm not sure why this happens.
If you set any filter in llListen such as channel number or llGetOwner as key, it doesn't happen. Does anyone tell me why, plz?

Hmmmmm - that's exactly the opposite of what BadGeo: Chat says should happen. Objects are supposed to ignore themselves.

Seagel, what happens if you put both scripts into the same prim? Does it still get into an infinte loop?

All, is this an error in the wiki, or a bug in LSL?

This is where you need to remember that "object" and "prim" are used interchangably, often in a confusing manner.

A script will ignore all chat that orginates from it's prim. But if it comes from another prim in the link set, then it will hear it.

Almost, but not quite, Strife. According to both general use and BadGeo: Object and according to BadGeo: ChatIn other words, all prims are objects, but not all objects are prims. Some objects are linked sets of multiple prims, which the wiki clearly says should not hear themselves.

So my question is: Do we bug-report that prims in a multi-prim object hear other prims within that object - or do we change the wiki to say that "Prims that output chat never..."?

Well, in brief, I answer Ben's this question.
No. It doesn't still get into an infinte loop when I put both scripts into the same prim.

Ben, I think BadGeo issue is another. The prim doesn't Say anything by itself and doesn't even listen to itself. It sends just its message via llMessageLinked. This trouble is that when the script listened to something by open channel, it would repeat to send messages permanently. Or, just repeating execution under the link_message event.

Strife, yes, it may be. But this is a reproducible issue.

The problem there is that:

1. Script A hears you say something, and uses llMessageLinked to pass it to script B.
   
2. Script B gets the link message, and says the message on channel 0.
   
3. Script A hears script B talking on channel 0 and uses llMessageLinked to pass what it hears back to script B.
   
4. Script B gets the link message, and says the message on channel 0.
   
5. Script A hears script B talking on channel 0 and uses llMessageLinked to pass what it hears back to script B.
   
6. etc
   
7. etc
   

BadGeo states that because these scripts are in the same object (you said your prims were linked together), script A should not hear script B chatting - but apparently it does.

Thank you, Ben. I think I'm a fool.

Surley object B says it and A listens to it and repeats it. So what I took for a trouble was my mistake. Sorry, for bothering you.

Speaking of BadGeo, it seems to make a mistake between object and prim in Wiki, I guess.

With everything others and myself have learned from your posts about animations, I'm glad I could return the help.

Thanks for your kindess.

Thanks for pointing this out - I fixed the chat page. I also did a little revision to make wording clearer, lemme know what you think
==Chris

Thank you, Crhis.

What about this?

but this practice is discouraged because it is best that there is nothing (the use of llMessageLinked is recommended instead)