How to sync player data across regions in a multi-region network

Multi-region networks let a player transfer between regions in one session. What they don't do is carry that player's data along: inventory, ender chest, advancements, permissions, economy balances — none of it travels with them. A player who transfers from your EU region to your NA region arrives with whatever that NA region's own servers already have on file for them, not what they were just holding in EU.

This isn't a bug or a missing checkbox in the panel — there's no database shared between regions today for a config toggle to point at. Each region's servers are their own independent set of worlds and player records, the same way two unrelated servers would be.

Why this doesn't get fixed by flipping a setting

A truetick network spans regions by giving each region its own proxy and its own backends (see Multi-region networks). There's no platform-run database connecting those regions' backends to each other — building and operating one is a real piece of infrastructure, not a flag we could turn on. So today, syncing player data across regions is something you set up yourself, on top of the network, using a plugin and a database you control.

The mechanism: a sync plugin plus your own database

The class of plugin this needs is usually called a cross-server data-sync plugin — it hooks into a server's inventory/ender-chest/stats events, writes them to a shared database on save or on disconnect, and reads them back when a player joins a server pointed at the same database. Point every backend across every region at the same database, and a transferring player's data follows them because the plugin — not the network — carries it.

One example of this class of plugin is HuskSync (checked 2026-08-17): its own description calls it "the modern, cross-server player data synchronization system," syncing inventories, ender chests, advancements and more across a Velocity network of Paper/Fabric servers, backed by Redis and a MySQL/MariaDB/Mongo/PostgreSQL database (the project's own listed options). We're naming it because it's a real, checkable example of the class — not a recommendation, and not something we've tested end-to-end ourselves. Search for it (or any alternative) the same way you'd search for any other plugin, from the Plugins tab on each backend — see Install plugins and mods.

Why this works on truetick: outbound connections from our nodes aren't blocked, so a plugin on one of your backends can reach a database that lives anywhere — your own VPS, a managed database host, whatever you point it at. We don't do anything to get in the way of this; we also don't do anything to make it easier than "install the plugin, configure it."

What we don't do

• We don't host the database. Standing up and running one is on you — your own VPS, or an external database provider.
• We don't install or support the sync plugin. It's a normal plugin install like any other; troubleshooting its config, its compatibility with your core and Minecraft version, and its own database schema is between you and the plugin's own documentation.
• We don't guarantee compatibility. A plugin built for Paper may not work on Purpur, Fabric, or whatever core you're running, and plugin compatibility across Minecraft versions is the plugin author's territory, not ours.

On timing

We haven't measured sync latency, so we're not going to give you a number for it. It depends on where you host the database (a database near your regions responds faster than one on the other side of the world), and on the plugin's own settings — not on anything the truetick platform controls. In broad terms, this class of plugin syncs data around the moment a player disconnects from one server and connects to the next, not on some separate schedule.

Steps, in order

1. Stand up a database the plugin can reach — a MySQL/MariaDB-style database on your own VPS, or a managed database from an external host. It needs to be reachable from the internet (or specifically from our nodes' outbound traffic), with credentials you control.
2. Install the sync plugin on every backend, in every region, that you want data to follow players between — from the Plugins tab, same as any other plugin (search the catalog, or upload the jar yourself).
3. Point the plugin's config at your database — the same database, same credentials, on every one of those backends. This is where the plugin's own setup docs take over; we don't have a truetick-specific step here because there isn't one.
4. Restart each backend so it picks up the new plugin and config — like any other plugin install, it doesn't apply until the next start.

From there, a player who transfers between your regions keeps their inventory, ender chest, and whatever else the plugin covers — because the plugin is carrying it, not the network.