StaffLink Pro

Installation

StaffLink Pro installs on every backend server (the Spigot/Paper servers behind your proxy) — not on the proxy itself. Cross-server chat travels over the proxy's plugin-messaging channel, so the plugin only needs to be present where your staff actually play.

1. Add the plugin

  1. Download the latest StaffLinkPro.jar from the releases page.
  2. Drop it into the plugins/ folder of each backend server.
  3. Start the server once to generate the default config.yml, then stop it.
Install on every server

For cross-server chat to work, the plugin must be on every backend server that staff use, and each one must share the same messaging channel (see below).

2. Enable proxy messaging

StaffLink Pro uses the proxy's plugin-messaging bus to relay chat between servers.

BungeeCord / Waterfall

Enable BungeeCord mode in each backend server's spigot.yml:

settings:
  bungeecord: true

Velocity

Use modern player-info forwarding. In Velocity's velocity.toml:

player-info-forwarding-mode = "modern"

And in each backend server's paper-global.yml (Paper) set the proxy secret to match Velocity's forwarding.secret. Plugin messaging is enabled by default on Paper.

3. Match the channel on every server

Open config.yml on each server and make sure the messaging channel is identical everywhere:

messaging:
  channel: "stafflink:staffchat"
  enabled: true

Then give each server a unique name so messages are labelled correctly:

server:
  name: "Survival"        # unique per server: lobby, survival, skyblock, ...
  display-name: "Survival"
Single server?

Running just one server with no proxy? StaffLink Pro still works — the staff channels, Discord bridge, SocialSpy and logging all run locally. Cross-server features simply have nothing to link to.

4. Start up and test

  1. Start all backend servers.
  2. Join with a staff account (ops have every permission by default).
  3. Send a message with /staffchat hello on one server and confirm it appears for staff on another.
  4. Run /staff to see the network-wide online staff list.

If messages stay local, re-check that every server shares the same messaging.channel and that BungeeCord/Velocity forwarding is enabled.

Optional integrations

Install any of these on the backend servers to unlock the matching features: