Skip to content

Fix snapshot trigger compile error in SyncManager #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Arbousier1 merged 1 commit into from
Jun 30, 2026
Merged

Fix snapshot trigger compile error in SyncManager #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/main/java/com/fastsync/sync/SyncManager.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1914,7 +1914,7 @@ private static org.bukkit.inventory.ItemStack[] snapshotItemContents(
private boolean canCollectComponentsOnly(UUID uuid, SaveKind kind,
com.fastsync.sync.dirty.ComponentDirtyMask.DirtySnapshot snapshot) {
if (!config.isComponentStorageEnabled() || dirtyMask == null || kind.releaseLock
|| (snapshotManager != null && shouldCreateSnapshot(kind.causeName))
|| (snapshotManager != null && shouldTriggerSnapshot(kind.causeName))
|| snapshot == null || snapshot.isEmpty()
|| !playersWithBaseline.contains(uuid) || !componentCursors.containsKey(uuid)) {
return false;
Expand Down Expand Up @@ -3829,7 +3829,7 @@ private SaveResult persistCollectedData(UUID uuid, PlayerData data, SaveKind kin
if (config.isComponentStorageEnabled()
&& dirtyMask != null
&& !kind.releaseLock
&& (snapshotManager == null || !shouldCreateSnapshot(data.getSaveCause()))
&& (snapshotManager == null || !shouldTriggerSnapshot(data.getSaveCause()))
&& dirtyMask.isAnyDirty(uuid)) {
// Pass the caller-provided snapshot (taken before collectPlayerData)
// so persistComponentsOnly's clearDirty after the DB write protects
Expand Down