Configuring
The fun part!
Last updated
Was this helpful?
The fun part!
Last updated
Was this helpful?
Your old config will be automatically converted to json5 the next time you run the bot.
Let's start off by opening the bot
folder. This folder contains a file called _config.json5
.
Now open that config file in your favorite file editor. If you don't have one installed I recommend visual studio code (). You should see a file that looks almost identical to the one included below.
Let's start by pasting that token you got earlier into the tokens.discord field. I want to once again reiterate the importance of keeping that token secret. If you accidentally share that token anyone with access to it can log in as your bot.
change the id "286224826170081290"
in the owners array to your discord id.
change the clientID "592814450084675594"
to your bots discord id
change devServer from "devServerId"
to the id of your private server which you want the owner only commands on
add the server invite to the devServerInvite field
Thread-Watcher comes with 4 types of responses which all have their own style. You'll see these represented as "error"
, "success"
, "info"
, and "warning"
in the config file.
You can set the colour property to any valid colour hex and the emoji to either a valid utf-8 emoji representation or a discord emoji from any server your bot is in. A discord emoji represented as text looks something like <:statusinfo:960960247571300353>
Right now there's 2 supported databases that work with Thread-Watcher. Those 2 are mysql and sqlite3. If you anticipate that the guild count of your instance will be small I recommend you use the sqlite3 database as it is far easier.
set database.type
to DataBases.sqlite
You're done! ๐
create a database called threadwatcher
create a new user with read and write access to that database (or use an existing one)
change database.user
to the username of the database user
change database.password
to the password of the database user
change database.host
to your database ip. (127.0.0.1
if hosted on the same computer as the bot)
change database.port
to the port of your database. For mysql this is normally 3306
statsServer is used to make your bots stats available over the . Unless you are also hosting a website for your instance this is likely not of interest to you. You can disable it by setting statsServer.enabled
to false