Feedback Feature request: Stop play-in-editor on Application.Quit

It's kind of annoying that I can't actually test that the "quit" option is working in my game unless I make a complete build.
I haven't actually had many problems because of this, but it still is something annoying me.

You know what would be a reasonable thing to happen? How about my test play stops? Just the same as if I clicked the "play" button again.

Or maybe a pop-up window? Well that might be annoying. But still, something to show that the game actually would try to quit at this point.

 

Let me introduce you to preprocessors:

Code (CSharp):

1.         public void QuitGame()
2.         {
3. #if UNITY_EDITOR
4.             EditorApplication.ExitPlaymode();
5. #else
6.             Application.Quit();
7. #endif
8.         }

 

I think it would be much cooler if

Application.Quit()

closed the Unity Editor entirely.
I need more crash-esque Unity Editor functionality in my life, and this would do just that.

In all seriousness though, I see no reason at all why

Application.Quit()

does not stop playmode by default.

 

There's actually this:
https://docs.unity3d.com/2021.2/Documentation/ScriptReference/Application-isEditor.html
So you should be able to do it without preprocessor.

 

I'm not too fond of adding the editor namespace to a script just for this.
It's a valid idea and lets me see what this would be like, though.

Honestly I still think it should just be built in to the editor. Maybe make it an option?

 

It doesn't require the editor name space.

In any case neginfinity's answer is better than mine.

 

It does.

EditorApplication is declared within UnityEditor.

 

I shall tick off my Monday morning brain fart then. My brain thought the processors were being referred to there.

 

You still don't need to import it, you can simply use the fully classified name

Code (csharp):

1. UnityEditor.EditorApplication.ExitPlaymode();

 

So hey! It turns out that if you have that ExitPlayMode code in your script, you can't create a build! It counts as an error, even though it works fine within the editor.

So yeah, a formal addition to the editor is still requested.

 

Did you have the conditional compilation flag around it? Because without it the build will try to reference the Unity Editor namespace, which it can't.

 

I did, in fact. The code should have been considered unreachable.

 

Did you put the conditionals around the namespace as well?

 

Unreachable code is still compiled, and compilability is the issue at hand.

 

On somewhat unrelated note, one of the amusing quirks of C# in comparison to C++, is that dead code that is never used can affect executable side. First, there's metadata (reflection data and attributes), which can grow quite large, second is that reflection you can't with certainty determine that something is never called. In comparison, C++ compiler and linker usually aggressively removes every unused function...