- After importing the pro version files, the free version was overridden. This is not a good behavior, because the pro version is an other product.
- Importing overrides the old files without asking for premission. If it is in your hand, don’t do it.
- Replacing files in my own directory ‘myscripts’, just because i copied the free version in it to change the files like the TargetMover.cs. I improved the TargetMover.cs file with an enhanced intelligent priority based formation for an RTS game (4-5 days work). This file was overridden by importing the Pro version, but for what reason? Just because the Directories have the same names? But this directory is in my own directory ‘myscript’, how can you change files in my directory? The strange thing is, the copied path finding was not populated with the pro version directories and files, just the free version files were overridden… Next time make a backup of the overridden files, or ask before you change them. Recursively search for a file in all the directories and change it is reckless!
Hi
I am sorry that you lost your work this way. Unfortunately it is not up to me, I also know UnityPackages are horrible at updating existing structures, but it is my only alternative (without going through lots of trouble to create a custom importer script).
If I would code it myself I wouldn’t have overridden those files.
That the pro version replaces the free version is however logical, if the pro version and the free version were both in the same project, that would just cause a lot of issues and is not something you would want to have.
To avoid these kinds of issues in the future I recommend that you start using some kind of version control (like git). It is really useful to have your whole project under version control. For example if something like this happened, I could just use a simple command to revert it to my last commit, or I could do a diff/merge to check what the pro version changed and merge in my custom changes to it.