​

Database Sync

​

How It Works

1. Hytale storage - Player data (level, XP, stats) is stored by Hytale in JSON files under universe/players/. This is always the authoritative source.
2. Database mirror - When enabled, the plugin copies this data to an external database table whenever it changes.
3. When sync runs:
   • On startup - All players from disk are synced to the DB (table is created if it does not exist).
   • On change - Whenever a player levels up, gains XP, allocates stats, or has stats reset, their data is synced asynchronously.

​

Configuration File

​

All Parameters

​

Example Configuration

{
  "Version": "0.2.0",
  "Enabled": true,
  "JdbcUrl": "jdbc:mariadb://localhost:3306/rpgleveling",
  "Username": "rpguser",
  "Password": "rpgpass",
  "MaxPoolSize": 10
}

{
  "Version": "0.2.0",
  "Enabled": true,
  "JdbcUrl": "jdbc:postgresql://localhost:5432/rpgleveling",
  "Username": "rpguser",
  "Password": "rpgpass",
  "MaxPoolSize": 10
}

{
  "Version": "0.2.0",
  "Enabled": true,
  "JdbcUrl": "jdbc:h2:file:./mods/Zuxaw_RPGLeveling/data/sync;MODE=MySQL",
  "Username": "",
  "Password": "",
  "MaxPoolSize": 5
}

​

Connection URLs

• Replace host, port, and database with your values.
• H2 file mode stores data locally; no external server is needed. Username and Password are usually empty.
• All table names use the RPGLeveling_ prefix for consistency with the plugin.

​

Table Schema

​

Example Queries

SELECT * FROM RPGLeveling_players WHERE uuid = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx';

SELECT uuid, username, level, experience, available_stat_points, allocated_stats
FROM RPGLeveling_players WHERE username = 'PlayerName';

​

Important Notes

• Sync is one-way. Edits in the database (e.g. via SQL) are not applied to players in-game.
• Hytale storage wins. If there is any conflict, the in-game data is authoritative.
• Performance - Sync runs asynchronously; it does not block gameplay.
• Failure handling - If the DB is unreachable, sync fails quietly and is logged. The game continues normally.