Bug Moving scripts

I notice that if you move scripts or change the name of a folder the object loses the script. It does not update the objects.

I even tried creating a new folder, moving a single script. The object loses it asking for where it is.

I think the word is detaches from the object.

Any fix for this?

 

Do you see in the Inspector of the object a yellow warning sign with a message that reads, that there may be a script error or the script is missing?

If you move the script within the editor, this should not happen.

If you move it outside the editor (eg Explorer, Finder) and you don't move the .meta file along with it, then losing the script reference is possible.

 

SCRIPTS OR ASSETS ARE MISSING OR BLANK

ALWAYS move all Unity assets by using the Unity Editor. Any other way risks disconnecting the GUID in the meta file from the original file, and this will result in all connections to that asset being broken.

Some info about Missing script warnings, broken prefabs, GUIDs, renaming GUIDs, etc:

https://forum.unity.com/threads/problem-with-git-and-missing-scripts.1090876/#post-7024801
https://forum.unity.com/threads/scr...ead-after-loading-editor.998413/#post-6487297
https://forum.unity.com/threads/scr...ead-after-loading-editor.998413/#post-6488230

EVERYTHING in Unity is connected to the above GUID, which is stored ONLY in the metafile, and hence why the metafiles ALWAYS MUST be source-controlled.

When Renaming: It is super-easy to inadvertently change the GUID by renaming outside of Unity. Don't do that. Instead:

- close Visual Studio (important!)
- rename the file(s) in Unity
- in Unity do Assets -> Open C# Project to reopen Visual Studio
- now rename the actual classes, and MAKE SURE THE FILE NAMES DO NOT CHANGE!

If you are NOT using source control while you do this, renaming files is an EXTREMELY dangerous process. Use source control at all times so that you can trivially revert if you miss a critical step and damage your project.

 

everything needs to know the asset path, to know where it is. If you change the path, without any chance of it updating that path, that path will get lost. Yup...

An analogy would be you set your favorite toy on the kitchen counter last you remember, you mom sees it and places the toy in your room. When you go back to where you last knew its location, the kitchen counter, it's not there! Error!

 

Yea I am moving everything in the editor. I know if you move it outside the editor it does this. But it also does it inside.

I tested it several times.

If I have a script, I used visual studio to change the class name. Does not update. Calls it missing. If I put the name back it updates.

If I move the script in the editor it does not update either. I have to remove the script and attach it back on the object. It reads as missing on the object.

 

Ohh yeah, doing it that way is a real pain. I've often found it much easier to make a new script named properly in Unity, then just copy/paste into the new script.

If I remember correctly(doing the hard way), you have to rename it in Unity, then rename it in VS, also have to rename the Class name in the script, then click on properties of the file in the properties window of VS and fix it's file name and path(if changed) in that too..

But as I mentioned, it's just much easier to make a new script, and just copy/paste the code over.

 

I've had no issue renaming files in VisualStudio *IF* I do it via refactoring the class name which also renames the file. But this only works because I have the Unity extensions in place and working as well. I'm not sure if renaming works in the project explorer since I basically never do it that way out of habit. Either way if you don't have the unity extensions in place and working properly (which can be trickier than it sounds) it won't work at all.