4999c372ec
Root cause of lag (TPS 9-16, MSPT spikes to 4846ms): PlayerEvent.SaveToFile triggered synchronous JDBC writes on the server main thread every Minecraft autosave cycle. With 35 players this caused hundreds of network round-trips to MySQL blocking the tick loop for up to 4846ms (97x the 50ms limit). Fixes applied: - onPlayerSaveToFile: now fully async. Entity state is snapshotted on the main thread (pure memory ops, <1ms), then ALL DB writes are submitted to the background executor. Main thread never blocks on MySQL again. - snapshotPlayerData: now captures ALL entity-dependent mod data (Curios, Accessories, CosmeticArmor, NeoForge attachments) on the main thread. Previously these were read from a background thread which is not thread-safe and could cause data corruption. - writeSnapshotToDB: single method that writes all player data in one background pass: player_data + curios + mod_player_data. - Auto-save background task: removed ModCompatSync.storeAll(player), storeSophisticatedBackpacks, storeSophisticatedStorageItems, storeRefinedStorageDisks from background thread. These all accessed entity state off-thread. Mod compat data is now in the main-thread snapshot; backpack/SS/RS2 contents are saved on logout/shutdown. - Added ModCompatSync snapshot API: snapshotAccessories(), snapshotCosmeticArmor(), snapshotAttachments(), writeModSnapshot() for clean separation of entity reads vs DB writes. |
||
|---|---|---|
| .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