Closed Amgelo563 closed 3 years ago
You will also need the USER
partial. The reason why this works in Client#messageReactionAdd
is because Discord sends the user object, but only sends the id of the user in Client#messageReactionRemove
(discord.js attempts to resolve a user object, and stops if it cannot).
Thanks, after adding the USER
partial it worked. Is this officially documented anywhere? I spent a really long while searching and could not find any documentation which lead me to think it was a bug, I apologize if it's documented though.
It's just logic. That event pass two parameters: a User
and a MessageReaction
object so both can be uncached and, in order for the event to be triggered, you need to enable both partials!
Issue description
The
messageReactionRemove
event doesn't seem to trigger at all on non cached messages even with Partials.Weirdly enough the exact same code does work as intended with
messageReactionAdd
, I can react to messages older than the bot's age and it'll log it after caching it using Partials, but it doesn't work at all withmessageReactionRemove
. It only works on messages that are sent after the bot booted up or messages thatmessageReactionAdd
fetched into cache.Codesample
discord.js version
discord.js@13.1.0
Node.js version
v16.9.0
Operating system
Windows
Priority this issue should have
Medium (should be fixed soon)
Which partials do you have configured?
CHANNEL, MESSAGE, REACTION
Which gateway intents are you subscribing to?
GUILDS, GUILD_MESSAGES, GUILD_MESSAGE_REACTIONS
I have tested this issue on a development release
No response