ROMUnite.
Sign in

For Discord servers

More players for your server's games

The ROMUnite Network bot links your server to others that play the same games, retro or modern. When someone pings a role for a game, players on every linked server can answer, and they all end up in one chat.

Add to Discord How it works See both designs

What your server gets

Answers to every ping

Ping @Tekken and the call goes out to every server in the network that plays Tekken over the same connection method, plus ROMUnite's own players. Quiet nights stop being quiet.

One chat across servers

Everyone who answers ends up in one conversation, wherever they came from: in your channel or in a thread, whichever design you pick. What's said on your server shows on theirs and on ROMUnite, so a game gets organised in one place.

Events everyone can see

Make an event in Discord's Events tab and the bot offers to share it: it shows on ROMUnite and on other servers that play it, and interest counts the same everywhere.

You stay in charge

You choose which roles are linked to which games and whether your server sends, receives or both. Changes to a linked server wait for a moderator, and any server can be blocked.

Two ways invites can look

Each server chooses how invites from other servers show up there, in /network setup or on My servers, and can change it any time. Threadless and thread servers still reach each other: each sees an invite its own way.

Threadless (recommended)

Easiest for members; you may get fewer invites from other servers because a channel holds one conversation at a time.

Threads

Accept buttons and a thread per invite; handles several invites at once.

  1. 1 Someone pings a role

    Andrew pings @nfs on his own server, the way he always has. There's nothing else to press.

    # looking-to-play EA Hub Example

    • Andrew

      @nfs let's play

  2. 2 It arrives on another server

    On Retro Racers it's an ordinary message that pings the role they linked to those games. The grey line says who is calling, from where, and for which games. It has no buttons.

    # looking-to-play Retro Racers Example

    • ROMUnite Network app

      @racing let's play

      Andrew on EA Hub · NFS Most Wanted, Burnout 3 and 2 more

  3. 3 Someone answers and they talk

    Sam answers right in the channel. Everything said there reaches every server that got the ping, and Andrew's reply comes back under his name. While they keep talking, the link stays open.

    # looking-to-play Retro Racers Example

    • Sam

      I'm in for Most Wanted. Give me five minutes.

    • Andrew (EA Hub)

      Hosting now, room is ROM-NFS.

  4. 4 The link closes

    With 10 minutes left, Andrew's server gets a quiet warning. Only Andrew can press Extend, and a link lasts 3 hours at most. When it closes, every threadless server in it gets one grey line, and the threads and ROMUnite are told who's no longer connected. If nobody outside Andrew's server has joined, nobody needs to know: it closes without a word.

    # looking-to-play EA Hub Example

    • ROMUnite Network app

      The link to other servers closes in 10 minutes.

      Extend 30 min

    • ROMUnite Network app

      The link to other servers has closed.

Good to know

  • A channel holds one link at a time. While it's busy, invites from other servers skip it, and a ping made there stays on your server.
  • The first answer narrows the invite to the games that channel's role covers, on every server.
  • The bot stays quiet: apart from the warning and the closed line, members won't notice it's there.
  • An event made on a threadless server gets no chat thread there. Its chat is on ROMUnite and its Discord server, and opens by saying the host isn't in it, so nobody waits on them for an answer.
  • Someone who joins with Accept or on ROMUnite is heard everywhere saying “count me in”, with the host named, so nobody waits for them to speak. Leaving on ROMUnite is announced too.
  • A reply, made here, on another server or on ROMUnite, arrives as a reply everywhere, linked to the message it answers.
  • Talking keeps an invite open, wherever it's said: once it's down to its last 10 minutes, if anyone spoke in the last 10, it gets 10 more, up to 3 hours in all. A quiet invite closes on time.
  • An event's game room opens 10 minutes before it starts and stays open 75 minutes, longer than an ordinary invite's 30, here and on every server.

A good fit if

  • Your members ping roles to find opponents for games that are hard to fill.
  • You'd like your community to meet players from other servers.
  • You run events and want more people to see them.

Maybe not if

  • You want your server's pings to stay inside your server: then keep it to receiving only, or don't add it.
  • Your roles aren't about games or ways to connect, so there's nothing to link.
  • You'd rather not let messages from other servers into your channels or threads.

How to set it up

  1. 1

    Add the bot with the button above. Discord asks you to pick your server and confirm what it may do.

  2. 2

    Run /network setup. It walks you through linking each role to the games and connection methods it's for.

  3. 3

    Choose how invites reach you: threadless (plain messages in your channel, recommended) or threads (an Accept button and a thread per invite). Then choose whether your server sends calls out, takes them in, or both, and whether it shares events.

  4. 4

    Apply. A ROMUnite moderator looks it over, and the bot tells you when you're live.

  5. 5

    Then ping your roles as you always have. On a threadless server, a ping goes out for every game its role covers. On a thread server, if a role covers several games, the bot asks the person pinging which one, and they can save their answer as a preset.

It asks to read and send messages, start and post in threads, manage webhooks (so people show under their own names), and create and manage events (to show the network's events in your Events tab). It never reads anything outside the channels it's in.

Watch a server being set up

What an admin sees, from adding the bot to going live. It takes a few minutes.

Step 1 of 6

Add the bot

Press Add to Discord, pick your server and confirm.

discord.com Retro Racers Example

  • ROMUnite Network app

    Add ROMUnite Network to a server

    Pick the server, then confirm what it may do.

    Server
    Retro Racers
    Authorize

Snoozing and blocking

Threadless invites have no buttons, so moderators use one command for both designs. /network-moderate snoozes pings or every invite for a while, and blocks or unblocks servers that sent you invites in the last week. /network-snooze opens the same panel.

Snoozing is for moderators; blocking and unblocking need the Manage Server permission.

# mods Retro Racers Example

  • Mia used /network-moderate

    ROMUnite Network app

    Moderate the network

    Not snoozed. Invites from the network arrive and ping their roles as usual.

  • ROMUnite Network app

    What to snooze

    Pings only

    Invites still arrive, without pinging

    All invites

    No invites arrive

  • ROMUnite Network app

    Block a server that invited you this week

    EA Hub

Set it up by asking an AI assistant

Admins can skip the menus: connect Claude or another MCP app to ROMUnite and say what you want. It reads your server's roles and channels, finds the right games and connection methods, and makes the links.

  • “Show me my servers and how each one is set up.”
  • “Link @Racing to Burnout 3 and NFS Underground on PS2 over PCSX2 netplay.”
  • “Make my server receive calls but not send them, and share our events.”
  • “Apply my server to the network.”

Link your Discord account on ROMUnite so it knows which servers you run, make a token on Settings, MCP, and add ROMUnite to your assistant. Everything it changes is also on the My servers page.

Make a token My servers More about ROMUnite and AI assistants

What each permission is for

Discord lists these when you add the bot, and you can untick any of them. Each is used only for what it says here, so turning one off stops just that part.

View Channels Needed for anything
Seeing the channels you point it at. Without it, it can't post anywhere.
Send Messages Needed for anything
Posting invites and answering in the channels you choose.
Embed Links Needed for anything
Showing each invite as a card with the game, the open seats and the join buttons.
Read Message History
Checking whether its invite card is still the newest message, so a new invite joins that card instead of stacking up new posts.
Manage Webhooks
Relaying chat between your server, other servers and the site under each player's own name and picture, instead of everything coming from the bot.
Create Private Threads
A private room for each game that only the players who join can see. Not needed if your server uses the threadless design.
Create Public Threads
A chat thread under each event it copies to your server.
Send Messages in Threads
Talking in those game rooms and event threads.
Manage Channels
Making the multi-invite channel when you ask for one during setup. It's only used for that.
Create Events
Copying network events onto your server's Events list.
Manage Events
Keeping the events it copied up to date when their time or details change.