So a little query that would make life a lot easier and reduce the calls made to the API.
When a user quits the guild, or is kicked from the guild, the username of the user that has been removed/left the guild does not show up in the logs at all. The only way to get an idea of who it might have been is to go and check the v2/guild/:id/members list and then compare to a previously cached version of that list. If you’re dealing with a rogue officer that’s gone off the deep end, this can be a tedious problem to manage.
If a user /gquits the guild, then there is simply an event that looks like the following.
[{"id":xxx67,"time":"2016-xx-xxT12:55:04.096Z","type":"kick"}]
If the user is kicked from the guild, then the event does include the "kicked_by" property with the name of the officer or person that kicked them.
[{"id":xxx63,"time":"2016-xx-xxT14:40:08.081Z","type":"kick","kicked_by":"xxxxxxxx.xxxx"}]
If you later invite a person that was kicked/gquit then you can see both the "user" and "kicked_by" properties without issue.
[{"id":xx77,"time":"2016-xx-xxT22:55:11.096Z","type":"kick","user":"xxxxxxxx.xxxx","kicked_by":"xxxxxxxx.xxxx"}]
Is there a way we can get the full details of the user and kicked_by properties for all instances of this event? It’d make managing a userlist a lot easier. Wouldn’t have to go pull the members list just to see who gquit/got kicked. Just update the already-cached members list locally.
kinthiri.9604 – Co-leader of Anvils Hammers [HARD] – Stormbluff Isle