PlayerDataSync

🚀 Overview

PlayerDataSync keeps player data synchronized across every server in your Minecraft network.

Whether players move between Survival, Lobby, Creative, SkyBlock, Minigames or anything else, their progress follows them automatically.

No manual file transfers. No duplicated inventories. No lost progress.

Player data lives in one shared database. With Redis enabled, changes propagate between servers the moment they happen — your network behaves like a single world.

✨ What Gets Synchronized

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

📍 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.

🧰 More Than Just Sync

• 🔴 Redis live sync — propagate changes between servers instantly instead of waiting for the next join
• 🔐 AES encryption — encrypt stored profiles with your own key
• 💾 Automatic backups — compressed snapshots before data is overwritten
• 🔁 Storage migration — move between MySQL, MariaDB, PostgreSQL and MongoDB with one command
• ⬆️ Legacy import — bring profiles over from the original PlayerDataSync
• 📤 Import / export — move individual player profiles in and out
• 💬 Discord webhooks — notifications for sync successes and failures
• ⏱️ Autosave — periodic saves as a crash safeguard
• 🚫 Exclusions — skip specific worlds or specific item types
• 📊 bStats & FastStats metrics
• 🧩 Developer API — events and Persistent Data Container hooks for your own plugins

🌟 Why PlayerDataSync?

Running player data across multiple servers without proper synchronization leads to:

• Lost inventories
• Item duplication
• Missing experience
• Inconsistent progress

PlayerDataSync removes those failure modes by synchronizing automatically whenever data changes.

Benefits

• ✅ One shared player profile across your whole network
• ✅ Instant propagation with Redis
• ✅ Four database backends to choose from
• ✅ Asynchronous — the main thread stays free
• ✅ Skips redundant saves when nothing changed
• ✅ Open source (MIT) and actively maintained

🧱 Supported Platforms

The download is the Paper/Spigot plugin. The Fabric and Velocity builds are bundled inside it under bundled/ — extract whichever you need.

Please note:

• Fabric is not yet at feature parity. Advancements and statistics are not synchronized on Fabric. The 1.20 and 1.21 Fabric builds additionally lack Ender Chest, potion effects and attributes; the 26.x builds have those.
• Forge is currently unavailable while its build tooling catches up with the Minecraft 26.x toolchain.
• On Fabric, use MariaDB, PostgreSQL or MongoDB. The MySQL driver is not bundled and mod loaders do not supply one. The MariaDB driver connects to MySQL servers just fine. Paper and Spigot are unaffected.
• SQLite is not supported.

⚙️ Configuration

Full documentation: 👉 https://pds.devvoxel.de/config

• Paper / Spigot: plugins/PlayerDataSyncReloaded/config.yml
• Fabric: config/playerdatasync.properties, created on first start

storage:
  type: "mariadb"   # mysql, mariadb, postgres, mongodb
  host: "localhost"
  port: 3306
  database: "minecraft"
  username: "root"
  password: ""

redis:
  enabled: true     # strongly recommended for multi-server setups
  host: "localhost"
  port: 6379

sync:
  inventory: true
  ender_chest: true
  economy: true     # requires Vault + an economy plugin
  location: false   # teleports players on join

💬 Commands & Permissions

Everyday operation is fully automatic — players never touch a command. For administrators, everything lives under /playerdatasync (aliases /pds, /pdasync) behind the playerdatasync.admin permission.

📈 Performance

• ⚡ Asynchronous database operations — the main thread is never blocked
• 🔄 Redundant saves are skipped when the inventory has not changed
• ⏳ Configurable minimum interval between saves
• 💾 Compressed backups
• 📉 Low CPU and memory footprint

Suitable for small communities and large networks alike.

📋 Requirements

• ☕ Java 21+ (Java 25 for Minecraft 26.x servers)
• 🗄️ MySQL, MariaDB, PostgreSQL or MongoDB
• 🧱 Paper, Spigot or Fabric server
• 🌐 Multiple servers pointed at the same database
• 🔴 Redis (optional, recommended) — instant cross-server propagation
• 💰 Vault + an economy plugin (optional) — required for economy sync

🛠️ Support

• 💬 Join our Discord server
• 🐛 Report bugs on GitHub
• 📚 Read the documentation
• 💡 Share feature requests and suggestions

❤️ Credits

Developed with ❤️ by DerGamer09

If PlayerDataSync helps your network, consider leaving a review on SpigotMC, Modrinth, Hangar or BuiltByBit. Your feedback shapes what gets built next.