PlayerDataSync Reloaded
github.com
What it is
PlayerDataSync Reloaded synchronizes player state across Minecraft multi-server networks, including survival clusters and competitive mini-game networks. It can share inventories, armor, Ender Chests, health, hunger, saturation, experience, potion effects, advancements, statistics, game mode, flight status, optional location, attributes and Persistent Data Container data. MySQL, MariaDB, PostgreSQL and MongoDB are listed as persistence backends. Native Redis Pub/Sub supports near-instant handovers between nodes. GZIP compression and asynchronous thread pools move serialized-data work away from the main server thread, while optional AES-256 encryption protects sensitive profiles. The project provides an event-driven API, expansion hooks for custom Persistent Data Container data and Vault balance synchronization. Installation puts the plugin JAR on each server and configures database credentials in config.yml. Requirements are Paper or Folia 1.20+ and Java 25 or higher. The project is free, open source and MIT licensed. Fabric and Forge support have stated limits, and SQLite is unsupported.
Spec sheet
- Purpose
- PlayerDataSync Reloaded synchronizes player data across multi-server Minecraft networks.Read 9 Oct 2026 · github.com
- Deployment
- Installation instructions say to put the plugin JAR in the plugins directory on each server and configure database credentials in config.yml.Read 9 Oct 2026 · github.com
- API
- The project provides an event-driven developer API and expansion hooks for syncing custom Persistent Data Container data.Read 4 Oct 2026 · github.com
- Security
- The README describes optional AES-256 encryption for sensitive player profiles.Read 9 Oct 2026 · github.com
- Support
- The README directs users to GitHub issues for bug reports, documentation, and a community Discord for support.Read 9 Oct 2026 · github.com
- License
- The GitHub repository identifies the project as MIT licensed.Read 9 Oct 2026 · github.com
- Compatibility
- The README lists Paper or Folia 1.20+ and Java 25 or higher as requirements, while describing Folia compatibility.Read 4 Oct 2026 · github.com
- Data stores
- The README lists MySQL, MariaDB, PostgreSQL, and MongoDB as supported persistence backends.Read 9 Oct 2026 · github.com
- Data synchronized
- It supports syncing inventories, armor, Ender Chests, health, hunger, saturation, experience, potion effects, advancements, statistics, game mode, flight status, optional location, attributes, and Persistent Data Containers.Read 9 Oct 2026 · github.com
- Databases
- The README lists MySQL, MariaDB, PostgreSQL, and MongoDB as persistence options.Read 4 Oct 2026 · github.com
- Developer API
- The README describes an event-driven API with expansion hooks for syncing custom data through Persistent Data Containers.Read 9 Oct 2026 · github.com
- Economy integration
- The README says Vault can synchronize player balances across the network.Read 9 Oct 2026 · github.com
- Free availability
- CraftingStudioPro lists the PlayerDataSync plugin as “Kostenlos” (free).Read 4 Oct 2026 · craftingstudiopro.de
- Known alpha caveat
- The 26.8-ALPHA release says its economy fix, location teleport, and Redis live sync had not been exercised against a running server with Vault, Redis, or a real multi-server setup.Read 9 Oct 2026 · github.com
- Known limits
- The 26.8-ALPHA release says Fabric does not sync advancements or statistics, Forge is not built, and SQLite is unsupported.Read 9 Oct 2026 · github.com
- Limit: Fabric
- The 26.8-ALPHA release notes say Fabric does not sync advancements or statistics, and older 1.20 and 1.21 Fabric modules also lack Ender Chest, potion effects, and attributes.Read 4 Oct 2026 · github.com
- Limit: Forge
- The release notes say Forge is not built in the listed releases because ForgeGradle does not support the required Gradle 9 toolchain.Read 4 Oct 2026 · github.com
- Live sync
- The README describes native Redis Pub/Sub messaging for near-instant data handovers between nodes.Read 9 Oct 2026 · github.com
- Performance
- The README describes GZIP compression and asynchronous thread pools intended to keep work off the main server thread.Read 9 Oct 2026 · github.com
- Player data
- It syncs inventories, armor, Ender Chests, health, hunger, saturation, experience, potion effects, advancements, statistics, game mode, flight status, and Persistent Data Container data.Read 4 Oct 2026 · github.com
- Redis
- The README describes native Redis Pub/Sub support for near-instant data handovers between nodes.Read 4 Oct 2026 · github.com
- Server compatibility
- The README lists Paper or Folia version 1.20+ and Java 25 or higher as requirements.Read 9 Oct 2026 · github.com
- Who it is for
- The README describes the product for Minecraft networks such as survival clusters and competitive mini-game networks.Read 4 Oct 2026 · github.com
Strong points and limits
Strong points
- Synchronizes many player-state categories
- Supports four listed database backends
- Native Redis Pub/Sub handovers
- Optional AES-256 profile encryption
- Event-driven API and Vault integration
Limits
- Requires Paper or Folia 1.20+
- Requires Java 25 or higher
- Fabric omits some synchronized data
- Forge is not built in listed releases
Who it suits
It suits Minecraft network operators running Paper or Folia servers that need shared player state and database-backed persistence. Developers can use its event API and custom-data hooks.
Verdict
PlayerDataSync Reloaded covers broad player-state synchronization with several databases, Redis messaging and developer hooks. Confirm platform limitations and the 26.8-ALPHA caveat before deploying economy, location or live-sync features.
Where Specifiction places it
- Minecraft Backup Software#18 of 307.0