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 '4c7ec9ec21'
${ noResults }
HuskSync/docs/API-Events.md

2.5 KiB
Raw Blame History

HuskSync provides three API events your plugin can listen to when certain parts of the data synchronization process are performed. These events deal with HuskSync class types, so you may want to familiarize yourself with the API basics first. Two of the events can be cancelled (thus aborting the synchronization process at certain stages), and some events expose methods letting you affect their outcome (such as modifying the data that is saved during the process).

Consult the Javadocs for more information. Please note that carrying out expensive blocking operations during these events is strongly discouraged as this may affect plugin performance.

Bukkit Platform Events

Tip: Don't forget to register your listener when listening for these event calls.

Bukkit Event class Cancellable Description
BukkitDataSaveEvent ✅ Called when player data snapshot is created, saved and cached due to a DataSaveCause
BukkitPreSyncEvent ✅ Called before a player has their data updated from the cache or database, just after login
BukkitSyncCompleteEvent ❌ Called once a player has completed their data synchronization on login successfully†

Fabric Platform Callbacks

Access the callback via the static EVENT field in each interface class.

Fabric Callback Cancellable Description
FabricDataSaveCallback ✅ Called when player data snapshot is created, saved and cached due to a DataSaveCause
FabricPreSyncCallback ✅ Called before a player has their data updated from the cache or database, just after login
FabricSyncCompleteCallback ❌ Called once a player has completed their data synchronization on login successfully†

†This can also fire when a user's data is updated while the player is logged in; i.e., when an admin rolls back the user, updates their inventory or Ender Chest through the respective commands, or when an API call is made forcing the user to have their data updated.