twin / discord-bot-go Goto Github PK

For instance, we'd only want to give permission to one command in one server.
Though some configuration could stay global, like the OwnerId and the BlackList (?)

I can imagine permissions becoming very messy if the bot is used in multiple guilds (see #2), which is why moving part of the configuration to a SQL/NoSQL database would be a very good idea.

At first, I was thinking of maybe just using something like SQLite, but perhaps something like MongoDB would be more future-proof (or rather, scalable).

The bot should, if commanded to, implement self-assignable roles.

For instance, enabling self-assignable color roles would do the following:

• Create a category called roles
  • Nobody except the bot and its admins themselves should be allowed to post in the channels of this category
• Create multiple roles who have the effect of changing the color of the name of a person (e.g. color-red would set the color of the user to red, color-white would change the color of the user to white, etc.)
• Create a channel in the newly created category named roles-color
• Send a message in that channel with each color next to an emoji

e.g.

:regional_indicator_a: color-red
:regional_indicator_b: color-white
...

• Listen to reaction events on that message
  • If the reaction is the emoji representing one of the roles, then give the user who reacted said role (e.g. user reacts with :regional_indicator_a:, bot assigns role color-red to user)