Configuration Guide

As a server manager, you have many commands at your disposal to modify AutoRoom to work exactly the way you want.

Create

#

As outlined in the getting started documentation , the /create command creates a new AutoRoom Source on an existing voice channel. When a user joins this voice channel (AutoRoom Source), a new voice channel (AutoRoom) will be created in the destination category, and the user will be moved into it. There, they are free to use and modify their AutoRoom as they see fit.

Premium servers are allowed to have an unlimited number of AutoRoom Sources, whereas non-premium servers are limited to just one.

Remove

#

This is the opposite of create. Use /remove to remove an AutoRoom Source, turning it back into a normal voice channel.

Modify

#

Access

#

The /modify access command allows you to choose what access is used by default for new AutoRooms. The options are as follows:

The AutoRoom Owner (the user who creates the AutoRoom by joining the AutoRoom Source) will be able to switch access modes at any time, unless you disable that feature .

Category

#

The /modify category command allows you to change the category that the AutoRoom Source creates it’s AutoRooms in.

Features

#

AutoRooms have a set of features that control how users can interact or modify them. For non-premium servers, this is a subset of features and cannot be changed. For premium servers, you have full control over what features are enabled or disabled. Below are the current features, whether or not they are allowed on non-premium servers, and if they are on by default in premium servers.

Name

#

For premium servers, the /modify name command changes the channel name that AutoRooms start with. By default this is {{member.name}}'s Room, which would display like “PhasecoreX’s Room” for the user PhasecoreX. This setting supports templating, which you can learn more about by clicking here . Templates allow for the name to be dynamic based on the AutoRoom Owner or other variables.

Message

#

For premium servers, the /modify message command sets a message that will be sent to the AutoRoom when it is first created. Like the AutoRoom name, this message also supports templating, which allows for dynamic messages based on the AutoRoom Owner or other variables. You can learn more about the template system by clicking here .

Roles

#

By default, the AutoRoom Owner can allow or deny any user or role access to their AutoRoom. If you have certain roles that you don’t want to ever be denied (admin or mod role, for example), you can use the /modify roles command to set that up. Do note, this is not for member roles. Info about member roles can be found further down

Reset

#

If you want to clear out the custom name, custom message, or allowed roles set on an AutoRoom Source, you can use the /reset name, /reset message, and /reset roles commands.

Control Panel

#

For premium servers, by default , a control panel will be created in every AutoRoom that is created. If you want to have a dedicated text channel for the controls, the /cpanel command allows you to create a long-lived AutoRoom Control Panel in a given text channel.

List

#

The /list command will show you all of your AutoRoom Sources, along with their current settings and whether or not there are any setup issues with them. You can also supply an argument to the command to view info on a specific AutoRoom Source.

Member Role

#

Some servers utilize a member role to keep track of and differentiate new users from trusted users. A member role is a base role that all users have on a server, usually granted after some sort of vetting process. Support for member roles should be automatic, assuming you deny (at minimum) the connect permission on the everyone role and allow it for the chosen member role. AutoRoom will detect the lowest role that can connect to an AutoRoom Source and, assuming it isn’t the everyone role, will use that as the member role for all AutoRooms it creates. When an AutoRoom Owner switches access modes or modifies access, the member role will always be taken into account, which prevents users without the member role from being able to join AutoRooms. On member role servers, AutoRoom Owners won’t be able to allow the everyone role into their AutoRooms.

Use the /list command to verify that the AutoRoom Source is detecting your member role properly. If it isn’t, be sure that the everyone role is disallowed the connect permission, and your member role is allowed.

Privileged Roles Instead Of Member Roles

#

The only gotcha to this automatic member role system is when you want to have an AutoRoom Source that only certain privileged roles are allowed to join (VIP users for example). If you deny the connect permission for the everyone role and allow it for the privileged role, it will be treated as a member role (since it’s the exact same scenario as described above ). If you want only those privileged users to join an AutoRoom Source to make an AutoRoom, but then everyone is allowed to connect to their created AutoRooms, you will have to ALLOW the connect permission for the everyone role on the AutoRoom Source, but DENY the view channel permission.

Here’s a table listing permissions on the AutoRoom Source that hopefully explains a bit better:

Basically, there are two ways to prevent a user/role from connecting to a channel: connect permission and view permission. AutoRoom ONLY looks at the connect permission to determine member roles. Use the view permission for hiding channels in this scenario.

Permissions

#

When an AutoRoom Source creates an AutoRoom, it will set certain required permissions on the AutoRoom in order to work properly. If you want any additional permissions on the AutoRoom, you will need to set them on the AutoRoom Source, as well as setting that permission as “allow” for the AutoRoom app either in the server or on the destination category.

For example, if you allow creating invites in the server, but want to prevent creating invites for AutoRooms, you would have to add the “deny” Create Invite permission to the everyone role on the AutoRoom Source, and then add the “allow” Create Invite permission to the AutoRoom app role in the server, or in the destination category.

Other Settings

#

Along with the permissions mentioned above, when an AutoRoom Source creates an AutoRoom, it will copy some of it’s settings to the AutoRoom. For premium servers, all of the following will be copied. For non-premium servers, only the user limit is copied over. Bitrate and Age-Restriction flag will be the Discord default for new voice channels.