Group.Invitor.Fixed

Thanks a lot for reading these instructions for Group.Invitor.Fixed service ! This service is part of SimpleServiceBot product, from MyRoBoT (click for more information).

GROUP.INVITOR.FIXED SERVICE PRESENTATION

This service is an extension of Group.Invitor standard service. See this link to know more.

Group.Invitor.Fixed service removes some limitations of Group.Invitor service, by allocating you a slot for your group on a dedicated bot.

You accept the risks of having one single bot while renting this service: service can stop if bot software is under restart.

Please note however that MyRoBoT is going further than competition to try to avoid denies of services (DOS). In particular, instead of 1 bot per group proposed by competition, MyRoBoT will grant you 2 bots per group, thus reducing the DOS situations.

FIXED BOT ADDED FEATURES

Although a Fixed bot has a higher probability of failure, it can also propose a bigger set of features.

In comparison to Group.Invitor service, the Fixed version can ensure:

• Invitations to closed, payable enrollments or private groups
• Invitations to a specific group role (See Tips & Tricks)
• Avatar group Ejection
• Role Addition to an avatar already being member
• Role Removal from an avatar already being member
• Enhanced featues like the "Ban" one: This service can store a list of 200 banned avatars
  • A newly banned avatar will be ejected immediately from the group
  • This avatar won't be able to join group via standard Group.Invitor prims
  • The bot will browse group members every hour, kicking out banned avatars if any
  • A fixed bot will listen for group chat: a group officer (with good permissions) will be able to ban someone by directly requesting the ban from the group chat: The syntax is:

    ban AvatarFirstName AvatarLastName

    For instance:

    ban Maeva Anatine

Note1: Of course, trying to eject, ban or remove an owner role to a group owner will fail

PACKAGE ADDED FEATURES

The standard Group.Invitor package perfectly fits the Group.Invitor.Fixed service.

Moreover, once used with a Fixed bot, it can propose enhanced features:

• Role can be specified while specifying group name
• Ban lists are enabled

In addition, a supplemental package is provided to you, to benefit from additional features of Fixed service.

Currently this supplemental package contains 2 plugins for renting systems (see below).

STATISTICS ADDED FEATURES

The Web statistics will show all situations in addition to the existing ones:

• Ejected: there was an ejection request, and it was done
• Not ejected: there was an ejection request, but avatar is not part of group (or can't be ejected)
• Ejected for Banned reason

PRICES

As a group slot is dedicated to your group in a bot, you need to rent this slot.

Current price is:

Duration	Cost
1 week	LS 100

Of course, the Group.Invitor standard price per invitation request applies in addition to this price (see this link for more), with following changes:

• Similarly to the per invitation request debit, there is ALSO a debit on a per ejection request, working the same way (however, blacklists concepts do not apply to ejection)
• Role addition or Role removal are considered as sorts of invitation and ejection (and they will be displayed like this in the statistics). As a consequence, both these situations will debit 1 credit each

To rent a group slot, please contact us: contact us (There will be a way to rent in release. Not in beta stage)

SETTINGS

Once you added your 2 bots inside your group with invitations, you will need to allocate correct permissions to the bots for them to do their job. This means (in addition to "standard" permissions)

• "Invite People to this Group" permission
• "Eject Members from this Group" permission
  • To activate when ejections are requested
• "Assign Members to assigner's role" permission
  • To activate if bot must invite to specific roles.
• "Remove Members from Roles" permission
  • To activate if ejections are requested, or to remove someone from a role.

PLUGINS

The list of supported services will continuously increase (contact us to claim for a system support). Currently, supported ones are:

• Apez.AutoLease
• HippoRent

Each service needs to be configured. For this, you need to add some scripts on specific prims, and a notecard named Group.Invitor.Config that contains the group name for which you want an invitation, similarly to Group.Invitor standard plugins.

However, the format of notecard you put in renting services is slighly different:

• It must contain 1 or 2 lines. Not more
• 1st line must contain group name, and optionally a group role, separated from group name with a special sign: |||
• 2nd line contains either a keyword, or is empty. This will have an impact on end of renting:
  • "LeaveRole" keyword: avatar who was renting will be removed the role being specified in 1st line.
    If no role or "Everyone" role is specified, avatar will be ejected from group
  • "LeaveGroup" keyword: at end of renting, avatar will be ejected from group
  • empty line: avatar will remain in group as-is
  Example of notecard:
  
  
  MyRoBoT|||Managers
  LeaveRole

At the time the group name is correctly configured, the added scripts will start to invite people when rent begins.

The prims where to put scripts are:

• Apez.AutoLease: inside your lease box
• HippoRent: inside your rent box

Avatars can be banned with 2 means:

• through standard Group.Invitor prims (go in BlackList menu)
• Or in Group chat: simply type in group chat: "ban firstname lastname" to ban an avatar

Yes you can !. In fact, the A tip also applies to people in your group who have Eject permission in the group.

Also, you can add a notecard inside your standard prims with the name of the avatar to which you want to give control

Usually, when choosing Group option in an invitor menu, you will give a group name.

However, you can also indicate a group role, separating group name and group role in your answer by the specific separator |||

For instance:

MyRoBoT|||Officers

Of Course, if role doesn't exist, you'll get an error.

Please ensure also that this configuration will not invite people to a too permissive role.