SB_INVITE_SEND
Invites resident to the group.
// Command usage:
API parameters
llMessageLinked function accepts str and id parameters. Their meaning for SB_INVITE_SEND is explained below:
| Variable | Required | Description.
| |
|---|---|---|---|
| str | yes | flags, separated by commas
The following flags can be used:
See the "Examples" section below. | |
| id | yes | avatar UUID | |
Comments
Important: existing members check
Bot updates the list of existing members every 15-20 minutes. Thus:
- if avatar leaves the group, bot will not invite him to the group during the next 20 minutes.
- if avatar just joined the group, an immediate second join command will send another group invitation (bot still does not know about new group member).
By default, existing group members are not invited. Use the FORCE flag to invite them too.
Take this into account while testing your group inviter.
Roles
By default, an invitation is being sent to "Everyone" role. This can be changed by using the Role flag.
1. Use the role name, not the role title! The name is case-sensitive
Make sure that you use the role name. Using the role title (or the role tag name) won't work. Also remember that role name is cAsE SeNsItIvE!
If role-name is misspelled, then invite will work though but will invite avatars to default Everyone role.
2. Give the necessary permissions to the bot!
Inviting to the specific role requires additional group setup:
- "Assign members to Assigner's Roles" ability given to the bot
- Bot have to be a member of that role.
If bot has lack abilities, the flashing pop-up appears in viewer of the invited person, reporting that "Inviter is lack of permission...".
Read Inviting residents to custom role page for more details.
Examples
Invite resident to the group on touch:
touch_start(integer detected) {
// "FORCE" means to invite existing group members too
llMessageLinked(LINK_SET,SB_INVITE_SEND,"FORCE",llDetectedKey(0));
}Also see Group Inviter Script for a complex group inviter example.
