Difference between revisions of "LlSay"

From Second Life Wiki
Jump to navigation Jump to search
m
(Reflow the text to read more accurately easily: 1. Point to llInstantMessage as to llOwnerSay; 2. Fill out blank spots in lists; 3. Conform to more English grammatical conventions; Etc.)
Line 11: Line 11:
|spec
|spec
|constants
|constants
|caveats=*Text can only be a maximum of 1024 bytes.
|caveats=
*Text spoken can only be heard within 20 meters of the speaking prim (rather than the root). This is contrary to how [[listen]]s work, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
*Text spoken can only be heard within 20 meters of the speaking prim (rather than the root). This is contrary to how the event [[listen]] works, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
*A prim can '''not''' hear itself, to prevent problems with recursion.
*Text can only be a maximum of 1024 bytes.
*A prim cannot hear itself, to prevent problems with recursion.
|examples=<lsl>default
|examples=<lsl>default
{
{
     state_entry()
     state_entry()
     {
     {
         llSay(0,"This is an incredibly useless program." );
         llSay(0,"Hello, Avatar!");
     }
     }
}</lsl>
}</lsl>
To avoid making your object spam its neighborhood, use llOwnerSay or llInstantMessage.
To avoid making your object spam its neighborhood, use [[llInstantMessage]] or [[llOwnerSay]].
|helpers
|helpers
|also_events=
|also_events=
{{LSL DefineRow||[[listen]]|}}
{{LSL DefineRow||[[listen]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|Receives chat}}
|also_functions=
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llListen]]|Ask for listen events}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the {{#var:PUBLIC_CHANNEL}}}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to the owner only (or to some other user only) to avoid spamming the {{#var:PUBLIC_CHANNEL}}}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the PUBLIC_CHANNEL}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|}}
|also_tests
|also_tests
|also_articles
|also_articles
|notes=
|notes=
Consider using [[llOwnerSay]] or channel {{#var:DEBUG_CHANNEL}} for debugging purposes.
* Channel {{HoverText|0|Zero}} is the {{#var:PUBLIC_CHANNEL}}. Everyone can hear chat transmitted on this channel. All other channels are private channels (not sent to users).
 
* Consider using llInstantMessage, llOwnerSay, or the {{#var:DEBUG_CHANNEL}} for debugging purposes. If DEBUG_CHANNEL is used as '''channel''', the script will say '''msg''' to the Script Warning/Error window.  
If one object 'says' something to another object (e.g., a button that, when touched,
* 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  (although never more negative than the most negative 32-bit integer that is -2,147,483,648), ''e.g.'',
turns on a lamp), it is a good idea to use a very negative channel  (if never more negative than the most negative 32-bit integer that is -2,147,483,648), e.g.,
<lsl>
<lsl>
     llSay(-5243212,"turn on");
     llSay(-5243212,"turn on");
</lsl>
</lsl>
Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to [[llTextBox]] was to use [[llDialog]] which was limited to 24 bytes.
Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to [[llTextBox]] was to use [[llDialog]] which was limited to 24 bytes.
If {{#var:DEBUG_CHANNEL}} is used as '''channel''', the script will say '''msg''' to the Script Warning/Error window.
Channel {{HoverText|0|Zero}} is {{#var:PUBLIC_CHANNEL}}. Everyone can hear chat transmitted on this channel. All other channels are private channels (not sent to users).
|cat1
|cat1
|cat2
|cat2

Revision as of 11:42, 24 December 2008

Summary

Function: llSay( integer channel, string msg );

Says the text supplied in string msg on channel supplied in integer channel.

• integer channel – output chat channel, any integer value
• string msg – message to be transmitted
Channel Constant Description
DEBUG_CHANNEL 0x7FFFFFFF Chat channel reserved for script debugging and error messages, broadcasts to all nearby users.
PUBLIC_CHANNEL 0x0 Chat channel that broadcasts to all nearby users. This channel is sometimes referred to as: open chat, local chat and public chat.

Caveats

  • Messages sent on channel zero[1] 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.
  • Text spoken can only be heard within 20 meters of the speaking prim (rather than the root). This is contrary to how the event listen works, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
  • Text can only be a maximum of 1024 bytes.
  • A prim cannot hear itself, to prevent problems with recursion.
All Issues ~ Search JIRA for related Bugs

Examples

<lsl>default { 

   state_entry()
   {
       llSay(0,"Hello, Avatar!");
   }

}</lsl>

To avoid making your object spam its neighborhood, use llInstantMessage or llOwnerSay.

Notes

  • Channel 0 is the PUBLIC_CHANNEL. Everyone can hear chat transmitted on this channel. All other channels are private channels (not sent to users).
  • Consider using llInstantMessage, llOwnerSay, or the DEBUG_CHANNEL for debugging purposes. If DEBUG_CHANNEL is used as channel, the script will say msg to the Script Warning/Error window.
  • 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 (although never more negative than the most negative 32-bit integer that is -2,147,483,648), e.g.,

<lsl> 

   llSay(-5243212,"turn on");

</lsl> Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to llTextBox was to use llDialog which was limited to 24 bytes.

See Also

Events

•  listen                 – Receives chat

Functions

•  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
•  llShout – Sends chat limited to 100 meters
•  llWhisper – Sends chat limited to 10 meters

Deep Notes

Search JIRA for related Issues

Footnotes

  1. ^ Channel zero is also known as: PUBLIC_CHANNEL, open chat, local chat and public chat

Signature

function void llSay( integer channel, string msg );
Retrieved from "https://wiki.secondlife.com/w/index.php?title=LlSay&oldid=184713"