-
Notifications
You must be signed in to change notification settings - Fork 19
Description
We have discussed how we want to change the bot's setup workflow to use buttons instead of multiple commands as we have it right now. Here is a list of what should change.
Instead of having a config command with multiple subcommands, we should create one command that displays a button per configurable item or a drop down list with option for each. Here is an inspiration of how it could look.
Configuring notifications
Show a channel selection and a disable button or a channel selection option depending on if a channel has already been set up or not.
Configuring a group
Show an integer input option and a disable button or just an integer option depending on if a group has been configured already.
Configuring an rsn
I propose we move setting an rsn to this command as well and make it clear that setting an rsn doesn't mean linking your discord with your in-game account. So we show a string option and a disable button or just a string option depending on if an rsn has already been configured.
Currently the /setrsn command is a little confusing and is leading to people thinking it somehow links their in-game account with their discord which isn't true because multiple people can configure the same rsn. We should make it clear that configuring an rsn only sets a default rsn for the other commands that require an rsn as input.
Other
If a user has admin permissions all options should be available. If the user doesn't have admin permissions only the configuration of an rsn should be available.
When this implemented, we should not immediately remove the currently available commands but rather turn them into a message saying that the configuration of the bot has been moved. The message could has ephemeral set to true so they only show up to the one who sent the command.
What should the new command be? Keep it /config or change it to something else, such as /setup?