Updates setting-a-default-value-for-an-arg.md

Auto commit by GitBook Editor

Author: lilyissillyyy

SUMMARY.md

@@ -1,21 +1,35 @@
 # Summary
 
+## Starting
+
 * [Introduction](README.md)
 * [Getting Started](getting-started.md)
-* [Making Your First Command](making-your-first-command.md)
-* [Adding More Command Groups](adding-more-command-groups.md)
-* [Using Args in Commands](using-args-in-commands.md)
-* [Using Multiple Args in One Command](using-multiple-args-in-one-command.md)
-* [Using a Validator for an Arg](using-a-validator-for-an-arg.md)
-* [Using Aliases in Commands](using-aliases-in-commands.md)
-* [Using Throttling in Commands](using-throttling-in-commands.md)
-* [Setting a Default Value for an Arg](setting-a-default-value-for-an-arg.md)
-* [Using Client Values in a Command](using-client-values-in-a-command.md)
-* [Using a RichEmbed in a Command](using-a-richembed-in-a-command.md)
-* [Setting a Command to Guild Only](setting-a-command-to-guild-only.md)
-* [Checking for Client Permissions](checking-for-permissions.md)
-* [Checking for User Permissions](checking-for-user-permissions.md)
-* [Using an async run Method](using-an-async-run-method.md)
-* [Removing the Unknown Command Response](removing-the-unknown-command-response.md)
-* [Setting a Database Provider](setting-a-database-provider.md)
+
+## Commands & Groups
+
+* [First Command](making-your-first-command.md)
+* [Adding Groups](adding-more-command-groups.md)
+* [Guild Only](setting-a-command-to-guild-only.md)
+* [async run Method](using-an-async-run-method.md)
+* [Client Permissions](checking-for-permissions.md)
+* [User Permissions](checking-for-user-permissions.md)
+
+## Args
+
+* [Args](using-args-in-commands.md)
+* [Multiple Args](using-multiple-args-in-one-command.md)
+* [Validators](using-a-validator-for-an-arg.md)
+* [Aliases](using-aliases-in-commands.md)
+* [Throttling](using-throttling-in-commands.md)
+* [Default](setting-a-default-value-for-an-arg.md)
+
+## Settings
+
+* [Settings Provider](setting-a-database-provider.md)
+
+## Other Stuff
+
+* [Client Values](using-client-values-in-a-command.md)
+* [RichEmbeds](using-a-richembed-in-a-command.md)
+* [Unknown Command Response Removal](removing-the-unknown-command-response.md)
 

adding-more-command-groups.md

@@ -1,4 +1,4 @@
-# Adding More Command Groups
+# Adding Groups
 
 Before we make our new argument-powered command, I think we should place it within it's own command group. Then, we can have multiple commands sorted separately in our help command and folder structure.
 
@@ -29,9 +29,9 @@ client.registry
     .registerCommandsIn(path.join(__dirname, 'commands'));
 ```
 
-You can add as many of these as you want. 
+You can add as many of these as you want.
 
 The next step is to create another folder in your `commands` folder, called `group2`, just like with our `group1` folder.
 
-And there you go, another command group for our new command! 
+And there you go, another command group for our new command!
 

checking-for-permissions.md

@@ -1,4 +1,4 @@
-# Checking for Client Permissions
+# Client Permissions
 
 Sometimes you're going to have a command and start getting a `Forbidden` error. Why? Well, most likely you don't have permissions in the guild to do something. Commando will automatically check for the Send Messages permission and reroute the command to a DM, but for things like Embed Links or Manage Messages you may want to perform a permission check before using the command. Thankfully, this is quite simple.
 

checking-for-user-permissions.md

@@ -1,4 +1,4 @@
-# Checking for User Permissions
+# User Permissions
 
 In the last chapter we talked about how to check for bot permissions, in this chapter, we're going to be using a `hasPermission` method to check whether or not the user is the owner before using the command.
 

making-your-first-command.md

@@ -1,4 +1,4 @@
-# Making Your First Command
+# First Command
 
 So now that we've set up a command group and registered our command folder, we're ready to make our first command file! First, you're going to need to, of course, create a new file for the command. Hop over to your `commands` folder, and then your `group1` folder, and make a new file called `reply.js`. This is going to be a simple command that only replies with a message when used. We'll go into arguments and all that later.
 

removing-the-unknown-command-response.md

@@ -1,4 +1,4 @@
-# Removing the Unknown Command Response
+# Unknown Command Response Removal
 
 Sometimes, you may want to remove the \(somewhat annoying\) unknown command response from your bot. Be it Cleverbot or other reason, sometimes you just want it gone, and it's quite simple to remove.
 

setting-a-command-to-guild-only.md

@@ -1,4 +1,4 @@
-# Setting a Command to Guild Only
+# Guild Only
 
 You may have noticed that should you use your say command in a DM, you are going to get a `Forbidden` error due to attempting to delete a message from the other user in DM. One easy way around this? Setting the command to guild only!
 

setting-a-database-provider.md

@@ -1,4 +1,4 @@
-# Setting a Database Provider
+# Settings Provider
 
 Commando has a built-in way of storing guild settings. By default things such as the guild's custom prefix or disabled commands will be stored for Data Persistence, and you can also have your own custom settings as well.
 

setting-a-default-value-for-an-arg.md

@@ -1,6 +1,6 @@
-# Setting a Default Value for an Arg
+# Default
 
-Sometimes you may want an argument to be optional. In that case, you can use `default`. 
+Sometimes you may want an argument to be optional. In that case, you can use `default`.
 
 Let's say you have a command that rolls a dice, it's args would probably looking something like this:
 
@@ -27,7 +27,7 @@ args: [
 ]
 ```
 
-And then it will be 6 if no argument is set. 
+And then it will be 6 if no argument is set.
 
 You can take advantage of this to create completely optional arguments, for example:
 

using-a-richembed-in-a-command.md

@@ -1,4 +1,4 @@
-# Using a RichEmbed in a Command
+# RichEmbeds
 
 You may have noticed that if you try to use a RichEmbed in your command, that there's no way to create the new embed, as `new Discord.RichEmbed()` is going to say `Discord` is undefined. That's because when using a RichEmbed, we need to require Discord.js alongside Commando.
 

using-a-validator-for-an-arg.md

@@ -1,4 +1,4 @@
-# Using a Validator for an Arg
+# Validators
 
 Sometimes you're going to want an argument to be a certain thing, for example, a certain text, or maybe you want to check the length, there's many things you may want to do. This can be accomplished with a `validate` in your arg.
 

using-aliases-in-commands.md

@@ -1,4 +1,4 @@
-# Using Aliases in Commands
+# Aliases
 
 Aliases are simply different ways to call the same command. They're extremely simple to do.
 

using-an-async-run-method.md

@@ -1,4 +1,4 @@
-# Using an async run Method
+# async run Method
 
 `async` is a simple way to make your Promise-Powered code look _extremely_ neat. Normally with promises, we would use `.then` to continue running the command after the promise has resolved.
 

using-args-in-commands.md

@@ -1,4 +1,4 @@
-# Using Args in Commands
+# Args
 
 Sometimes when using commands we may want to get data from our user to narrow down the command further. In this section we'll create a command that pulls a string from the message and says it back to the user.
 

using-client-values-in-a-command.md

@@ -1,4 +1,4 @@
-# Using Client Values in a Command
+# Client Values
 
 This one is easy. Say you wanted to use a client value in your command, for example, you wanted to get the amount of guilds the bot was in. Normally, you'd do this:
 

using-multiple-args-in-one-command.md

@@ -1,4 +1,4 @@
-# Using Multiple Args in One Command
+# Multiple Args
 
 Sometimes you may want to collect more than one piece of content from a message. Well, you're in luck, as Commando makes using multiple Arguments very simple.
 

using-throttling-in-commands.md

@@ -1,4 +1,4 @@
-# Using Throttling in Commands
+# Throttling
 
 Throttling is like rate-limiting, it only allows the command to be used in a certain period of time. A cooldown of sorts. They're very simple, as with most things I've explained in Commando.