items/, glyphs/ and pack/assets/, changed by hand on each
server every time you add an item.
NexoHub moves those files onto the proxy. You edit them in one place, every backend
picks up the change and reloads, and players download a single shared pack.
What you get
One place to edit
Change a file on the proxy and save. Every backend pulls it and reloads within
seconds, without a restart or a per-server edit.
One pack, one download
Players download the pack once, not once per server. Switching servers does not
re-download it.
Nothing broken gets sent
A file with a mistake in it never reaches your servers. Past versions are kept, so
one command undoes an edit.
Disposable backends
A backend keeps nothing of its own, so retiring one means stopping it.
Works with your other plugins
BetterHUD, ModelEngine and BetterModel keep working, even when different servers
use different HUDs and models.
One command to check it all
/nexohub doctor tests the address players are handed, the state of every backend,
and whether they will build the same pack.How it works
Your files live on the proxy in three layers._shared/ goes to every backend,
groups/<name>/ to the backends you list, and servers/<name>/ to one. A server that
needs one thing different gets it without a second copy of everything else. See
managing your files.
Each backend still builds the pack itself, which takes a few seconds on boot. The first
one to finish uploads it and the rest skip.
Backends hear about a change as it happens, and ask on a timer too, so a server nobody
is on does not sit on old files.
Two plugins
Install one proxy jar, not both. They are the same hub with a different plugin
descriptor, so nothing else on this site depends on which proxy you run.
Do you still need NexoProxy?
Yes. Keep it. NexoHub does a different job and replaces no part of it.
NexoHub does work without NexoProxy. Every server hands out the same link, so the
client already has the file and will not download it a second time. It still gets sent
the pack on each switch, though, and stopping that is NexoProxy’s job.
Start with the quickstart. If you already have Nexo running on several
backends, read moving an existing network instead.