SwitchUpCB

We are giving that decision (to send one or multiple requests at a route's first request) to the end user of our library through the use of a default bucket.

> I was under the impression that this was meant to be constructive in solving some type of issue. Unfortunately, I now realize that I have wasted my time and...

In addition to the above, https://discord.com/developers/docs/topics/gateway#rate-limiting can also be clarified. > Clients are allowed to send 120 gateway commands every 60 seconds, meaning you can send an average of 2...

Thanks for the correction @Zoddo.

> These are not actually described in the documentation but I have been able to deduce the types of rate limits Discord has: Global (Requests), Per Route (Requests), Per Resource...

@shaydewael Do you have a list of all the routes with top-level resources which use per-resource rate limits? `X-RateLimit-Scope` is unfortunately only returned on 429'd requests.

The issue is that there is no guarantee that top-level routes (which I assume are routes with guild, channel, webhook parameters coming first) are actually resource routes. This interpretation itself...

> This statement is rather ambiguous because "often" implies that it does NOT apply to every request containing a top-level resource; or started by a top-level resource. The problem is...

Given that @jhgg is at least a Senior Staff Engineer at Discord, and also the initial announcer of Discord Rate Limits, he may also be able to confirm the question...

@advaith1 Do you have any other information about classifying endpoints to per-resource rate limits prior to sending a request?