audit log action types MEMBER_MOVE/_DISCONNECT returning unexpected target_id

[NCPlayz]

For both action types:

MEMBER_MOVE: 26
MEMBER_DISCONNECT: 27

The target_id is the first person to have had the action per consecutive event.

Steps to reproduce:

1. Enter the voice channel with user X, and Y.
2. Move or Disconnect, using your own account, X first, then Y.
3. Fetch the audit log and match target_id with the corresponding user ID.

The target_id should be the first user which was moved or disconnected.

This seems unexpected as both events provide counts as an option, but do return any form of list representing the users who were moved or disconnected.

[Auralytical]

Oh yeah, target_id wasn't intended to be included in these events as it's combining multiple into a single entry.

[night]

fixed in next api deploy. old events may still retain target_id

[ChrisTalman]

May I ask as to why these events are grouped into a single entry, as opposed to each enjoying its own entry?

It would be useful to know exactly who was moved, at what time, and by whom. Currently, if a lot of events happen at around the same moment, it is not possible to know for certain who moved who.