Deploy and Host hypixel-chat-bridge on Railway

hypixel-chat-bridge connects Hypixel guild chat to Discord. Members talk to in-game players from a Discord channel, and the bot posts guild events and answers SkyBlock stat commands. One deployment can run several guilds and relay chat between them. You configure everything with /setup in Discord.

About Hosting hypixel-chat-bridge

You run one always-on service: a Discord bot plus one Minecraft account per guild. On first start the bot DMs you a Microsoft sign-in code for each account, then stores the login tokens so redeploys don't ask again. The bot keeps its settings, links, blacklist and tokens in SQLite on the attached Volume. Set DATABASE_URL to use MongoDB or Postgres instead. To deploy, you need a Discord bot token, your Discord user ID and the ID of the channel to bridge. Add a Hypixel API key to turn on stat commands, join requirements and GEXP tracking.

Common Use Cases

Chat with in-game guild members from Discord, shown as webhook, embed, plain text or Minecraft-style images
Run two or more Hypixel guilds from one bot with a shared chat
Screen join requests against requirements and a blacklist, with a waitlist for a full guild

Dependencies for hypixel-chat-bridge Hosting

A Discord bot with the Message Content and Server Members intents turned on
A Minecraft account for the bot. Hypixel can ban bot accounts, so use an alt.

Implementation Details

Required variables: DISCORD_TOKEN, OWNER_ID, GUILD_CHANNEL_ID. The template mounts a Volume at /app/data for the database and caps Node's heap at 256 MB with NODE_OPTIONS. Add guilds in /setup → Accounts or with ACCOUNT_2_GUILD_CHANNEL_ID. Docs: https://github.com/treeot/hypixel-chat-bridge

Why Deploy hypixel-chat-bridge on Railway?

Railway builds the repo's Dockerfile and keeps the bot running, restarting it if it crashes. The Volume keeps your data and Minecraft logins across redeploys, and the template asks for just three variables.