-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config flag that drops -quit from builder #13
Comments
Yup sounds good! Thank you for your nice suggestion and the details. Accepting PRs for this. |
Added this to the Roadmap to v3.0.0. It should probably be configurable through a plugin. |
More use-case details in linked issue ^ |
For anyone else running into the limitation: As a quickfix you could just fork the repo and remove the
|
I didn’t see any way to suppress |
Context
My team has a situation where we can’t run playtests because of asmdef’s in Unity not working with our project flow, but instead found a way to validate things in-game by running a scene from the command line (scene is started from a static method). We want to start the scene to run the tests before a build, but you can't enter playmode from a static method in
-batchmode
if-quit
is also present.A configuration option that allows removing
-quit
from the Unity command line parameters would solve our issue (although it means we need to handle the exiting of the editor ourselves withEditorApplication.Exit(0)
)Suggested solution
Add a config like
quit
Bool whether the editor should quit after building
Note: If quit is disabled, your build method must handle exiting Unity with
EditorApplication.Exit(0)
on its ownrequired: false default: true
Considered alternatives
Forking the builder and monkey patching it
Additional details
We can't call
/opt/unity/Editor/Unity
ourselves since it's gone when you leave the build step. It would also mean we have to redo the licensing/etcThe following is some bash code that can handle the optionally passing -quit, although I don't have an equivalent for the Powershell build.ps1
The text was updated successfully, but these errors were encountered: