THIS IS NOW DEPRECATED AND ON PERMANENT MAINTENANCE MODE

A replacement is currently in the works. This will no longer get new features, and only critical bugs and security flaws will be fixed. Please see this post for more information.

Please note that this is heavily outdated. This may not be functional anymore.

DSA Discord Bot

A Discord bot originally made for the DSA Esports server, which is now being made as a general-purpose / esports discord bot.

Need help? Check out the support server.

Commands

A command list can be DM’d to you by pinging it and adding ‘help’ or by saying ‘{prefix}help’. You can also do ‘{prefix}sayhelp’ to send it to the current channel instead.

Alternatively, an online command list is available.

Installation

This bot was primarily made for running on a repl.it node.js server, accompanied with express and UptimeRobot, which is easier for running it 24/7. It can also be run on any normal software after making a few adjustments.

Please note that, at this time, the main focus is on the actual bot itself. This makes the process of forking it and running a custom version pretty tedious. At this time, if you want to run your own version, you’re best off forking the repl and setting it up on repl.it.

There are plans to improve the installation process, but as of right now, no efforts are being made.

Getting the bot on repl.it

@TylerFlowers/DSA-Disc-Bot">Fork this repl
In config.js, you can make any adjustments you want to make, such as the default prefix. Just follow the notes.
Skip the next section and go straight to the rest of the installation process.

Getting the bot on node.js

Download node.js
Download the repository. You can do this through here (GitHub) or through the repl (link above)
Extract it.
In your command prompt / terminal, make sure the selected directory is the same folder as the extracted one and run npm install
- If you have errors while running this, use Node v14 and run npm install -g windows-build-tools. Make sure you’re running that on PowerShell in admin mode.
- If that doesn’t work either, run this: choco install -y visualstudio2019buildtools visualstudio2019-workload-vctools then this: npm config set msvs_version 2019 (Do note that this requires Chocolatey)
In config.js, you can make any adjustments you want to make, such as the default prefix. Just follow the notes.

The rest of the installation process

Making the discord bot user and adding it

Make a new developer application on Discord Developer Portal.
Open the application, go to the Bot Settings and add a bot.
Configure any settings you want.

Configuring Discord info

On repl.it/your bot folder, make a new file named “.env”
In the Discord Developer Portal, go to the bot settings and copy the token.
In the .env file, type in “token=” and paste in your bot token.
In Discord, copy your ID (or whoever you want to specify as the owner) by right clicking on it and selecting ‘Copy ID’. If you don’t see that option, go to the Appearance settings and enable ‘Developer Mode’
Back in the file, make a new line, type in “id=” and paste in the ID.
Your .env file should now look like this:
```
token="bottoken"
id="ownerid"
```

Adding Challonge and smash.gg API keys

Challonge and smash.gg require API keys for commands that don’t require them or don’t do actions requiring an account (i.e. challongematches or smashggtourney)
You may skip this section if you aren’t using this bot for esports purposes, but some commands will not function if you do.

On Challonge, log in and copy your API key.
In .env, make a new line, type in “challongeapi=” and paste in your API key.
On smash.gg, log in and go to your developer settings.
Create a new token and set the description to something you can remember later (e.g. “Discord Bot”)
Copy down the token somewhere safe. Smash.gg does not let you view it again, and if you lose it, you’ll have to make a new one.
In .env, make a new line, type in “smashggapi=” and paste in your token.

The file should now look like this:

token="bottoken"
id="botid"
challongeapi="challongeapikey"
smashggapi="smashggtoken"

Adding YouTube API keys

YouTube require API keys for any command that needs data from YouTube, (i.e. play)
You may skip this section if you aren’t using this bot for music purposes, but some commands will not function if you do.

Head to the Google Cloud Platform and create a new project.
- If you haven’t used this platform before, accept to the terms and conditions and create a new project by pressing “CREATE PROJECT”.
- If you have and have already made a project, press the dropdown menu next to the Google Cloud Platform logo, then press “NEW PROJECT” in the top right corner.
Name this project whatever you want.
Using the search bar, go to YouTube Data API v3 and enable it.
Press the “CREATE CREDENTIALS” button on the right, select “YouTube Data API v3” and Public Data.
Copy the API key given to you, go to .env, type in “ytapi=”, and paste in your key.
- If you lose this key, you can go to “APIs and Services”, “Credentials”, “API Keys”, and copy the key.

The .env file should now look like this (If you’ve been following along with all prior steps):

token="bottoken"
id="botid"
challongeapi="challongeapikey"
smashggapi="smashggtoken"
ytapi="ytapikey"

Adding YouTube cookies

While this isn’t required, you may recieve a 429 error code. Click here for more info.

Open a web browser and go to YouTube
- You can do this with an account, but do note that doing so will allow users to play any private / purchased videos you have access to.
Open up dev tools
- On Chrome / Chromium, this is CTRL+SHIFT+J, or CMD+OPT+J on Mac.
- On Firefox, this is CTRL+SHIFT+I, or CMD+OPT+I on Mac.
Go to the Network tab.
Click on any request.
- On Chrome / Chromium, this is one of the items listed under “Name”.
Go to the Headers tab if you aren’t there already.
Scroll down to “Request Headers”
Find the “Cookie” header and copy everything.
Go to .env, type in “ytcookie=”, and paste in your cookie value.
- It should look like this: "key1=value1; key2=value2; key3=value3"

The .env file should now look like this (If you’ve been following along with all prior steps):

token="bottoken"
id="botid"
challongeapi="challongeapikey"
smashggapi="smashggtoken"
ytapi="ytapikey"
ytcookie="ytcookie"

IF you’re still experiencing 429 issues: Please note that this may not come into effect until a few days later. This is an issue with YouTube and can not be fixed. You may try to use a VPN or different IP address if you’re self-hosting.

Running it, finally

If you’re on repl.it, press the Run button.
If you’re on node.js, run node index.js in your command prompt/terminal (make sure the current directory is the same one as the bot’s directory)
You’re done! (At least, if you don’t want UptimeRobot)

Regarding UptimeRobot

UptimeRobot is a “pinging service”, meaning it pings a service (like a website, or a discord bot) every 5 minutes. This was implemented as this bot was hosted on repl.it, which previously was a requirement. As of 2/2/2021, however, this is no longer the case if you pay their subscription. You also don’t need this service if you’re running it on any other platform. If you want to use this service, read “Configuring UptimeRobot”. If you don’t, you can simply ignore it. You can also set HostWeb to false in config.js if you want to save resources.

Configuring UptimeRobot

On the upper right corner, a website will show up with the current date and time. Copy its URL.
On UptimeRobot, add a new monitor.
Set the monitor type to HTTP(s), set the friendly name to anything you want, and set the URL to the one you copied.
Anddd now you’re done!

Licensing and Legal Disclaimers

This bot is completely public domain and can be used by anyone for any purpose. For full disclaimers, please read legal.txt.