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
Since discord nerfed their rate limit for channel renaming down to only twice every 10 minutes, it's no longer acceptable to just check each channel in a loop every X seconds/minutes if they need to be renamed.
Instead, we need a system without loops that catches various events (user activity changes, users joining the channel...) depending on the template used (e.g. only catch user activity changes if @@game_name@@ is used in the template) and queues up a rename for the channel.
Then there could be a queue handler that decides if it's safe to rename the channel (to avoid hitting the rate limit) and sends the actual request when it's safe to do so.
For bonus points, if a user uses the vc/name command and the queue handler decides it's not safe to rename the channel yet, it could return a callback so the bot can respond to the user and tell them exactly how soon the channel will be renamed. Currently with the loop only running once every 10 minutes, the vc/name command can have no effect for 10 minutes, with no feedback to the user to explain why.
The text was updated successfully, but these errors were encountered:
Since discord nerfed their rate limit for channel renaming down to only twice every 10 minutes, it's no longer acceptable to just check each channel in a loop every X seconds/minutes if they need to be renamed.
Instead, we need a system without loops that catches various events (user activity changes, users joining the channel...) depending on the template used (e.g. only catch user activity changes if
@@game_name@@
is used in the template) and queues up a rename for the channel.Then there could be a queue handler that decides if it's safe to rename the channel (to avoid hitting the rate limit) and sends the actual request when it's safe to do so.
For bonus points, if a user uses the
vc/name
command and the queue handler decides it's not safe to rename the channel yet, it could return a callback so the bot can respond to the user and tell them exactly how soon the channel will be renamed. Currently with the loop only running once every 10 minutes, thevc/name
command can have no effect for 10 minutes, with no feedback to the user to explain why.The text was updated successfully, but these errors were encountered: