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
I'm finally getting 3.0 finished in the next month or so. In the current code, I have an httpRequest event that is emitted for the client after every request, but I'm going to have to rework it because it gives users the raw request tables before or while they are used internally, which isn't great for two reasons: 1) I'm trying to avoid using raw tables where ever possible and 2) if the user edits those tables, they may affect the request. I'll have to think about this one when I revisit event payloads.
You could potentially have a place in the client where the information is kept -- on request via a client option -- so that people can check the information. Of these headers i think limit (the number of requests left before you need to wait) is probably the most important/interesting to end users.
It'd be helpful to have a built-in method for checking rate limits via Discord's HTTP Headers: https://discord.com/developers/docs/topics/rate-limits#header-format.
The text was updated successfully, but these errors were encountered: