Another Minecraft-Discord Bridge
AMCDB is a Fabric/Quilt mod to connect your Minecraft server to a Discord
server. You can connect in-game chat to a Discord channel, set up a channel
for the server console, and even run server commands from anywhere!
Here's what it looks like in Minecraft...
...and here's what it looks like in Discord!
In case you prefer to see in-game messages in Discord appear to come from
players (and see their player heads as avatars!), AMCDB supports Discord
webhooks as well:



Follow these steps to set up AMCDB on your server.
Note: you'll need to be an admin of the Discord server you want to connect.
You need a Fabric or Quilt server. Once you have that set up, make sure
Fabric API is in your mods folder -
that's the one dependency AMCDB has.
Then, grab the latest AMCDB .jar file from
GitHub Releases
or Modrinth. It'll be something like amcdb-1.1.6.jar.
Put that in your mods folder.
Next, start up your server. It will crash -- that's just because you haven't
configured AMCDB yet. Now that you've started the server once, there should be
a file called amcdb.properties inside your config folder. Open that file in
your text editor and keep it around for the next step.
If you've used a different Minecraft-Discord mod before, you might already
have a bot. You can reuse it as long as it has the right permissions on your
server - just put the token in the amcdb.properties file.
If you don't have a Discord bot:



amcdb.properties file you opened earlier, find the line that startsamcdb.discord.bot.token= and paste your bot token on the end of thatamcdb.discord.bot.token=MTA2OTdyNTM0NzUxMyQ0MjMyNA.GYMgJ0.cvrf8Ah0jFQ8MtGQHsgDh2MrT_Iq8-56EUbm0c


bot option. Another box labeled Bot
AMCDB has a lot of settings you can configure, but besides the bot token,
there's only one you need to get started -- you need to tell AMCDB the ID of
the channel you want to use for the in game chat. You'll probably want to
create a new text channel for this, since all the messages in that channel
will appear in Minecraft and vice versa.
To get the channel ID, enable Developer Mode in your Discord app. Open
the settings menu, then Advanced on the left. Then, turn on Developer
Mode.
Once Developer mode is turned on, you can right click on the channel you want
to use and click Copy ID. Paste that ID into amcdb.properties right next
to amcdb.discord.chat.channel=. It'll look like this:
amcdb.discord.chat.channel=1046313040837832782
If you want to set up a channel for the server console, copy its ID too and
paste it next to amcdb.discord.console.channel=. The console channel supports
running commands that you send via Discord; this feature is disabled by default
for safety, but you can enable it by changing the settingamcdb.discord.channels.console.enableExecution= to true.
Then save the amcdb.properties file and start your Minecraft server again.
If you've done everything correctly, anything you type in the game chat
should appear in the Discord channel, and anything you type in the Discord
channel should appear in your game!
Feel free to explore the rest of the amcdb.properties file, as that's where
all of the configuration settings for AMCDB live. If you change anything,
you'll need to stop and start your Minecraft server for the new settings to
take effect.
If you want to display Minecraft player heads as Discord avatars, you'll need
to enable webhook mode. This is optional -- AMCDB will work fine if you don't
set up a webhook.
To set up a webhook, follow these steps:
amcdb.properties next to amcdb.discord.channels.chat.webhookUrl=.# at the beginning.amcdb.properties file and restart your server. YouGenerally, you can upgrade AMCDB simply by replacing the .jar file with the
new version.
When you upgrade, it's a good idea to check whether new properties have been
added to amcdb.properties; you can find latest version of the default
configuration here. Occasionally, new
required properties are added; this will cause your server to fail to start
after updating the .jar until you add the new properties to your
configuration.
You can also update your properties file by forcing AMCDB to generate a new one:
amcdb.properties to a temporary name, e.g. amcdb.properties.old.jar file and start your server. AMCDB will generate a newamcdb.properties template, and the server will stop just like with a newamcdb.properties.old to the new amcdb.properties.amcdb.properties.oldamcdb.properties.