1d30184aba
CRITICAL - New player data loss (players lose everything): - store() INSERT now includes last_server column. Without it, last_server stayed NULL, causing ALL subsequent writes (AND last_server=?) to fail silently — new players' data was never saved after initial INSERT. - writeSnapshotToDB now handles legacy NULL last_server with (last_server=? OR last_server IS NULL) and auto-claims ownership. - Same NULL handling in writeGuardedModData for mod_player_data table. CRITICAL - online=0 stuck at 1 (players unable to connect): - Removed AND last_server=? from deadPlayerWhileLogging and syncNotCompletedPlayer logout paths. These fire before doPlayerJoin sets last_server, so the guard always failed → online stayed 1. CRITICAL - Backpack duplication via viewer race: - snapshotBackpackData() now captures backpack NBT on the MAIN THREAD (not just UUIDs). Previously saveBackpacksByUuids read BackpackStorage on an async thread — another player viewing the backpack could take items between the main-thread refresh and the async read. - .copy() freezes the NBT state at snapshot time. CRITICAL - Backpacks in ender chest not synced: - snapshotBackpackData() and doBackPackRestore now scan the ender chest in addition to main inventory. PlayerInventoryProvider.runOnBackpacks only scans equipment/inventory, missing ender chest backpacks entirely. Anti-duplication - Container closing on disconnect: - Owner's container menu is force-closed before snapshot to prevent post-snapshot modifications by viewers. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| gradle/wrapper | ||
| src/main | ||
| .gitattributes | ||
| .gitignore | ||
| build.gradle | ||
| docker-compose.yml | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| README.md | ||
| settings.gradle | ||
PlayerSync
PlayerSync is a Minecraft Forge mod that synchronizes player data across multiple servers using a MySQL backend. It allows players to maintain their inventory, equipment, experience, advancements, and more when moving between servers in a network.
Mod Support
Any other mods support is also possible.
Development Setup
Database Setup (Docker)
A docker-compose.yml file is provided for easily setting up a MariaDB database instance for development testing.
- Make sure Docker is installed.
- Inside your work directory run:
This will download the MariaDB image (if not already present) and start a database container in the background.docker compose up -d - Stoppinng the Database
docker compose down
Data Persistence: The database uses a Docker volume, ensuring your data persists even if you stop and restart the containers.
Database Management Tool
The docker-compose.yml also includes an Adminer service, a lightweight database management tool.
- Access Adminer in your web browser at http://localhost:8080.
- Log in using the server with
- username:
playersync - database:
playersync - password: see docker-compose.yml
- username:
For debugging purposes, you can enable use_legacy_serialization to have readable database fields. This can cause crashes and unintended side-effects. Do not enable this on a production server if not absolutely necessary!
Running the Mod
The project uses Gradle for building and running. Use the provided Gradle wrapper (gradlew for Linux/macOS, gradlew.bat for Windows).
- Make sure that the MySQL database you configured is running.
- Run the Server
or on Windows:./gradlew runServer
This task compiles the mod and starts a dedicated Minecraft server instance with the mod loaded in the.\gradlew.bat runServerrundirectory. - Run the Client
or on Windows:./gradlew runClient.\gradlew.bat runClient