Add `INVITES_DISABLED` guild feature

[advaith1]

[onerandomusername]

Is there any documentation on how this behavior will work when this feature is enabled?

[Jupith]

You'll still be able to fetch all invites, aswell as create them, just users trying to join via them will get an error.

[wasdennnoch]

Does that also affect joining via discovery and lurking (or possibly even OAuth guilds.join) or is it purely restricted to invites?

[Jupith]

It effects discovery yes, not sure about the scope.

[MinnDevelopment]

Is it intentional that there is no audit log entry for disabling invites?

[shaydewael]

I believe this is just an experiment right now

[advaith1]

it is out to all community servers as of today

[onerandomusername]

The internal API validation for setting this feature is a bit incorrect, and I've just created 6 public update webhooks when setting BOTH community and invites_disabled features in the same api request. The backend creates the public update webhook but errors with a 403 on the invites_disabled feature as the community feature wasn't initally set. This in turn doesn't remove the public_updates webhook but doesn't save it as the webhook, either. Then another webhook is created on the next request (while debugging) and now I have six phantom webhooks.

Additionally, this feature can be set when disabling community which maybe be an additional bug which may or may not be related.

I'll create an issue for this since that would likely be easier to track.

[onerandomusername]

Is it known if this has fully rolled out yet?

[shaydewael]

the feature is still being refined, but we should be good to publish the documentation at this point