An easy-to-use Discord soundboard bot. BYO audio files and quip away!
The purpose of the DisQuip Bot project is to provide a simple sound board bot that is easy to install, configure, and run. After installation, simply create a directory structure with your own quips (audio files) and run the bot! Then, head on over to your favorite Discord server, and punch in commands like !aoe3 11 and the bot will play the corresponding quip for you into your voice channel.
Head on over to Contents to get started.
I found myself wishing I could easily play taunts from the Age of Empires video games while playing other games with my friends. So, I built out a prototype that went by the name of "AOE Taunt Board." It was a hit, so I figured I'd make a publicly distributable version for you, the reader!
Installation Overview Installation Preliminaries
Install Docker On Windows Download the DisQuip Bot Docker Image
Prerequisites Quick Note For Mac/Linux Users Install FFmpeg (Windows) Configure Python Virtual Environment and Install DisQuip Bot
Running for Docker Install Running for Local Install Updating Configurations or Audio Files
Depending on your personal level of computer literacy, installation takes ~10-60 minutes. There are two different ways to install the DisQuip Bot:
- Docker Based Installation: If you already have Docker installed, this is the easiest path to take. If you do not already have Docker, note that Docker is a large program (the installer for Docker alone was 407MB on 2020-10-11), and it takes a little extra work to Install Docker on Windows compared to to Mac/Linux. However, once Docker is installed, there are significantly less steps required to get the DisQuip Bot running compared to the Local Installation.
- Local Installation: The local installation process is relatively straight forward and will lead to a leaner installation if you do not have Docker installed and don't plan to install it in the future. However, it involves downloading and installing several programs as well as manually placing program files in directories of your choosing.
Whichever route you choose, be sure to first take care of the Installation Preliminaries.
No matter which installation route you take (see Installation Overview), we're going to need a directory to place configuration and audio files. The directions here will assume that you created a new directory called disquip-bot in your home directory. On Windows, that's typically C:\Users\<youruser>\disquip-bot. Please create this directory before going forward. To keep these directions simple, this directory will be referred to as ~/disquip-bot going forward.
Download disquip.ini and place it in ~/disquip-bot. Later, in Configuration we'll be modifying this file.
Create a new directory called audio_files underneath ~/disquip-bot. This is where we'll be placing our quips later on (Audio Files).
Note that if you're running Windows, you'll need at least Windows 10 version 2004. More details can be found at Install Docker on Windows.
The Docker installation process is simpler for Linux users (and maybe for Mac users as well?), so no directions are provided here. Head on out to the Docker documentation to get started.
How you proceed depends on the edition of Windows 10 you're running. Many users will likely have Windows Home, and should thus carefully follow the directions at Install Docker on Windows Home. If you have a Windows edition other than Windows Home, carefully follow the directions at Install Docker on Windows Pro, Enterprise, or Education.
The easiest way to tell the Windows edition, version, and build you're running is to type "About" into the Windows search bar, and open click on the "About your PC" box. In the window that opens, scroll down to "Windows specifications" to get information about your Windows installation.
Inevitably, Docker's installation instructions will instruct you to Install Windows Subsystem for Linux. At the time of writing (2020-10-11), you can stop after completing "Step 5 - Set WSL 2 as your default version." No need to move on to "Step 6 - Install you Linux distribution of choice" unless you would like to.
Once you have Docker installed, it's time to download the Docker image for DisQuip. Open up your favorite terminal (e.g. Command Prompt on Windows) and enter in the command docker pull blthayer/disquip-bot:latest. You'll now have a runnable Docker image with all the DisQuip Bot prerequisites already installed.
For Advanced Users: If you would prefer to build your own Docker image rather than pull a pre-built one, that is of course an option. Start by cloning or downloading the repository locally. Then, in your terminal change directories to the repository and run docker_build.bat. Linux/Mac users should be able to convert this to a .sh script in a matter of seconds :) Additional info: The main Dockerfile is simply called Dockerfile. For caching convenience, a build needs run for both of the Dockerfiles in the docker_ffmpeg directory. I've hard-coded the Docker repository and tags throughout the Dockerfiles and helper scripts, and you may wish to change those when you run your own build.
Local installation involves installing Prerequisites and then installing the DisQuip Bot.
This bot depends on a wonderful package called discord.py. There are additional dependencies that need installed for voice support for Mac/Linux. Please check out their installation instructions and install the prerequisites before continuing.
TL;DR:
DisQuip Bot should be operating system agnostic, but to date has only been tested on Windows (I know, gross.).
DisQuip Bot is a Python program and thus requires that you install Python. Specifically, ensure you are running a version of Python >= 3.6. Before going any further take a moment to download Python and then install it.
For Windows users: later we'll be downloaded a compressed .7z archive that we'll need to extract. For extraction, we'll use 7zip. Please download and install.
In order to stream audio files over the internet, a handy program called FFmpeg is used. Windows users should refer to Install FFmpeg (Windows). Mac/Linux users are assumed to be highly computer literate users who can get FFmpeg working solely given the link to FFmpeg :) If anyone would like to provide directions for Mac or Linux I'm happy to add them here.
Fortunately, helpful folks like Gyan Doshi exist and provide pre-built FFmpeg distributions. Installing is as simple as:
- Download the appropriate build from gyan.dev. I've successfully used the git-essentials FFmpeg build. You can find other builds at FFmpeg or build it yourself from source code.
- Extract the downloaded
.7zarchive to~/disquip-bot/ffmpegusing 7zip. For me, that looks like:- Navigate to the
Downloadsfolder (TypicallyC:\Users\<your user>\Downloads - Right click the downloaded
.7zfile (it'll be named likeffmpeg-2020-10-11-git-7ea4bcff7b-essentials_build.7z) - Hover over
7-zip, and selectingExtract files.... - In the pop-up:
- Change
Extract to:entry to~/disquip-bot/ffmpeg, replacing~with your full file system path. - Uncheck the checkbox directly below the
Extract tobox. - Check the
Eliminate duplication of root folderbox. - Click
OK.
- Change
- Navigate to the
After following the directions above, you should have one sub-folder in ~/disquip-bot/ffmpeg named something like ffmpeg-2020-10-11-git-7ea4bcff7b-essentials_build. Within that sub-folder should be directories called bin, doc, and presets. There will also be a pair of files called LICENSE and README.
Later on in Configuration, you'll need the full file system path to ffmpeg.exe in the bin directory.
After you've installed Python, we'll be configuring what's known as a virtual environment to install Python dependencies as well as the DisQuip Bot. Here are directions for Windows (similar on Mac/Linux):
- Start a Command Prompt (shortcut:
Win + Rkeys, typecmd, hitEnterkey). - Change directories to your
~/disquip-botdirectory using thecdcommand. This should work:cd %USERPROFILE%\disquip-bot. - Run the command
py -3 -m venv venvto create a virtual environment directory calledvenvin~/disquip-bot. If you have multiple versions of Python 3.x installed, you can specifypy -3.8, for example. - Activate the virtual environment by running the command
venv\Scripts\activate.bat. Your command line should now be prefixed with "(venv)". - Python installs packages with a tool called
pip. Update it by running:python -m pip install --upgrade pip. - Install the DisQuip Bot and its dependencies by running
python -m pip install disquip-bot.
As mentioned in the second sentence of this document, this project is a "bring your own audio files" project. If you've followed the directions, you should have a directory called audio_files in your ~/disquip-bot directory. Within that audio_files directory there must be subdirectories that contain audio files. An example structure might look like:
-- audio_files:
------ AgeOfEmpires1
---------- 01 Yes.mp3
---------- 02 No.mp3
------ MontyPython
---------- I fart in your general direction.wav
---------- Bleed on me.wav
---------- Weirdo.wavHow this structure is set up has meaning. To explain via example, assuming commands are prefixed with an exclamation mark (!):
There will be two available commands, !AgeOfEmpires1 and !MontyPython (case insensitive). You can define Aliases for shorter names. The !AgeOfEmpires1 command can accept 1 of 2 possible arguments, "1," or "2". A quip command would look like !AgeOfEmpires1 2, which would stream "02 No.mp3" into your current voice channel.
Similarly, the !MontyPython command can accept 1 of 3 arguments, "1," "2," or "3." The files are sorted alphanumerically, so !MontyPython 1 would stream Bleed on me.wav into your current audio channel.
It's worth noting that the names of the audio files, excluding their file extensions (e.g., .mp3), will be used in creating Help messages. So, the more descriptive, the better!
The internet is full of audio files that are available to you for no cost. For example, myinstants.com has all sorts of files. You can also easily make your own using your PC's microphone. Also, FFmpeg is a very powerful tool that you could use to create clips. Want nearly 1,000 community-sourced quips from 1998? Head on over to Age of Empires Heaven.
If you love Age Of Empires here are a few suggestions:
- Age of Empires 2 on Steam: I found the taunts in
C:\Program Files (x86)\Steam\steamapps\common\Age2HD\resources\en\sound\taunt. - Age of Empires 3 on Steam: I found the taunts in
C:\Program Files (x86)\Steam\steamapps\common\Age Of Empires 3\bin\Sound\taunts - Age of Empires 1: A tad more work, and the gain is rather minimal. If you're dedicated, read on:
- Subscribe to the "Age of Empires 1 Taunt Pack" on the Steam Workshop.
- The mod will download automatically in Steam.
- Check the logs at
C:\Program Files (x86)\Steam\steamapps\common\Age2HD\Logs\2020.10.03-0839.59(the ultimate file name will of course be different). - You should find a
Modtext file. Open it up. - Find where the mod was installed. For me it was at
C:\Program Files (x86)\Steam\steamapps\workshop\content\221380\927865693. - Go there, and dig in:
C:\Program Files (x86)\Steam\steamapps\workshop\content\221380\137168612\resources\en\sound\taunt. - Copy the taunt files to your Age of Empires directory. Perhaps
aoe1to keep it short?
It took me more time than I had hoped to figure this out, so hopefully these directions save you some time. We need to Create a Discord Application and then Add the Bot to Servers.
- For starters, you of course need to have a Discord account.
- Navigate to the Discord applications site.
- Click on
New Application - OPTIONAL: If you'd like, add a custom icon in the
APP ICONarea. Perhaps a snip-and-sketch of your favorite game? - Click on the
Bottab in the left-handSETTINGSarea. - Click the
Add Botbutton. - In the pop-up window, click on
Yes, do it!.
Don't close that web browser or tab! Stay right where you are and move on to Add the Bot to Servers.
Scroll down to the bottom of the OAuth2 tab for the application you made in Create a Discord Application. In the SCOPES area check the bot box.
The DisQuip bot only needs the following permissions: - TEXT PERMISSIONS: "Send Messages" - VOICE PERMISSIONS: "Connect" and "Speak"
Scroll down to the BOT PERMISSIONS area and click the appropriate boxes corresponding the permissions listed above.
Finally, click on the Copy button in the SCOPES area. Paste the link into a new tab in your web browser. You'll need to login to Discord. A pop-up will appear and you'll need to select a server from the ADD BOT TO: drop-down and then click Continue. Click Authorize and then prove you aren't a robot yourself.
If you've followed all the steps in this section, your bot now should have permissions to listen to and send text messages as well as send audio messages into a voice channel.
Don't close your web browser just yet! Keep that tab open and continue to Configuration.
All the necessary configuration parameters for DisQuip Bot are defined in disquip.ini, which you should have downloaded during the Installation Preliminaries. Rather than list every configuration option here, they're all listed in disquip.ini. Open that file with your favorite text editor (I strongly recommend Notepad++ if you're using Windows so that you can get syntax highlighting) and update the file according to your installation. Please read the entire file. Don't forget to hit "save" when you're done! :)
Here are a couple areas worth discussion explicitly:
Remember when I asked you to keep your tab open from the Discord applications site? Here's where you'll use it. In the Bot tab, find the are where it says TOKEN. Click the Copy button to copy your token to the clipboard. Use the copied value to update the api_token field in disquip.ini. Don't forget to save the file.
It's nice to have descriptive directory names like "monty_python" or "AgeOfEmpires1" but that can be cumbersome to type for a quick quip. To alleviate this, the DisQuip Bot supports aliases for commands. Check out the [aliases] section of disquip.ini
After you've performed all the installation and configuration steps above, you're ready to run! Running the bot looks different depending on whether you took the Docker Based Installation or Local Installation path. Read on!
If you're on Windows, download the file called docker_run.bat from DisQuip Bot on GitHub and place it in your ~/disquip-bot directory. Simply run the script inside the ~/disquip-bot directory to fire it up! This script assumes you've placed all files as directed in these directions. If you didn't, the script will be easy to tweak. For Mac/Linux users, docker_run.bat will be very easy to port to a shell script.
To stop the bot, use the Ctrl + C keyboard command. Unfortunately, this will only kill the command window and not the actual Docker container. Run docker container ls to view running containers. Locate the name (NAMES column) of the running container and then execute docker stop <name>.
This is pretty quick and easy! :)
- Using a command prompt, change directories to
~/disquip-botviacd %USERPROFILE%\disquip-bot. - Activate your virtual environment via the command
venv\Scripts\activate.bat. - Execute the command
disquip-botto fire it up.
When you're done, simply kill the command window you have running or use Ctrl + C to stop the program.
The DisQuip bot does not dynamically detect changes to audio files or configurations. After making a change, simply stop the bot and start it again to pick up any changes.
The bot will listen to all the text channels of the server(s) you added it to and look for messages that start with the cmd_prefix defined in disquip.ini. This defaults to the exclamation mark (!).
The DisQuip Bot will automagically join the voice channel you're currently in once it receives a valid command. Note that DisQuip Bot can only be in one voice channel per server at any given time.
Start exploring!
Assuming your command prefix is !, simply type !help into a text channel the bot has access to. It'll respond with a listing of available commands and some other helpful information.
Rather than running the DisQuip Bot on the same machine you're using to chat and play games, you may want to host it on a server. This will preserve resources on your local machine and allow the DisQuip Bot to stay online even when you aren't.
The service directory in this repository has one sample implementation for running the DisQuip Bot as a service on a Raspberry Pi 3 Model B running the Raspbian GNU/Linux 9 (stretch) operating system. The directions there should apply to many different flavors of Linux. If you'd like to get started, check out service/README.rst.
- Backwards incompatible change:
disquip.ininow requires apre_normalizefield in the[disquip]section. - By default, all audio files will first be pre-normalized to a peak amplitude of 0 dB. This is accomplished using ffmpeg-normalize.
- New
randomcommand!.