Address trole problems #322

Merged
Sirdog merged 2 commits from bug/trole-not-removed into dev 2026-05-29 20:22:36 -04:00
Owner

Firstly, fixed the typo that #315 notates.

Secondly, tried to address the bug that #319 notates. I am unsure if the bug is fixed, as I could not find a simple cause. My only guess is that at the time that the bot attempted to read the member's roles some network shenanigans happened to make it return False. So, I've added more in-depth handling, added a catch for any Exception class rather than the 2 previously specified, and have an embed being sent to the sysop channel directly for visibility.

As a result, needed to add the sysop channel to the variables file, so added the field to the example file.

Firstly, fixed the typo that #315 notates. Secondly, tried to address the bug that #319 notates. I am unsure if the bug is _fixed_, as I could not find a simple cause. My only guess is that at the time that the bot attempted to read the member's roles some network shenanigans happened to make it return `False`. So, I've added more in-depth handling, added a catch for any Exception class rather than the 2 previously specified, and have an embed being sent to the sysop channel directly for visibility. As a result, needed to add the sysop channel to the variables file, so added the field to the example file.
Not sure if event is fixed, but added more handling and an explicit notification to sysop channel.
Sirdog deleted branch bug/trole-not-removed 2026-05-29 20:22:36 -04:00
Sign in to join this conversation.
No description provided.