Message Delete Has No Way To Check Which Audit Log Entry

[Skillz4Killz]

There is currently no way to check which audit log entry is in reference to the deleted message.

The target, in this case, is the mod user and not the message itself. Therefore, the only plausible solution is to fetch audit logs then filter them to where the message author id === target_id. However, in larger more active servers this can still be a big problem.

I have reports of wrong mods deleting messages in bot logs showing a mod deleted it because the target_id on both audit log entries is the same with no way to verify which belongs to which using a message id.

The entire purpose of audit logs is so you can know which user is taking action but at the moment this is near impossible.

After digging a little deeper into this, I have noticed that Discord Audit Logs do not show when a user deleted their own message at all. This is actually very bad from a moderation perspective as if a user sends a message that breaks a rule then deletes it there is NO WAY to tell this happened unless a moderator was actually there watching it happen.

I have also noticed that when a bot is used to delete messages, none of those are ever in the audit logs either.

Solution

Add a deletedMessages property that holds an array of message ids that were deleted. Also include messages deleted by message author or bots in audit logs.

extra: {
	count: 2
	deletedMessages: ['messageID', 'message2ID']
}

[Skillz4Killz]

Bumping this as 2 verified discord server's have requested a fix from me on the bot for this recently.

[TheAbyssSlayer]

Hello, how can i contact you?

[Andre601]

Can agree that this can be bad for Discords where you want to know who deleted what.
Sure there are bots that log all message actions (including deletions of messages from the creator itself) but it's only a semi-good solution since, as the issue pointed out, are no users available for when the creator itself deleted it and also no audit logs at all for when a bot deletes it, which makes moderating much harder (Again, bots have a solution by logging any deleted message, but it is hard to find out who now deleted it if the bot can't say who did it).

[erkinalp]

I think message IDs of deleted messages are intentionally not logged, so that the deletion is traceless.

[Skillz4Killz]

Bump Bump Bu-bu...bu-bump. Really need this to work 🙏

O and Andre its a larger issue than that. Once a moderator deletes a users message. Going forward there will always be a auditlog entry for this user. So now even if the user deletes the message themself i have no way of knowing whether the message was deleted by themself or by a mod since trying to filter the auditlog entries is impossible because the target is the message author and not the message id.

auditlogs.entries.find(e => e.channel?.id === message.channel.id && e.targetID === message.author.id)

Even on message delete when a user deletes their own message this will return a audit log now once a mod has deleted another one of their messages. This ends up causing logs to say that X mod deleted Y message even though NO mods deleted Y message.

[taylorsamy]

Bump. Any chance that this will ever be implemented?

[Tiffceet]

I have also noticed that when a bot is used to delete messages, none of those are ever in the audit logs either.

I am here for this, why is it that when bot deletes messages that is not theirs, it won't show up in the audit logs?
This is really bad if let say the admin invited malicious bot and has been deleting messages randomly and there is no way to trace back unless having a bot to watch for MessageDelete which is really counter-intuitive and not all admins on the platform are aware of this.

Any chance of getting this to work?

[averithefox]

Bump.

[TheAbyssSlayer]

Lmao

[erkinalp]

i think this is by design to prevent reverse victim chasing

[erkinalp]

remember, audit log is not replay log