Member kick events

[broman]

This was requested in #56, claimed to be shipping with audit logs, and it wasn't.
Pretty simple, would be nice to have either two separate events for kicking from and leaving a server, or a boolean flag on the current event.

[broman]

Gonna give this a quick bump after almost 3 months without a reply. Is this coming with API v7? Is this coming at all?

[night]

The member kick events that Jake alluded to are within the audit log. We did not say we were adding additional gateway events for kicks specifically. Bots can use the audit log to determine if a kick (or any other moderation activity) occurred.

[MinnDevelopment]

What about pruned members?

[Brayzure]

Can such information be provided via the gateway at some point in the future? It seems like a really nice QoL improvement.

[Zoddo]

I'm bumping this one. Currently, the only way to know if a user was kicked is to fetch the audit log everytime a member leave a guild. This happens pretty frequently in big guilds, or if the bot is in a lot of guilds. Additionally, this don't allow us to catch users kicked by a prune.

Having a flag or a separate event, would allow us to fetch the audit log only when a user got kicked, thus reducing the traffic to the API a lot.

Ideally, the kick/ban's author & reason would be included in the gateway event, totally suppressing audit log requests.

[jhgg]

No need to bump. This request has been noted, and we have allotted time to work on it some time later this year. :)

[Zoddo]

Oh, ok. I bumped it because the night's comment suggested that this wasn't planned 😃

[AEnterprise]

personally i am against the event including the responsible moderator and reason, most servers do not have audit logs exposed to non moderators, nor do they have a public channel where a bot logs this info

adding that to the event would expose info to non moderators who currently don't have access to this info and imo it should still be up to the server mods/admins to decide who can or can not see this info

[Zoddo]

These information can be sent only to users/bots with proper permissions. Like GUILD_BAN_* events who are sent only to members with the BAN_MEMBERS permission.

[jhgg]

The kick event will only be decorated with the mod whomst kicked the user if you have audit log perms.

[AEnterprise]

is there any update on this? having a dedicated kick event would allow bots to rely on that instead of having to poll the audit logs every time someone leaves

[cheesycod]

^

[broman]

Bump. Been a few years lads. Hope everybody’s been making it through this stuff alright. Working from home is an absolute pain.

Anyways, this was supposed to ship with audit logs but it never was. Then Jake noted it would be worked on later in 2019. Then 2020 happened, so fair enough on a delay. But it’s 2021 now :) any update?

[broman]

4 years later! Man time flies. Before the world had ever heard of Covid-19, I was told Discord would be working on this “later this year”. Since then we had an entire US presidency, a global pandemic, I proposed to my partner, and now we’re planning a wedding. And despite all of this, sadly there has been no progress.

As fun as it is to get led on, it’s been 7 years now. Can we either implement this feature (that was going to be worked on 6 years ago), or admit that this won’t be happening and finally close it?

[AEnterprise]

there is an audit log event now (requires having audit log perms) you can use as alternative now: https://discord.com/developers/docs/events/gateway-events#guild-audit-log-entry-create

[broman]

I’m aware, it’s been like that for a while. But that’s not what I was told would be coming