alt Hacker NewsWhat I really want is the ability to do more operations which are decoupled from the editor. Even just being able to reliably type check Unity C# code without a running editor would be great, or running unit tests. Would really improve things like CI as well as the ability to run parallel development sessions.
Replies
Rider and Visual Studio do this but you mean outside an IDE that's doing incremental builds on change?
Hmm I guess yeah you're going to need multiple separate workspaces to work on multiple large changes in parallel. For games that can be a large cost.
Multiple sandboxes on the same workspace wound be nice.
I did that for my Unity games like a decade ago, you can too :) Requires a design that has one core and then using Unity basically as a renderer/viewer though, but is a relatively easy design actually. And yes, automation and DX gets so much easier. I think Captain of Industry is built like this too, remember reading about it here on HN from the developers in some comments.
Headless execution exists and is one of the simplest ways to get at this experience.
The biggest issue with unity is that the editor (even when headless) is designed to take an exclusive lock over the physical project directory. This can be solved by doing a robocopy of the project to a temporary path, deleting any lock files, and then running headless execution there. You can keep the same temp path(s) over many iterations with incremental sync so it's not copying the entire universe each time.
This works for CI, LLM automation, etc.