Ember Plugins · Free proxy plugin

Ember Bridge

Only works with Ember Essentials

Bridge relays a small private protocol that only Ember Essentials speaks. Put it on the proxy, run Ember Essentials on every backend, and the network features switch on. Backends without Ember Essentials are ignored: nothing breaks, nothing happens.

The proxy half of a network.

FreeVelocityBungeeCordJava 25One jar, both proxiesNo databasePairs with Ember Essentials

Get Ember Bridge

What it is

One jar for either proxy. Drop it into a Velocity or BungeeCord plugins/ folder. Each proxy reads its own manifest and ignores the other's, so there is one download and nothing to choose.

Chat, messages, requests and the list, across servers. Chat lines arrive with a prefix saying where they came from. /msg and /r find people on any server and confirm delivery rather than guessing. /tpa carries the request across and waits for consent there. /glist shows everyone, grouped by server; /server switches; tab completion suggests names from the whole network.

Nothing to run. No database, no open port, no password. Everything travels on the plugin message channel the game already has between a proxy and its servers. The one cost is that a message can only leave a server while somebody is on it - which for chat is exactly right.

Free, and only useful with Ember Essentials. The bridge speaks to Ember Essentials on the backend servers and to nothing else. Its value is in Essentials; charging for the other half would be charging twice.

Setting it up

1. Put EmberBridge.jar in the proxy's plugins/ folder and restart the proxy.
2. On every backend server, in Ember Essentials' config.yml, set cross-server-chat.enabled: true and give each server a cross-server-chat.server-name. That name is the chat prefix, and it is also how a home remembers which server it is on.
3. Restart the backends.

The usual proxy prerequisites still apply and belong to the proxy's own documentation: online-mode=false on the backends, modern forwarding with a matching secret on Velocity, and nothing able to reach the backend ports directly.

Bedrock players need two more settings or their chat is silently blocked: force-key-authentication = false in velocity.toml, and enforce-secure-profile=false in every backend's server.properties.

Homes, warps and money

Those cross too, but not through the bridge. They are data, not messages, and the bridge deliberately carries no data. Ember Essentials' shared database does that job; the bridge only moves the player when a home or warp is on another server. See Proxy networks in the Essentials documentation for the whole picture, including the storage settings.

Compatibility

Proxies	Velocity 3.3+ (Java 25), BungeeCord and Waterfall 1.21+
Backends	Ember Essentials on Paper, Purpur or Folia 26.2+
Bedrock	Chat, messages and teleports work through Geyser; tab completion does not reach Bedrock, which is Geyser's limit, not ours
Other proxy plugins	Uses its own ember:bridge channel and the proxy's legacy BungeeCord channel; does not touch anyone else's

Commands

The bridge itself adds no commands. /glist, /server, /msg, /r, /tpa and the rest belong to Ember Essentials and simply start reaching across servers once the bridge is present.

License

Free, for any server. Redistribution as part of another product is not permitted; linking to the download is.

Listing image

A single tall image with everything on this page, for store listings: ember-bridge-listing.jpg. It is regenerated whenever features change, so the link stays the same.