Prim to prim discussions

What is the best way for prima to talk to each other? For example I have one prim that needs to tell another prim a piece of information every 10 minutes or so. They need to be able to relay this information over as long a distance as possible. Right now I'm using llsay (99, "text" but I am sure there is a distance limit. I need something that would allow communication across an entire sim.

Any suggestions greatly appreciated.

llEmail.

limitation: delays the mailing script for 20 seconds...

so perhaps you could use a llMessageLinked to pass a message from the main script to another script in another object, and that second script does the emailing.

If the 20s delay doesn't matter, than forget that recommendation.

The range limits are

llWhisper: 10m
llSay: 20m
llShout: 100m

yeh, i'm not afraid to admit it, i am a noob scripter. I am tired of my scripts shouting to each other, this seems to be a cool alternitive to a repeater. How would you allow the object recieving to recieve the emial? Is there like an llListenforEmail or something?
Or does it continue as normal. I am using a defcon feature in my builds and they have to comunicate from a main hub a few thousand m away to get commands from it.

email event

...which only fires when you call llGetNextEmail and it's got an email in the queue, so you probably want to use a timer to call that regularly.

Almost!

You'll need to periodically call llGetNextEmail. If the receiving object is not regularly watching any event handlers, you'll probably have to put this inside the timer event handler and set the timer event with llSetTimerEvent.

If there is an email in the queue when you llGetNextEmail, then the email event handler will fire.

Here's some sample code that should give you the idea:

default
{
	state_entry()
	{
		llOwnerSay("My address is " + (string)llGetKey() + "@lsl.secondlife.com");
		llSetTimerEvent(30.0);
	}

	timer()
	{
		llGetNextEmail("", "");
	}

	email(string time, string address, string subj, string message, integer num_left)
	{
		llOwnerSay("I just got an email from " + address + " with subject " + subj + " that says " + message);
		if (num_left > 0) {
			llGetNextEmail("", "");
		}
	}
}

Thank you very much for all the wondeful responses. I will yet them tonight!

everything above this post I quoted... i don't get one word your saying T.T

Well, with the listen event, if someone within range says something that matches, the listen event gets triggered automatically. So if one object llShouts and another is listening on the same channel, the listen(...) event in that second object will get called.

The email(...) event is different - it doesn't get called on its own. It only gets called when you specifically check your email - kinda like hitting Send/Receive in Outlook Express. So you need to do the same thing here - keep hitting Send/Receive to preiodically check if you have any more emails.

That's what Intent said, and what Ordinal's script does. He starts a 30 second timer, and in the timer() event, he calls llGetNextEmail. This means his script checks for a new email every 30 seconds - like hitting the Send/Receive button every 30 seconds. If there is a new email available, the email(...) even will get triggered, where you can read the email and figure out what's in it and take whatever action you need to.

Thank you very much for all the wondeful responses. I will yet them tonight!

There are several ways around the 20s script delay with llEmail. My personal favorite involves llLinkMessage and several slave Mail Scripts. Another I have heard suggested is to rez a new obect and with the llEmail script in it and pass the info for the e-mail via a whisper on a random negative channel.