InventorySync PRO — Installation

Installation
Requirements for this build
Game servers: the supplied backend targets the Minecraft 26.2 Spigot API and requires Java 25+. It includes Spigot/Paper/Folia scheduling support and can run on compatible Purpur builds. Use a distribution intended for your actual server version; this Wiki does not establish compatibility with every Minecraft release.
Optional proxy: BungeeCord or Velocity compatible with your server setup. Proxy modules use Java 17 bytecode, but you must meet the Java requirement of the proxy build you run. The game-server module still requires Java 25+. SQLite and MySQL drivers are included in the Universal JAR.

Install on one game server

1. Stop the server and back up player data and the plugin folder if upgrading.
   
2. Place InventorySyncPRO-1.7.0-Universal.jar in plugins/. Keep only one InventorySyncPRO JAR; individual Maven module JARs are not the distribution.
   
3. Start once to generate plugins/InventorySyncPRO/config.yml and messages.yml. Defaults use SQLite, GLOBAL profiles, enabled EnderChest/XP synchronization and a disabled proxy bridge.
   
4. Stop the server, choose your profile mode and mappings, then start again. Storage, synchronization and backend bridge changes require a full restart.
   
5. Grant staff the permissions they need. Test reconnecting, switching profile worlds, a saved offline view and a backup before opening access to players.
   

Install across a network

1. Install the Universal JAR on each participating backend. Stop those backends while preparing shared settings. Create a MySQL database and an account permitted to use the plugin tables.
   
2. Set storage.type: MYSQL and the same reachable database on every backend. Assign each backend a unique storage.server-id. Keep the full synchronization/group configuration and administration policy consistent across backends.
   
3. Choose GLOBAL, PER_WORLD or PER_GROUP. Keep sync.restore-on-join and sync.kick-on-failure true; MySQL mode requires both. See Configuration for a Survival-1/Survival-2/Lobby example.
   
4. If using the optional bridge, also install the same JAR on BungeeCord or Velocity. Start once to generate proxy.properties. Enable the bridge on the backends and proxy, and use the same random secret everywhere.
   
5. With the bridge enabled, backend IDs must exactly match the registered proxy backend names, including case. Names allow letters, digits, dots, underscores and hyphens, at most 32 characters; ALL is reserved. Configure the optional allow list with those same names.
   
6. Restart the backends and proxy. Confirm startup, run /isync status on each backend, and /isyncproxy status if using the bridge. Test a transfer, a separate group, XP/EnderChest restoration and a permitted remote edit with a test account.
   

SQLite is local to one backend; do not share its file between servers. Keep player UUID forwarding and backend access restrictions correctly configured. The proxy needs no database credentials and does not replace MySQL.