PlayerDataSync

PlayerDataSync

Seamless Cross-Server Player Data Synchronization​

von
3.1K Downloads
bukkitfabricfoliaforgepaperpurpurspigotvelocitymanagementoptimizationstorage
Server mit dieser Mod mieten

Über diese Mod

🧩 PlayerDataSync

Seamless Cross-Server Player Data Synchronization
Keep inventories, Ender Chests, XP, health, attributes and more synchronized across every server in your network.

Servers & Players


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

Category Included
Items Inventory, Ender Chest, selected hotbar slot
Progression Experience, levels, advancements, statistics
Vitals Health, absorption, hunger, saturation, exhaustion, air, fire ticks, freeze ticks, arrows in body
State 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.


🧰 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

Component Supported
Minecraft 1.20 – 26.2
Server software Paper, Spigot, Fabric, Velocity (proxy bridge)
Java 21+ — Minecraft 26.x servers require Java 25
Database MySQL, MariaDB, PostgreSQL, MongoDB

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.

Command Description
/pds status Sync statistics, error counters, excluded worlds
/pds save <player> Force-save a player
/pds saveall Force-save everyone online
/pds load <player> Reload a player from storage
/pds list List stored profiles
/pds backup Create a backup
/pds export / /pds import Move profiles in and out
/pds migrate Migrate between storage backends
/pds toggle Toggle syncing at runtime
/pds debug on|off Toggle verbose logging
/pds reload Reload the configuration

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

Verfügbare Versionen

PlayerDataSync 26.7-Releaserelease
MC 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2bukkit, fabric, folia, forge, paper, purpur, spigot, velocity
30. Juli 2026
PlayerDataSync 26.5.4-Releaserelease
MC 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2bukkit, folia, paper, purpur, spigot
5. Mai 2026
PlayerDataSync 26.5.3-Releaserelease
MC 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2bukkit, folia, paper, purpur, spigot
5. Mai 2026
PlayerDataSync 26.5.2-Releaserelease
MC 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2bukkit, folia, paper, purpur, spigot
3. Mai 2026
PlayerDataSync 26.5.1-Releaserelease
MC 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2bukkit, folia, paper, purpur, spigot
1. Mai 2026

PlayerDataSync auf dem Server installieren

1

Server bestellen

Bestelle einen Minecraft Java Server mit mindestens 3 GB RAM (4 GB empfohlen).

2

bukkit Loader setzen

Wähle im Panel unter "Egg" den bukkit-Loader und die passende Minecraft-Version (26.2).

3

Mod installieren

Öffne den Mod-Browser im Dashboard und suche nach "PlayerDataSync". Klicke "Installieren" – fertig! Alternativ: Lade die .jar via SFTP in den /mods Ordner.

Kompatibilität

Mod-Loader

bukkitfabricfoliaforgepaperpurpurspigotvelocity

Minecraft-Versionen

26.2, 26.1.2, 26.1.1 (+71 weitere)

Server-seitig

Nicht unterstützt

Empfohlener RAM

4 GB(min. 3 GB)

Häufige Fragen

PlayerDataSync Server crasht beim Start – was tun?

Häufigste Ursache: falsche bukkit-Version oder zu wenig RAM. Prüfe im Server-Log (latest.log), ob ein "OutOfMemoryError" oder "Mixin"-Fehler auftritt. Bei Mado Hosting: Stelle sicher, dass mindestens 3 GB RAM zugewiesen sind und der Loader zur Mod-Version passt (26.2). Über das Panel kannst du den Loader mit einem Klick wechseln.

Ist PlayerDataSync mit bukkit und fabric und folia und forge und paper und purpur und spigot und velocity kompatibel?

PlayerDataSync unterstützt offiziell bukkit, fabric, folia, forge, paper, purpur, spigot, velocity für Minecraft 26.2, 26.1.2, 26.1.1. Achtung: Forge- und Fabric-Mods sind NICHT untereinander kompatibel – wähle einen Loader und bleibe dabei. Im Mado Dashboard werden inkompatible Loader-Kombinationen automatisch erkannt.

Server laggt mit PlayerDataSync – wie optimiere ich die Performance?

Empfohlener RAM: 4 GB (+1 GB pro 8 Spieler). Prüfe mit /spark profiler, ob PlayerDataSync den meisten Tick-Time verbraucht. Häufige Fixes: Server-View-Distance auf 8-10 reduzieren, bei Forge "performant" oder "starlight" als Zusatz-Mod installieren. Bei Mado Hosting läuft dein Server auf NVMe-SSDs mit dedizierten CPU-Kernen für minimale Latenz.

Modded Server mieten

Installiere PlayerDataSync mit nur einem Klick auf deinem Server.

Empfohlener RAM
4 GBab €5.2/Monat
Min. 3 GB | +1 GB pro 8 Spieler
Jetzt Server erstellen
1-Klick Mod Installation
NVMe SSD Speicher
DDoS-Schutz inklusive

Details

Lizenz
LicenseRef-All-Rights-Reserved
Server-seitig
Nicht unterstützt

Unterstützte Versionen

26.226.1.226.1.126.11.21.111.21.101.21.91.21.81.21.71.21.6+64 mehr