Thank you for this, I’ll take a look into it later. Appreciate it homie.
1 Like
Don’t take a look later, take a look now and edit your solution on this post so that people who eventually uses this will have a working solution instead of the current unworking at all solution you’ve pushed.
2 Likes
You know, an easy way you could prove you own the bot is a credits section on the website!
I have credit sections in the games I work on, and although I do believe you own the bot, others do not, so this might be something to consider.
seems too much, make it 10 minutes.
Ratelimit got removed a while back
that is bad as your violating discord Ratelimits and they might ban you
what? violating a ratelimit won’t get your account banned, also have you not heard of something called proxies?
… discord literally put that in their TOS.
TOS reading is required.
Discord only allows proxies which has a ratelimit to not humilate discord.
When you violate a rate limit, your given a timeout. It is IP relative and doesn’t link back to an account.
Thats only true for proxies. Proxies implemented that.
If you keep hitting this limit you get a risk of ur account banned. And the abusers one day will get you banned by spammng your proxy. Now save your account before they do so.
1 Like
Lol, I don’t think you understand how this works. My account will not be banned since it’s not a direct link of my account. It’s being requested by an IP, not an account, so there is no way of them either finding out my account even if they did.
Do you know that this way your proxy will end up getting rate limited or even banned from the discord api. Unless this is a rotating proxy i wouldn’t recommend using it as most of the time it can be rate limited
And to be honest not having a rate limit can cause an overload of your system and slow it down a lot but also if this proxy is not a rotating one the ip can get rate limited because a user spams your api and yours spams discord’s making the proxy unable to work for other users as well
So you quite literally just explained a proxy? It’s definitely dangerous to use a webhook though, its rate limited to 30 webhook triggers per minute (can result in things not working etc.) - using a discord bot is way safer as that’s not capped.
Discord did not, even in developer portal you can see that the IP you’re overloading from is simply going to be temporarily restricted, which occurs when 10000 requests are sent within 10 minutes that resulted in an error code like for example 401, 403, 404, and 429.
Proxies are irrelevant unless you’re planning to make tens of them
if theyre sending it to your api, ofc it will send to your IP.
You got it all wrong buddy, hate to break it to you.
Simple example to put it in other words: if you have 10 clients that each send a request within 1 second, it doesn’t matter if they all wait the exact same amount of time, because all requests will eventually hit within 1 second. The emphasis is on the rate - requests have to be queued and only allowed to be released while the rate cap has not been reached.
1 Like
Everyone complaining about the “rate limit” you’ve implemented is right. Maybe you’re failing at visualizing it, but if you trigger ten chatted events and just put an arbitrary wait before the code runs, then all those requests still happen within the same amount of time- just 1.5 seconds later.
Exactly. He didnt implement it right, hes just delaying the request which will hit the ratelmit just after 1.5 seconds.
Did you ever end up implementing a rate-limiter?
Also the ;verify does not seem to work and there’s no documentation on the endpoint website. Wanted to use this, but it’s not really apparent to me why it is not working.