Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow per-guild binding of system channels #39

Closed
eibex opened this issue Jun 16, 2020 · 0 comments · Fixed by #40
Closed

Allow per-guild binding of system channels #39

eibex opened this issue Jun 16, 2020 · 0 comments · Fixed by #40
Labels
enhancement Software improvement

Comments

@eibex
Copy link
Owner

eibex commented Jun 16, 2020

Allow to set a system channel for each guild (server) the bot is being used in for messages related to commands or errors arising from reaction-role messages hosted in a channel from a certain guild.

The config.ini system channel should be used as a fallback when not set.

My current idea entails:

  • adding a guild_id column to the messages database table
    • a migration function to fill this column in the already existing rows
  • creating a systemchannels database table with columns: guild_id and channel
  • adding the appropriate commands to bind guild system channels
  • adding the appropriate checks to clean the database if a channel/guild is deleted
  • modifying the system_notification function (currently in bot.py) to check if a system channel is set for a guild that was the source of a notification
@eibex eibex added the enhancement Software improvement label Jun 16, 2020
@eibex eibex closed this as completed in #40 Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Software improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant