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

Voice Channel Region Incorrectly Reroutes When Stage Channel Exists in Community Server #7189

Open
ferrenza opened this issue Oct 1, 2024 · 0 comments
Labels
bug synced Synced to internal tracker

Comments

@ferrenza
Copy link

ferrenza commented Oct 1, 2024

Description

When a guild is set as a community server and has at least one stage channel, changing the voice region to certain locations results in the voice channel being rerouted to different regions. This issue occurs with the following regions:

hongkong → rerouted to Singapore
india → rerouted to Singapore
sydney → rerouted to US-West
south-korea → rerouted to Japan

However, when the stage channel is removed or doesn't exist in the guild, the voice region functions as expected.

Steps to Reproduce

Steps to Reproduce:

  1. Create a community server guild.
  2. Create 1 voice channel
  3. Add at least one stage channel.
  4. Set the voice channel region to Hong Kong, India, Sydney, (south-korea manually by postman)
  5. Observe that the voice channel region reroutes to different regions as listed above.

Expected Behavior

The voice channel should stay in the selected region (Hong Kong, India, Sydney, or South Korea) regardless of the presence of a stage channel in the guild.

Current Behavior

When a stage channel exists in a community server guild, setting the voice region to the regions mentioned results in rerouting to different regions.

Screenshots/Videos

image
image

Client and System Information

stable 331573 (1886297) Host 1.0.9164 x64 (52826) Build Override: N/A Windows 10 64-bit (10.0.19045)

@ferrenza ferrenza added the bug label Oct 1, 2024
@lmle lmle added the synced Synced to internal tracker label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug synced Synced to internal tracker
Projects
None yet
Development

No branches or pull requests

2 participants