Bots cannot edit guild features

[AlmostSuspense]

Description

Trying to edit a guild's features array will return a 403 error with the "This feature has been temporarily disabled" error message. I've been experiencing this issue for a while, hence the report now because I feel like it's not so temporary anymore and given that there's been no announcement or documentation update, I thought it'd be fair to at least ask about it in an issue

Steps to Reproduce

• Send a PATCH request to /guilds/:id with a bot that optionally has admin permissions if you're trying to add the COMMUNITY flag like I did:

curl --location --request PATCH 'https://discord.com/api/v10/guilds/{guildId}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bot {token}' \
--data '{
    "features": ["COMMUNITY"]
}'

Expected Behavior

Either the COMMUNITY flag being enabled normally, or a notice in the documentation/DDevs that this is no longer possible; since this endpoint has been unavailable for quite some time now

Current Behavior

Using the above request will return the following error:

{
    message: 'This feature has been temporarily disabled',
    code: 40006
}

Client and System Information

Getting this error both with discord.js and Postman; given the nature of the error, it's fair to say the used library is not relevant

[advaith1]

this is based on the data you send btw - if you send the same data as the client does, or you are doing a different change to the features list, then it works fine

the error message is unhelpful tho, it should be fixed

[AlmostSuspense]

I'm not sure what you mean by "doing a different change"? solved via discord, apparently other fields need to be sent as well:

{
  "features": ["COMMUNITY"],
  "verification_level": 1,
  "default_message_notifications": 1,
  "explicit_content_filter": 2,
  "rules_channel_id": "1",
  "public_updates_channel_id": "1"
}

[onerandomusername]

IMO this is still a bug because the error message doesn't actually hint at the solution.

[AlmostSuspense]

yeah i made another issue with a better wording regarding the misleading error

• 6015