If you check the documentation over at discord you can see that the base url is now only instead of discordapp.
By changing the api url inside the discord.js Client we can get the bot up and running. This seemed to fix the issue, many of you might have noticed that discord recently switched their domain from to just and that seems to cause the issue. Ofcourse make sure that if you have a different variable name to change it, in my case its bot.
#Discord translate bot error 429 code#
If your bot doesnt connect, gives a 429 status code or just returns a something took too look error you should do the followingĮither remix this extremely basic base project and create a bot in it:Īfter importing the Client from the discord.js module and creating a new client i.e: const = require("discord.js") Lately alot of my discord bots just would not want to connect and it has been bothering me a bit.īut i found a solution to this problem and this may help you guys out too. Please if you are here just to hate on me, complain or try to help me, do not comment as i do not want to waste my time replying to comments that arent relevant to helping others, that instead try to help me Encountering error 429 is a terrible experience, but it doesnt mean rate limiting is a bad thing. The HTTP error 429 is actually an HTTP status code it’s a client error that is sent back from server to signal to inform users that they have reached the rate limit allowed.
Im aware of the meaning of the status codes and im aware of the watch.json and vice versa. It says you have made too many requests, hitting the rate limit of an API. Just to clarify before you read the rest of this post, I myself do not require any help, im just giving some help for the ones who are willing to try it instead of complaining,
0 kommentar(er)
