My folder structure got messy lately, because I was adding quite a few assets from the asset store. Normally, I don’t need to do any code changes there, so I thought maybe I could put them in a separate folder “External” inside the assets folder. One of my fears is, that an update from the asset store would create a new folder in the assets directory with all new and changed files. Did anyone try that / is there a possibility to define the path where the assets from the assets store should be saved in the current projects file structure?
The asset store import process is going some changes in the upcoming 5.3 release.
In any case, i think the import process looks at the GUID for the assets, and not their paths only; it should figure out that you moved those assets (you can create a small test in a new project - import the package, move it and then try to import it again).
I have run into the problem a few times where importing an updated asset duplicates content. What I do now is update in the asset store window, then right-click on the updated asset in my project view before selecting reimport. Hassle, but a lot less painful when you have a lot of asset store stuff lurking in a project.
