uxmEssentials-Velocity

What it does

uxmEssentials keeps cross-server state consistent over a small "this changed" bus rather than shipping full payloads around the network. This add-on is the Velocity transport for that bus: drop it on your proxy and the backends relay their sync notices through it over plugin messaging no Redis required.

When a player sets a home, deposits money, edits a vault, or trades across servers, the origin publishes a short notice; every other backend drops its cached copy of that row and re-reads the authoritative value from the shared database. The database stays the single source of truth, and a change never travels as a full object.

What stays in sync

Homes, warps, player-warps, economy, vaults, trade, vanish, moderation, holograms, NPCs, the vote party, and the messaging ignore list every context uxmEssentials replicates across nodes that share one database.

Setup

1. Drop uxmEssentials-velocity-0.8.0.jar into your Velocity plugins/ folder.

2. On each backend, pick the transport in plugins/uxmEssentials/config.conf:

   network {
     enabled   = true
     server-id = "survival-1"   # unique per backend
     transport = "velocity"     # velocity | redis | both
   }
   

3. Start the proxy and the backends. The bus comes up automatically; with no proxy, Redis, or peer present it falls back cleanly to local-only, so single-server behaviour never changes.

Requirements

• Proxy: Velocity 3.x with this add-on installed.
• Backends: Paper 26.2 running uxmEssentials 0.8.0, all sharing one database (SQLite is single-writer use MySQL / MariaDB / PostgreSQL for a real network).
• Main jar required this add-on does nothing on its own; it is the transport for uxmEssentials.

Notes

Open source (GPL-3.0). You only need this jar if you run a Velocity network and want cross-server sync without Redis. For a proxy-less setup, use the Redis add-on instead the same bus, a different transport.