Just wanted to note that if you're using localhost to run the bot, you'll have to launch the server with the -allowlocalhttp parameter (see this note in the docs [wiki.facepunch.com] ).

Burn it down to the ground and consume the ashes and shat it out for nature to collect it and remove it's remaining particles.

Okay, some heads up. I'm working on a v2 of the Discord Muter. I'm not sure when it'll be ready, so you should still use this one, but my proposed feature list looks a little like this...

- A Centralised Bot, in Discord Bots - Basically, one of the main aims of Discord Muter 2.0 will be to get rid of the "Setup your own bot" part of the instructions. The bot will still be open source, so that you can host your own if you care. This is because it's the issue I'm asked about the most, by far.
- More options with the Bot in the Discord channel - Obviously we're going to need a level of security, so the two way Auth code will move to the bot.
- Move to Dead Player Channel, not just mute - I've looked into it, it's entirely doable - Thanks Jackson1, awesome idea.

Anyway. If anyone has any other features they'd like to see from v2.0, let me know, I'm happy to add it to the list. Obviously the primary features come first, but new features can always be added as I go along.

No worries, thanks for getting back to me!

Sorry @jackson1, I thought I'd replied to this ages ago.

I'm going to look into adding a mechanism that would move the players to a different channel when they died. That's the only mechanism that would allow dead players to talk. This is a limitation of Discord.

Feel free to join the Discord Server [discord.gg] if you want to discuss it further.

Awesome, thanks! I just think it would work a bit more like the native GMOD TTT voice chat that way, with dead players still being able to talk to each other instead of sitting on mute for 5 minutes. Cheers!

@LuckyTiger, can you join the discord help channel, and I'll try to help walk you through it.

@Jackson 1, I can certainly look into it. I've not thought of that before, but I can look at how the API for Discord.js works, and see if it supports moving players to new rooms. Feel free to join the discord channel, or watch the GitHub repo for updates.

Thanks for the addon, gonna try this out soon as I couldn't get Marcel's version to work. Do you think instead of muting players, it would be possible to move them from one voice channel to another? i.e. The server sets up a "Dead" channel, and once killed, the bot moves them from main chat to "Dead" and then back again once the round ends. I know it's probably a lot of work to make it happen (plus Discord would give an audio alert when a player leaves/rejoins, but could be disabled manually), but it would be cool to have the option to either mute or move, maybe as an additional convar or something.

How do you add "heroku/nodejs" buildpack? I'm on step 4 and have it connected to my GitHub but I don't quite understand how to add the pack.

@Aleuvian Very strange. If you get a moment, can you jump on discord to work through it with me?

I'm having issues getting this working for TTT2. It works through ULX, but the bot doesn't seem to be detecting when the round ends.

The port should be either ":443" (if you're using a secure connection, with HTTPS), or ":80" (if you're using an insecure connection, with HTTP). When you setup the bot, it should show you in settings if you're using HTTP or HTTPS, as part of the domain. (see here: https://i.imgur.com/VWXnNYC.png . You can see this by going to https://dashboard.heroku.com/apps , clicking your bot's name under Production, then going to Settings).

If you're struggling too, feel free to drop into discord, and I'll try to give you some one-on-one support: https://discord.gg/yg6KJ8c .

Well, the address is "sorta" correct. I added the :433 at the end because I'm not sure what my address number should be.

@a very organized kuno: The two things that can cause that are if you don't have the right address for the bot in (eg: https://my-discord-bot.heroku.com:433) , or you have a miss-match of the API Key's.

If you know that the bot address is correct, take a look at the output of the node bot. I added logging that should tell you if the bot is receiving a request, but has the wrong key.

Let me know if you're still having a problem. Let's see if I can write up an FAQ from your issue :)

I sorta got it working, but when I use the !discord command it says
"Request to bot failed. Is the bot running?
Err: invalid url"

Oh sweet thanks! This is actually incredibly helpful!

@YourFrostyFriend, yeah, that's exactly what it does. You've then got the choice of them being muted for a few seconds (`discord_mute_duration`), or being muted until the round ends (`discord_mute_round`).

Got a quick question, would this happen to mute someone in TTT automatically as soon as they die?

This is exactly what I was looking for! Awesome. Thanks a lot.

Pretty cool!