Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Missing VOICE_STATE_UPDATE event for users becoming speakers in a Stage channel #2764

Open
3 tasks done
Fry2412 opened this issue Aug 16, 2023 · 1 comment
Open
3 tasks done
Labels

Comments

@Fry2412
Copy link

Fry2412 commented Aug 16, 2023

Check The Docs

  • I double checked the docs and couldn't find any useful information.

Verify Issue Source

  • I verified the issue was caused by Discord.Net.

Check your intents

  • I double checked that I have the required intents.

Description

Honestly, I don't know if this is an API or Discord.Net issue

Description.

I noticed that the VOICE_STATE_UPDATE event in the Discord.Net package fires correctly when a user enters, leaves or becomes a listener in a Stage channel. However, the event will not fire when a user goes from being a listener to a speaker in the Stage channel.

Steps to Reproduce:

  1. create a stage channel in a Discord server.
  2. connect a user to the Stage channel as a listener.
    Observe that the VOICE_STATE_UPDATE event is triggered.
  3. let the user become the speaker in the stage channel.
  4. observe that the VOICE_STATE_UPDATE event is not triggered.

Expected behavior

The VOICE_STATE_UPDATE event should also fire when a user goes from being a listener to a speaker in the Stage channel. This allows changes in the user`s voice state to be tracked comprehensively and responded to accordingly.

Actual Behavior:

The VOICE_STATE_UPDATE event is not triggered when a user goes from being a listener to a speaker in the Stage channel. This misses an important feature to react appropriately to these changes in voice state.

Additional Context:

This issue impacts applications that use stage channels and need to monitor users' voice state. Adding an event for this situation would improve functionality and allow more accurate tracking of voice state changes.

I am happy to assist in resolving this issue if needed. Thank you very much for your support!

Version

3.11.0

Working Version

No response

Logs

n.a.

Sample

No response

Packages

  • Discord.Net
  • Microsoft.AspNet.SignalR.SelfHost
  • Microsoft.Extensions.Configuration
  • Microsoft.Extensions.Configuration.Json
  • Microsoft.Extensions.DependencyInjection
  • MongoDB.Driver

Environment

  • OS: Windows 11 22H2 22621.1992
  • Architecture: x64
  • SDK: .NET sdk 7.0.101
@Fry2412 Fry2412 added the bug label Aug 16, 2023
@Misha-133
Copy link
Member

Misha-133 commented Aug 16, 2023

@quinchs https://github.com/discord-net/Discord.Net/blob/dev/src/Discord.Net.WebSocket/DiscordSocketClient.cs#L2283-L2306
Should we invoke the UserVoiceStateUpdated even if we also invoke RequestToSpeak or SpeakerAdded/Removed events? There's a bit of inconsistency in current implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants