59bd884263
- Migrate connection pool from manual LinkedBlockingQueue to HikariCP (eliminates isValid() ping on every query visible in Spark profiler) - Move ALL DB writes off server thread: logout uses snapshot+async+latch, shutdown uses snapshot+CompletableFuture.allOf for parallel saves - Pre-read curios/accessories/cosmeticarmor/attachments on background thread during login (4-7 fewer DB queries on main thread per login) - Auto-save interval increased to 5 minutes - Fix pool shutdown ordering: shutdownPool() now runs AFTER all shutdown saves complete (previously could fire before, silently losing all data) - Fix connection leak in executeQuery/executePreparedQuery when prepareStatement throws (leaked connections exhaust HikariCP pool) - Fix duplication bug: saveStorageContents guard used nbt.size()<=1 which blocked legitimately emptied backpacks from saving to DB - Fix stale SaveToFile overwriting logout: check playerLocks.containsKey before writing to prevent stale background task from regressing data - Remove LIMIT 1000 on startup online=0 reset (could leave players stuck) - Add executorService.shutdown() on server stop to prevent JVM hang - Add apply methods (applyCuriosFromData, applyAccessoriesFromData, etc.) to separate entity writes from DB reads for thread-safe restore - Add UUID collectors (collectBackpackUuids, collectSSUuids) and background save methods for snapshot+async logout/shutdown pattern |
||
|---|---|---|
| .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