Jump to navigation Jump to search
All Issues ~ Search JIRA for related Bugs
|LSL Portal||Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials|
|DEBUG_CHANNEL||Chat channel reserved for script debugging and error messages, broadcasts to all nearby users.|
|PUBLIC_CHANNEL||Chat channel that broadcasts to all nearby users. This channel is sometimes referred to as: open chat, local chat and public chat.|
- Messages sent on channel zero and DEBUG_CHANNEL are throttled to a rate of <200/10sec, per region, per owner/user.
- Once the rate is exceeded, all following messages on channel zero or DEBUG_CHANNEL will be dropped until the send rate is again below 200/10sec for the previous 10 sec. Dropped messages, despite being dropped still count against the limit.
- listen works, where a can only be heard by any prim in the object if and only if the root prim is capable of hearing it. can only be heard within 20 meters of the speaking prim (rather than the root). This is contrary to how the event
can be a maximum of 1024 bytes. This can convey 1024 ASCII characters, or 512 UTF-8 characters such as
- A prim can not hear itself, this to prevent problems with recursion. It can however hear other prims within the same object.
- Channel PUBLIC_CHANNEL. Everyone can hear chat transmitted on this channel. All other channels are private channels (not sent to users, with the exception of DEBUG_CHANNEL). is the
- Consider using llInstantMessage, llOwnerSay, or the DEBUG_CHANNEL for debugging purposes. If DEBUG_CHANNEL is used as , the script will say to the Script Warning/Error window.
- Note, however, that when using DEBUG_CHANNEL, what you consider to be 'debugging messages' will still be seen by others as scripting errors indicated by the floating 'script error' icon.
- If one object 'says' something to another object (e.g., a button that, when touched, turns on a lamp), it is a good idea to use a very negative channel, e.g.,
-5243212but don't just use any number take a look at the User-Defined Protocols & APIs and choose one that won't interfere with other protocols. If you are going to sell your script widely, please add it to the appropriate known chat channels list so others won't interfere with your product (do keep in mind you should build your product so that it handles interference appropriately).
- From at least September 2016 (see Release Notes/Second Life Release/126.96.36.1990038), viewers have been able to chat on negative channels, although chat is limited to 254 characters. Negative channels have been popular for script communications because the standard SL client was unable to chat directly on those channels (
/-xxxx messagewould not chat
-xxxx). The only way for a viewer to generate chat on negative channels prior to llTextBox was to use llDialog which was limited to 24 bytes.
- Be aware that if you mistakenly use an integer bigger than the maximum or smaller than the minimum, SL will treat the literal number as a float and convert it implicitly to an out-of-range integer, resulting in
1, without giving a script/syntax error (since this implicit conversion is legitimate). This means that all scripts listening to an out-of-range integer will be listening to channel 1 instead! (see also llListen).
|•||llListen||–||Ask for listen events|
|•||llInstantMessage||–||Sends chat to the owner only (or to some other user only) to avoid spamming the PUBLIC_CHANNEL|
|•||llOwnerSay||–||Sends chat to the owner only to avoid spamming the PUBLIC_CHANNEL|
|•||llRegionSay||–||Sends chat region wide|
|•||llRegionSayTo||–||Sends chat region wide to a specific avatar, or their attachments, or to a rezzed object of known UUID|
|•||llShout||–||Sends chat limited to 100 meters|
|•||llWhisper||–||Sends chat limited to 10 meters|