You can manage Wump's commands in various ways, some of them are:
Deleting a command's file
Disabling the command in it's extData
Editing the enabled commands inside of the configuration file
This is the simplest way to disable a command: by deleting it entirely. Although this is not recommended but it is an option, do as followed inside of the root directory:
delete.sh#!/bin/bash# Linux / Macrm -rf src/commands/Discord/<category>/<command># Windowsdel ./src/commands/Discord/<category>/<command>
This is a much safer way than just straight up deleting the command: by editing a command's extData. The structure of a command's extData is like this:
ping.jscmd.extData = {path : undefined,name : 'ping',syntax : 'ping',bearer : 'wump',aliases : [ 'pong' ],argument : [],description: 'Lists latencies',hidden : false,enabled : true,cooldown : 1000,category : 'Utility',ownerOnly : false,guildOnly : false,permissions: [ 'embedLinks' ]}
You can disable a command simply by changing enabled
to false
You can also hide a command but still make it usable by changing hidden
to true
Or you can make a command "op" only by setting ownerOnly
to true
The best way is by editing the Discord.commands
array inside of your configuration file, the syntax is as followed:
application.yml...Discord:...commands:- * # Enables all commands- wump.* # Enables all commands with bearer "wump"- wump.utility.* # Enables all commands in category "utility" from bearer "wump"- wump.utility.ping # Only enables the "ping" command in category "utility" from bearer "wump"