All FAQs

Please see this step-by-step guide on how to download and install GroupTools.

To activate (change) a group, use the command Agroup followed by the group name or the UUID key of the group.

To change the group title (tag) of your bot, you need to use the command Chtitle.

The command needs to be followed by the role UUID key, aswell as the name or UUID key of the group.

The full command to change the active title for the group "GroupTool debug2" would look like this:

Chtitle 1b02b4f1-d749-8b46-9429-b6f67f5557d4 GroupTool debug2

To clear the cache, just send the command Ccache

If you need to find the location of your bot and you don't have access to the bot window (ie. you are an operator of someone elses bot), just send the command Location to the bot, and it will respond with a SLURL of it's current location.

[ Join group by invitation ]

[ Join groups from the User Interface ]

There are no way (yet) to search for a group in the User interface, instead you have the option to look at another users profile and easily join the same groups they are member of.

Go to the world menu, and locate the "Show profile" menu item.

 

 

Clicking this menu, will give you an input dialog where you have to enter the name of the avatar you wish to see the profile of.

(Typing in your bot's name, or the word "me", will give you the profile of your bot, where you instead can leave multiple groups if you need to).

 

 

Clicking ok here will, if you entered the correct name (names has to be full first and last name, never the screen name), bring up the users profile.

 

 

Select the groups you wish to join (or leave, in case you are viewing your bots profile) by ticking the check boxes and click the "Join groups".

You will not get a message when it's done.

Just click the "refresh" button in the user interface to refresh the list of groups your bot is member of.

If your bots looks strange, ruthed or not fully rezzed, try rebake using the command Rebake

If it doesn't help, empty the cache and rebake again, or just relog.

Either the same way as you teleport anyone else. Just send the bot a TP.

The bot will accept the TP only if it's the master or an operator who is sending the teleport request.

The other way is to tell the bot to "goto <somehwere>".

Change the <somewhere> for either @HOME or a SLURL, and the bot will go right there.

Yes, there are two ways to let others use your bot.
You can either let them log yout bot in by asking them do download and install GroupTools and
use your license to log a bot in, or, you can add an Operators Group.

If you want others to control the bot, there are a few ways to do this.

1. Leave your computer on and let the bot stay logged in so others can control it.

- Create a group (or use one you already have) which you only allow people you trust in.
  (Anyone who is a member of this group can control the bot).
- Let your bot join the group.
- Add the group name (or UUID key) in the field for "operators group" that you wind in the
  settings panel in the Control Center.
- Relog the bot if it is logged in.

The avatars that is members of the group you added as operators group can now use most
of the commands for the bot.
A few exceptions exists, such as the commands "quit!" or "give money".
Only the master can force the bot to quit or deal with the bots monetary account.

2. Let your friends download and install the GroupTools client and use your license.

- They can add any avatar as a bot, but they must use your name as the master.
  (They are running the bot on your license).
- Follow the steps in the previous example.
- As with the previous example, you are the master and the same exceptions for the
  commands is effective here.
  They can however ofcourse log the bot out by simply closing the program, but only you as
  the master are allowed to use the "quit!" command, in case they left the computer and you
  want to log your bot in.

By purchasing another license, you could in that way keep your bot logged in while allowing
your friends to log in their avatar as a bot using your license.
Should your friends need the commands that is only available to the master,
they must purchase their own license.
     

To change group title (tag), use the command Chtitle folowed by the role title you want to use, and the group key of the group.

Use the commands RoleKeys and Group2Key to get the keys you need.

If you want your inworld scripted objects to communicate with your bot, you need to set up an access key, known as "Object Key".
This key can be set in either the control center, or by using the command Set objectkey.

The syntax for the command is:
Set objectkey [Enable|Disable] key

This key can be any alpha-numerical and most special characters and it is case sensetive!

Every time you use the command Set objectkey, you must specify whether the use of ObjectKey should be enabled or disabled.
You change the ObjectKey the same way that you set it the first time.
If you want your ObjectKey to be @MyKey123 you send the command set ObjectKey Enable @MyKey123

After the command has been sent, you need to let your bot know it should reload its settings, by using the command reload.

You can also change the access key in the control center.
The setting can be found in the settings panel under Misc -> Commands.

When the object key has been set, your scripted objects can start interacting with the bot.
The following is an example of how to make your bot invite an avatar to a group when he or she is touching the scripted object.

Not all commands will work with scripted objects.
You can see which commands support scripted objects usage by looking in the <link> Scripted Object Commands </link>

Also, all commands that support scripted objects usage will show the scripted objects syntax when the help for the command is shown.
It would look like this:
Manual usage: Invite GroupKey GroupRoleKey Avatar (key or name) [| message]
Object usage: Invite ObjectKey GroupKey GroupRoleKey Avatar (key or name) [| message]

If you need a command that is not yet supported with object interactions, send us an email and ask for it to be added, we will try to add it as soon as possible, or for the next release, depending on how fast it takes to add the support.

There are several ways of getting a group key.
Either through scripted objects inworld, by looking it up in the group info (if the viewer supports it).
Or by asking your bot about the key.

However, the bot can only give you keys of groups that the bot is a member of.
By sending an IM to your bot with the message Group2Key My Group your bot will reply with:
[09:21:35]  Midday Ibor: Group "My Group" has key: 00000000-0000-0000-0000-000000000000

Your bot can listen to chat from both avatars and objects on channel 0 (public chat channel) and will,
provided it is in range to hear the chat, hear any of the following:
Whisper (10 meters), Normal (20 meters), Shout (100 meters) or (in case of Scripted Objects) llRegionSayTo.

If you want your bot to listen to the chat, you will find the setting in the Control Center under Settings -> Misc -> Chat -> Listen to chat.

When you enable this feature, you have three choices to make. 

This setting can also be changed by IM commands, by using the command "Set ListenToChat".
For more info on how to use the command, see the command help by issuing the command "Set ListenToChat Help".

This setting will NOT affect chat sent as Instant Messages (IM) to the bot.
Your bot will ALWAYS see IM's, regardless of this setting!

Performing a clean install can sometimes help with a few errors, as well as preventing errors when installing an update.

Start first by installing GroupTools from the Add/Remove programs in the Windows Control Panel.

When this is done, download the GroupTools Cleaner from the Download section.
If asked, choose to Run the program, rather than Save, as the program does not install itself.

When you start the program, you will see a small window with a button.

IMPORTANT:
This application will remove ALL files that is used by GroupTools.
This means your bot credentials and settings that you have saved will be removed, along with any other files that GroupTools is using.
Timed Messages will NOT be affected by this, they will be kept safe!

To find out who is nearby, simply send the command Nearby to your bot, and it will present you with a list of nearby avatars not further away than 64 meters.

Please send an email to support@grouptools.eu.
Make sure to give us your mastername.
We will remove your curent password.
Once this is done, you need to make a new backup of one of your bots to create a new password.

Yes, you can indeed share your settings.
There are currently two ways of doing that.

Export your settings for your bot(s) to a file, save it to your computer and send it to the by email, skype etc. and have your coworked import the file from the ControlCenter manually.
Export your settings for your bot(s) to a file, have it uploaded to our cloud server, and have your coworked import the file from the ControlCenter directly from the cloud server.

1.1 On your end, open the ControlCenter and find the File menu in the upper left corner.
      1.1.1 Select "Export saved bots".
      1.1.2 Select the bot you wish to export and click "OK".
              (The top most alternative "EXPORT ALL THESE BOTS!" is visible if you have more than
              one bot.
              This alternative will export ALL bots into one single export file instead of one file/bot

              which the other alternatives does).
      1.1.3 Enter a password to protect the backup file with and click "OK".
              (In case the file gets lost or stolen, it will be protected with this password).
      1.1.4 Click the Save button to save the file on your computer.
      1.1.5 Select a location on your computer where the file will be saved, and click "OK".
      1.1.6 The file is now saved where you chose to save it. You are now ready to send the file
              to your coworker.

1.2 On your coworkers end, ask your coworker to open the ControlCenter and find the File menu in the upper left corner.
      1.2.1 Select "Import saved bots".
      1.2.2 Select "Disk".
      1.2.3 Locate the file named "GroupTool2_Settings_Bot.Name_EXPORT.zip" and click Open.
      1.2.4 If your coworker already has bots registered in the ControlCenter,
              the import will ask wether it should ADD the new bot to the current list of bots,
              or if it should REPLACE the entire list.
              If no previous bots exists, the import will simply just add the bot without any
              questions.
      1.2.5 Your coworker will be asked to enter the password used when creating the backup file.
              Enter the password and click OK, and the bot will be added to the list in ControlCenter.
      1.2.6 The bot is now added and ready to be used!

2.1 On your end, open the ControlCenter and find the File menu in the upper left corner.
      2.1.1 Select "Export saved bots".
      2.1.2 Select the bot you wish to export and click "OK".
              (The top most alternative "EXPORT ALL THESE BOTS!" is visible if you have more than
              one bot.
              This alternative will export ALL bots into one single export file instead of one file/bot

              which the other alternatives does).
      2.1.3 Enter a password to protect the backup file with and click "OK".
              (In case the file gets lost or stolen, it will be protected with this password).
      2.1.4 Click the Upload button to save the file on our cloud server.
      2.1.5 If this is the first time you use this service, you will be asked to create a password.
              Enter a password for your account (should NOT be the same as your previous entered
              backup password, second life password etc. Please make it unique.)
      2.1.6 The file is now saved on our cloud server. Your coworker can now import it.

2.2 On your coworkers end, ask your coworker to open the ControlCenter and find the File menu in the upper left corner.

      2.2.1 Select "Import saved bots".
      2.2.2 Select "Uploaded".
      2.2.3 Your coworker will be asked to enter a mastername and botname.
              If they are supposed to get a backup which used the option "EXPORT ALL THESE
              BOTS!", then do not enter anything in the botname field and instead check the box
              labeled "Import all bots?".
      2.2.4 Your coworker will be asked to enter your account password.
              Enter it and click OK.
      2.2.5 A new window will open, where all available backup files for this particular bot is
              visible. They are stamped with date and time when they were created.
              Select the file to be used and click the button "Import bot from this file".
      2.2.6 If your coworker already has bots registered in the ControlCenter,
              the import will ask wether it should ADD the new bot to the current list of bots,
              or if it should REPLACE the entire list.
              If no previous bots exists, the import will simply just add the bot without any
              questions.
      2.2.7 Your coworker will be asked to enter the password used when creating the backup file.
              Enter the password and click OK, and the bot will be added to the list in ControlCenter.
      2.2.8 The bot is now added and ready to be used!

This feature came with version 2.2.35.0

From this version, you can add/remove protection to your license, so that you can be sure that nobody is using your license without your consent.

1. Add protection
2. Change password
3. Remove protection

If you want to add protection to your license, follow these steps:

1.1. Log in with one bot.
1.2. Once your bot is ready, locate the File menu in the upper left corner.
1.3. Select License protection -> Add protection
1.4 A dialog will appear in the upper right corner, asking you to enter a password.
      Enter the password you wish to use, confirm it in the field below and click OK.

1.5 Your license is now password protected no matter which bot you use.
      Once a bot has logged in under your license, a password prompt will show up in the upper
      right corner. If no password is given within 2 minutes, the bot will log out.

Please remember, that there is no way that the GroupTools can remember your password.
You will need to enter the password EVERY TIME the bot logs in to Second Life, even when
the bot is disconnected and automatically reconnects!

If you need to change the password, start with loging the bot in.
If you know the password but just want to change it, enter the current password when asked for
it and find the File menu in the upper left corner and select License protection ->
Change password.
If you have forgot the password, simply click the button "Forgot password" when prompted for
the password.

Your bot will log out no matter which of the above methods you are using.
An email will be sent to your registered email address, which contains a link to where you can
change the password.
Follow the link and enter a new password and you shall be ready to log in with your new
password again.
If somebody is trying to use your license and are requesting a new password, they will not be
able to change the password unless they also have access to your registered email address.
If you did not receive the email within an hour, please contact us at support@grouptools.eu
If you need to change your email address, either use the terminal at the GroupTools office,
or contact us on support@grouptools.eu 

When contacting us by email, Please make sure to give us your master name.
We will contact you ASAP (either inworld or by email) to verify that you are the rightful owner
of the license and help you get the password/email changed.

If you want to remove the password protection, log the bot in and find the File menu in the

upper left corner.
Select License protection -> Remove protection.
You will be prompted for the current password, please enter it.
If the password is correct, the protection will be removed.

The GroupTools inviter is configured by editing the notecard named "config", which can be found inside the object.
The notecard consists of 7 lines, namely:

BotName = Bot Name
BotKey = Bot UUID key
ObjectKey = ObjectKey
GroupName = Group Name
GroupKey = Group UUID key
RoleKey = 0
InviteMSG = I will invite you to GroupName shortly! Please wait..

To properly configure the inviter, please enter each setting after the equal sign, making sure not to add or remove any additional lines.
It is important that each setting is on it's own line.
At the end of this article, you will see a working configuration for one of our bots (with the exception of the ObjectKey, that for security reasons has been changed).

To make a difference between the text of this guide, commands and settings, the text is bold for commands and italic for settings.

LINE 1.
First of all lines, is the identification of your bot, the BotName line.
In our case, the bot is named "Broke Trapdoor", so the first line should be:
BotName = Broke Trapdoor

LINE 2.
Next line, is the UUID key of your bot, the BotKey line.
If you don't know the UUID key of your bot, simply give the command "mykey" in an IM to your bot. Like this:

Tadao Nordenskiold: mykey
Broke Trapdoor: My key: 29d181f7-555c-4b03-95fb-94716755bf42


In our case, the BotKey should be:
BotKey = 29d181f7-555c-4b03-95fb-94716755bf42

LINE 3.
Next line is the ObjectKey. This is a special password which you set in the ControlCenter.
The ObjectKey is there to protect your bot from being used by other scripted inworld objects which you have no control of.
Without the correct ObjectKey, your bot will simply deny access to the given command.

You will find the ObjectKey setting in ControlCenter under Settings -> Misc -> Commands -> ObjectKey.
Tick the box to enable the setting, and enter a password in the text box, like this:


The ObjectKey is case sensitive.
In this case, the config line should be:
ObjectKey = MySecretObjectKey

LINE 4.
The next line, GroupName, should be quite obvious, the configuration needs to know the name of the group you wish to send invitations to.
Your bot needs to be member of this group, and be allowed to invite new members to the group and the specific (if any) role.

In our case, we want to send an invitation to the group named "GroupTool customers".
The config line should then be:
GroupName = GroupTool customers

LINE 5.
The next line is the UUID key of the group, the GroupKey line.
If you don't know the key of the group, and don't know how to find it in your viewer, you can ask the bot, using the command Group2Keylike this:

Tadao Nordenskiold: Group2Key GroupTool customers
Broke Trapdoor: ec9d8079-f51c-ec04-7d72-a225a018aac6

The bot will give you the UUID key of the group you asked for.

The config line for GroupKey should then be:
GroupKey = ec9d8079-f51c-ec04-7d72-a225a018aac6

LINE 6.
The next line is the RoleKey, which identifies which role your bot should give to your new members.
If you want your new members to have the "Everyone" role, you can simply make this setting either:
RoleKey = 0   or   RoleKey = Everyone

In our case, we want to invite new members to our VIP role.
But we don't have the role key, only the name of the role.
We will then ask our bot to give us the key, by using the command RoleKeys like this:

Tadao Nordenskiold: rolekeys GroupTool customers
Broke Trapdoor: Available roles in group: "GroupTool customers" (key: ec9d8079-f51c-ec04-7d72-a225a018aac6)
Role/Title name: "GroupTool VIP" has key 902e9f64-7f2f-157d-2087-892830979bd0
Role/Title name: "GroupTool customer" has key 00000000-0000-0000-0000-000000000000

As we can see from the response of the bot, we can see that the role "GroupTool VIP" has the key "902e9f64-7f2f-157d-2087-892830979bd0".
Our config for the RoleKey should thereby be:

RoleKey = 902e9f64-7f2f-157d-2087-892830979bd0

Please note: A group member must ALWAYS be member of the Everyone role.
No matter if you invite a new member to a specific role or not, they will ALWAYS get the Everyone role as well!

 LINE 7.
The very last line, is the InviteMSG line.
This line holds a message that the bot will send to the new member just before it attempts to send the invitation.
The line must be present, but can be empty.
If you don't want a message to be sent, just leave it as InviteMSG =  without anything after the equal sign.

In our case, we want to notify the new member that an invitation is about to be sent.
Our config is:
InviteMSG = I will send you an invitation to the group GroupTool Customers shortly! Please wait...

So, as we are at the end of our configuration, let's show it as a full config notecard.

BotName = Broke Trapdoor
BotKey = 29d181f7-555c-4b03-95fb-94716755bf42
ObjectKey = MySecretObjectKey
GroupName = GroupTool Customers
GroupKey = ec9d8079-f51c-ec04-7d72-a225a018aac6
RoleKey = 902e9f64-7f2f-157d-2087-892830979bd0
InviteMSG = I will send you an invitation to the group GroupTool Customers shortly! Please wait...

The GroupTools inviter+ is configured by editing the notecard named "config", which can be found inside the object.
The notecard consists of minimum 2 lines, namely:

Bot=Bot Name;Bot UUID Key;ObjectKey
Group=Bot Name;Group Name;Group UUID Key;Role Key

To properly configure the inviter, please enter the settings after the equal sign, separated with semi-colons ( ; ).
It is important that the BOT and GROUP config lines are on completely separate lines.
At the end of this article, you will see a working configuration for one of our bots (with the exception of the ObjectKey, that for security reasons has been changed).

To make a difference between the text of this guide, commands and settings, the text is bold for commands and italic for settings.

LINE 1.
The BOT line.
This line is separated into 3 sections, separated by a semi-colon ( ; ).
The first section, "Bot Name", is the name of your bot.
The second section, "Bot UUID key", is the UUID key of your bot.
The third section, is the ObjectKey that you enter in the Control Center for your bot.

In our case, we want to use 2 bots.
The reason for this, is because our two different bots are inviting to two different groups, and no bot is member of both groups.
Our bots are Gaia Unplugged (sending invitations to the group Gaia Streams customers) and GroupTool Scientist (sending invitations to the group GroupTool customers).

Because of this, we need to use two different BOT lines, which would look like this:
BOT=Gaia Unplugged;b5eaa604-ef64-4784-b935-f821200441dc;MySecretObjectKey
BOT=GroupTool Scientist;fdc92d85-0bcd-4bb4-8292-8539892c251c;MySecretObjectKey

If you don't know what the UUID key of your bot(s) are, you can ask the bot(s) to give them to you.
You do that by sending the command "mykey" as an IM to the bot, like this:

Tadao Nordenskiold: mykey
Gaia Unplugged: My key: b5eaa604-ef64-4784-b935-f821200441dc

You will also need to set the ObjectKey of your bot.
You will find the ObjectKey setting in ControlCenter under Settings -> Misc -> Commands -> ObjectKey.
Tick the box to enable the setting, and enter a password in the text box, like this:

Please remember that the ObjectKey is case sensitive!
Do NOT use any spaces!

LINE 2.
The GROUP line.

This line is separated into 4 sections, separated by a semi-colon ( ; ).
The first section, "Bot Name", is the name of your bot which is member of the group in the second section.
The second section, "Group Name", is the name of the group you want your bot to send invitations for.
The third section, "Group Name", is the UUID key of the group you want the bot to send invitations for.
The fourth section, is the RoleKey, corresponding to the role, that you want the newly invited member to have.

As we in our case want to use two bots with two different groups, we need two GROUP lines.
They look like this:

Group=GroupTool Scientist;GroupTool Customers;ec9d8079-f51c-ec04-7d72-a225a018aac6;Everyone
Group=Gaia Unplugged;Gaia Streams Customers;9a878301-e910-76c8-0d4e-5733cdd1e066;2d281471-5727-5641-3321-a481a5de4311

The first line, shows that the bot GroupTool Scientist should send invitations to the group "GroupTool Customers", which has the UUID key "ec9d8079-f51c-ec04-7d72-a225a018aac6", and new members should get the role "Everyone".

If you don't know the UUID key of the group, you can ask your bot to give it to you by using the command "Group2Key" like this:
Tadao Nordenskiold: Group2Key GroupTool Customers
GroupTool Scientist: ec9d8079-f51c-ec04-7d72-a225a018aac6

We do not want our newly invited members to have any specific role other than the "everyone" role. We will therefore set the last section to "Everyone" or "0" (both works equally good).

The second line, which is a bit more special compared to the first one, shows that the bot Gaia Unplugged should send invitations to the group "Gaia Streams Customers," which has the UUID key "9a878301-e910-76c8-0d4e-5733cdd1e066", and new members should get the role "2d281471-5727-5641-3321-a481a5de4311".

In this case, we have created a special role, "Gaia Stream VIP's", which has the RoleKey "2d281471-5727-5641-3321-a481a5de4311".
The only way to get the rolekey, is by asking your bot.
As with the above example with the first group line, you get the UUID key of the group by asking your bot with the command "Group2Key".
To get the rolekeys, you use the command "RoleKeys" like this:
Tadao Nordenskiold: RoleKeys Gaia Streams Customers
Gaia Streams (Gaia Unplugged): Available roles in group: "Gaia Streams Customers" (key: 9a878301-e910-76c8-0d4e-5733cdd1e066)
Role/Title name: "Gaia Stream VIP's" has key 2d281471-5727-5641-3321-a481a5de4311
Role/Title name: "♫Gaia Streams♫" has key 00000000-0000-0000-0000-000000000000

So, as we are at the end of our configuration, let's show it as a full config notecard.

BOT=Gaia Unplugged;b5eaa604-ef64-4784-b935-f821200441dc;MySecretObjectKey
BOT=GroupTool Scientist;fdc92d85-0bcd-4bb4-8292-8539892c251c;MySecretObjectKey
Group=GroupTool Scientist;GroupTool Customers;ec9d8079-f51c-ec04-7d72-a225a018aac6;Everyone
Group=Gaia Unplugged;Gaia Streams Customers;9a878301-e910-76c8-0d4e-5733cdd1e066;2d281471-5727-5641-3321-a481a5de4311

The GroupTools Timer is configured by editing the notecard named "config", which can be found inside the object.
The notecard consists of minimum 5 lines, namely:

Admin = Firstname Resident
Botname = BotFirstName BotLastName
Botkey = Bot UUID key
ObjectKey = ObjectKey
LogOutAfter = X minutes

To properly configure the timer, please enter each setting after the equal sign, making sure not to add or remove any additional lines.
It is important that each setting is on it's own line.
Near the end of this article, you will see a working configuration for one of our bots (with the exception of the ObjectKey, that for security reasons has been changed).

To make a difference between the text of this guide, commands and settings, the text is bold for commands anditalic for settings.

LINE 1.
First of all lines, is the Admin line, which help you set who (besides you) can control (override) the timer.
(For more information about overriding the timer, please scroll down to the end of this article.)

The avatar name you enter at this line, will gain ability to handle the timer for your bot.
The admin line can hold one name only!
If you need more than one admin, simply add more admin lines.
The example config at the end of this article will show you what it looks like to have 3 admins.

In our case, we want the avatar Midday Ibor to be administrator of this timer.
admin = Midday Ibor

LINE 2.
Next line, is the BotName line. This line represents the name of your bot and will also label the timer to help you distinguish
one timer from another (especially if you need more than one).

In our case, the bot is named "Broke Trapdoor", so this line should be:
BotName = Broke Trapdoor

LINE 3.
Next line, is the UUID key of your bot, the BotKey line.
If you don't know the UUID key of your bot, simply give the command "mykey" in an IM to your bot. Like this:

Tadao Nordenskiold: mykey
Broke Trapdoor: My key: 29d181f7-555c-4b03-95fb-94716755bf42

In our case, the BotKey should be:
BotKey =29d181f7-555c-4b03-95fb-94716755bf42

LINE 4.
Next line is the ObjectKey. This is a special password which you set in the ControlCenter.
The ObjectKey is there to protect your bot from being used by other scripted inworld objects which you have no control of.
Without the correct ObjectKey, your bot will simply deny access to the given command.

You will find the ObjectKey setting in ControlCenter under Settings -> Misc -> Commands -> ObjectKey.
Tick the box to enable the setting, and enter a password in the text box, like this:

The ObjectKey is case sensitive.
In this case, the config line should be:
ObjectKey = MySecretObjectKey

LINE 5.
The next line, LogOutAfter, Is the last of all config lines.
This line tells the timer how many minutes you want your bot to stay online.
When the timer has 30 seconds left, a message will be sent to your bot and tell it to log out in 30 seconds.
The bot will send you a message and tell you that it have received the command.
Broke Trapdoor: I will log out in 30 seconds.

When the 30 second times has been reached, the bot will send you another message and then log out.
Broke Trapdoor: I was told to set a timer and log out earlier. The timer has now reached its limit, so I am logging out!

In our case, we want the bot to stay online for 10 minutes.
The config line should then be:
LogOutAfter = 10

So, as we are at the end of our configuration, let's show it as a full config notecard.

Admin = Midday Ibor
Admin = GroupTool Scientist
Admin = Gaia Unplugged
BotName = Broke Trapdoor
BotKey = 29d181f7-555c-4b03-95fb-94716755bf42
ObjectKey = MySecretObjectKey
LogOutAfter = 10

Overriding the timer

The owner of the timer, and any administrators that has been granted access in the config card, can override the timer.
When touching the timer, a menu will let you either enable, disable or change the timer settings (LogOutAfter) of the timer.

If you don't have an account, you need to create one.
The cost for account creation is 50 lindens.
The entire fee will be available for you to use towards your bots online time.
Please see the menu item "Licenses" to see what the current online time fee is, or see the FAQ article "Why do you charge for the time my bot(s) is online?" to read more about why we charge for the online time.

If you have an account however, you can find the login site in the menu under "Hosting services" -> "Control Center".

If you want to run your bot(s) on our server using the hosted services, then the answer is YES.

If you however want to continue to run your bot(s) on your own PC like you have always done, then the answer is NO!

Paying for the time your bot(s) is online is ONLY affecting those who are running their bot(s) on our server using the hosted services!

Your username will always be your Second Life username (ie. the master name).

If you have lost your password, go to our office and touch the terminal. Follow the dialogs and choose "HOSTED", then "CHANGE" and then "PASSWORD".

Your password will be reset to a new one, and will be sent to your email.
If you did not get the email withing 2 hours time, please send us a support ticket and we will help you ASAP.

At the moment of writing this article (2015-09-20), yes.
(This article will be updated as we are reducing the limitations).

The hosted services is still under development.
We have not had the time to add all features yet, and this will take time.

At the moment when the article is being written, you can:

• * Log the bot in and out.
• * Use all IM commands.
• * Send group notices and IM's by using notecards.
• * Use the Timed Messages commands by converting notecards into Timed Messages.
     (Please see the FAQ article about converting notecards into Timed Messages).

The hosted service is not fully reliable yet either, in the sense of making sure your bot is online 24/7.
Right now, we are working on the following features:

• * Making sure your bot stays online until you tell it to log out.
  * Making commands available through the web interface.
  * Making Timed Messages available from the web interface.

Due to the limitations, we are also having a reduced online fee.

When the hosted services are having all it's intended features, the online fee will be 0.04 lindens/minute.
We will notify you at least 2 weeks (14 days) prior to any changes in the fees.

Please see the menu item "licenses" for the most current online time fee.

You will benefit from letting us host your bot if you answer yes to any or all of these questions:

• * I am using a Macintosh or Linux (GroupTools will only run on a PC using Windows).
• * I want to be able to log my bot in from my smartphone/tablet or anywhere else than at home.
• * I don't want or I can't to install GroupTools on my computer.
• * I want to be able to use my bot(s) without my computer being online/powered on.

The Hosted services simply let you have your bot(s) logged in to Second Life without the need of your PC being online/powered on.

The difference between the hosted services and the normal "stand alone" bots, are that when you are using the hosted services, you run your bot(s) on our servers and thereby don't have to download and install GroupTools on your own PC. (Please see the article "What's the benefit from letting you host my bot(s)?"

The server we make available for you to run your bots from, is not cheap.
Bandwidth (data transfered) and the hardware (the actual computer) has a substantial cost each month, which we need to cover for somehow.

We found that charging for the time that you actually use our server (when you bot has logged in properly and is fully available to be used, until you have logged it out), is the most fair to all users.

If you have any questions or an idea that would make the charge more fair, please let us know by sending a support ticket!

No, there are only two reasons why we would send any money back.

1. The services is discontinued and will not be available anymore.
2. You couldn't use the service at all (ie. You couldn't even log your bot(s) in.)

In any other case, your money will stay safe and secure on your account in case you decide to return to us!

Unknown error, please contact support!
Please also make sure to provide the following details:

• Your email address (we may need to contact you with questions)
• Master Name
• Bot name
• Detailed information of how what you did just before you got the error
    (eg. Started the program, chose bot, edited settings for X function and tried to log in).
• Screenshot (if possible)

Invalid license.

Our authentication servers could not validate your license.
Please check the following: 

1. You have actually registered for a license (trial or owned).
2. The master name you have entered is spelled correct AND
3. The master name is the same as the avatar you registered your license with.

Due to an unknown error, the program could not generate your authentication code.
Please restart the program and try again.

Please also make sure to provide the following details:

• Your email address (we may need to contact you with questions)
• Master Name
• Bot name
• Detailed information of how what you did just before you got the error
    (eg. Started the program, chose bot, edited settings for X function and tried to log in).
• Screenshot (if possible)

Not enough licenses.

This means our server has detected that you are running more concurrent bots logged in than your license allows.

This can also be a "false positive".
In case your bot logged out due to a crash, or for some other reason was not able to tell our servers that it logged out, our servers will still see your bot as online in second life.

Our automatic cleanup system takes between 2 - 5 minutes to remove your bot from the database, depending on how fast Second Life reports your bot as being offline.

Please wait a minute or two, and try loggin in again.

If you still get the same message, wait and try again.

Second Life can be slow on reporting back, this is nothing we can help.

We ask you not to contact support regarding this issue unless a minimum of 15 minutes has passed since you first encountered the problems and you tried to log back in atleast two times during these 15 minutes.

Your trial period has ended.
Please consider purchasing a license if you like the program.

Your version of GroupTools is too old.
You must update to a newer version!

Our authentication servers have detected a possible cheat to circumvent the license verification!

Your login attempt has been highlighted in our logging system.

If you believe this to be wrong, please contact support and provide us with your master and botname as well as the email address you used when you purchased your license.

Your bot has troubles to log in to a certain location and gives an error message similar to the message below.

Parcels teleport routing set to Landing Point which is at <78.9987, 157.427, 22.1517>
I will never be able to reach my target at: <75, 215, 401> unless my start location is set to my home, or the sim teleport route is changed to "Anywhere".

or

Parcels teleport routing set to Landing Point which is at <78.9987, 157.427, 22.1517>

Error code: 800

Please see the FAQ entry at http://grouptools.eu/faq/error-codes#800 for more info!

This message is displayed when you have set the bot to log in at a certain location, while the land parcel it is trying to log in to is enforcing a different teleport location.

There are three ways to solve the issue:

• Set the parcel teleport routing to Anywhere.
• Change the bot's login location to the same as the parcel landing point.
• If the land is group owned, invite the bot to the group owning the land, and make sure the bot has a role which allow the bot to override the teleport routing.
  The officers role usually allows to override the teleport routing.

When a bot is logging in, it will, among other things, report to the authentication server that it is going online using a certain license.
When it logs off, it will tell the authentication server that it is logging off and thereby not using the license anymore.

If the bot is crashing, the authentication server will still see the bot as being online since it didn't report that it logged off.
In these circumstances, we rely on Second Life to report to us whether your bot is online or not.
Second Life servers can take anything from 30 seconds up to 5 minutes before it reports the bot as being offline.
However, when you logged in and got the error message from the authentication server, you also hurried up the process for Second Life servers, which is now logging the crashed avatar off from the grid, thus reporting back to us that it is offline.

Waiting a few seconds and then trying to log in again usually solves this problem.
If not, please wait another 2 or 3 minutes and then try again.

If you still can not log in, please contact support!

Yes!
We have added a feature for you to import and convert your notecards to Timed Messages.
Depending on how many notecards you want to import, there are two ways of doing it.

Please read the "Please beware of:" section at the end before importing.

Importing one-by-one by dropping the notecard to the bot
(Best when importing ~5 notecards)

Open an IM with your bot and send the command timed import
Your bot will now ask you to give it a notecard.
When giving the notecard, the bot will read it and convert it to a Timed Message
and let you know when it's done.

Repeat for each notecard you wish to import.

Importing directly from the inventory of the bot

Log the bot out from the GroupTools viewer and log it in from a normal viewer like Firestorm
or a linden viewer.
Transfer all the notecards you want to import to the bot avatars inventory.
Log out and log back in using the GroupTools viewer.
Open the inventory, rightclick the notecard you want to import
and select "Import to Times Messages"
The bot will read the notecard and convert it to a Timed Message and let you know when
it is finnished.
Repeat for each notecard you want to import.
You can also import by double-click the notecard to preview/edit it before importing.
If you are editing, please save first, then click "Import as Timed message" from the
Notecard menu in the upper left corner.

Please beware of:

1. When importing the notecard (no matter which method you are using), any attachments
    to the notecard will be saved to the bots inventory.
    DO NOT DELETE THE COPIED INVENTORY ITEM!
    Doing so will cause your bot not to be able to attach the inventory item to any notices.

2. When the notecard has been imported, the notecard can safely be deleted. Just don't delete
    any attachments that was copied from the notecard as described above.

3. If you get an error that says the notecard is not correctly formatted, it means the bot could
    not recognize the notecard as a notecard used for notices and IM's.
    Please look over your notecard and try again!

4. If you want the Group IM to be different from the notice, you can add the following at the
    end of the notecard:

#INDIM
YOUR INVIVIDUAL GROUP IM MESSAGE HERE
#END_INDIM

    If you want a SLURL attached to the message, you also need to manually add it to the
    individual IM.

Yes, it is!

Just as with the notecards, you need to use an Operators group (read more about that in FAQ -> How to -> How can my friend or associate use my bot?).
Once your friend/associate is a member of this Operators group, they can start using your bot.

They manipulate your Timed Messages by using IM commands, and these are the commands they need to use:

Please see this guide for a step-by-step description of how to set up Timed Messages.

The PRO version of GroupTools currently have 102 IM commands,

-and 41 Scripted Object Commands available.

The LITE version of GroupTools currently have 61 IM commands,

-and 7 Scripted Object Commands available.

The amount of commands will grow larger as GroupTools is being developed.
Please don't hesitate to contact us with any feature requests or commands you wish it had.

All the columns are sortable.
By default, the list is sorted by Command category.
You can sort the commands differently by clicking the column headers.

If you want your bot to be able to answer other avatars with it's Artificial Intelligence capabilities,
there are some settings in the Control Center you need to make.

This video will show you a demonstration of how it works and which settings to make.
http://vimeo.com/83183931

You can find the settings in the Control Center under Settings -> RolePlay.

Enable RolePlay by checking it's box, then enable Replies under the Talk tab.
Select "Reply with 'AI' ".
A popup will notify you that you need to adjust some settings under Misc -> Chat.
Remember this, and proceed by selecting what kind of messages the bot should reply to. 

Now go you the Misc tab, and then to Chat.
Enable Listen to chat and select either Avatars Only or All, depending on your needs for other features in GroupTools.

You are now done and ready to log in!

IMPORTANT:

Please keep in mind, that your bot will NOT answer chat in local chat unless spoken to by name!
The name or display name of your bot MUST be used somewhere in the sentence every time you want it to reply.

There are three ways of getting help.

1. There is a group inworld called "GroupTools customers".
This group should be seen as a forum where mainly customers can connect and help eachother.

Of course, if a support rep is online and is seeing the question, they will answer too.

2. On the website is a link in the left hand menu to contact support.

Using this will create a ticket and is one of two preferred ways of getting help from us.

A ticket will be created shortly after you have submitted the form and a confirmation that we got your message should be sent to your email.

When we answer, the reply will end up in you email inbox, so please make sure you entered correct email address and keep an eye on your inbox.

We normally answer within an hour.

3. Using the "Contact support" button in the GroupTools Control Center or the GroupTools bot window.

If you have a bug or error to report, please use the button in the bot window before closing it (if possible), as this will give us more info regarding your problem aswell as giving you the opportunity to attach a screenshot of the problem.

In all other cases, please feel free to use the button in the Control Center.

As with submitting your question at the website, this will create a support ticket.

Please make sure your email address is correct and look for our answer in your email inbox.