Cliptok - A Discord bot for Microsoft Community

About

This bot is a Discord moderation bot specifically designed for the Microsoft Community.

The bot has not been designed for use outside of that server. A lot is assumed about the environment and you will encounter problems along the way. Modularity is not the goal of this project. You are on your own if you attempt to host this bot outside of the intended environment. (Good luck though, I hope it works out!)

GitHub Issues will only be accepted if they are reproducible on the production bot (Cliptok in Microsoft Community).

Configuration

If you're using the bot on the Microsoft Community Discord server, the configuration should be fairly simple since the default configuration values are filled in for you.

Simply copy .env-example to .env and edit in the token for your Discord bot. If you require a different prefix, that can be done in the same file.

If you're using the bot elsewhere, you will need to edit the configuration file more thoroughly, including all of the role IDs and the server ID. It is vital that every config value is present and valid.

Usage

There are two methods of launching this bot. Through Docker or as a standalone application.

If you are not familiar with deploying .NET (Core) and Redis applications, it is recommended to use the Docker method as dependencies are automatically handled for you without polluting your main system, and the setup can be handled with a few simple commands.

Setup - Docker

First you'll want to install Docker. On a Debian or Ubuntu-based Linux distribution this should be as simple as sudo apt-get install docker.io docker-compose.

Then:

1. Clone this repository and cd into the directory.
2. Copy .env to .env-example and add the bot token.
3. If you're not deploying for Microsoft Community, uncomment lines 21-23 in docker-compose.yml and edit the config.json to fit your needs.
4. Run the bot in the background: docker-compose up -d

That's it! If you ever need to see the logs, cd back into the directory and run docker-compose logs.

If you want to make a backup of the bot's data, that will be inside the data folder, though may be owned by root due to Docker limitations. It's up to the user hosting the bot to maintain their own backups (Or lack thereof).
The author(s) of the bot accept(s) no responsiblity for lost data due to negligence.

To update the bot in the future, git pull the repository and then pull and restart the containers:

• git pull && docker-compose pull && docker-compose up -d

Setup - Standalone

If you want to run the bot as a standalone application rather than a Docker container, you'll need to install the dependencies manually:

• .NET SDK 5.0, instructions can be found on the Microsoft website.
• Redis server, on Debian or Ubuntu-based Linux distributions this should be sudo apt-get install redis-server
  • It may be in your best interests to configure Redis to use AOF persistence. This will dramatically decrease the risk of losing data due to power failure or similar issues. You can find more information about that on the Redis website.
  • If running on Windows, WSL is preferred rather than any other method of running Redis.
    • You may need to sudo service redis-server start or redis-server manually on WSL.

Once you have everything installed:

1. Clone this repository and cd into the directory.
2. Set the CLIPTOK_TOKEN environment variable to your bots token.
3. If you're not deploying for Microsoft Community, edit the config.json to fit your needs.
4. Compile the bot for production: dotnet build -c Release.
5. Run the bot: dotnet run -c Release

If you go with this method you will have to fork the bot to the background yourself, through the use of a process manager like pm2 or a systemd service.

Limitations

Currently the bot will only work with one server. This choice was made because the bot was specifically created for a single server and will never be made publicly available. If you are looking to host a bot for multiple servers, this bot is not for you.

A lot of the configuration (Role IDs, emoji IDs, etc.) are in the config.json file and cannot be edited at runtime. This means the bot will have to be relaunched for changes to those settings to take effect. This may be improved in the future, however it is not a high priority.

Credits

Developer(s)

• Erisa

Code contributor(s)

• TorchGM

Special thanks

• TorchGM for testing and providing design feedback. Seriously, thank you Torch.
• The developers of DSharpPlus, without their library none of this would be possible.
• The excellent moderation team over at Microsoft Community, and all of its wonderful members.