Setup
Proxy & networks
Run one bridge across a BungeeCord or Velocity network — with or without backend installs.
DiscordSynthesis runs natively on BungeeCord and Velocity, and it also supports a hybrid mode where Spigot backends forward everything through the proxy.
Which setup do I want?
| Setup | Install on | Best for |
|---|---|---|
| Proxy-only | The proxy | The simplest network bridge — chat, links, events, reports for the whole network. |
| Proxy mode | Proxy and each Spigot backend | Networks that want Spigot-only extras (advancements, interactive item sharing) relayed through the proxy. |
Proxy-only
Install DiscordSynthesis on the BungeeCord or Velocity proxy and configure it there. Backends run nothing. This covers cross-server chat, account linking, join/leave, deaths, reports, and server-switch tracking.
Proxy mode (proxy + backends)
Install the plugin on the proxy *and* every Spigot backend. On each Spigot server, set proxy mode on so it forwards to the proxy instead of talking to Discord directly.
# SPIGOT ONLY — forward everything to the proxy
proxyMode: true
# This server's identifier on the network
serverName: lobbyNote
serverName must be unique per backend and is what you reference in per-server channels and nicknames.
Per-server channels
Route each backend to its own Discord channels by enabling per-server channels and listing overrides in channels.yml.
perServerChannels: trueThen add a serverChannels block per server — see Channels.
Network options
serverNicknamesdefault: {}- Pretty display names per server id, e.g.
lobby: 'Cool Lobby'. Used in logs and messages. blacklistedServersdefault: []- Servers excluded from chat sync and command log entirely.
hiddenServersdefault: []- Servers whose players are hidden from the player count, bot status, stat channels, and
/players— events are still logged. Good for test/staff servers. perServerChannelsdefault: false- Turn on to route each server to its own channels via
serverChannels.
Shared database
For links and reports to work network-wide, point every server and the proxy at the same MySQL/MariaDB database. See Database.