Skip to content

GitLab

Last edited by Friendliness
Page history

Server Management

Table of Contents

Information

The commands in this section are designed to help you manage your server. They allow you to easily assign or unassign roles from your members, set up temporary voice channels, use a ticketing system, host giveaways and events or even purge channels.

Note: All of the role-related commands require you to have the Administrator permission, alternatively you can also use them if you have one of the admin roles if the command is enabled in the admin commands.

General

These are some general commands you can use to manage your server more easily.

Overview

Command Example Explanation
-kick @users -kick @RudeMember#1234 @GoldSeller#1234 Kicks a user or several users. You can use a Discord ID instead of mentioning the user.
-ban @users -ban @RudeMember#1234 @GoldSeller#1234 You can use a Discord ID instead of mentioning the user.

Kick

This command kicksa user or several users from your server. 1

-kick followed by a username or Discord ID.

Example:

-kick @RudeMember#1234 @GoldSeller#1234

Ban

This command bans a user or several users from your server. 1

-ban followed by usernames or Discord IDs.

Example:

-ban @RudeMember#1234 @GoldSeller#1234

Universal Banlist

This feature provides an easy way to quickly ban known abusers, such as RWT-spam bots, spammers of phishing links and even scammers or hackers in RuneScape. Once enabled, the people on the list will automatically be banned from your server, even in advance. In case you disagree with someone's ban, you can still unban them with the [-uniunban](Commands/Server Management#uniunban) command, to prevent them from being re-banned automatically.

Overview

Command Example Explanation
-unibanlist Sends you a link to the universal banlist, with Discord IDs along with ban reason.
-universalban [mode] -universalban on Allows you to turn on or off the universal ban feature. Possible modes are: on & off
-uniunban [mode] [@users] -uniunban add 123456789 Adds or removes someone from the list of users that should not be banned by the universal banlist feature in your server. Possible modes are: add & remove

Unibanlist

This command sends you a link to the universal banlist, with Discord ID's along with reasons for their ban.

Example:

-unibanlist

Universalban

This command enables or disables the universal banlist in your server.

-universalban followed by the mode, namely on or off.

Example:

-universalban on

Uniunban

If you disagree with a ban or several bans on the universal banlist, yet you'd like to keep the feature enabled, you can use this command to ensure a user won't be automatically banned by the Universal Ban feature.

This could be seen as some "Ignore List" for the Universal Ban feature. When checking who to ban automatically, the bot will ignore the users you added to the UniUnban list. 1

-uniunban followed by add or remove, then followed by a user's ID or several IDs.

Example: -uniunban add 123456789 would prevent the user with the ID of 123456789 from being banned by the universal ban feature.

-uniunban remove 123456789 would then allow the user with the ID of 123456789 to be banned automatically again.

Role Commands

Giving a Role

You can also give a role to one or more members with a simple command. This is done by typing the following: 2

-role give @Role @User1 @User2 @User3 ...

Example:

-role give @Member @Friendliness#1337 @Example#1234

Would give the @Member role to the users: @Friendliness#1337 and @Example#1234.

Taking a Role

Additionally, you can also take away a role from multiple users. 2

-role take @Rolename @User1 @User2 @User3 ...

Information About a Role

This command gives you information, such as the Role ID and the amount of users, about all roles. When used with a specific role it will display who has the role. 2

-roleinfo or -roleinfo @Rolename

Role To Role

This command gives everyone with the first role specified, the other roles you specified. 2

-roletorole @RoleToCheck @RolesToGive...

Example:

-roletorole @Guy @Friend @Buddy

This command would give everyone with the @Guy role, the @Friend and @Buddy roles.

Role From Role

This command takes a role or several roles from everyone with the first role specified. 2

-rolefromrole @RoleToCheck @RolesToRemove...

Example:

-rolefromrole @Guy @Friend @Buddy

This command would remove the @Friend and @Buddy roles from everyone with the @Guy role. I'm not your buddy, friend!

Mass Assigning Roles

This command allows you to assign a role to everyone who doesn't have the role yet. 2

Note: This command has a cooldown of 5 minutes, to prevent hitting rate-limits. It may also be fairly slow but you'll get a confirmation message once it's done.

-massassign @Member would assign the @Member role to all of your server's users.

Mass Removing Roles

This command allows you to unassign a role from everyone who has a role. 2

Note: This command has a cooldown of 5 minutes, to prevent hitting rate-limits. It may also be fairly slow but you'll get a confirmation message once it's done.

-massremove @Member would remove the @Member role from all of your server's users.

Reaction Roles

These are all commands related to the Reaction Roles feature.

Roles Command

The following command will show you all of the available reaction roles in your server.

-roles

Adding Reaction Roles

This command adds a reaction to a message, which your users can click to assign a role to themselves. If they remove their reaction from the message, they will remove the role from themselves again.

Make sure you use an emote the bot is able to see, it can add reactions in the channel where the message is and make sure the bot is listed above any roles it has to assign to users. 3

-react add [Message ID] [@Rolename] [Emote]

Example:

-react add 123456789 @Member :100:

The example above would add a reaction role to the message with the ID 123456789, if a user reacts with 💯, they'll assign the @Member role to themselves. If they remove their reaction, the @Member role will be taken away again.

Removing Reaction Roles

If you've previously set up a reaction role and you'd like to remove it again, you can use the following command. Your users will no longer be able to react to the message to assign or unassign a role to themselves. 3

-react remove [Message ID] [@Role] [Emote]

Example:

-react remove 123456789 @Member :100:

Join Roles

These are roles that will be assigned to your members as soon as they join your server.

Adding Join Roles

Adds a role, or several roles, to the list of roles that should be assigned when a user joins your server. 2

-joinrole on @Role

Example:

-joinrole on @Member @New

The above command would assign the roles @Member and @New to anyone (not bots) who joins the server.

Removing Join Roles

Removes a role, or several roles, from the list of roles that should be assigned when a user joins your server. 2

-joinrole off @Role

Example:

-joinrole off @Member

Trigger Roles

These are roles that automatically unassign another role(s). Picture the following scenario:

You set up the @Unsubscribe role to trigger the removal of the @Subscribed role.

A user with the role @Subscribed wants to unsubscribe, once they receive the @Unsubscribe role, the @Subscribed role will automatically be removed. 2

Adding a Trigger Role

-triggerrole add @TriggerRole @RoleToRemove ...

Example:

-triggerrole add @Unsubscribe @Subscribed @Enlisted

This will make the @Unsubscribe role automatically remove the @Subscribed and the @Enlisted roles.

Removing a Trigger Role

-triggerrole remove @TriggerRole @RoleToRemove

Example:

-triggerrole remove @Unsubscribe @Subscribed

This will stop the @Unsubscribe role from removing the @Subscribed role.

Listing All Trigger Roles

The following command can be used to list the current Trigger Roles and the Roles they remove.

-triggerrole list

Sticky Roles

These are roles that will be reassigned to a member if they leave and rejoin the server. For example, you could make the @Muted role a Sticky Role. If someone tries to get rid of the role by leaving your server and rejoining, the bot will automatically re-assign the role to them.

Enabling Sticky Roles

This will enable the Sticky Roles feature for one or more roles. 2

-stickyroles enable @Rolename ...

Example:

-stickyroles enable @Muted @Silenced

This command would set up the @Muted and the @Silenced roles as Sticky Roles.

Disabling Sticky Roles

This will disable the Sticky Roles feature again.

-stickyroles disable

Clearing All Saved Sticky Roles

This will clear all users of their current sticky roles.

-stickyroles clear

Affiliations

The affiliates feature is designed to showcase partnered and supported servers. It allows you to connect your server to someone else's server and to highlight your cooperation with them.

This means you can make it easy for the members of your server to find out information about your partners, like what their server is all about or how to join their server.

Note: In all of these commands, you can type aff instead of affiliate too.

Enabling Affiliations

This command will enable the Affiliates feature for your server.

-affiliate enable

Note: After enabling the feature, you'll still have to create an Embed for your server, with the -affiliate embed command.

Disabling Affiliations

This command will disable the Affiliates feature for your server again.

-affiliate disable

Creating your Embed

This command allows you to create the basic embed for your server, in here you'll be able to show the name, a description, contact information and the invite URL to your server.

To further edit your embed (with more options!) you can use -affiliate edit, after creating your basic embed.

Example:

-affiliate embed "Title here" "A description" "Contact information" "https://Invite-URL.com"

Posting your Embed

After creating your embed you can preview or post your own embed by using the following command.

-affiliate self

Editing your Embed

Using this command will start a dialogue with the bot to select which of the fields you'd like to edit.

You can also use this to reset a value, by editing it and typing RESET as the value.

Note: Resetting a field won't work for the following fields: Server Name, Server Description, Contact Information, Invite URL.

Example:

-affiliate edit

You can find an example of how this works exactly in the video below.

Linking with other Servers

This initiates a link with another server or several servers. To use this command you'll need another server's ID.

-affiliate link followed by a server's ID or several server IDs.

Example:

-affiliate link 123456 789123

The command above would link your server, with the servers that have the IDs 123456 & 789123.

Finding out the Link Status

The following command allows you to find out which servers you've successfully linked with, which servers you've linked with but haven't linked with your server yet and which servers want to link with your server.

-affiliate links

Link Status Codes:

  • ✅ - means you've both linked with each other.
  • 🕑 - means you're waiting for a server to link with you.
  • ⏺ - means that server asked you to link with them.

Posting a Server's Embed

To post the embed of a server you've linked with, you can use the following command.

-affiliate post followed by a server's ID or several server IDs.

Example:

-affiliate post 123456 789123

The command above would post the embeds for the servers with IDs 123456 & 789123.

Note: To post a server's embed, both servers will need to be linked to each other. That means both servers have to have used the -affiliate link commands. To see the current status of your server links, you can type -affiliate links.

Posting all Embeds

This command will post all embeds of servers you're linked with.

Note: If you've manually removed some embeds, or some are missing, and you want to re-post them, you'll have to type -affiliate unpost all and then use this command again to post all of the embeds.

-affiliate post all

Unposting a Server's Embed

You can unpost a specific server's embed by using this command.

-affiliate unpost followed by a server ID or several server IDs.

Example:

-affiliate unpost 123456 789123

This would unpost the embeds of the servers with the IDs 123456 & 789123.

Unposting all Embeds

You can remove all embeds that have currently been posted by using the following command.

-affiliate post all

Ticketing

The bot also has a Ticketing feature built in, with various settings to help you customize it the way you want to.

You can create a button or several buttons, which can be clicked by users to create a ticket. When someone clicks the button, a channel will be created and the configured role(s) will be mentioned to alert them a new ticket is available.

Once a ticket is created, a new message will also appear in the logchannel which shows who created the ticket, when they did so and what the channel is.

The ticket can be closed by clicking the Close Ticket button. This will remove the user who created the ticket from their ticket, while still keeping it opened for staff to see. When a ticket is closed, a message will also be sent to the logchannel to show who closed the ticket.

The ticket can be removed completely by clicking the Delete Ticket button. This will create a transcript of all of the messages that were sent in the ticket, and pass it on to the logchannel along with who deleted the ticket.

The ability to customise the tickets is based on your Patreon tier. All of the limitations are also per server, for example if you have a limit of 3 buttons, this means you can create 3 buttons in every server, given you have the correct permissions.

Tier Ability
Free create a singular button
1 modify the text & title of the button you created
2 select a standard name for the channels that are created, in the format of {text-here}-{username} eg: #cool-ticket-username1234
3 spawn up to 3 customisable buttons, the message a user receives in the ticket is now also customisable
4 configure which button sends tickets to which category & which log channel
5 create infinite customisable buttons
6 custom ideas could be implemented

Overview

These are all of the ticketing commands, more in-depth info can be found in their respective sections.

Command Example Explanation
ticketing enable @role(s) -ticketing enable @Admin @Mods Enables the ticketing feature and grants the specified role(s) the ability to see and manage tickets.
-ticketing disable -ticketing disable Disables the ticketing feature again.
-ticketing button -ticketing button Creates a button your users can click to open up a ticket. These buttons can each be customized with their own settings.
-ticketing deletebuttons [Optional Button IDs] -ticketing deletebuttons 123456789 Deletes the specified ticket buttons. If you don't provide any button ID, all buttons will be deleted.
-ticketing buttons -ticketing buttons Shows you all of your buttons, along with their settings and where to find them.
-ticketing channel [Button ID] [Text] -ticketing channel 123456789 order Changes the name of channels created through a button to start with the specified text. In this example #order- followed by the user's username.
-ticketing message [Button ID] [Message] `-ticketing message 123456789 Thank you for creating a ticket! Will edit the message a new user sees when they created a ticket.
-ticketing category [Button ID] [Category ID] -ticketing category 123456789 987654321 Configures which category tickets should be sent to when this button is clicked.
-ticketing roles [Button ID] [@Role(s) here] -ticketing roles 123456789 @Admin @Mods This changes which roles can manage tickets created with this button.
-ticketing logchannel [Button ID] [#channel] -ticketing logchannel 123456789 #tickets-log Sets the specified channel up as the logchannel for tickets created with this button.

Enabling Ticketing

This command will enable the Ticketing feature and creates a Ticketing category and a #tickets-log channel. The role(s) you use as argument as the role(s) that can manage the tickets.

-ticketing enable followed by a role(s).

Example:

-ticketing enable @Admin @Mods

Disabling Ticketing

This command will disable the Ticketing feature again, so no further tickets can be created.

Note: You can still close and delete tickets that were currently opened.

-ticketing disable

Creating a Ticket Button

To actually use the ticketing feature, you'll have to create a button for your users to click. These buttons can be configured in many ways[^5] and will create a ticket for the interacting user.

afbeelding

-ticketing button will create a button for you to customise

Note:

  • Free users can spawn 1 button.
  • As Tier 3 Patreon or Insane Patreon, you can spawn up to 3 customisable buttons.
  • As a Tier 5 Patreon or Mega Patreon you can spawn an infinite amount of customisable buttons.

Deleting Ticket Buttons

You can use this command to delete specific ticketing buttons or all of them at once.

-ticketing deletebuttons will delete all of your buttons (after asking for confirmation).

-ticketing deletebuttons followed by the ID of button(s), will delete several buttons with the matching ID.

Displaying Current Ticket Buttons

This command shows you all of your currently created buttons, along with their settings.

Discord_4WZDKdbhM0

-ticketing buttons

Changing the text of a Button

To change the text in the embed of a ticket button, you can use this command.

-ticketing buttontext followed by a Button ID and your desired text, will set the text on the desired button to what you'd like.

afbeelding

Note: This command requires a Patreon tier of 1, the Friendly Patreon package.

Changing the standard name for created channels

With this command, you can configure what the prefix for your ticket channels should be.

An example: if you set this to coolticket, a new ticket channel that is created will be coolticket- followed by the user's username.

-ticketing channel [Button ID] [Text] will set the channel names of created tickets to the text you picked.

Example:

-ticketing channel 123456789 coolticket A ticket, created through this button, by me would then be called: #coolticket-friendliness1337

Note: To use this command you need a Patreon tier of 2, the Spicy Patreon package.

Modifying the message a user sees when they create a ticket

You can change the default message a user is greeted by in their ticket channel when they create a ticket.

afbeelding

-ticketing message [Button ID] [Message] will edit the message a new user sees when they created a ticket.

Example:

-ticketing message 123456789 Thank you for creating a ticket. The message sent in a ticket created with this button would be: Thank you for creating a ticket.

Note: This command requires a Patreon tier of 3, the Insane Patreon package.

Changing the Category tickets are created in

This command changes what category a new ticket, created by a button, will appear in.

-ticketing category [Button ID] [Category ID]

Example:

-ticketing category 123456789 987654321 this would make new tickets, created with the button with the ID of 123456789, be created in the category with the ID of 987654321

Changing which roles can access tickets

If you want to configure which roles can access which tickets, you can do this by changing the button's roles.

To do this, use the following command:

-ticketing roles [Button ID] [@Role(s) here]

Example:

-ticketing roles 123456789 @Admin @Mods

This would change who can access the channels, created with this button, to users with the @Admin & @Mods roles.

Note: To use this command, you need to be a Patreon tier of 4, which is the Super Patreon package.

Changing the logchannel for a button

If you want to separate where the ticket logs of each button go, you can use this command.

-ticketing logchannel [Button ID] [#channel]

Example:

-ticketing logchannel 123456789 #new-log-channel

The logs of a ticket created with this button will now be sent to #new-log-channel.

Note: To use this command, you need to be a Patreon tier of 4, which is the Super Patreon package.

Legacy Ticketing

NOTE: You can no longer enable this feature or create new tickets with it, but it will remain enabled temporarily for those who had it enabled in the past, so legacy tickets can still be handled.

The bot also has a Ticketing feature built in. This allows you to pick a role for the people who are going to be handling all of the tickets.

When someone uses the -ticket command to send in a ticket, a channel will be created and that role will be mentioned. A copy of the messages in the ticket's channel will be sent to a #tickets-log channel too.

To resolve the ticket, someone with the role to handle tickets can click the ✅ emote on the ticket. To remove the ticket, they can click on the ❌ emote on the ticket.

Note: People with the Administrator permission in your server will always be able to see and handle your tickets.

Enabling Ticketing

This command will enable the Ticketing feature and creates a #tickets-log channel. The role(s) you use as argument as the role(s) that can handle the tickets.

-ticketenable @RoleName ...

Example:

-ticketenable @Administrator @Moderator

This would enable the people with the @Administrator and @Moderator roles to handle your tickets.

Disabling Ticketing

-ticketdisable

Sending in a Ticket

This is what your users can use to send in tickets. It will create a private channel and mention the roles you set up to be able to handle your tickets.

Anything sent in this channel will also be forwarded to a #tickets-log channel. 2

-ticket, optionally followed by a message.

Purging

These commands allow you to delete a certain amount of messages in a channel or a certain amount of message from a specific user in a channel.

Note: The maximum amount of messages you can purge at once is 100.

Purge

This removes a certain amount of messages in a channel.

-purge followed by an amount.

Purge From User

This command removes a certain amount of messages in a channel, from a specific user. 1

-purgefrom @Username [Amount]

Example:

-purgefrom @Friendliness#1337 42

Events

The Events feature allows you to enable a role, for example the @EventPlanner role, to create and post events. Creating an event will make a temporary role with the name of the event.

Members of your server can enlist to get mentioned 30 minutes before the event starts and at the start of the event. They can do so by reacting to a posted event with the Notification emote.

Note: All events will use the UTC timezone.

Enabling The Events Feature

This command will allow the specified role(s) to create, host, delete and update the events hosted in your server.

-eventsenable @Role ...

Example:

-eventsenable @Moderator @EventPlanner

This would allow people with the @Moderator or @EventPlanner role to manage your events.

Note: After enabling the events feature, you'll have to pick a channel for your event reminders to be sent to. Information about how to do so is listed in the following section.

Setting up an Events Reminder Channel

This is the channel the reminders for your events, 30 minutes before the event and at the start of the event, will be sent to.

-eventschannel #channelname

Disabling The Events Feature

-eventsdisable

Creating an Event

After enabling the events feature and selecting a channel for reminders to be sent to, the roles you specified will be able to create an event using the following command. Users will automatically be reminded of your event both 30 minutes before and at the start of the event.

Note: When picking a time for your event, make sure you use UTC time (RuneScape's gametime)

The following command will start a dialogue with the bot, asking you for details of the event:

-event

Editing an Event

A created event can always be edited afterwards, this can be done by using the following command. Editing the name of an event will also modify the temporary role that was created when the event was created. 4

-editevent followed by the event ID.

Canceling an Event

It's also possible to cancel an event, this will also remove the temporary role that was created when the event was created. 4

-cancelevent followed by the event ID.

Posting a Singular Event

You can post a single event by using this command, if you'd like to post all of your current events, you can use the -events command instead. 4

-postevent followed by the event ID.

Posting All Events

All events can be posted, chronologically, by using this command. Users can then react to the posted messages with the Notification emote.

Doing so means they'll be notified 30 minutes before the event starts and right at the start of the event they signed up for.

-events

Note: Only the last posted events will allow users to sign up for the reminders.

Posting All Events - Compact (No Signups!)

This works the same way as the -events feature, the differences are: - This is a more compact way of displaying the events - Users won't be able to sign up with the Notification emote.

-postallevents

Additional Events Role

This allows you to pick a role that should always be mentioned at the start of your event, alongside the temporary role that was created for your event.

For example the @Events role, for people with an interest in all events.

-eventsrole set @Rolename

Example:

-eventsrole set @Events

Giveaways

This feature allows you to set up giveaways. After setting up a giveaway with the dialogue, a message will be posted in the channel you picked. A winner will then be drawn when the giveaway expires, from everyone who reacted with 🎉. If that emote can't be found, it'll default to the first reaction on the giveaway mesage.

By default only users with the Administrator permission will be able to host giveaways, you can also set a role for users to be able to create a giveaway. This can be found in this section.

Hosting a Giveaway

The following command will start a little dialogue with the bot. You'll be asked what the title of the giveaway should be, where it should be posted and when the giveaway should end.

Note: These use the UTC timezone.

-giveaway

Hosting a Giveaway - No Dialogue

This command allows you to set up a giveaway, without using the dialogue.

-fastgiveaway "Title Here" #Channel "Date Here" [Amount of Winners]

Example:

-fastgiveaway "Christmas Giveaway" #giveaway "2020-12-24 23:00" 2

The command above would create a giveaway with title: Christmas Giveaway, it'll be hosted in the #giveaway channel on the 24th of December, 2020, at 11PM and there'll be 2 winners.

Setting A Giveaway Role

This allows you to pick a role or several roles that are allowed to host giveaways in your server. For example if I want to allow people with the @GiveawayHost role to set up their own giveaways.

-giveawayrole set @Rolename ...

Example:

-giveawayrole set @GiveawayHost @Moderator

This would allow anyone with either the @GiveawayHost role or the @Moderator role to host giveaways.

Removing a Giveaway Role

This command will remove the currently set giveaway roles.

-giveawayrole unset

Rerolling a Winner

This command lets you reroll the winner of a giveaway.

-rerollwinner followed by the ID of the ID of the giveaway.

Getting a Random Winner

This command allows you to get a random winner from any message on which people have reacted.

-randomwinner followed by the ID of the message.

Cancel a Giveaway

-cancelgiveaway followed by the ID of the giveaway.

Temporary Voice Channels

This feature allows users to set up their own temporary voice channels.

Once this feature is enabled, a user can join the voice channel with the name: Join me to create a temporary voice channel!. The name of this channel can be changed without any issues, the channel can also be moved to another category.

By modifying who can see / connect to the Join my to create a temporary voice channel! channel, you can also limit who is able to create temporary voice channels.

Important: The category Temporary Channels should not be removed. If it is removed, the feature will no longer work. If the category is empty, it will not be visible to anyone without the Administrator permission.

These channels are hidden by default, unless configured otherwise in the settings, and allow the user who created them to make the channel visible, allow specific users or roles to see and join them and manage all other permissions of the channel.

Note: Anyone with the Administrator permission will still be able to see and manage hidden voice channels.

Enabling Temporary Voice Channels

-tempvoice enable

Disabling Temporary Voice Channels

-tempvoice disable

Displaying Temporary Voice Settings

This command will give you an overview of all of the current settings, such as:

  • Should the channels be hidden by default?
  • Should users be able to manage their channels?
  • Should users be able to use commands to manage their channels?
  • Is there a default name for the channels?
  • Is there a channel logs should be sent to?
  • Are there any roles that should be able to manage these channels? (Eg: Moderators)

Modifiying Temporary Voice Settings

To get an overview of all of the available settings, you can type -tempvoice settings. If you'd like to see what all of the available options are for modifying settings, type -tempvoice available.

Visibility

This setting allows you to modify whether all channels should be hidden by default or not.

-tempvoice hide off would make channels no longer hidden by default. -tempvoice hide on would make channels hidden by default again.

Note: If this setting is active, channels can no longer be hidden by users.

Command Usage

This setting allows you to choose whether users can use the temporary voice commands or not.

-tempvoice commands off would disable the use of commands. -tempvoice commands on would enable the use of commands.

Note: If commands are disabled in your server, users won't be sent a message upon joining the channel.

Channel Management

This settings allows you to choose whether your users can manage their own personal channels or not.

-tempvoice manage off would disable the management of the channels. -tempvoice manage off would enable the management of the channels.

Note: If users decide to manage their channels, your Manager Roles will still be able to

Manager Roles

This settings allows you to select a role or several roles that should be able to manage these temporary voice channels.

-tempvoice role @Role1 @Role2 ...

Example: -tempvoice role @Admins @Mods will give Admin & Mods the ability to manage these channels.

To remove the Manager Roles, use the following command:

-tempvoice role None

Log Channel

This setting allows you to select a channel for logs of channel creation / deletion to be sent to.

-tempvoice log #channel would send chat logs to #channel

To stop sending logs to a channel, use the following command:

-tempvoice log None

Temporary Voice Commands

The following commands are only available while you're in a temporary voice channel you created. You can use these in a channel or just send the bot a DM.

Hiding a Temporary Channel

This command hides your temporary channel, so it's hidden from everyone except for the people who you explicitly gave access and anyone with the Administrator permission or one of the Manager Roles.

Your temporary channel is hidden by default when it's created, unless configured otherwise by your server administrator.

-vchide

Note: If anyone joined your channel while it was visible they won't be kicked out, however if they leave they won't be able to re-join it.

Showing a Temporary Channel

This command opens up your temporary channel, everyone can join and see the channel.

-vcshow

Granting Access to your Temporary Channel

This command adds a specific user or role to the temporary channel. 1

-vcadd followed by a role or username.

Example:

-vcadd @Staff

This would give everyone with the @Staff role permission to join the channel.

Removing Access from your Temporary Channel

Removes someone's access from the temporary channel. 1

-vcremove followed by a role or username.

Example:

-vcremove @Staff

This would remove access to your temporary channel from everyone with the @Staff permission.

Sizing your Temporary Channel

Changes the size of your temporary channel.

-vcsize 10 would change the maximum size of your channel to 10

-vcsize 0 would remove the maximum size limit.

Disabling Bot Temporary Voice PM

This command prevents the bot from messaging you a list of commands when you create a temporary voice channel.

-tempvoicepm off would turn the messages off.

-tempvoicepm on will enable the messaging again.

Note: If commands are disabled in your server, users won't be sent a message upon joining the channel.

  1. Note: You can also use a user's ID instead of mentioning them. ↩
  2. Note: You can also use a Role ID or name of a Role instead of mentioning the role. It's also possible to use the ID of users instead of mentioning them. ↩
  3. Note: You can also use a link to a message instead of a Message ID and the ID or name of a Role instead of mentioning the role. ↩
  4. Note: The event ID can be found when creating an event or after an event has been posted. ↩