Proper Multi message listener format

Hi all,

I want to write my talker/listeners in a way that is as sim friendly as I can. Might someone please comment on the following structure, and let me know if I am being evil to sims with these methods?

Thanks so much!
(just want do do the right thing for everyone)

The Talker:

touch_start(integer total_number)
{
if (condition == TRUE)
{
llSay(123, "Msg1" );
}
else
{
llSay(123, "Msg2" );
}
}


The Listener:

state_entry()
{
llListen(123,"",NULL_KEY,"Msg1";
llListen(123,"",NULL_KEY,"Msg2";
}

listen(integer channel, string name, key id, string message)
{
if (message == "Msg1"
{
llSay(0, "Msg 1 received.";
}
else
{
llSay(0, "Msg 2 received.";
}
}

Depends of the distance - llWhisper is better if distance between talker and listener is 10m or less'
Channel in negative numbers and really big works better because of less chance of chatter from other objects on same channel.


In your example this is not needed since you only compare for Msg1

also if you know the object key of the talker object you can use that key instead of NULL_KEY

Someone wrote a tip sheet about listens, I can't seem to find it right now, but maybe someone else have it. But the general ideal is that listens can be very laggy since they have to process all chat within range. It outlined the steps that have to be processed for listens, example: 1) in range 2) on channel etc.

The wiki has some tips:
http://lslwiki.net/lslwiki/wakka.php?wakka=llListen

Hi Destiny, thanks for the comments!

You say that the second listen is not needed... but I find that it is... if it is not there, for Msg2, then the listen event is not triggered at all... unless I am missing something.

Thanks for the whisper tip... that works fine!

If you want to receive more text pattern then just set up an open listen on that channel and filter locally. This is, somewhat paradoxically, more sim friendly than setting up specific Listens. The reason I have heard quoted is that the server is doing less work by routing everything to you than by having to check for just one or two specific strings.

Keep in mind, that if these are for prims that are linked together, it may be better to use llMessageLinked and link_message() {} instead.

Thx Jopsy...

I wish this was the case... This is for a HUD that talks to a vehicle. Wouldn't it be cool if linked messages could be sent to the things you are sitting on?!!!!

-Ryder-

Oh... super! That is exactly the kind of tip I was looking for

-Ryder-