Closed Lord-Ptolemy closed 8 years ago
It looks like the event is passing a reference to the original Message object instead of a copy or entirely new Message object. So when the original cached object gets updated in the line before the event is fired, the reference is updated as well, and both messages being passed are the new message.
can someone test latest indev
Check 76ab439... I may or may not have forgotten to push.
Oh, weird. That didn't show up for me like 5 mins ago when I made that comment linking the code. Okay, yeah, possibly fixed. Can test in just a few moments.
Edit: Nope still the same. The issue comes from msg
being a reference, not the update to nmsg
coming before or after the event is fired.
~~Edit 2: Helps if I update my discord.js to indev before testing... ¬_¬ It looks fixed to me. @Lord-Ptolemy confirm?~~
(final?) Edit: Nope. Initial testing was fine, but further testing shows it's still borked.
Running latest indev version, can confirm messageUpdated is now showing the old message and new message properly.
Confirmed fixed, indev
This wasn't entirely fixed... Check in next time :P
< Will do..
http://discordjs.readthedocs.org/en/stable/docs_client.html#messageupdated Discord.js: NPM 5.3.2 Node: LTS 4.2.3
newMSG & oldMSG are the same.
Am I just missing something or is it really broken?