Bridge [ Talk In-game From Discord ]

Bridge connects your Necesse server to a Discord channel. And optionally, Discord messages appear in-game.

[hr][/hr]

What It Does

Game ➜ Discord

• 🟢 Server online / 🔴 Server offline notifications
• Player joins and leaves, with current player count and session playtime
• Player chat relayed to Discord
• Player deaths
• Achievement unlocks
• Daily activity report — who is online and when offline players were last seen

Discord ➜ Game (optional, requires a Discord bot)

• Discord messages appear in-game as [noparse][Discord] username: message[/noparse]
• Type !players in Discord to see who is currently online

Scheduled Reboot Warnings (optional)

• Warns players before your server's scheduled auto-reboot — in game chat and in Discord
• The countdown is tied to server start, so it re-syncs itself after every reboot
• Warn as many times as you like, e.g. at 30 minutes, 10 minutes and 1 minute

[hr][/hr]

For Players

Nothing to do! The mod runs entirely on the server — you do not need to install it yourself.

[hr][/hr]

Setup for Server Admins

The mod automatically creates bridge_config.txt in your server root on first launch. Fill in only what you need — everything is optional.

Mode 1 — One-Way (Game ➜ Discord)

[olist] [*] In Discord: channel settings ➜ Integrations ➜ Webhooks ➜ New Webhook ➜ Copy Webhook URL [*] Open bridge_config.txt and paste it:

WEBHOOK_URL=your-webhook-url[/code]
[*] Start the server — events appear in Discord immediately
[/olist]

[h2]Mode 2 — Two-Way (Game ⬌ Discord)[/h2]

[b]Step 1 — Create a bot[/b]
[olist]
[*] Go to discord.com/developers/applications
[*] New Application ➜ Bot ➜ Reset Token ➜ copy the token (this is your BOT_TOKEN — keep it private!)
[*] Under Privileged Gateway Intents, enable [b]Message Content Intent[/b] ➜ Save
[/olist]

[b]Step 2 — Invite the bot to your Discord server[/b]
[olist]
[*] Go to OAuth2 ➜ URL Generator
[*] Scopes: [b]bot[/b] — Permissions: [b]Read Messages[/b] + [b]Send Messages[/b]
[*] Open the generated URL and invite the bot
[/olist]

[b]Step 3 — Get your channel ID[/b]
[olist]
[*] Discord Settings ➜ Advanced ➜ enable [b]Developer Mode[/b]
[*] Right-click the target channel ➜ Copy Channel ID
[/olist]

[b]Step 4 — Fill in bridge_config.txt[/b]
[code]WEBHOOK_URL=your-webhook-url
BOT_TOKEN=your-bot-token
CHANNEL_ID=your-channel-id

Discord messages appear in-game as [noparse][Discord] username: message[/noparse]. Messages over 200 characters are trimmed automatically.

Activity Report (optional)

A daily embed listing online players and when each offline player was last seen. Create a second webhook in any Discord channel and add it:

ACTIVITY_WEBHOOK_URL=your-activity-webhook-url[/code]
The embed sends once per day. If the server restarts, it picks up where it left off and fires at the right time automatically.

[h2]Reboot Warnings (optional)[/h2]

If your server auto-reboots on a schedule, Bridge can warn players before it happens — in game chat and in your Discord channel.
[code]REBOOT_CYCLE=6h
REBOOT_WARNINGS=30m, 10m, 1m
REBOOT_MESSAGE=Server will auto reboot in {time} - please plan accordingly

REBOOT_CYCLE — how often your server reboots. Accepts 6h, 5h 50m, 90m, 30s. REBOOT_WARNINGS — how long before the reboot to warn, comma separated. REBOOT_MESSAGE — what players see. [noparse]{time}[/noparse] is replaced with the time remaining, e.g. "10 minutes".

With the settings above, a server rebooting every 6 hours warns players 5h30m, 5h50m and 5h59m after it starts. The countdown begins at server start, so it lines itself back up after every reboot — there is no clock or timezone to configure.

Leave REBOOT_CYCLE blank to turn this off. Note that Bridge only announces the reboot — restarting the server is still handled by your own script or host panel.

[hr][/hr]

Troubleshooting

• Nothing in Discord — check WEBHOOK_URL is correct and bridge_config.txt is in the server root folder (same folder as Server.jar)
• Discord messages not showing in-game — check BOT_TOKEN, CHANNEL_ID, and that Message Content Intent is enabled on your bot
• Console shows HTTP 401 — bot token is wrong or was reset; generate a new one in the Developer Portal
• Console shows HTTP 403 — bot lacks permission to read the channel
• Reboot warnings not firing — the console prints the schedule at startup. If it says a duration is invalid, check the format: use 6h or 5h 50m, never a bare number like 90. Each warning must also be shorter than REBOOT_CYCLE
• Temporary Discord outages and rate limits are handled automatically and silently — if the console shows a Bridge error, it needs your attention