It won't listen to me!

For the life of me, i can not get llListen to hear llSay from another script.

i.e.


default
{
state_entry()
{

llSay(5511,"stop";
llSleep(10);
llSay(5511,"go";
llSleep(10);
llResetScript();
}
}

from the chat bar, /5511 stop and /5511 go, work just fine. Both scripts are in the same prim. Why would it work with chat and not from this script?

What am I missing?

Objects can't hear their own chat messages - use llMessageLinked to talk between scripts in the same object..

THANKS!

I didn't know that.

I only discover a few hundred things I didn't know about SL every day!

Off to fix it!

TY again.

If they could hear themselves, all scripts that listened and talked would have to check that they weren't hearing themselves - if they didn't do this check, you'd get scripts losing their minds and getting stuck in feedback loops...

Glad I could help (and several others did in your other thread - I just made it to this one first ).

"losing their minds and getting stuck in feedback loops..."

That seems to be what is happening to me since I started SL.

Yes they did say, llMessageLinked, but I was in the wrong forum and got yelled at, LOL, (not really), stupid browser tabs!

Your concise reply, "Objects can't hear their own chat messages" helped me a lot. There many obscure things to learn in SL, and I appreciate everyone that has helped me, in BOTH forums.

When you learn the reason WHY things do not work the way you expect, it becomes a learning experience.

I just moved the script to another prim and it worked perfectly.

BTW

Don't try llScream(5511,"go";

it didn't work either, hehe!

for what it's worth.. llMessageLinked() and link_message() {}
seem to be more efficient than llListen()'s. For communicating between prims on a linked object (or on a single prim) they're definitely the way to go! =)

Agreed...if you're going to have messages traveling through the same object, you should really use llMessageLinked(). Not only is it faster than an llListen, it's also more secure.

To clarify things, as I am doing a build, I experiment with possible animations first. Although I am still learning LSL, the quick and dirty way to script, to achieve my desired effect is the first and foremost objective. If in fact, I am on the right track and what I expect to see from my animation is achieved, next, but not always, I look for the proper and most effective way to optimize my script.

I first started off with millions of timers. I couldn't figure out why I couldn't walk across the room anymore. As I learn about LSL I fumbled my way into more efficient scripting.

I care about creating lag, and want to do my part in preventing as much as possible and not introduce any more that necessary.

To a somewhat novice, and totally confused woman, I have to admit, things that are obvious to the 'enlightened' are not so to some of the rest of us.

That simple "Objects can't hear their own chat messages" from Meade was like a bolt from the blue! I don't remember EVER reading that in LSLWiki.

I learned programming by 'Trial and error', am used to the old Flow Chart system, and find myself totally buried in {{ help me }}'s

I realize it is not your job to "Set one straight" so to speak, but a brief explanation is like a gold mine to me.

When I got my first 'Prim hair' I wore a bald wig underneath. Since then, because of all of the hair I have pulled out learning LSL, I don't need it anymore!

hehe!

Thank ALL of you for you input

Warning! Warning! Danger Will Robinson! Danger! Danger!

Sometimes it might be more secure. Depends on what you're doing, where you're doing it, and what you're trying to accomplish. There are cases where it is more secure, and cases where it isn't. Depends entirely on what information you're trying to hide, and from whom.

Do note that if your object has modify permissions, and someone wants to see what link messages are being passed around inside, they need only drop in a script of their own to view them. I've done this in objects I wanted to alter the behavior of, but all the scripts were no-modify. Could still do what I wanted by sending the right link messages, after decoding the inter-script communications.

(Sorry, whenever I see the word "secure" used in a generalization, huge alarms go off in my head. All generalizations are false, and false beliefs about security can be disastrous.)

Just when I was about to give up, I finally got my animation working.

Thanks to all for your help. Maybe someday, I will get past the "Hello Avatar" stage of LSL.

The final product is a soaring / flapping buzzard. I just have the test version about completed, but am having a dickens of a time getting control of the 'little bugger'.

Once I can work out the controls, maybe I can sell it.

You can view it here: http://www.youtube.com/watch?v=D9dYu5WwOv0

Comments are welcome.

Thanks again,

Yes, sorry. I should have been more specific...

...I was meaning secure as in no chance of 'cross-talking' with other scripts in the area that may be using listens and llSays.