BuildOptions.Development is ignored when running a batch mode build for the win64 buildTarget

6.5.X

As Designed

Thank you for reporting a bug to Unity. After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. We will close this case as 'As Designed.' The issue in this reproduction project is caused by the batch file generating two separate builds. The first is a non‑development build created by the command -buildWindows64Player buildoutput/build.exe. The second is produced by the custom build method com.magicfuelgames.unitybatchmodeexecute.BatchModeExecute.UnityBatchModeExecuteMethodWindows. If the intention is to build only through the custom method, the line that invokes -buildWindows64Player buildoutput/build.exe must be removed from Assets/batchbuild.bat. In addition, the output path defined in BuildConfigurator.cs (located under Packages/com.magicfuelgames.unitybatchmodeexecute/Editor, around line 356) should be updated so that the custom build method writes to buildoutput/build.exe. After applying these changes, Unity will correctly generate a single development build in the %ProjectPath%/buildOutput directory.