Document set voice channel status

[MinnDevelopment]

Permission:

Usage:

[advaith1]

the name of this PR is outdated

[advaith1]

Suggested change

	| status? | ?string | the voice channel status (0-500 characters) |
	| status? | ?string | the voice channel status (0-500 characters), only included in the Guild Create event |

[Puncher1]

Is there a reason for this?

[Earlopain]

Can documentation for the status field in the auditlog options be added as well?

[advaith1]

the Channel Update event description should be updated to say that it doesn't trigger for status updates like last_message_id

[MazeXP]

Can the status field added to the Modify Channel API call added as well

[sebm253]

Can the status field added to the Modify Channel API call added as well

a different endpoint is used for changing voice status and a PR for this already exists: #6400

[sdanialraza]

Can you update the documentation for the list of intents as well with the intent required intent for this event?

[Cynosphere]

It seems to also emit CHANNEL_TOPIC_UPDATE gateway event, which doesn't seem to be documented either.

Only difference is topic instead of status and the fact that this events have been existing for longer (first instance of it my bot saw was on July 11th). They were only ever setting it to null (stage channel related maybe?) and do not fire on normal channel topic updates.

[advaith1]

that is the old name, it was replaced

[sdanialraza]

Is this supposed to be id or channel_id?

[Misha-133]

it's just id
example payload:

<- Dispatch [VOICE_CHANNEL_STATUS_UPDATE] : 
{
  "status": "123",
  "id": "111...",
  "guild_id": "490..."
}

[sdanialraza]

Alright, thank you!

[sdanialraza]

• Document set voice channel status #6398 (comment)

Can you update the documentation for the list of intents as well with the intent required intent for this event?

@MinnDevelopment Could you do this please?

[Puncher1]

Looks like that there's a bug with the Discord UI. After editing the channel (e.g. the channel's name) the status gets reset (Set a channel status) but the GUILD_CREATE event still has the status in the payload (see below). I assume that it's a UI bug and not a API bug because why should the status be reset if the channel was edited?

{
    ...
    "status": "test",
    "name": "voice-111",
    ...
}

[cobaltt7]

Hey, is there any way to get this merged soon?

[bogomazov]

Also interested

[xXM0d3reXx]

any information when official merge? waiting for over half a year now

[advaith1]

The fates of hang status and vc status are not decided yet, since hang status has a partial rollout and may fully replace vc status, so we won't be documenting vc status until we are confident it's sticking around.