Bind a server to Discord

Binding a server to a Discord guild is meant to turn on three things, and the panel's own "bound" label names all three: a chat bridge (messages relay both ways between the server and a channel), a /whitelist slash command your Discord members can use, and a /status command. /whitelist and /status work as soon as you're bound — the chat bridge doesn't, until a bridge channel is actually picked; see below. Any account member with access to the server can set this up — it isn't owner-restricted the way Members or Wallet are.

Binding a guild

Click Generate code — it's a short-lived, single-use pairing code with a live countdown. Invite the bot to your Discord server (the panel's own link, when configured, opens Discord's bot install flow), then in that guild run /setup code:XXXX-XXXX before the code expires.

Running /setup requires the Manage Server permission in that Discord guild — if nobody with that permission runs it, nothing binds. /setup opens a config view inside Discord itself (also Manage-Server-gated) where you pick a server, then separately the bridge channel, and optionally which Discord roles beyond Manage-Server holders can use /whitelist; there's no equivalent picker in the panel — the whitelist role count shown here is read-only.

Picking a server alone does not turn the chat bridge on. Until you also pick a bridge channel, Discord's own config view says so plainly — "bridge off (no chat relay)" — right where the channel would otherwise be named. /whitelist and /status already work at that point; only the chat relay is waiting on a channel.

The "Add App" gotcha. Discord's own Add App button on the bot's profile installs it with the app's default install settings, which can add slash commands to a guild without actually adding the bot as a member of it. /setup then appears to work but the bridge has nothing to post through. Use the panel's own invite link (it explicitly requests the bot scope) rather than "Add App" from Discord's UI, and if commands show up but chat never bridges, check whether the bot is actually listed as a member of the guild.

What's bound, once it's bound

The tab shows the guild ID, the bridge channel (or "not set" if /setup hasn't picked one yet), and how many Discord roles are allowed to use /whitelist beyond Manage Server holders (0 by default — Manage Server always works regardless). The chat bridge also posts a note when the server goes to sleep and when it wakes back up, not just player chat — useful if your community doesn't otherwise know the server is metered and scale-to-zero. A message sent from Discord while the server is asleep isn't silently lost — it gets a 💤 reaction in Discord instead, so the sender knows it didn't reach anyone; a broken binding reacts with ⚠️ instead.

A binding can show "Bridge broken — re-run /setup in Discord" instead of the normal bound state. That means the bridge lost the ability to post to the channel — commonly the bot was removed from the guild or lost access to the channel — and the fix really is just running /setup again once that's corrected.

Unbinding

Unbind on this tab removes the binding immediately, with a confirmation first. The chat bridge, /whitelist, and /status all stop working for that server in Discord the moment you do — running /setup again is the only way back.

Troubleshooting

Bot has slash commands in my guild but chat never bridges. Two different causes produce the exact same symptom, and it's worth checking both: (1) most likely, /setup bound a server but never had a bridge channel picked — check Discord's own config view for "bridge off (no chat relay)", or this tab for "not set", and pick a channel. (2) The bot was installed via "Add App" defaults and isn't actually a member of the guild — see the gotcha above; re-invite it through the panel's link and run /setup again.

/whitelist says I'm not allowed. You need either Manage Server in that guild, or one of the specific Discord roles the guild's /setup config granted — the panel shows how many roles are configured but not which ones; ask whoever ran /setup (they can re-run it to check or change the role list).

Status shows "Bridge broken." The bridge can no longer post to the configured channel — check the bot's still in the guild and can see that channel, then re-run /setup.