-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hit a 429 #84
Comments
That means you hit a rate limit with discord. were you pushing a LOT of logs really quickly? discord isn't great to use for logging EVERYTHING really just important things like large monetary transactions, specific items, actions and such |
I’ve been using your bot and jd_logs. I’ve had some problems setting up my fiveM server but all I’ve been doing is using the commands for both bots. yours for whitelisting and server admin testing and the other is a bot for logs such as shooting, damage, logging in and out |
So by shooting do you mean a log is sent every time a bullet is fired? so if there's a shootout or use of a machinegun or something it's sending 10-20 logs per second? cause logs like that can have your ip banned from the discord api for abuse. actions like that you'd want to save to memory temporarily for 30 seconds to a minute and dump all the logs you need in a single log. |
Sorry I should of been clearer. From the testing I have done and that is with two bots; zdiscord and JD_Logsv3 running at the same time. Since moving to zaphosting the two bots seem to reach rate limit and zdiscord gives out the error about that. After about two outs the bots will reconnect and work but only at 994/1000 limit. When that is reached they disconnect again. Since last night I have stopped using the latter bot and only have yours running and I've seen a better stability. However; now there is a Event Code: 4000 now happening. This is now causing the bot to reconnect and it repeats doing this. I don't know if that's normal for zdiscors to be doing but so far I haven't reached a rate limit. JD_ logs was the bot that was sending events to certain channels and I feel if I had a busy server that would be spamming a lot ( regardless it's now offline and no longer used ). Zap hosting typically replied just now to my ticket only seeing the Event Code: 4000 and has totally disregarded the rate limit. I'm about to inform them that it was happening beforehand. |
4000 is an unknown error if it's coming from discord's api o.o really weird you'd get that unless something is wrong on zap? Also could try to reset your token and see if that makes any difference |
No problem I'll The funny thing is I have a rocket node server that I moved from and I've got it on there working no problem, same key. I feel it's zap, they have been getting ddosed lately |
Also to go with the error 4000 it keeps sending heartbeat if that's anything |
That's normal. The heartbeat is how the script keeps in touch with the bot api and keeps it active, as long as heartbeats keeps pinging every 20 seconds discord keeps the session active. when heartbeats stop it assumes the bot is offline and stops sending events. |
the bot started acting strange and when i started it with logs its hitting a 429 error
The text was updated successfully, but these errors were encountered: