We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please describe the problem you are having in as much detail as possible: The messageDeleteBulk event is fired twice
Include a reproducible code sample here, if possible:
const { Client } = require('discord.js'); const bot = new Client(); bot.on('message', msg => { if (msg.content === '!bulk-delete') msg.channel.bulkDelete(2); }); bot.on('messageDeleteBulk', m => console.log(`Bulk deleted ${m.size} messages.`)); bot.login('token');
Further details:
discord.js version: Master
node.js version: 8.6.0
Operating system: Windows 10
Priority this issue should have – please be realistic and elaborate if possible: Medium-High
I found this issue while running code on a user account
I have also tested the issue on latest master, commit hash: 68a3058
The text was updated successfully, but these errors were encountered:
I've just confirmed this on the provided hash (latest at time of writing). Looking into it now.
Sorry, something went wrong.
fix(MessageBulkDeleteAction): remove deleted messages from cache
351f1b2
Fixes discordjs#2036
fix(MessageBulkDeleteAction): remove deleted messages from cache (#2046)
356778b
Fixes #2036
Successfully merging a pull request may close this issue.
Please describe the problem you are having in as much detail as possible:
The messageDeleteBulk event is fired twice
Include a reproducible code sample here, if possible:
Further details:
discord.js version: Master
node.js version: 8.6.0
Operating system: Windows 10
Priority this issue should have – please be realistic and elaborate if possible: Medium-High
I found this issue while running code on a user account
I have also tested the issue on latest master, commit hash: 68a3058
The text was updated successfully, but these errors were encountered: