-
-
Notifications
You must be signed in to change notification settings - Fork 723
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] rate limited #411
Comments
Discord is rate limiting you, it's not a bug or anything like that, it's because you're sending too many requests when you delete messages |
How do I prevent this? |
you don't, it's there to prevent people Ddosing Discords servers |
Bruh, this never happened before though when i first started using it 😭 but ok then |
Discord has made rate limiting a lot stricter in recent years, so it is indeed possible that you used to be able to delete faster. I would recommend setting the delete delay in the advanced section to 2500 ms. The current default is out of date, see https://github.com/victornpb/undiscord/wiki/delay and #402. |
Oh ok thanks for the help I see if this would make it work better so it doesn't pause on the rate limited message for too long. |
as already said, it's not a bug, it's expected behavior and determined by the discord server. in personal tests, for you it may be different, I arrived at the values, as the lowest values, [search delay: 6400] and [delete delay: 2000] when deleting more than 500 messages at once. any value below displays the message "being rate limited by the API". for a smaller number of deleted messages, lower values can be used. however, with these values I delete more than 10K without any API mishap. [40K+ at the moment... and it will take more than 1 day.] _o/ edit: please read #414 for newer results... update: [search delay: 1000] and [delete delay: 2200] tested for 999 messages at once with success. (about 400ms faster :p ) |
keep getting this popping up every 5 seconds while it's deleting messages and I don't know what to do. This never used to happen before last time I used it. I tried changing the "search" and "delete" delays and it still continues happening.
The text was updated successfully, but these errors were encountered: