HuskLegacy
/
HuskSync
forked from public-mirrors/HuskSync
1
0
Fork 0
Code Pull Requests Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
dependabot/gradle/xyz.jpenilla.run-paper-2.3.1
dependabot/gradle/org.junit.jupiter-junit-jupiter-api-5.11.0
dependabot/gradle/com.google.guava-guava-33.3.0-jre
dependabot/gradle/org.junit.jupiter-junit-jupiter-params-5.11.0
dependabot/gradle/org.junit.jupiter-junit-jupiter-engine-5.11.0
feat/data-edit-commands
1.3
1.3.2
1.4
1.4-SNAPSHOT
1.4.1
2.0
2.0.1
2.0.2
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
3.0
3.0.1
3.0.2
3.1
3.1.1
3.1.2
3.2
3.2.1
3.3
3.3.1
3.3.2
3.3.3
3.4
3.5
3.5.1
3.5.2
3.5.3
3.6
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.6.8
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '29d8f2ecf4'
${ noResults }
HuskSync/docs/Data-Rotation.md

3.7 KiB
Raw Blame History

HuskSync provides options for backing up and automatically rotating user data. That way, if something goes wrong, you can restore a user from a previous snapshot of user data.

Snapshots

HuskSync creates what is known as "Snapshots" of a user's data whenever it saves data.

Each user data snapshot has:

  • a unique ID
  • a timestamp (when it was created)
  • a save cause (why it was created)
  • a flag to indicate if the snapshot has been pinned (preventing it from being rotated)
  • a map of saved data

By default, HuskSync will automatically replace the user's current snapshot in the database if it has been less than 4 hours since the last snapshot was created. This can be changed in the config.yml file by changing the snapshot_backup_frequency setting under synchronization. Setting this to "0" will save a new snapshot each time data is saved.

HuskSync will keep the 16 most recent data snapshots for each user (including their current data). After that, when a new user snapshot is set, the oldest snapshot will automatically be deleted. You can change the number of snapshots to keep by changing the max_user_data_snapshots setting (minimum 1).

Pinned user data snapshots are exempt from being replaced/rotated and can only be deleted manually in-game.

Viewing user data

To view a list of a user's snapshots, use /userdata list [username]. Their most recent snapshots will be listed from the database, from newest to oldest. You can click the buttons to navigate through their pages.

Data snapshot list

Snapshots marked with a star after the number have been pinned. Hover over it to view more information.

You can then click on the items in the list in chat to view an overview of each snapshot. Alternatively, to view a user's most recent data snapshot, use /userdata view [username].

Data snapshot viewer

Managing user data

You can use the "Manage" buttons to manage user data. These buttons will only appear if you have the userdata command manage permission. (See Commands)

  • Click on "Delete" to remove the data
  • Click on "Restore" to restore the user data. If the user is online, their items and stats will be updated, otherwise their data will be set to this snapshot upon their next login.
  • Click on "Pin" to pin the user data. An indicator will appear in the data viewer and list marking the snapshot as being pinned.

Save causes

Data save causes, marked with a 🚩 flag, indicate what caused the data to be saved.

  • disconnect: Indicates data saved when a player disconnected from the server (either to change servers, or to log off)
  • world save: Indicates data saved when the world saved. This can be turned off in config.yml by setting save_on_world_save to false under synchronization.
  • server shutdown: Indicates data saved when the server shut down
  • inventory command: Indicates data was saved by editing inventory contents via the /inventory command
  • enderchest command: Indicates data was saved by editing Ender Chest contents via the /enderchest command
  • backup restore: Indicates data was saved by restoring it from a previous version
  • api: Indicates data was saved by a call to the HuskSync API
  • mpdb migration: Indicates data was saved from being imported from MySQLPlayerDataBridge (See MPDB Migration)
  • legacy migration: Indicates data was saved from being imported from a legacy version (v1.x - See Legacy Migration)
  • converted from v2: Indicates data was automatically converted from HuskSync v2.0's data format
  • unknown: Indicates data was saved by an unknown saveCause.