Server Configuration

We can now configure the bot for your liking for your server.

Lets Start

First, we need to see what our servers configuration is set to. To view this, do the command .config This will return an embedded message with our current server configuration.

Make sure you have embedded messages enabled. Or when attempting to use commands, you will receive an error telling you to enable them.

Have a quick look over this message, we are now going to change these settings to what we like.

To use configuration commands, you will need to be the Server Owner or have the Administrator permission.

Welcomer Configuration

Welcomer is a server setting that can send messages to a specific channel when a user joins. But to use it, we will first need to enable it. You can do this by running the command .config-welcomer enable

Of course, to disable welcomer you can use the same command but instead change enable to disable.

Lets take a look at the first setting we can configure for welcomer. Which is the welcomer channel. Without this setting configured, our welcomer will not send a message - it will also not send a message and give you an error if the channel that was set is no longer valid. .config-welcomer channel [#channel]

This will set the welcomer channel. To test that our channel configuration works, we can do .config-welcomer test

This will run your welcomer configuration, and send a fake welcomer message to the set channel. However, since we have no welcomer message set, it will send the default one. This brings us onto the next welcomer setting. We can change the welcomer message, to do this we run the .config-welcomer message [message]

There are a few placeholders we can use in our welcomer message however, to make it perfect. Just include these in your configuration message, and when someone joins, the placeholders will be replaced by what they represent.

  • {user} = This will show as the user who joined's mention

  • {userdiscrim} = This will show as the user who joined's discriminator

  • {server} = This will show the servers name

  • {date} = This will show the date the user joined

Once again, we can do the welcomer test command to see what it looks like. If we ever want to change the message, we can rerun this command, and if we include nothing, it will reset back to the default.

User-join Configuration

When users join your server you can set something to happen. This setting allows you to add roles and change the nickname of the user that joins, when they join. However, firstly we'll have to enable the module. .config-userjoin enable

Once it is enabled, we can now continue to use the other configuration commands. If we wanted to give the user a role when they join, we can do that by running the command..config-userjoin role [@role]

This will add the tagged role to the user that joins your server. If you do not specify a role, it will disable auto-role. Secondly, we can change the nicknames of users who join our server. Simply run the command. .config-userjoin name [name]

This will change the users nickname when they join. To disable it, just don't mention a name when running the command.

Staff Configuration

We want our server to be clean and tidy. And to do that, Kewl Bot comes equipped with many moderation & administrator commands, and in particular staff settings. There is no need to enable this, as most staff commands will always be enabled. But no one will be able to use the commands until a staff role is defined. To set the staff role, we can run the command. .config-staff role [@role]

Now that we have access to all the moderation commands. We can continue to configuring the rest of our staff settings. Next we have to consider if we would like administrative commands to be enabled. Take a look at this for some extra information.

If we want to enable the administrative commands, we can run this command. And if wanted, we can change the enable parameter to disable to do the opposite. .config-staff admin enable

Next, we have to decide if we want link blocker enabled. By default this is disabled, and if any links including discord invites are sent in chats the bot has access to, they will be deleted. To enable or disable we can run this command. .config-staff linkblock enable

The next setting that we can configure is our word filter. There is no need to enable/disable this as if there are no words in the filter, it wont do anything. When a word in the filter list is sent in a channel the bot has access to, that message will be deleted and another message will be sent warning the user not to use them words. To add a word to the filter, simply run the following command. .config-staff fitleradd [word]

But, our minds change, and if we want to remove a word from the filter we can with one simple command! .config-staff filterremove [word]

Lastly, by default no warning cap is set. But you can easily set this up with a command. A warning cap is when a certain amount of warning points are obtained by a user, it will ban that user from the server. This feature uses the points warning system included in the moderation commands. To set a warning cap enter this command. You can set it back to 0 to disable it. .config-staff warncap [points amount]

If the bot does not have permission to ban, or is below the user its banning. This feature will not work.

Server Logging Configuration

One of the very most useful things in a bot to have is logging. And logging is important, it puts all information in a single place for us to view and shows us whats happend when, where and sometimes why. KewlBot comes equipped with all this great stuff, but we'll need to enable it to use it. Use the following command to do this. .config-log enable

That still wont allow us to begin logging however. We will need to set a logging channel, accessible by the bot. We can use this command to do this. .config-log channel [#channel]

This will make logging start, and post to the set channel. But there's more. Logging has three levels, low, medium and high. These determine how much you want Kewl Bot to log. Here is a list of each level and what they log. By default it is set to medium.

Low Level Logging

  • Channel Create

  • Channel Delete

  • Member Joined

  • Member Leave

  • Role Created

  • Role Removed

Medium Level Logging

  • Channel Create

  • Channel Delete

  • Member Joined

  • Member Left

  • Message Delete

  • Message Edited

  • Role Created

  • Role Removed

  • Member Banned

  • Member Unbanned

High Level Logging

  • Channel Create

  • Channel Delete

  • Emoji Create

  • Emoji Delete

  • Member Banned

  • Member Unbanned

  • Member Joined

  • Member Left

  • Message Delete

  • Message Edited

  • Role Create

  • Role Delete

  • Channel Updated (Name, topic, ect)

  • Role Updated (Name, color, ect)

  • Member Nickname Changed

  • Member Role Added

  • Member Role Removed

To set which level we want our server to be logged at, we can run a simple command. .config-log level low|medium|high

Now would be a good time to review your server configuration and check if its all okay. You can always go back and change it. Remember to view your setup you can do .config

Tickets Configuration

Tickets are a fantastic addition to your discord server, and are a great and efficient way to help and support people. With the Kewl Bot ticket system, when a ticket is created it will create a channel with only users with the staff role and the ticket author (creator) able to view it. But first, we need to enable it! You can use this command. .config-tickets enable

Once you've done that, you need to look back and check if you set a staff role if not, tickets will still not be able to be used. Tickets are pretty much done, however if you really want to, you can set the message sent in the ticket channel when a ticket is made. .config-tickets message [message]

For this message, some placeholders are available for use.

  • {user} = A mention of the user who created the ticket

  • {reason} = The reason the ticket was made

Music Configuration

The music feature is disabled and is being worked on at the moment! Check back soon!

It can still be enabled via the config command but nothing will happen, it just changes a JSON file at the moment.