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: $59.99. The latest store price is $119.99.
View 4 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| $119.99 | Latest store price | |
| $119.99 | Unity First Price 2026-08-26 2026-08-26 | |
| $59.99 | Unity New Release Discount 2026-08-26 2026-09-02 | |
| $59.99 | Unity New Release Discount 2026-08-26 2026-09-02 |
Sale and bundle history
The 3 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About Project Stability Toolkit
- Tools, Systems & Learning > Development Tools & Automation
Project Stability Toolkit provides Package Quarantine, NoReload Doctor, and Mobile SDK Conflict Doctor. You get all three complete tools, with their full workflows and reports.
Inspect packages before import
Package Quarantine checks a local .unitypackage before its files enter your project. See overwrites, GUID risks, Editor code, settings changes, and other clear warning signs.
It creates a verified recovery snapshot, opens Unity's normal import window, and records what really changed. You can keep the import or review a safe rollback.
Find fast Play Mode bugs
NoReload Doctor finds static-state risks when Domain Reload is turned off. Run repeat Play Mode cycles and see values, objects, events, and errors that stay or grow between runs.
Use Fast Play for daily work and Safe Play for a clean comparison.
Stop Android SDK conflicts
Mobile SDK Conflict Doctor checks AAR, JAR, Maven, manifest, Gradle, AndroidX, native library, and EDM4U evidence. It shows which SDK owns each file and why two SDKs may fight.
You can also import failed build logs and connect the error to the files that caused it.
Protect the whole project
Use the three tools together to check what enters the project, what survives Play Mode, and what may break an Android build.