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
{{ message }}
This repository has been archived by the owner on Sep 5, 2021. It is now read-only.
Discord has a rate limit. We will probably have to queue up chat messages for X number of seconds and then blast them off into the discord server. We don't want to submit a message for every server.
The text was updated successfully, but these errors were encountered:
Why not just handle the rate limits when they happen? When a bot is rate limited, the API gives you back a number of milliseconds to wait before sending again; you can just put things on a queue then, instead of doing it all the time. Seems needlessly slow for people who might be doing quick running commentary or something (cough tourney matches).
my concern is that the discord system is intelligent enough to be able to determine who keeps hitting the rate limit and apply even higher ones to the point where it is limited badly. Even if they don't do that know, who knows when/if. And tbh i'd rather not find out.
Good point - maybe we should use the rate limit headers they give you normally then to make sure things don't go too fast. For one thing, I don't want to start displaying multiple messages at a time and get this alignment problem, if we don't have to:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Discord has a rate limit. We will probably have to queue up chat messages for X number of seconds and then blast them off into the discord server. We don't want to submit a message for every server.
The text was updated successfully, but these errors were encountered: