-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
messageReactionRemove event does not trigger #2922
Comments
Though this is being addressed in #1376, discord.js currently only emits the |
You are wrong. Just take a look at the code sample: I cache the message manually in order to show it's not working as intended. |
This has been addressed in #3070, please try out the PR and tell me how it works for you! |
Closing due to inactivity |
@amishshah |
You can fix this by manually listening for the raw events and then emitting I used the template code at this link and it works perfectly. |
Seems like this should be reopened because it still happens. Even if you cache the message manually, it doesn't emit the event unless you unreact, react, and unreact again. Even in the example of looking at raw packets that @pimhakkert posted, it says "// There's no need to emit if the message is cached, because the event will fire anyway for that", yet clearly it wont. I have confirmed that the code in that works, but you MUST remove that line that checks if it's cached, otherwise it will skip "cached" messages, and not emit the event, just like it does without this script. |
Please describe the problem you are having in as much detail as possible:
If you put reaction on a message and then log in with the bot, the messageReactionRemove event not gonna happen when you remove your reaction from this message even if you cache this message.
While trying 'raw' event I found out that message.reactions is empty after fetching message from there and thus event emitter sends undefined reaction in this case.
However if you add reaction with the bot online it all works as expected.
Include a reproducible code sample here, if possible:
Further details:
The text was updated successfully, but these errors were encountered: