This article was originally posted on Random Bits. Check it out for more Unity related content.
What can you do when a team member suffers a recurring Unity editor crash, losing all level design work ? My answer was to write a small and helpful editor extension - auto save! (and then blog about it).
This post describes a simple solution for implementing auto save in Unity that saves the currently open scene every 5 minutes (configurable).
The code is available for easy consumption in a few ways:
The code is imported and works out of the box, import / paste it into your Unity project and you're good to go.
It started a few days ago: a member of our team started experiencing occasional Unity editor crashes a few times daily. We do not know the exact reason for crashes, but we suspect it may be related to memory issues combined with voodoo magic. No matter what the root cause was, these crashes caused real damage in lost data (game levels) which we could not afford having.
In order to keep lost work to a minimum, I suggested to implement a basic auto save solution, so at least we can go back to a backup in case the editor crashes.
Solution - AutoSave
The solution uses pretty simple editor scripting to the rescue. The process can be described in 3 main steps:
- Hook a delegate to EditorApplication.update.
- In this method, check if the scene should be saved (if the configured time has elapsed. The default is 5 minutes).
- In case we need to save, generate a new unique name for the scene and save it to disk.
In order to have the code up and running when you launch the editor, the class is marked with the [InitializeOnLoad] attribute and initialization is done in its static constructor.
Show Me the Code
This is the complete code, you can paste it into your project:
Built In AutoSave
It should be noted that apparently Unity does autosave the current scene every time you enter play mode. If this is enough for you (for example - the game crashed during play mode), a copy of the scene can be found in YourProject/Temp/__EditModeScene.
The code in this post helps ensuring no scene data is lost when experiencing editor crashes. I deliberately kept it short & simple so it can be easily "digested". Autosaving can be further visited by adding any of the following:
- Configuration - Allow controlling autosave (turning on/off, setting time interval) from an editor window or menu item.
- Capping number of autosaves - Nobody really needs 50 copies of the open scene; instead, only 1 or 2 copies can be saved and recycled on every new save.
- New save triggers - The current code saves every X minutes. The code can be adapted to save under different scenarios.