A Minecraft Forge mod that synchronizes player data across multiple servers using a MySQL backend.

Go to file

laforetbrut 1bf2a67e8d Optimize auto-save: snapshot on main thread, DB write on background Spark showed 5.66% server thread from auto-save DB writes blocking the tick loop (~1-2ms per player per query, ~8 queries per save). New approach: - snapshotPlayerData() captures ALL entity data into an immutable PlayerDataSnapshot record on the main thread (fast, no DB I/O) - writeSnapshotToDB() writes the snapshot to DB on the background thread via executorService (slow DB I/O off main thread) - Mod data (Curios, Accessories, CosmeticArmor, NeoForge attachments) still read entity state on main thread but their DB writes happen inline (they manage their own connections) - Sophisticated Backpacks/Storage/RS2 saves happen during snapshot phase on main thread (they need entity access for inventory scan) Expected: ~60-70% reduction in main thread blocking from auto-save. Vyrriox		2026-03-26 21:31:43 +01:00
.github	Bump gradle/actions from 4 to 5	2025-10-14 16:55:21 +08:00
gradle/wrapper	migrate from ForgeGradle to ModDevGradle legacy	2025-05-02 22:40:39 +00:00
src/main	Optimize auto-save: snapshot on main thread, DB write on background	2026-03-26 21:31:43 +01:00
.gitattributes	Initial commit	2022-12-08 16:59:20 +08:00
.gitignore	add support for Minecraft 1.20.4 with ModDevGradle	2025-05-04 18:43:11 +00:00
build.gradle	Fix Sophisticated Storage shulkers/chests/barrels losing contents on transfer	2026-03-26 17:12:29 +01:00
docker-compose.yml	use volume for docker-compose db to persist data	2025-05-01 18:42:58 +00:00
gradle.properties	fix #151	2026-01-14 20:26:26 +08:00
gradlew	migrate from ForgeGradle to ModDevGradle legacy	2025-05-02 22:40:39 +00:00
gradlew.bat	migrate from ForgeGradle to ModDevGradle legacy	2025-05-02 22:40:39 +00:00
LICENSE	Create LICENSE	2022-12-08 17:11:47 +08:00
README.md	readme: add section on how to setup a dev env	2025-05-01 16:59:05 +00:00
settings.gradle	half done, noticed about advancement can't store normally	2025-06-07 00:55:30 +08:00

README.md

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:
```
docker compose up -d
```
This will download the MariaDB image (if not already present) and start a database container in the background.
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

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
```
./gradlew runServer
```
or on Windows:
```
.\gradlew.bat runServer
```
This task compiles the mod and starts a dedicated Minecraft server instance with the mod loaded in the run directory.

Run the Client

./gradlew runClient

or on Windows:

.\gradlew.bat runClient