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: $14. The latest store price is $15.
View 5 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| $15 | Latest store price | |
| $15 | Unity Permanent Decrease 2026-10-15 2026-10-22 | |
| $20 | Unity First Price 2026-08-04 2026-08-04 | |
| $14 | Unity New Release Discount 2026-08-04 2026-08-18 | |
| $14 | Unity New Release Discount 2026-08-04 2026-08-18 |
Sale and bundle history
The 4 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About BundleGuard — AssetBundle Update Guard & Version Diff
- Tools, Systems & Learning > Development Tools & Automation
If you ship content updates with raw AssetBundles without re-releasing the whole app, your bundles can quietly drift between versions. An asset gets removed or renamed, a type changes, a script comes off a prefab, a shared bundle stops being built — and the update breaks for everyone still on the previous version. It fails late, in production, and it's painful to trace.
BundleGuard turns each build into a versioned snapshot of your AssetBundles, then compares any two versions and warns you — before you ship — about anything that would break live clients: removed assets, changed types, prefabs whose script no longer resolves, and dependency changes between bundles, like a shared bundle that vanished or a new dependency older clients have no way to know they must download. It also tells you how much of your next update is genuinely new content versus bundles that were rebuilt for no reason, and can drill down to the exact asset — and even the component inside a prefab — that changed.
How it works: open BundleGuard → Compare Builds, point it at your old and new build folders (or saved snapshots), and click Compare — BundleGuard reads the finished bundles, with or without their .manifest files (it never builds or changes anything). Save a snapshot for each release; before the next update, compare them. You get a clear, color-coded report of breaking changes, the full catalog diff, and an update-impact summary — how many MB players will re-download, and how much of that is wasted churn. Export the whole comparison as JSON for a release ticket or your own tooling.
Wire it into CI. The same check runs headless: after your pipeline builds bundles, one command compares them against the version you shipped and fails the build when the update would break players still on it. A separate exit code tells "this update breaks players" apart from "BundleGuard could not check", so a misconfigured step never looks like a pass. The report comes out as JSON for tooling or Markdown for a pull-request comment, and changes that are breaking on purpose go in an ignore file, so one planned removal does not leave the pipeline red forever.
Works with any project, any genre. BundleGuard is a developer tool, not content — there are no assets to customize and it isn't tied to a genre. It works with any Unity project that ships raw AssetBundles (not Addressables), and is especially valuable for live-ops and mobile titles that push frequent content updates. Analysis is strictly editor-only and read-only: BundleGuard never modifies your project or your assets.
BundleGuard turns each build into a versioned snapshot of your AssetBundles, then compares any two versions and warns you — before you ship — about anything that would break live clients: removed assets, changed types, prefabs whose script no longer resolves, and dependency changes between bundles, like a shared bundle that vanished or a new dependency older clients have no way to know they must download. It also tells you how much of your next update is genuinely new content versus bundles that were rebuilt for no reason, and can drill down to the exact asset — and even the component inside a prefab — that changed.
How it works: open BundleGuard → Compare Builds, point it at your old and new build folders (or saved snapshots), and click Compare — BundleGuard reads the finished bundles, with or without their .manifest files (it never builds or changes anything). Save a snapshot for each release; before the next update, compare them. You get a clear, color-coded report of breaking changes, the full catalog diff, and an update-impact summary — how many MB players will re-download, and how much of that is wasted churn. Export the whole comparison as JSON for a release ticket or your own tooling.
Wire it into CI. The same check runs headless: after your pipeline builds bundles, one command compares them against the version you shipped and fails the build when the update would break players still on it. A separate exit code tells "this update breaks players" apart from "BundleGuard could not check", so a misconfigured step never looks like a pass. The report comes out as JSON for tooling or Markdown for a pull-request comment, and changes that are breaking on purpose go in an ignore file, so one planned removal does not leave the pipeline red forever.
Works with any project, any genre. BundleGuard is a developer tool, not content — there are no assets to customize and it isn't tied to a genre. It works with any Unity project that ships raw AssetBundles (not Addressables), and is especially valuable for live-ops and mobile titles that push frequent content updates. Analysis is strictly editor-only and read-only: BundleGuard never modifies your project or your assets.