PlayerDataSync

# 🧩 PlayerDataSync

One player profile for your whole network.

Inventories, Ender Chests, XP, health, effects, attributes and economy follow your players to every server — automatically, safely, in the right order.

[!(https://faststats.dev/embed/default:5b846603-95f8-4e64-b64c-c5cb16879210:servers-and-players?w=800&h=300&theme=dark)](https://faststats.dev/project/playerdatasyncreloaded/minecraft-plugin)

# 🚀 Overview

Players on a network expect one thing: what they had on Survival is still there on SkyBlock, and what they earned on SkyBlock is waiting for them back on Survival.

PlayerDataSync makes that happen. Every server writes to one shared database, every server reads from it on join, and Redis tells the others the moment something changed. Your network behaves like a single world.

No manual file transfers. No duplicated inventories. No lost progress. No "my boots are gone".

# ✨ What Gets Synchronized

Every entry is an individual toggle in the config, so you decide exactly what travels with your players.

| Category | Included | |----------|----------| | Items | Inventory (incl. armor and off-hand), Ender Chest, selected hotbar slot | | Progression | Experience, levels, advancements, statistics | | Vitals | Health, absorption, hunger, saturation, exhaustion, air, fire ticks, freeze ticks, arrows in body | | Effects & state | Potion effects, game mode, flight, walk & fly speed, fall distance, player time, player weather | | Advanced | Attributes, Persistent Data Container, Vault economy balance | | Optional | Location (disabled by default — see below) |

### 📍 About location sync

Location sync teleports players to their stored position on join. It ships disabled (`sync.location: false`) because it only makes sense when the destination server has a world of the same name. If that world is missing, the restore is skipped with a log warning instead of dropping the player somewhere wrong.

# 🛡️ Built to Never Roll Back

Most sync plugins work fine until two things happen at once. PlayerDataSync is designed around exactly those moments:

• Proxy handshake. With the Velocity bridge, a server switch waits until the old server confirms its save. The new server never reads the database before the write has landed.
• Ordered loads. Join event, proxy notification and Redis notification all trigger loads — they are queued per player, so the newest record is always the one applied last.
• No premature saves. Autosave, quit and proxy saves are refused until the stored profile has been applied. The stale local player file can never overwrite the database.
• No redundant re-applies. A late notification for a record the player already has is ignored. Gear equipped in the meantime stays equipped.
• Save on shutdown. `/stop` and `/pds reload` save every online player and wait for the writes. Paper kicks players after disabling plugins — we save before that happens.
• Honest failures. A failed database write is counted, logged and retried on the next save instead of being silently marked as "unchanged".
• Encrypted means encrypted. If encryption is enabled and fails, the save fails. Plaintext never reaches the database by accident.

# 🧰 More Than Just Sync

• 🔴 Redis live sync — other servers reload a profile the moment it was saved; the subscriber reconnects automatically if Redis drops
• 🔐 AES encryption