Is your feature request related to a problem? Please describe.
The verification process currently clutters up the public #bot-commands channel, which is also used for server and ITS status messages.
Describe the solution you'd like
Send the current Unverified message via DM
User responds with $verify via DM
Send the current Request sent! message back via DM
Alert the admins in #admin-notifications as is current behavior
(optional) Add a command $verified @user for Spike to send the user a DM saying they've been verified. We should by no means require this step, but offer it as an option since the original verification message would no longer be accessible by admins. May want to run this by them first as well.
Rename #bot-commands to something like #system-status, add new channel name to consts.json, and leave old bot-commands key as an alias for backwards compatibility.
Describe alternatives you've considered
Additional context
This stems from a conversation about tweaks to the verification system prior to potentially listing the server in the student hub.
Is your feature request related to a problem? Please describe.
The verification process currently clutters up the public #bot-commands channel, which is also used for server and ITS status messages.
Describe the solution you'd like
Unverified
message via DM$verify
via DMRequest sent!
message back via DM$verified @user
for Spike to send the user a DM saying they've been verified. We should by no means require this step, but offer it as an option since the original verification message would no longer be accessible by admins. May want to run this by them first as well.consts.json
, and leave oldbot-commands
key as an alias for backwards compatibility.Describe alternatives you've considered
Additional context
This stems from a conversation about tweaks to the verification system prior to potentially listing the server in the student hub.