InvSYNC

Fixed

• Items could get lost or duplicated when a player switched servers through a proxy such as Velocity or BungeeCord. The proxy keeps the player on the previous server until the next one has accepted the login, so the next server claimed the data before the previous one could save. On top of that a claim was only refreshed by the auto-save and counted as abandoned after ownership.stale-after-ms, so the next server took it over and loaded the last auto-save, and the final save of the previous server was refused.
• Data is now claimed in the configuration phase (Paper 1.21.7 and newer). The proxy has dropped the player from the previous server at that point, so its final save is what the next server loads. The player is still not in the world.
• A running server refreshes its claims every quarter of ownership.stale-after-ms. Only a server that stopped running can lose a claim to the stale takeover.
• A login that ends before the player reaches the world releases its claim at once instead of after 30 seconds.

Added

• /invsync backups <player> lists the copies on the server's disk, and /invsync restore <player> local:<id> applies one. Saves refused after a server switch were always kept there, this brings them back. Every restore keeps the replaced state as a snapshot. Permission invsync.admin.backups.
• Refused saves are filed as -refused.snapshot and no longer rotate out with the routine copies.