-
Notifications
You must be signed in to change notification settings - Fork 1
/
config.yaml
269 lines (211 loc) · 7.7 KB
/
config.yaml
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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
# override permissions for any command
permissions:
whitelist: "${ ROLES.COMMUNITY_MANAGER }"
# # Its possible to set permissions for internal commands too.
# role:
# whitelist:
# - "${ ROLES.COMMUNITY_MODERATOR }"
#
# # Its possible to set permissions for custom commands
# echo:
# whitelist:
# - "${ ROLES.COMMUNITY_MODERATOR }"
#
# # Its possible to set permissions for custom commands in folders
# characters/amber:
# whitelist:
# - "${ ROLES.COMMUNITY_MODERATOR }"
# Only delete stuff after this line if you know what you're doing.
modules:
moderation:
enabled: true
loggingChannel: ${ CHANNELS.WARN_LOGS }
wordCensorConfig:
matches:
- regex: gook\b
flags: i
warn: true
- regex: niglet\b
flags: i
warn: true
- regex: tranny\b
flags: i
warn: true
- regex: cunt\b
flags: i
- regex: retard(ed)?\b
flags: i
warn: true
- regex: nigur\b
flags: i
warn: true
- regex: \bcum\b
flags: i
- regex: chink\b
flags: i
warn: true
- regex: autist\b
flags: i
- regex: ni(gg|bb)(er|a)?\b
flags: i
warn: true
- regex: fagg(ot)?\b
flags: i
warn: true
warnConfig:
permissions:
whitelist:
- "${ ROLES.COMMUNITY_MANAGER }"
- "${ ROLES.COMMUNITY_MODERATOR }"
- "${ ROLES.COMMUNITY_HELPER }"
cooldownPeriod: 1 month
levels:
# Free warning
- action: NOTICE
- action: MUTE
duration: 5 mins
- action: MUTE
duration: 15 mins
- action: MUTE
duration: 30 mins
- action: MUTE
duration: 1 hour
- action: MUTE
duration: 1 day
- action: BAN
muteConfig:
permissions:
whitelist:
- "${ ROLES.COMMUNITY_MANAGER }"
- "${ ROLES.COMMUNITY_MODERATOR }"
- "${ ROLES.COMMUNITY_HELPER }"
muteRole: ${ROLES.MUTED}
userNotes:
enabled: false
permissions:
whitelist: "${ ROLES.COMMUNITY_MANAGER }"
pointsSystem:
enabled: false
permissions:
whitelist: "${ ROLES.COMMUNITY_MANAGER }"
loggingChannel:
vanityRoles:
enabled: true
# Who can use the /vanityrole command, anyone with MANAGE_ROLES if not set.
permissions:
whitelist:
- "${ ROLES.SUPPORTER_AAA }"
- "${ ROLES.BOOSTER }"
# Log whenever someone's custom role is updated
loggingChannel: "${ CHANNELS.CUSTOM_ROLES }"
createRoleAfter: "741007547254964325"
reactRoles:
enabled: true
# Who can use the /reactroles command, anyone with MANAGE_ROLES if not set.
permissions:
whitelist:
- "${ ROLES.COMMUNITY_MANAGER }"
configs:
ALPHA_PING:
title: "Get pinged for alpha releases"
description: |-
React with 📣 to get notifications when a new alpha is released.
***Note**: Reactions will be removed if the bot successfully gives you the role.*
reactions:
"📣":
role: "1005830991945941003"
description: "Get pinged for Alpha Releases"
FEEDBACK:
title: "Feedback Role"
description: |-
React with 📣 to get notifications when feedback is required for any new features of the app.
***Note**: Reactions will be removed if the bot successfully gives you the role.*
reactions:
"📣":
role: "676012997264539649"
description: "Get pinged for feedback"
DEVICEOS:
title: "What is your primary device of use for Paperback?"
color: 0x2f3136
description: |-
React with the matching emoji for specific roles
***Note**: Reactions will be removed if the bot successfully gives you the role.*
reactions:
# REACTION EMOJI ID: ROLE
"iOS:965748659964772382":
role: "${ ROLES.IOS }"
description: "<@&${ ROLES.IOS }>"
"iPadOS:965748660078018590":
role: "${ ROLES.IPADOS }"
description: "<@&${ ROLES.IPADOS }>"
"MacOS:965748659847303219":
role: "${ ROLES.MACOS }"
description: "<@&${ ROLES.MACOS }>"
modMail:
enabled: true
# This restricts who can open a thread. If this is not set, anyone can open a thread by DMing the bot
permission: "${ ROLES.COMMUNITY_CLEARANCE }"
ignoreRole: "${ ROLES.MODMAIL_IGNORED }"
channels:
logging: "${ CHANNELS.MODMAIL.LOGGING }"
threads: "${ CHANNELS.MODMAIL.THREADS }"
# Role kits
roleKits:
enabled: true
# This restricts who can use the /rolekits command. if its not set, anyone with the MANAGE_ROLES permission can use the command.
permission: "${ ROLES.COMMUNITY_MANAGER }"
# The kits that are available
kits:
Template:
name:
permissions:
blacklist:
- ""
addRoles:
- ""
removeRoles:
- "${ ROLES.COMMUNITY_MODERATOR }"
# Verification Module
verification:
enabled: true
# This restricts who can use the /verification command. if its not set, anyone can use the command.
permission: "${ ROLES.COMMUNITY_MANAGER }"
# This sets the channel to use for sending the initialMessage into. If this is not set then the bot will not automatically send the welcome message.
welcomeChannel: "${ CHANNELS.WELCOME }"
# The role to add to users when they successfully accept the rules.
verifiedRole: "${ ROLES.COMMUNITY_CLEARANCE }"
interactions:
# You can use this to set a different greeting message. If this is not set then initialMessage is used.
greetingsMessageInteractionPath: "verification"
# The initial message displayed when the /verification is run.
initialMessageInteractionPath: "verification"
# The interaction to display when the user presses the verification button.
rulesAcknowledgementInteractionPath: "serverRulesAcknowledgement"
# Verification button settings
button:
title: "I agree*"
type: "PRIMARY"
supportThreads:
enabled: false
# This restricts who can use the /supportthreads command. if its not set, anyone with MANAGE_THREADS permission can use the command.
permission: "${ ROLES.COMMUNITY_MANAGER }"
configs:
main:
# The interaction to display when the command is run.
displayInteractionPath: "support"
# The interaction to display when someone interacts with the supportThreadButton
supportThreadConfirmationInteractionPath: "supportDisclaimer"
# The interaction to send in the opened thread
supportThreadDisplayInteractionPath: "supportThreadPrompt"
# The channel to open the thread in
supportThreadChannel: "${ CHANNELS.SUPPORT }"
# Configure the button to open a support thread, if this is not set then a button with the label "HELP" is used
supportThreadButton:
title: "Open a Thread"
type: "SECONDARY"
# Interaction to display when the user clicks the troubleshootButton
troubleshootInteractionPath: "self-help"
# An optional button that displays an interaction upon clicking. if this is not set, no button is displayed
troubleshootButton:
title: "Help"
type: "PRIMARY"