Question about Discord.JS's rate limit handling
I used ChatGPT just to have it summarize how Discord.JS handles rate limiting.
My scenario was something along the lines of: "How will Discord.JS handle rate limits if I sent 1 message to 100 different webhooks?"
I wouldn't hit the webhook rate limit, but I would hit the global rate limit.
1: The response from ChatGPT was that Discord.JS (for example) will send 50 of those messages and then queue the remaining requests once the rate limit retry-after time has passed, is this true?
2: If yes to question 1: If not 50, how many requests will Discord.JS send at a time?
3: Is there any sort of method/technique I should be using for my given scenario, or is relying on Discord.JS's rate limit handing fine enough?
Thanks for any answers!
2 Replies
- What's your exact discord.js
npm list discord.js and node node -v version?
- Not a discord.js issue? Check out #other-js-ts.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!- To pass a message from one user across all servers with the bot into a specific channel (1 message to however many servers).
- Yes, I believe
Possibly, I was considering that, but:
The idea was not for it to be an one-way announcements channel (e.g, from dev guild to servers), but a global channel where the owner from any server can post their message, will an AnnouncementChannel still work?
I'm not sure I quite understand this.
Also, I'm not sure 10 publishes per hour will be enough in the future. If that's the case and I decide not to use AnnouncementChannel, although it may put some strain on the API, will it generally be fine to just to use text channels?
Gotcha, thank you.