A proper way of knowing why GUILD_CREATE was fired

[izxxr]

Currently, there is no "convenient" and documented way of determining why a GUILD_CREATE event was dispatched. As the documentation states, it is dispatched when:

• Initially loading guilds when connecting to gateway.
• Client joining a new guild.
• An unavailable guild becoming available to client.

However there is no way of properly differentiating between these cases and why a GUILD_CREATE event is fired. There is an unavailable field on guild object that shows different behaviour in GUILD_CREATE events that can potentially be used for differentiating these cases but this behaviour is undocumented and not really convenient according to #4518.

There should either be a proper note about unavailable key's behaviour just like GUILD_DELETE's documentation or another convenient way for determining the reason of GUILD_CREATE dispatch.

Since the most common use case is to distinguish the occurrence of GUILD_CREATE event on new guild join, One solution is, Similar to THREAD_CREATE event, there could be an additional newly_joined field in GUILD_CREATE event that is true when bot is joining a new guild.

[devsnek]

expected guilds are listed in the READY event (with unavailable:true) iirc, before they are dispatched as full GUILD_CREATEs as they get connected to your session, so I think you can differentiate with that? any GUILD_CREATEs you get that aren't part of the initial list are new joins, as of that session anyway. if you wanted to handle joins that happened while you were offline for some reason, you could compare your member joined_at timestamp i think.