Open GoldenAngel2 opened 1 year ago
For the voice stuff, that's known because the previous auditlog is updated instead afaik, hence why it won't get fired again
For the voice stuff, that's known because the previous auditlog is updated instead afaik, hence why it won't get fired again
@Lulalaby So if its known it should still be documented. And then we now have the question of why there is not a GUILD_AUDIT_LOG_ENTRY_EDIT event.
Ya that's a thing a dev should answer 🤷♀️
Ya that's a thing an dev should answer 🤷♀️
a*
+1, any update?
Why don't we have a GuildAuditLogEntryUpdate yet??? How can we track that
Discord should really correct voice logs, on large servers it's impossible to determine precisely which staff has actually moved or disconnected another member. Not to mention that Discord still hasn't implemented the missing audit logs concerning the reorganization of channel order and roles. I really doubt that solving the audit log problem would require a lot of resources and development time. What are the folks at Discord up to?
Any news on this ?
Description
The audit log event only gets sent once for the first action taken instead of all actions taken by a moderator.
For the following audit log events:
MEMBER_MOVE
(26),MEMBER_DISCONNECT
(27),MESSAGE_DELETE
(72)Steps to Reproduce
Message Deletes
manage messages
delete the messages from that different accountVoice Member Disconnects
Voice Member Moves
Same as the other two
All of them should be sent per-action taken with 'count' being increased.
Expected Behavior
It sends the audit log event on every action taken, with the correct values.
Current Behavior
It only sends the audit log event on the first action taken.
Screenshots/Videos
No response
Client and System Information
Discord WS: v10 DIscord API: v10