-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.default.toml
70 lines (58 loc) · 3.07 KB
/
config.default.toml
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
# If this file is called config.default.toml, you don't need to edit it to
# configure the bot. If it's config.toml, follow the instructions in comments.
# A bot token is required to log in to Discord. WARNING: Anyone with your token
# can control your bot! See https://discord.com/developers/applications for
# more information.
# Uncomment the following line and paste a token between the quotes.
#token = ""
# The bot is designed to work in no more than one guild. On desktop, a guild's
# ID can be found by right clicking its icon and clicking "Copy Server ID".
# Uncomment the following line and paste a guild ID between the quotes.
#guildId = ""
# Some plugins assume a central log channel. On desktop, a channel's ID can be
# found by right clicking the channel and clicking "Copy Channel ID".
# Uncomment the following line and paste a log channel ID between the quotes.
#logChannelId = ""
# The bot interprets messages starting with the command prefix as commands.
commandPrefix = "!"
# If discoverPlugins is true, the bot will load any plugins it finds in the
# plugins directory. You can explicitly enable and disable plugins in the
# plugins section, below.
# Change false to true on the following line to automatically load plugins.
discoverPlugins = false
[plugins]
# Add entries here to enable and disable specific plugins. The name given
# must match the plugin's file name up to just before the first dot, if any.
help = true
onboard = false
# The permissions system determines who can use what commands in what
# channels. None of the role or channel names are hardcoded. Define whatever
# ones are needed.
# WARNING: Many commands could be very destructive if ordinary server members
# could run them. Consider carefully what permissions are appropriate for your
# server!
[permissions.roles]
# Each field is a name associated with a list of role IDs. This is done so
# they can be referred to by neat names inside of rules. On desktop, a role's
# ID can be found by clicking the picture of someone with that role, right
# clicking the role, and clicking "Copy Role ID". Make sure each ID is quoted.
staff = []
[permissions.channels]
# Each field is a name associated with a list of channel IDs. On desktop, a
# channel's ID can be found by right clicking the channel and clicking "Copy
# Channel ID". Make sure each ID is quoted.
# Define one or more rules, beginning each with a [[permissions.allowed]]
# heading. Each rule specifies:
# - a list of roles, using the names specified under [permissions.roles] above;
# - a list of commands, or the string "*" for all commands; and
# - a list of channels, using the names specified under [permissions.channels],
# or the string "*" for all channels.
# Whenever someone tries to run a command, the bot will check if any rule
# grants permissions for any one of that user's roles to run the given command
# in the given channel. If there is one, it will run; otherwise, it will not.
[[permissions.allowed]]
roles = ["staff"]
commands = "*"
channels = "*"
# Each plugin may request its own settings. Run the bot to find out what they
# are, then add them as needed.