viverse-storage

To save game state to the cloud for VIVERSE apps, you use the CloudSaveClient SDK to perform secure upsert and retrieval operations. This requires a valid VIVERSE access token and a registered 10-character Studio app ID to persist user-scoped data.

Cross-device synchronization works by managing local-to-cloud data merging for authenticated users. When a user logs in, the CloudSaveClient SDK automatically promotes and merges local guest progress into the cloud, ensuring consistent game state across all devices.

Yes, local storage serves as a fallback for guest users before authentication. The storage skill handles guest-to-cloud merging automatically, promoting local progress to the cloud upon the user's first successful authentication to prevent data loss.

To prevent data loss during page transitions, implement resilient exit-save mechanisms using fetch with keepalive. This ensures data integrity and reliable cloud persistence even if the user closes the page or navigates away before the upsert operation fully completes.

To set up cloud persistence, you need a valid VIVERSE access token and a registered 10-character Studio app ID. You use these credentials to initialize the CloudSaveClient SDK and securely synchronize your local game state with the cloud infrastructure.

The best way to handle user-scoped application data is using the CloudSaveClient SDK for cloud persistence. It manages secure upsert and retrieval operations, cross-device synchronization, and local-to-cloud data merging for authenticated users automatically.