
uxmEssentials Redis
The Redis transport for uxmEssentials' cross-server bus, keep homes, warps, economy, vaults and more in sync across your network over Redis pub/sub, no proxy needed. Requires the uxmEssentials plugin.
- Загрузки
- 2
- Подписчики
- 0
- Обновлён
- 27 июня 2026 г.
- Лицензия
- GPL-3.0-only
Опубликован 27 июня 2026 г.
uxmEssentials Redis add-on
The Redis transport for uxmEssentials' cross-server bus keep homes, warps, economy, vaults, and more in sync across a network over Redis pub/sub, with no proxy required.
Paper 26.1.2 · Java 25 · Folia-ready · Companion to uxmEssentials · Open source (GPL-3.0)
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 Redis transport for that bus: point it at a Redis server and a plain set of backends sharing one database and one Redis instance sync directly, with no Velocity proxy in the middle.
When a player sets a home, deposits money, or edits a vault on one server, the origin publishes a short notice over Redis pub/sub; 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, moderation, holograms, NPCs, the vote party, and the messaging ignore list every context uxmEssentials replicates across nodes that share one database.
Setup
Drop
uxmEssentials-redis-0.3.0.jarinto each backend'splugins/folder, alongside the main uxmEssentials jar.Point uxmEssentials at your Redis server and pick the transport in
plugins/uxmEssentials/config.conf:network { enabled = true server-id = "survival-1" # unique per backend transport = "redis" # velocity | redis | both redis { host = "127.0.0.1" port = 6379 password = "" db = 0 channel = "uxmessentials:bus" } }
Ченджлог
0.3.0Альфа26.1.2, 26.2 · 27 июня 2026 г.
The Redis transport for uxmEssentials' cross-server bus.
Point network.redis at a Redis server and set network.transport = redis (or both)
in the main plugin every backend sharing one database and one Redis instance then stays
in sync over Redis pub/sub, no Velocity proxy required.
Keeps these in sync across nodes: homes · warps · player-warps · economy · vaults · moderation · holograms · NPCs · the vote party · the messaging ignore list.
- A write publishes a small "this changed" notice; peers drop their cache and re-read the authoritative row the database stays the single source of truth.
- Folia-ready: all Redis I/O runs on its own Netty event loop, off any region or tick thread.
Requires: the uxmEssentials plugin (Paper 26.1.2) and a reachable Redis server.
Комментарии
Загружаем…