LlInstantMessage

Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

InstantMessage

llInstantMessage

Summary

Function: llInstantMessage( key user, string message );

2.0	Forced Delay
10.0	Energy

Sends an Instant Message specified in the string message to the user specified by the key key.

• key	user
• string	message

Caveats

• This function causes the script to sleep for 2.0 seconds.
  • For applications where this is problematic, it's possible to place the call to llInstantMessage in a child script and pass the information to that script via other means.
• The message sent can not be longer than 1024 bytes.

Examples

key owner;

default {

    on_rez(integer start_param)
    {
        owner=llGetOwner();  // get the key of the objects owner.
    }
    touch_start(integer total_num)
    {        
        llInstantMessage(owner,llKey2Name(owner)+", " + (string)total_num +" Avatar(s) touched me!");
    }
}

Notes

Instant Messaging has the benefit of allowing communication from an object to an avatar anywhere in the Grid. The downside is that an object cannot receive an Instant Message, therefore an avatar cannot send an Instant Message to an object. It's a one-way communication avenue. Also, the two-second script delay can be considered a downside in some applications.

See Also

Functions

• llWhisper
• llOwnerSay
• llSay
• llShout

Deep Notes

Signature
function void llInstantMessage( key user, string message );