From d6016b83b477fbbd6a169eed098bebe529f9c8d0 Mon Sep 17 00:00:00 2001 From: Jiralite <33201955+Jiralite@users.noreply.github.com> Date: Fri, 7 Nov 2025 12:35:18 +0000 Subject: [PATCH] fix: update usage --- autoresponses/autoresponses.toml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/autoresponses/autoresponses.toml b/autoresponses/autoresponses.toml index 9e82c67..bf7d8e7 100644 --- a/autoresponses/autoresponses.toml +++ b/autoresponses/autoresponses.toml @@ -1,13 +1,13 @@ [member-arrive] keyphrases = ["members didn't arrive in time"] content = """ -Discord introduced a rate limit on requesting all guild members [(src)]() --# While the announcements state 01/11/2025 as roll out date, they have confirmed that this has only taken full effect a few days ago. +Discord introduced a rate limit on requesting all guild members [(source)]() +-# Despite the announced 01/10/2025 rollout date, it only took effect recently. -- Apps can now request all members **once** per **30s** per guild. +- Apps may only request all members **once** per **30s** per guild. - You will have to update your code accordingly to make sure this doesn't affect your app. -- Look for instances of [`guild.members.fetch()`]() with no or multiple user ids. --# We are working on making the `GuildMemberManager#fetch()` call reject, if we receive this rate limit after requesting members. This will likely land in the next release. +- Look for instances of [`guild.members.fetch()`]() with no user ids. +-# We are working on making the `GuildMemberManager#fetch()` call reject if we receive this rate limit after requesting members. This will likely land in the next release. -# If you confirmed this cannot be the reason, you can find other caveats [in our guide]() <:djsguide:862626783890636830>. """ reply = true