-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[BUG] Fallback Channel Method Bugs #3002
Comments
Coolguy3289
added a commit
to Coolguy3289/modmail
that referenced
this issue
Apr 19, 2021
Addresses modmail-dev#3002 Will add a 1 channel buffer to the check to account for Discord API bugs preventing the category from actually reaching 50 channels.
That's kinda weird. It's like the bot didn't save the new 'fallback_category_id' or something. |
Well it did, and it used that category, but once it was filled up, it didn't migrate/update the config for the new one. Rather, it did, created the new thread and seems to have just dumped it for the old value. I've tried removing the config value and it's doing the same thing. |
Coolguy3289
changed the title
[BUG] Discord Max Channels Per Category Bug
[BUG] Fallback Channel Method Bugs
Apr 22, 2021
fourjr
added
approved
bug
This is a confirmed bug
staged
Staged for next version
and removed
maybe: bug
An unconfirmed bug
labels
Apr 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Categories usually have a max channel limit of 50, this is checked in thread.py however there is a bug in the Discord API where a category having 49 channels is returning "Category has reached the maximum number of channels" causing the thread creation to fail since the check to trigger the fallback category functionality is contingent on the category having 50 channels.
Bot Info
Bot version (check with
@modmail about
): 3.9.3Host method (Heroku, self-host, etc): Self-Host
Error Logs
http://haste.thegamingcorner.net/imelisejom.sql
After some extra Debug Logging
http://haste.thegamingcorner.net/igelukovez.sql
The text was updated successfully, but these errors were encountered: