Skip to main content

​
Introduction

jar has a variety of commands that you can use to configure entire commands and modules. You can enable or disable commands and modules, as well as restrict them to specific roles.

​
Disabling commands

With the disablecommand command, you can disable a command for a specific user or channel. This means that the command will no longer be available to use by that user or channel you specified.
Only the server owner can use the command that is bound to be disabled.
You can use the alias dcmd instead of disablecommand, to make the command easier to type.
To disable a command, use the disablecommand command, followed by the user or channel you’d like to disable it for & the command you’d like to disable. 
disablecommand <user or channel> <command>

,,disablecommand @jaradc purge
You should see a message confirming that the command has been disabled.

​
Disabling commands for the whole server

You can also disable a command for the whole server by using the disablecommand all command. This means that the command will no longer be available to use by anyone in your server, only the server owner. 
disablecommand all <command>

,,disablecommand all purge
You should see a message confirming that the command has been disabled for the whole server.

​
Enabling commands

With the enablecommand command, you can re-enable a command for a specific user or channel. This means that the command will be available again to use by that user or channel you specified.
You can use the alias ecmd instead of enablecommand, to make the command easier to type.
To enable a command, use the enablecommand command, followed by the user or channel you’d like to enable it for & the command you’d like to enable. 
enablecommand <user or channel> <command>

,,enablecommand @jaradc purge
You should see a message confirming that the command has been enabled.

​
Enabling commands for the whole server

You can also enable a command for the whole server by using the enablecommand all command. This means that the command will be available again to use by everyone in your server. 
enablecommand all <command>

,,enablecommand all purge

​
Disabling modules

With the disablemodule command, you can disable a module for a specific channel. This means commands that belong to the module will no longer be available to use by the channel you specified.
Only the server owner can use the module that is bound to be disabled.
You can use the alias dmod instead of disablemodule, to make the command easier to type.
Make sure you use the correct case for the module name, as it is case-sensitive. (e.g. Moderation not moderation)
To disable a module, use the disablemodule command, followed by the channel you’d like to disable it for & the module you’d like to disable. 
disablemodule <channel> <module>

,,disablemodule @jaradc Moderation
You should see a message confirming that the module has been disabled.

​
Disabling modules for the whole server

You can also disable a module for the whole server by using the disablemodule all command. This means that the module will no longer be available to use by anyone in your server, only the server owner.
Make sure you use the correct case for the module name, as it is case-sensitive. (e.g. Moderation not moderation)
disablemodule all <module>

,,disablemodule all Moderation
You should see a message confirming that the module has been disabled for the whole server.

​
Enabling modules

With the enablemodule command, you can re-enable a module for a specific channel. This means that the module will be available again to use by that channel you specified.
You can use the alias emod instead of enablemodule, to make the command easier to type.
Make sure you use the correct case for the module name, as it is case-sensitive. (e.g. Moderation not moderation)
To enable a module, use the enablemodule command, followed by the channel you’d like to enable it for & the module you’d like to enable. 
enablemodule <channel> <module>

,,enablemodule @jaradc Moderation
You should see a message confirming that the module has been enabled.

​
Enabling modules for the whole server

You can also enable a module for the whole server by using the enablemodule all command. This means that the module will be available again to use by everyone in your server.
You can use the alias emod instead of enablemodule, to make the command easier to type.
Make sure you use the correct case for the module name, as it is case-sensitive. (e.g. Moderation not moderation)
enablemodule all <module>

,,enablemodule all Moderation
You should see a message confirming that the module has been enabled for the whole server.

​
Difference between restrictcommand and restrictcommand reverse

You might be wondering how the restrictcommand command differs from restrictcommand reverse.
  • The restrictcommand command restricts a command to specific roles:
    • If users have the specified role, they can use the command.
  • The restrictcommand reverse command blocks a command for specific roles:
    • If users have the specified role, they cannot use the command.
You can only apply one of these restrictions to a command at a time, not both.

​
Restricting commands

With the restrictcommand command, you can restrict a command to a specific role. This means that only users with the specified role will be able to use the command.
You can use the alias rc instead of restrictcommand, to make the command easier to type.

​
Adding a restriction

To restrict a command, use the restrictcommand add command, followed by the command and role you’d like to restrict it to. 
restrictcommand add <command> <role>

,,restrictcommand add purge @Mod
You should see a message confirming that the command has been restricted.

​
Restricting subcommands

If you want to restrict a subcommand, add an underscore (_) between the command and subcommand. For example, to restrict the purge bots command to the Mod role, you would do the following: 
restrictcommand add <command> <role>

,,restrictcommand add purge_bots @Mod
Same as before, you should see a message confirming that the command has been restricted.

​
Removing a restriction

To remove a restriction, use the restrictcommand remove command, followed by the command and role you’d like to remove the restriction from. 
restrictcommand remove <command> <role>

,,restrictcommand remove purge @Mod
You should see a message confirming that the restriction has been removed.

​
Removing a subcommand restriction

To remove a subcommand restriction, add an underscore (_) between the command and subcommand. For example, to remove the restriction from the purge bots command, you would do the following: 
restrictcommand remove <command> <role>

,,restrictcommand remove purge_bots @Mod
You should see a message confirming that the restriction has been removed.

​
Listing all restrictions

To list all the restrictions on your server, use the restrictcommand list command. 
restrictcommand list

,,restrictcommand list
You should see a list of all the restrictions on your server.

​
Removing all restrictions

To remove all restrictions on your server, use the restrictcommand clear command. 
restrictcommand clear

,,restrictcommand clear
You will be asked to confirm that you want to remove all restrictions. If you confirm, you should see a message confirming that all restrictions have been removed.

​
Reverse restricting commands

With the restrictcommand reverse command, you can block a command from being used by a specific role. This means that if a user has the specified role, they will not be able to use the command.
You can use the alias rc rev instead of restrictcommand reverse, to make the command easier to type.

​
Adding a reverse restriction

To reverse restrict a command, use the restrictcommand reverse add command, followed by the command and role you’d like to reverse restrict it from. 
restrictcommand reverse add <command> <role>

,,restrictcommand reverse add purge @Mod
You should see a message confirming that the command has been reverse restricted.

​
Reverse restricting subcommands

If you want to reverse restrict a subcommand, add an underscore (_) between the command and subcommand. For example, to reverse restrict the purge bots command from the Mod role, you would do the following: 
restrictcommand reverse add <command> <role>

,,restrictcommand reverse add purge_bots @Mod
Same as before, you should see a message confirming that the command has been reverse restricted.

​
Removing a reverse restriction

To remove a reverse restriction, use the restrictcommand reverse remove command, followed by the command and role you’d like to remove the reverse restriction from. 
restrictcommand reverse remove <command> <role>

,,restrictcommand reverse remove purge @Trial Mod
You should see a message confirming that the reverse restriction has been removed.

​
Removing a subcommand reverse restriction

To remove a subcommand reverse restriction, add an underscore (_) between the command and subcommand. For example, to remove the reverse restriction from the purge bots command, you would do the following: 
restrictcommand reverse remove <command> <role>

,,restrictcommand reverse remove purge_bots @Trial Mod
You should see a message confirming that the reverse restriction has been removed.

​
Listing all reverse restrictions

To list all the reverse restrictions on your server, use the restrictcommand reverse list command. 
restrictcommand reverse list

,,restrictcommand reverse list
You should see a list of all the reverse restrictions on your server.

​
Removing all reverse restrictions

To remove all reverse restrictions on your server, use the restrictcommand reverse clear command. 
restrictcommand reverse clear

,,restrictcommand reverse clear
You will be asked to confirm that you want to remove all reverse restrictions. If you confirm, you should see a message confirming that all reverse restrictions have been removed.