using UnityEditor outside of Editor folder when compiling build?

Questions & Answers
1

DESPERATELY need help. I have some scripts in a folder called Scripts, NOT in an Editor folder.

One of these scripts contains ‘using UnityEditor’. It has a function it uses to save the state of the scene in a new scene, load another scene to play a video, then loads the temporary scene. This works fine in the Editor and everything is brilliant.

BUT when I go to compile the game in to a build, BAM, it doesn’t work. I desperately need help and will be closely monitoring this question every minute until I have an answer or…something. I can submit code etc.

Main error:

“The type or namespace name `UnityEditor’ could not be found. Are you missing a using directive or an assembly reference?”

I have read that to fix this error, the script in question should be moved to the Editor folder. This I do. Then other scripts fail because they don’t know how to refer to the script in the Editor folder. Is there anything I can do? Please anyone, help! :frowning:

Many thanks in advance.

2

Damned if you do, damned if you don’t. :slight_smile:

If the class is referenced (directly or indirectly) by code going into the build, but its functionality isn’t actually used in the player, you can use conditional compilation to build a stub version into the player, which doesn’t reference UnityEditor. Basically, like this:

#if UNITY_EDITOR

using UnityEditor;
public class Whatever {
    public void foo() { EditorApplication.Beep(); }
}

#else

public class Whatever {
    public void foo() { }
}

#endif
3

Welll… if you don’t actually need to permanently save the game, just put it “somewhere” while some other scene is doing its thing, try this:

  1. Have a gameobject, with a script which does the following:
  2. Gets a list of all the gameobjects in the scene, in a class member variable.
  3. Disable all of them EXCEPT the gameobject itself.
  4. Load the new scene additively. This scene should have exactly ONE root object; all other objects should be its children. This root object should have a known name.
  5. Do whatever you want to with the new scene. Afterwords…
  6. Destroy the root object of the new scene.
  7. Re-enable all of the objects in your saved list of gameobjects.
4

I tried a bunch of these solutions and ones very similar to this. Nothing was working until I realized I had a few empty .js files that I had saved and never added any script to. Once I deleted these blank .js files everything seemed to work. Double check any scripts you may have left blank and if you have any delete them.

5

Just remove the “using UnityEditor;” and you’re golden.

In batch mode, if you pull in UnityEditor, but are not referencing any of its objects, Unity preprocessor doesn’t know to skip that library so it throws the error.