Price history
Recorded standalone sale prices and the latest available store price, in USD. Historical dots use the sale start date and its recorded offer price. Prices can change during a sale; this is not a daily price log. Bundle prices and upcoming offers are excluded. History covers up to the 100 most recent recorded offers.
Lowest recorded standalone price in this history: $24.99. The latest store price is $24.99, matching the lowest recorded price shown here.
View 2 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| $24.99 | Latest store price | |
| $24.99 | Unity First Price 2026-06-20 2026-06-27 |
Sale and bundle history
The 1 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About OSL Secure Save
- Tools, Systems & Learning > Game Templates & Systems
OSL Secure Save is for Unity Gaming Services projects that want Cloud Save writes checked outside the game client. Calls made through OSLSaveManager go to the included Cloud Code script, where per-key type, range, delta, and operation rules are evaluated before data is written.
Why / Key Benefits:
Move rule checks off the client: Evaluate configured write rules in UGS Cloud Code before committing through the package workflow.
Control each key: Define expected type, minimum and maximum values, maximum additive delta, and allowed AddOnly, Replace, or Both operations.
Configure without a custom server: Deploy the included osl_master_save.js endpoint and use UGS services instead of hosting a separate backend.
Change rules independently: Load osl_secure_save_rules from Remote Config when available, with an embedded fallback rule set.
Recover delivery failures: Persist package API writes through an authenticated, versioned local queue; retry transient failures and preserve exhausted or permanent failures for an explicit recovery decision.
Typical Workflow:
1. Define validation rules in the OSL Rule Builder.
2. Deploy osl_master_save.js to UGS Cloud Code.
3. Optionally publish the generated rule JSON as osl_secure_save_rules in Remote Config.
4. Write through OSLSaveManager; Cloud Code validates and then stores accepted data in Cloud Save.
5. Read the resulting values from the Default access class through the package API.
Requirements:
Minimum Unity Version: Unity 2021.3 LTS
Tested Unity Versions: Unity 2021.3.45f2 and Unity 6000.3.12f1 (package-isolation import and compile)
Required UGS services/packages: Core, Authentication, Cloud Code, and Cloud Save
Optional: UGS Remote Config for remotely managed rule JSON.
Limitations / Scope:
Validation applies to writes sent through the package's Cloud Code path. Because the included script stores data in Cloud Save's Default access class, the host project must avoid or separately restrict direct client write paths.
This is not a general local save-file system and does not provide complete anti-cheat coverage.
The local retry queue uses separate encryption and integrity keys, atomic replacement, last-known-good backup recovery, and corrupted-file quarantine. It is a recovery mechanism and casual-tamper deterrent, not a secure server-side data store.
The built-in key provider preserves compatibility with existing queues. Projects that require platform-backed key storage can inject IOSLQueueKeyProvider before first accessing OSLSaveManager.Instance.
Why / Key Benefits:
Move rule checks off the client: Evaluate configured write rules in UGS Cloud Code before committing through the package workflow.
Control each key: Define expected type, minimum and maximum values, maximum additive delta, and allowed AddOnly, Replace, or Both operations.
Configure without a custom server: Deploy the included osl_master_save.js endpoint and use UGS services instead of hosting a separate backend.
Change rules independently: Load osl_secure_save_rules from Remote Config when available, with an embedded fallback rule set.
Recover delivery failures: Persist package API writes through an authenticated, versioned local queue; retry transient failures and preserve exhausted or permanent failures for an explicit recovery decision.
Typical Workflow:
1. Define validation rules in the OSL Rule Builder.
2. Deploy osl_master_save.js to UGS Cloud Code.
3. Optionally publish the generated rule JSON as osl_secure_save_rules in Remote Config.
4. Write through OSLSaveManager; Cloud Code validates and then stores accepted data in Cloud Save.
5. Read the resulting values from the Default access class through the package API.
Requirements:
Minimum Unity Version: Unity 2021.3 LTS
Tested Unity Versions: Unity 2021.3.45f2 and Unity 6000.3.12f1 (package-isolation import and compile)
Required UGS services/packages: Core, Authentication, Cloud Code, and Cloud Save
Optional: UGS Remote Config for remotely managed rule JSON.
Limitations / Scope:
Validation applies to writes sent through the package's Cloud Code path. Because the included script stores data in Cloud Save's Default access class, the host project must avoid or separately restrict direct client write paths.
This is not a general local save-file system and does not provide complete anti-cheat coverage.
The local retry queue uses separate encryption and integrity keys, atomic replacement, last-known-good backup recovery, and corrupted-file quarantine. It is a recovery mechanism and casual-tamper deterrent, not a secure server-side data store.
The built-in key provider preserves compatibility with existing queues. Projects that require platform-backed key storage can inject IOSLQueueKeyProvider before first accessing OSLSaveManager.Instance.