From 08d45cc2abba781245e3f5a2c356048e343f2335 Mon Sep 17 00:00:00 2001 From: Michael H Date: Wed, 17 Feb 2021 07:33:17 -0500 Subject: Update docs to be clearer about discord limitations --- docs/intents.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/intents.rst') diff --git a/docs/intents.rst b/docs/intents.rst index 8ba036c9..38264b19 100644 --- a/docs/intents.rst +++ b/docs/intents.rst @@ -118,8 +118,9 @@ It should be noted that certain things do not need a member cache since Discord - :func:`on_message` will have :attr:`Message.author` be a member even if cache is disabled. - :func:`on_voice_state_update` will have the ``member`` parameter be a member even if cache is disabled. -- :func:`on_reaction_add` will have the ``user`` parameter be a member even if cache is disabled. -- :func:`on_raw_reaction_add` will have :attr:`RawReactionActionEvent.member` be a member even if cache is disabled. +- :func:`on_reaction_add` will have the ``user`` parameter be a member when in a guild even if cache is disabled. +- :func:`on_raw_reaction_add` will have :attr:`RawReactionActionEvent.member` be a member when in a guild even if cache is disabled. +- The reaction add events do not contain additional information when in direct messages. This is a Discord limitation. - The reaction removal events do not have the member information. This is a Discord limitation. Other events that take a :class:`Member` will require the use of the member cache. If absolute accuracy over the member cache is desirable, then it is advisable to have the :attr:`Intents.members` intent enabled. -- cgit v1.2.3