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

Route: /guilds/:id/regions #78

Closed
1 task
SamuelScheit opened this issue Feb 4, 2021 · 8 comments
Closed
1 task

Route: /guilds/:id/regions #78

SamuelScheit opened this issue Feb 4, 2021 · 8 comments
Labels
Module: API Route All route issues
Milestone

Comments

@SamuelScheit
Copy link
Member

  • regions
@SamuelScheit SamuelScheit added the Route All route issues label Feb 4, 2021
@SamuelScheit
Copy link
Member Author

You'll no longer need to settle on choosing one server region that your voice channels run on for your whole server. Instead you'll be able to use a different region for each of your voice channels.

But what does this mean for you?
- Each of your voice channels will have a voice region setting. More regions means better call quality because you're not forcing one region for everyone.
- We've also added a new option called "Automatic." By default, all voice channel regions will be set to "Automatic." This means that the region will be automatically determined based on the first person to join an empty voice channel, and the region can change anytime a voice channel becomes completely empty and new person joins it.
- You still have the option to set a specific region if you want though. This option will be moving from Server Settings and is now found in each voice channel settings page.

We recommend using the default region, "Automatic", so you don't need to constantly change voice channel regions based on who is in a voice channel (Let Discord handle that!), but you're always able to make changes under Voice Channel Settings at any time.

Also — because there's a region setting for each voice channel now means that the permissions to manage this have changed. Instead of granting roles the Manage Server permission to change the server region, any roles that have the Manage Channel permission will be able to adjust the voice channel region if needed.

https://support.discord.com/hc/de/articles/360060570993

/channels will also have the option to individual change voice regions

@Stilic
Copy link
Contributor

Stilic commented May 24, 2021

I doing this now!

@Stilic
Copy link
Contributor

Stilic commented May 24, 2021

image
I will check the rtc_region proprety for code this first.

@SamuelScheit
Copy link
Member Author

the thing is, we don't store the rtc_region yet.
You will probably have to wait until we finish the rtc base to do this

@Stilic
Copy link
Contributor

Stilic commented May 24, 2021

He send a PATCH request

@SamuelScheit SamuelScheit assigned Stilic and unassigned xNaCly May 24, 2021
@Stilic
Copy link
Contributor

Stilic commented May 24, 2021

#148

@SamuelScheit SamuelScheit linked a pull request May 24, 2021 that will close this issue
@Stilic
Copy link
Contributor

Stilic commented May 24, 2021

{
	"id": null,
	"type": 2,
	"name": "vocal",
	"position": 0,
	"parent_id": null,
	"bitrate": null,
	"user_limit": 0,
	"rtc_region": null,
	"guild_id": null,
	"permission_overwrites": [],
	"nsfw": false
}

@xNaCly xNaCly changed the title [Route] /guilds/:id/regions /guilds/:id/regions Aug 10, 2021
@xNaCly xNaCly changed the title /guilds/:id/regions Route: /guilds/:id/regions Aug 10, 2021
@xNaCly xNaCly added Module: API and removed Route All route issues labels Aug 12, 2021
SamuelScheit added a commit that referenced this issue Aug 30, 2021
@AlTech98
Copy link
Contributor

AlTech98 commented Sep 4, 2021

Should be closed by commit b59cbdb

@SamuelScheit SamuelScheit added this to the Milestone V2 milestone Sep 19, 2021
@SamuelScheit SamuelScheit modified the milestones: Milestone V2, Discord Core Oct 11, 2021
MaddyUnderStars pushed a commit that referenced this issue Mar 1, 2023
MaddyUnderStars pushed a commit that referenced this issue Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Module: API Route All route issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants