Quick answer: Cloud save conflicts arise when a player has saves on multiple devices (or offline edits) that diverge, and the sync system can't automatically tell which should win. Bad resolution overwrites newer progress with older, losing the player's work. Fix it by tracking each save's recency reliably, resolving conflicts in favor of the newer or more-progressed save, and, when ambiguous, asking the player rather than silently picking wrong.
Cloud saves are great until they conflict, the player plays on one device, then another, or offline, and now there are two diverging saves and the system has to decide which to keep. Done wrong, conflict resolution silently overwrites the player's newer progress with an older save, which is lost progress and infuriating. Fixing cloud conflicts is about resolving them correctly and never destroying the better save.
Why Cloud Conflicts Happen
Cloud saves sync the player's save across devices, but divergence is possible: the player plays on device A (advancing the save), then on device B before B synced A's progress (or while offline), so now A and B have different, conflicting saves. The cloud system has to reconcile them, and the danger is choosing wrong, overwriting the newer/better save with the older one. Conflicts also arise from sync timing (a device uploading a stale save over a newer cloud save) and offline play (edits made offline conflicting with cloud state on reconnect).
The core problem is that without good information about which save is newer or more advanced, the system can pick the wrong one, and a wrong pick means lost progress. So conflict resolution quality is everything.
How to Diagnose It
The symptom is players losing progress when playing across devices or after offline play, they advance, then find an older state restored (the conflict resolved against their newer save). Reports of 'my progress went backward' or 'I lost progress after playing on another device' point at conflict resolution overwriting newer with older. Check your resolution logic: how does it decide which save wins, and can that decision pick the older save?
Bugnet captures player reports with context, so progress-loss reports tied to multi-device or offline play surface and can be recognized as cloud-conflict issues. Because these silently destroy progress (the player just sees their work gone), they're high-impact even if reports are modest, each is a lost-progress incident, and they're easy to under-count because players may not realize it's a sync issue.
How to Fix It
Resolve conflicts correctly and safely. Track save recency reliably, attach a trustworthy notion of which save is newer or more-progressed (a timestamp you can trust, a play-time counter, a progress metric, or a version/sequence number), so the system can compare. Prefer the newer / more-progressed save, when a conflict is detected, keep the one that represents more recent or more advanced progress, rather than blindly picking by sync order. Never silently overwrite newer with older, the cardinal rule, if there's any risk of losing newer progress, don't auto-discard it.
For genuinely ambiguous conflicts (where you can't confidently tell which is better), ask the player, present the choice (with helpful context like progress/time) so they decide, rather than guessing and potentially losing their work. And keep the non-chosen save around (don't immediately delete it) so a wrong resolution is recoverable. After fixing, verify multi-device and offline-then-online scenarios keep the better save and never lose newer progress. Correct, conservative conflict resolution, prefer newer, never silently destroy progress, ask when unsure, is what makes cloud saves trustworthy.
Cloud conflicts lose progress when sync overwrites newer with older. Track recency, prefer the more-progressed save, never silently discard newer, and ask the player when unsure.