If you check the documentation over at discord you can see that the base url is now only instead of discordapp. Props to this thread (in Replit's Discord server) where I found the answer. By changing the api url inside the discord.js Client we can get the bot up and running. I found a fix It turns out that you can run kill 1 in the shell tab to destroy the current container and switch to a new one. 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. I wonder if it might be due to the purging of the last 50 messages almost every time the bot is interacted with. Ofcourse make sure that if you have a different variable name to change it, in my case its bot. The servers aren't too over populated at all (100 members but probably half that interact with the bot) and it's not too spammy when they interact with the 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 Im aware of the meaning of the status codes and im aware of the watch.json and vice versa.
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)
