Making a discord bot using the discord.js Commando framework
Discord.js Commando Framework tutorial
Next, let's get started
Step 1: Setting up the project
Create a new folder (Make sure there are no spaces in your folder name) in your system and open command prompt or power shell in the folder.
Run the command
npm initand fill out the form, If you don't know what you're doing, then leave everything to default and type in you name when it asks for
After this, you will see a new file named
package.jsonin your folder.
Now use the following command to install the required libraries
Now you'll see a new folder named
node-modulesin your bot's folder and you're ready to start coding the bot.
Step 2 : Writing the index.js file
Create a new file in your bot's folder called
index.jsand open it with your favourite text editor.
Now write the following code in the beginning of your index.js file.
These lines will import the necessary libraries to use.
Next, write the following code
This will create a
CommandoClientObject which is an extension of
discord.js.Clientclass and set the owner of the bot as yourself to allow you to use the owner only commands that come built-in with Commando.
Now we will import the default commands for our bot.
Now let's make a handler that displays a message in the console when the bot is logged in and ready to use.
Next, set up the settings provider, Commando comes with built-in sqlite settings provider to allow default commands like
Last of all, login the bot
Testing the defaults
Run the bot by using the command
node indexin your console.
After a while you will see a message similar to this: -
You will also observe that your bot comes online so it's ready to be checked out.
Use the help command which in my case is
It shows something like this in your DMs: -
groups: The commands in a commando bot are grouped together under categories. the
groupcommand can be used the list these categories.
enable/disable: Commando framework comes with an in-built feature of enabling/disabling commands in different guilds, these commands do the job.
load/unload: These commands can be used to register commands from outside the code.
reload: This command can be used to reload a command after you've made changes to the code to refresh it.
help: The in-built help function ( very detailed ).
prefix: Commando also comes with a feature to change the default prefix in different servers, the
prefixcommand helps the users do it.
ping: Does exactly what help says.
eval: runs the code passed as an extension of the
index.jsfile and returns the output ( recommended not to use ).
These are the commands that come built-in with commando framework.
Creating your own commands
First of all, create a folder named
commandsin your bot's root directory.
Next make the following change in your code
This will create a new group named Starter Commands for your bot which can be referred to in the code by the name test and also read the files inside the commands folder and treat them as commands for the bot.
Inside the commands folder, create another folder named
testand inside the test folder, create a file named
foo.jsas the first command will be a simple foo-bar command.
foo.jsfile and change it's contents to
The first line imports the predefined
Commandclass from the Commando Framework.
Next, we created the command as a extension of the
The constructor is run as soon as our index.js reads this file. Inside our constructor, we set the basic details about our command.
name, memberName: set the name of the command.
aliases: sets what other commands can be used to do the same thing.
description, details: describe what the command does.
examples: sets an example for the user on how to use the command.
group: sets our command will be part of which command group.
The next part is the run method, it is called whenever the user uses the command, the parameter msg is the message sent by the user, it's of the type
We make our bot respond with
barwhenever the user uses the
module.exports = fooCommandexports the command making it readable by our index.js file.
Now, let's test out our foo command.
Run the bot using
node indexand use the help command.
You will see something new at the end of the help menu
Let's use help about our command, use the help foo command. You should see something like: -
Let's use our command now, there are 4 ways to do it now.
==fin a server
You will see that the bot responds with
barwherever you use the command.
Now that we are done with one command, let's make another one that takes in input (arguments) from the user.
Create a new file named
say.jsin your test folder.
Write the following code in the say.js file.
Let's see what's new!
- client_permissions: defines a list of permissions that your not will need for the command to work properly.
- args: Defines what arguments the user has to enter.
- key: defines the name of the argument.
- prompt: defines what the bot will say if the user has not provided the argument
- type: defines the type of the argument.
- The run method now has 2 parameters, the second one is the arguments, we are asking the user to pass.
msg.delete()deletes the message sent by the user.
Let's test out our say command
If you use the help command now, you will see a new entry at the bottom for the say command.
Use help say before using the command.
You should see something similar to: -
Notice how Commando prepared the format for how to use the command, trust me it's a handy feature.
saycommand now without passing any arguments.
You will see that the bot asks you for the text to say, also with a message like
This is another feature of Commando framework - command cancellation.
You can either say something for the bot to repeat it or wait for 30 seconds to cancel the command or say cancel yourself.
You can also pass on the argument while using the command as in the examples.
Validating and throttling
Now let's think, what if the user was trying to send links or spam in the server using our say command?
That can easily be prevented by validating the
saycommand and making sure that there was no link in the argument passed.
As for the spam, it can be prevented by throttling i.e. making sure that the command is not used more than a specified number of times in a specified amount of time.
Here's a sample code (This is modified
say.jsfile) : -
Now let's see: -
- argument.validate: a function that checks for validation of the argument passed. Returns
truewhen valid and the
error messagewhen invalid.
- throttiling: an object that specifies how many usages in how much duration of time are allowed.
- argument.validate: a function that checks for validation of the argument passed. Returns
Messing with the defaults
You can also modify the default commands: -
You can find them at
In there, you will see 2 folders containing the command files.
help.js- shows help for the various commands.
ping.js- displays the bot's ping to the discord server.
prefix.js- changes the prefix for the server ( guild Only command ).
enable.js- enables a command in a server.
disable.js- disables a command in a server.
groups.js- lists all command groups.
load.js- loads a new command.
reload.js- reload a command.
unload.js- unloads a command.
That's all you need to know to get started, put your imagination to the test and make amazing bots. Here's the link to the official docs for more reference: https://discord.js.org/#/docs/commando/master/general/welcome
Also here's a link to a Commando bot by @kpostal10 named Bug Bot just for reference: https://repl.it/@kpostal10/BugBot
Looks good, warning to anyone that follows this tutorial on repl.it, using sqlite as the settings provider might break or become corrupt.
Can someone help me with "Messing with the defaults", actually am noob at js and from where can I get that node_modules inside my bot's directory? Isn't it about repl.it, so accord to that I cannot find this thing inside repl.it.
how do i use the npm init command? if you run it in the terminal i keep getting an error.
Command class names like
sayCommand should be in pascal case since they are classes. There are also several other bugs in your code, I fixed them in this GitHub gist.
Additionally, you should never edit anything in
node_modules since updating dependencies will overwrite anything in there. To modify the default commands, just don't register them. Instead, you can register your own if you'd like.
For other things that can't be solved by extending classes from Commando you can make a fork of the GitHub repository and use that in your bot.
@pizzafox As for the Command Classes, I prefer keeping them that way. Also this tutorial is completely bug free, and all the difference I see in your gist and this is use of regular expressions, and its not really a good idea to use regular expressions in a tutorial as most people don't understand them. If you really found an actual bug, let me know.
Additionally, you can edit something in the
node_modules, it's not a big deal ( unless you're using heroku ), also, going through the files in the module source, people might learn new ways of doing many things. Appreciate the info though.
@pizzafox As for the class name being captiol, it does not matter all you are doing is exporting the class object. Weather or not it is captiol will not affect the function of the bot. For how long I've been doing JS bots this is one of the better tutorials I've seen; Espically for commando. Also just because it is not regex does not mean it will not work the same. I like the fact that he showed that it can be more than one line in the validate function because a novice might do more custom validation in that check.
As for the other "bugs" you fixed I would like to know which ones they are? Because I pasted his code in a bot and it ran just fine as it is.
And for editing the node_modules that complitly fine. I've done it for my bot to add a header to the built in help method saying that this bot was coded in commando and who made it.
@kpostal10 For starters, the bot doesn't check if it can delete the command message. Also, it should return the response message.
If you ever run your bot on another host or Commando has an update to the help command, your changes will be lost. I strongly suggest you move it to a separate command like I did in my bot
@pizzafox first of all, it does check if it can delete the command message, instead of doing lazy things like https://gist.github.com/pizzafox/ad192e8519c69f63565980e446a13ecc, you should try doing a little hard work, returning the response message is optional, if not shown properly like in your gist, people might not even understand if it's a function, and as I said, this is not an absolute beginner tutorial, but it's still a tutorial, doing things like what you did with your bot might still be confusing moreover the bot you linked does exactly same as the built-in help command. This tutorial is not for pros, it's for everyone who knows the basics.
You might wanna give it a thought about what you say and maybe do the honor of reading the whole thing.
@TheDrone7 The client permissions weren't there when I copied your command to make my edits. It seems you tried to add it in after I posted my comment. Make sure you change it from
The help command I posted actually has a few new features, which you can see in the run function.
As an experienced Commando user, I'm just trying to improve this tutorial to help out newcomers. I apologise if my tone seemed critical.
@pizzafox Nothing wrong with being critical about a post, there is just a right and wrong way to appraoch it. Dont want to come off sounding like a "know-it-all" but you also want to make it to where what you are saying makes sense and is contributing (not taking away from) the post.
Thanks for providing another perspective to the bot.
Also @TheDrone7 might want to check the docs:
This is a really nice list of all the things you can put when you make a command in the constructor: https://discord.js.org/#/docs/commando/master/typedef/CommandInfo