You've leaked your token

[BytewaveMLP]

Hey there.

It's come to my attention that you've leaked your bot token in your config file. You should regenerate this as soon as possible before someone does something malicious with it.

As a side note, it's a good idea to store your tokens in a file NOT tracked by Git or version control. You should provide a config.example.json and leave it empty save for some sane default settings, and put your actual config.json in .gitignore so Git refuses to track it. This won't fix your problem immediately, as you still have a public token in your repository, but it should save you the trouble going forward.

Sorry for the rude awakening by logging in with it earlier, but I hope it was an attention grabber. You could end up with nuked guilds or spammed ads if this was a public token, so it's a good idea to protect your tokens at all costs. I hope you understand.

[BytewaveMLP]

You've merely committed your new token; you haven't untracked config.json from git and added it to your .gitignore.

You'll want to regenerate your token again, untrack your config.json using git rm --cached, add it to your .gitignore, and commit your new .gitignore like I said.