API Events for voice moves and disconnects

[SammyWhamy]

It would be amazing to have API events for when users get moved, disconnected, moved into audience, or are invited as speaker in a voice channel or stage. Currently it's impossible for bots to monitor this behaviour, meaning when staff in a server abuse these permissions there's no feasible way to track down who's doing this.
I saw there was an older issue regarding audit logs which was closed because it would cause too much stuff in the audit logs. But I think a gateway event would solve this issue perfectly and only for those that actually need it.

[almostSouji]

This all emits VOICE_STATE_UPDATE, the caveat is that this of course only reflects the state change on the member, not who initiated that change. The audit logs for these events are inherently quite vague,

There have been prior mentions that the "who did this" question should be answered by audit logs, not gateway payloads, so I imagine that also applies here.

[SammyWhamy]

Voice state updates do indeed only show the actual change between voice states. Audit logs do indeed show Disconnects and the user that performed the action. Audit logs will also show channel moves, but not from which channel. I guess this could be figured out by combining audit logs and gateway events but that doesn't seem very easy either.
The main issue in my case however is that there's no events nor audit logs for moving someone to the audience in a stage or inviting someone to speak.

My suggestion would be to add some "who did this" to the VOICE_STATE_UPDATE event (Would solve the above-mentioned moving issue as well), and emit VOICE_STATE_UPDATE or separate events for moving to and inviting from the audience. This along with a field for the user that initiated the request.