BotControl/example_dot_botctrl at main · slbotcontrol/BotControl · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
#### BotControl Configuration ${HOME}/.botctrl
#
# Example BotControl configuration file for use with the botctrl command
#
# Configure API credentials for each bot and copy the file to ${HOME}/.botctrl
# For security make the file accessible by owner only:
#   chmod 600 ${HOME}/.botctrl
#
## CORRADE Command Control Configuration
#
#  To control Corrade bots from the command line you must configure a group, password, and URL
#
#  REQUIRED configuration parameters to control Corrade bots:
#      CORRADE_GROUP  CORRADE_PASSW  CORRADE_URL
#
export CORRADE_GROUP="<your-corrade-bot-group-name>"
export CORRADE_PASSW="<your-corrade-bot-group-password>"
export CORRADE_URL="https://your.corrade.server"
export CORRADE_RANGE="64"
export API_URL_bot1_name="${CORRADE_URL}/bot1/"
export API_URL_bot2_name="${CORRADE_URL}/bot2/"
# Default Corrade Bot Name, this name will be used if none is specified
export CO_BOT_NAME='<bot1 name>'
##
## LIFEBOTS Command Control Configuration
#
#  To control LifeBots bots from the command line you must configure an API key and Bot secret
#
#  REQUIRED configuration parameters to control LifeBots bots:
#      LB_API_KEY   LB_SECRET
#      LifeBots bot secrets are unique to each bot. Aliases can be used for each, e.g.
#          LB_SECRET_BOT1_NAME
#
# LifeBots Developer API Key
export LB_API_KEY='your-api-key'
export LB_SECRET='your-bot-secret'  # Also referred to in the doc as an access code

# If you have more than one bot you can set each bot's secret like this
export LB_SECRET_BOT1_NAME='your-first-bot-secret'
export LB_SECRET_BOT2_NAME='your-second-bot-secret'
export LB_SECRET_BOT3_NAME='your-third-bot-secret'
# Replace spaces in the Bot's name with "_"
# For example, if the Bot's name is "John Doe" then the entry would be:
export LB_SECRET_John_Doe='john-doe-bot-secret'

# Default LifeBots Bot Name and ID
export LB_BOT_NAME='your-default-bot-name'
# LifeBots Bot ID
export LB_BOT_ID_Bot_Name='lifebots-bot-id'

# OAuth Applications
# If you have configured OAuth applications then the client id and secret can be set here
export LB_CLIENT_ID_app_name='your-oauth-app-client-id'
export LB_CLIENT_SECRET_app_name='your-oauth-app-client-secret'

#### COMMON Settings used by both Corrade & LifeBots bots
# The following optional convenience entries are supported to allow
# specifying an alias on the command line rather than a SLURL or UUID
# All configured aliases can be listed with the command "botctrl -a alias"
#
# Second Life Bot ID
export SL_BOT_ID_Bot_Name='secondlife-bot-id'
# Login siton UUID
export LOGIN_SITON_Bot_Name="uuid-of-siton-object"

#### ALIASES
##
## Bot name aliases for use with the "-c name" and "-n name" command line options
export BOT_NAME_bot1="Bot1 Name"
export BOT_NAME_bot2="Bot2 Name"
export BOT_NAME_bot3="Bot3 Name"

## SLURL aliases for use with the "-l location" command line option
# Slurl aliases can be set for use with the location option, -l location
# For example, the following 2 SLURL aliases could be used with -l beach or -l club
# to teleport the bot to the beach or the club specified in these SLURLs
export SLURL_beach="http://maps.secondlife.com/secondlife/BEACH_REGION_NAME/X/Y/Z"
# Urlencode spaces in the region name by using %20 instead of space
export SLURL_club="http://maps.secondlife.com/secondlife/CLUB_REGION%20NAME/X/Y/Z"

## UUID aliases for use with the "-u uuid" command line option
# UUID aliases can be set for use with the UUID option, -u uuid
# For example, the following UUID aliases could be used with -u dancepole
# or -u couch to seat the bot on the specified object
export UUID_dancepole="dance-pole-object-uuid"
export UUID_couch="couch-object-uuid"