You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
guild_id
column to themessages
database tablesystemchannels
database table with columns:guild_id
andchannel
system_notification
function (currently in bot.py) to check if a system channel is set for a guild that was the source of a notificationThe text was updated successfully, but these errors were encountered: