AdminBot raises events to inform your script about errors, chat IMs and other things happened. To catch it, use the LSL link_message event (see AdminBot Examples for usage patterns).
LSL link_message event has the following syntax:
link_message( integer sender_num, integer num, string str, key id )
For AdminBot, num will contain the event code (see below). str and id value depend on the event.
The following events can be raised by AdminBot gateway:
|Event / Description||str||id|
|Raised when command error occurs.|| first line - command status code
second line - text explaination
|Raised when group has been set successfully (group exists and not expired)||group name||group UUID|
|Raised when there was an error setting the group (group does not exist, expired etc)|| first line - group status code
second life - group expiration date
|Raised after successful AdminBot initialization. Delivers the bot name and UUID serving the choosen group.||SL bot name||SL bot UUID|
Group status request events
|Reply when you request the group status using SB_STATUS_QUERY|| first line - group status code
second line - group expiration date
Avatar status request events
|The reply to a SB_AVATAR_GROUP command.|| 0 - avatar is not in the group
1 - avatar is in the group
Group chat events
|Raised when bot successfully connects to the group chat (see SB_CHAT_LISTEN)||---||Group UUID|
| Raised when bot receives the group chat message.
*Group chat saving must be enabled.
|Resident name: Message||Resident UUID|
The numeric values are available here: Commands and events values.