Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
CloseFor some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
CloseSchedules an AssetDatabase.Refresh to occur on the next Editor application tick.
This method provides a better alternative to AssetDatabase.Refresh for situations where script assets, and other assets which depend on those scripts (such as prefabs) are modified at the same time.
This method is used internally by the package manager code when updating package samples to avoid duplicated imports. You only need to use this method if you are writing editor code which modifies or imports changes to script assets and assets which depend on those scripts at the same time.
In situations where you write scripts that modify only non-script assets, calling AssetDatabase.Refresh is sufficient, and causes your modified assets to be imported immediately.
However, in the scenario where you modify assets and the scripts they depend on, calling AssetDatabase.Refresh is not ideal because the dependent assets (such as prefabs) get imported twice. This occurs because AssetDatabase.Refresh runs immediately within your own script, and the Editor can't reload the scripting domain while your own C# code is running. Therefore only your non-script assets are imported in the refresh. The Editor then reloads the scripting domain after your script completes, triggering a second import on those assets which depend on the modified scripts.
Scheduling an AssetDatabase refresh on the next application tick instead of using AssetDatabase.Refresh means the refresh does not occur while your C# code is running, therefore the domain reload occurs first, and all assets are imported only once, after the domain reload.
Additional resources: AssetDatabase.Refresh
using System.IO; using UnityEngine; using UnityEditor;
public class Sample : MonoBehaviour { [MenuItem("Sample/Copy Assets")] static void CopyAssets() { CopyDirectory("Backup", "Assets"); AssetDatabase.ScheduleRefresh(); }
static void CopyDirectory(string source, string destination) { Directory.CreateDirectory(destination);
var sourceInfo = new DirectoryInfo(source); foreach (var nestedSource in sourceInfo.GetDirectories()) { CopyDirectory(nestedSource.FullName, Path.Combine(destination, nestedSource.Name)); }
foreach (var sourceFile in sourceInfo.GetFiles()) { File.Copy(sourceFile.FullName, Path.Combine(destination, sourceFile.Name), true); } } }
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.