You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a token that is associated with many guilds, which leads to immediate gateway rate limiting on startup due to guild subscriptions.
In previous versions, it was possible to simply pass guild_subscription_options which has been removed in version 2.0, as the auto-subscribing system has been removed. Now, chunk_guilds_at_startup is utilized.
However, passing chunk_guilds_at_startup=False to the Client did not solve the issue. The rate limit significantly delays the on_ready event.
Debug logs look like this:
[...]
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
[Repeated for every guild until hitting ratelimit...]
Gateway is ratelimited, waiting 53.96 seconds.
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Gateway is ratelimited, waiting 0.00 seconds.
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Gateway is ratelimited, waiting 0.00 seconds.
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Gateway is ratelimited, waiting 0.00 seconds.
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Subscribing to guild 111111111111111111 with payload {'guild_id': '111111111111111111', 'typing': True, 'threads': True, 'activities': True}
Dispatching event ready
[...]
Is there a way to fix this or to pass a similar argument to the client function?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a token that is associated with many guilds, which leads to immediate gateway rate limiting on startup due to guild subscriptions.
In previous versions, it was possible to simply pass guild_subscription_options which has been removed in version 2.0, as the auto-subscribing system has been removed. Now, chunk_guilds_at_startup is utilized.
However, passing chunk_guilds_at_startup=False to the Client did not solve the issue. The rate limit significantly delays the on_ready event.
Debug logs look like this:
Is there a way to fix this or to pass a similar argument to the client function?
Beta Was this translation helpful? Give feedback.
All reactions