- What's your exact discord.js
npm list discord.jsand nodenode -vversion? - Not a discord.js issue? Check out #1081585952654360687.
- 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!
#Question: GUILD_PRESENCES rate limit
52 messages · Page 1 of 1 (latest)
Question: GUILD_PRESENCES rate limit
No. Intents just are for receiving events
it however might slow your network down if you have bad connection. because that intents causes a lot of initial data and also a lot of emitted events
@fallen flame @vast oriole Okay thanks for your answers, but there's something I can't understand, It was suggested me to remove the "GuildMessageReactions" intent because it was a bot restriction reason.
How is it possible that my bot is restricted, when I do not perform spam actions ?
who suggested that
Intents are for receiving eventd
Its what you do in those events that might get you ratelimited
So I perform actions with the database which can sometimes take a while but it has nothing to do with the discord API, this is not a cause of ratelimit right ?
Do you run more than one process with the same token?
What kind of process ? What do we call a process ?
Can you show the full error please?
No only one instance
where can I find this?
Above and below where you got this screenshot from
That is still only part of it. Copy all of it into a pastebin
https://sharemycode.fr/6m2
It is good like that ?
Share live code snippets with anyone, anywhere. Aand keep control of it.
So you make raw requests with axios. Not djs related
Djs handles ratelimits for you. Axios is just a dumb http lib and can’t
Why do you use axios at all?
You… hit the ratelimit because of those requests. Just listen to client.rest.on('rateLimited',…) if you want to know when you were about to hit a ratelimit. You don’t need to check yourself. That’s literally doing the opposite of what you want it to do
Discord.js queues requests if you would hit a ratelimit and wait until the ratelimit resets to then send the requests in the queue
Sure. Because the requests of djs aren’t the cause of your ratelimit. Your custom ratelimit check is. Just remove that entirely, it doesn’t help you at all, it causes your issues
You mean the request axios ?
To help you understand how I set up the system, the axios handleRateLimit request is in no way called via commandSlash or others, it's outside, I have an API running, I make a request via a web server to retrieve information to check if my bot is restricted or not but otherwise i don't use it.
Your comment literally says it does it every 5 minutes 
i just forgot to remove it ^^'
Its called there
with express App
And the issue is: each time you call that axios while being at the rateLimit it‘ll cause a 429. and those are the cause of your cloudflare ban you face

You can just get that information from client.rest. Querying the API to find out if your rateLimited is a bad idea in itself.
I use that only to know if my bot is restricted or not, because 2 days ago my bot stopped running without any log data on the client.on('rateLimited')
Is it possible to have a report of why the bot was blocked?
Do you do any other raw requests with axios or whatnot?
It tells you why: because you caused too many 429 errors. From your axios request
No only for that i checked my project
Yes but get more informations because that doesnt help me ^^
Huh? Why not? Stop using your axios and wait for the cloudflare ban to pass. They last an hour afaik