[Feature Request] Pass along member_count on GUILD_MEMBER_ADD and GUILD_MEMBER_REMOVE

[cryptiklemur]

Not sure of the technical implications here, but adding member_count to these events would help to encourage stateless bots.

My particular use-case: DiscordServers needs member counts. We currently have to keep track of every servers member count and update based on these events. Would much rather stop tracking every server and just update the count when the event comes in.

[cryptiklemur]

Something to add, with the potential update coming out that will restrict bots that use the guild members events to 100 guilds, large bots (specifically server list bots) will be unable to reliably track the number of members in a guild unless verified. I don't care about the member in these events, I just want a reliable count when it changes. It would be nice to get a different event for that?

[apple502j]

But aren't these events not dispatched for those bots?

[night]

We most likely would not add a count to these events, as they are related solely to the member object (not the guild). We do return member count in guild responses in some places (like guild ready or invites), so perhaps a feature request you could make would be related to a new event which gives you updates of that value or a way to request that value in the response via API.

[cryptiklemur]

I definitely don't want to request that value via an API call. That's monumentally resource-intensive for both parties. Also seems like it would be resource-intensive to ask for a new event type, but that would be the desired solution on my end (less privacy concerns, less bandwidth, etc). Will open a new issue.

[Skillz4Killz]

Why not just emit GUILD_UPDATE instead of making a new event for it?