Local

24 June 2018

C10 - removed firstname, lastname and agent parameters in flavor of the name parameter.
C10 - added the region parameter.

9 October 2018

5 June 2016

21 April 2015

Release 7.105 - the local notification has been upgraded to include the source type, the audible level and the volume.

4 April 2015

Release 7.94
The local notification no longer passes script errors from the debug channel as part of local chat. Instead, the new debug notification has been introduced for that purpose.

5 March 2015

local (Notifications)
Type	Corrade progressive notification
Notification	`local`
Data	`type`, `firstname`, `lastname`, `owner`, `item`, `position`, `message`, `entity`, `audible`, `volume`
Structure	ChatEventArgs
Description	Messages on local chat.
Commands	None.
Last Changes	C10 added `name` and `region` parameters.

Data

Data	Description
`type`	The type of the notification.
`owner`	The owner UUID of the person sending the message.
`item`	The item UUID of the object sending the message.
`position`	An LSL vector representing the position of the originating chat.
`message`	The message sent.
`entity`	Either `System`, `Agent` or `Object`.
`audible`	Either `Not`, `Barely` or `Full`.
`volume`	Either `Normal`, `Whisper` or `Shout`.
`name`	The name of the object or avatar sending the message.
`region`	The region where the message was detected.

Some messages on local chat will appear with Barely but no message data will be sent - in such cases, Corrade has sensed that a message was sent by someone on local chat but was too far away to receive it. You should check that the data returned by the local notification contains a message key and handle the case appropriately when it does not.
This notification is radar-bound.