I tried from the south but it wouldn't work that way. Had to destroy the German infantry interrupting the rail line going to Alexandria then make sure my supply ran to Alexandria with the barrels showing on the map. I had to make sure the rail line was uninterrupted from the north of the map to Alexandria.

Or with a custom build output path ~/Unity/Hub/Editor/2019.4.30f1/Editor/Unity -batchmode -nographics -logfile stdout.log -projectPath /path/to/the/project -buildPath path/to/build/destination -executeMethod ScriptedBuilds.Originally posted by me:finally got it to work for me (learning the tutorial). ~/Unity/Hub/Editor/2019.4.30f1/Editor/Unity -batchmode -nographics -logfile stdout.log -projectPath /path/to/the/project -executeMethod ScriptedBuilds.PerformHeadlessLinuxBuild -quit Simply use the scenes from the build settingsīuildOptions.EnableHeadlessMode | BuildOptions.StrictModeĪnd then e.g. if the output folder doesn't exist create it now Var args = Environment.GetCommandLineArgs() add '-buildPath some/Path' if you want a different output path Var buildPath = Path.Combine(Application.dataPath, 'BUILD') As a fallback use /BUILD as output path Instead of using -buildXYZ you could use -executeMethod and within that method define the exact player and build settings you want before starting the build process #if UNITY_EDITOR Under CommandLine Arguments you can find for how to trigger a scripted build via the console. You can also build to the Windows version as a console app so that stdin and stdout are accessible. With the UNITY_SERVER define, which means you can write server-specific code for your applications. When you enable this option, Unity builds managed scripts Usually you would go to the BuildSettings and enableĮnable this checkbox to build the Player for server use and with no visual elements (headless) without the need for any command line options.

they do not apply to the actual resulting built application ) However, these two flags only apply to this instance of the UnityEditor which performs the build. As you can see I used 'batchmode' and 'nographics' flags which were supposed to prevent the user interface to appear.

Unity hub command line