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: FREE. The latest store price is FREE, matching the lowest recorded price shown here.
View 2 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| FREE | Latest store price | |
| FREE | Unity First Price 2026-07-22 2026-07-29 |
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 Configurable Autosave
- Tools, Systems & Learning > Development Tools & Automation
Lose an hour of level design to a crash and you only make that mistake once. Configurable Autosave saves every open scene while you work, so an editor crash, a power cut, or an accidental Play Mode entry never costs you more than one interval of work.
It runs quietly in the background. A save icon in the status bar shows the current state at a glance, and a countdown notification appears before each save so you always have a moment to skip it. Nothing is hidden in a config file — every option lives in one window, and changes apply the moment you make them.
FULLY CONFIGURABLE
Every behaviour is a setting, not an assumption:
- Save interval, from 10 seconds to 10 minutes.
- Countdown duration, from 0 to 30 seconds. Set it to 0 for silent, instant saves.
- Save only when a scene actually has unsaved changes, so you are not writing identical files to disk and creating version control noise.
- Save before entering Play Mode.
- Log each save to the Console, off by default so a short interval never floods your log.
Settings are stored per user in EditorPrefs, not in the project, so everyone on your team keeps their own preferences and nothing is committed to version control.
SUITABLE FOR ANY PROJECT
This is an editor workflow tool, not gameplay content, so it is genre-agnostic and pipeline-agnostic. It is equally useful in a 2D mobile game, a VR title, or an architectural visualisation. Solo developers and teams both benefit — the only requirement is that you open scenes and edit them.
SAFE BY DESIGN
Autosave never writes during Play Mode, because changes made while playing are discarded by Unity and saving them would be wrong. It also stands down while the editor is compiling or importing.
Every script lives in an Editor folder, so nothing compiles into your player build. Your build size is unchanged.
It runs quietly in the background. A save icon in the status bar shows the current state at a glance, and a countdown notification appears before each save so you always have a moment to skip it. Nothing is hidden in a config file — every option lives in one window, and changes apply the moment you make them.
FULLY CONFIGURABLE
Every behaviour is a setting, not an assumption:
- Save interval, from 10 seconds to 10 minutes.
- Countdown duration, from 0 to 30 seconds. Set it to 0 for silent, instant saves.
- Save only when a scene actually has unsaved changes, so you are not writing identical files to disk and creating version control noise.
- Save before entering Play Mode.
- Log each save to the Console, off by default so a short interval never floods your log.
Settings are stored per user in EditorPrefs, not in the project, so everyone on your team keeps their own preferences and nothing is committed to version control.
SUITABLE FOR ANY PROJECT
This is an editor workflow tool, not gameplay content, so it is genre-agnostic and pipeline-agnostic. It is equally useful in a 2D mobile game, a VR title, or an architectural visualisation. Solo developers and teams both benefit — the only requirement is that you open scenes and edit them.
SAFE BY DESIGN
Autosave never writes during Play Mode, because changes made while playing are discarded by Unity and saving them would be wrong. It also stands down while the editor is compiling or importing.
Every script lives in an Editor folder, so nothing compiles into your player build. Your build size is unchanged.