I've been following the documentation for local debugging of game servers, as documented here:
The first step is to edit `MultiplayerSettings.json` and set `RunContainer` to false and `OutputFolder` to somewhere to save output. And then to run MockVmAgent.exe in PowerShell.
When I do this, I get the following error:
```
Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Microsoft.Azure.Gaming.VmAgent.Common.Interfaces.ProcessRunner.CreateAndStart(Int32 instanceNumber, GameResourceDetails gameResourceDetails, ISessionHostManager sessionHostManager) in D:\t2\src\VmAgent\VmAgent.Common\Interfaces\ProcessRunner.cs:line 55
at Microsoft.Azure.Gaming.MockVmAgent.MultiplayerServerManager.CreateAndStartContainerWaitForExit(SessionHostsStartInfo startParameters) in D:\t2\src\VmAgent\MockVmAgent\MultiplayerServerManager.cs:line 49
at Microsoft.Azure.Gaming.MockVmAgent.Program.Main(String[] args) in D:\t2\src\VmAgent\MockVmAgent\Program.cs:line 69
```
After much trial and error, I worked out that it's trying to open the asset, specified in the "ServerStartParameters/AssetDetails/LocalFilePath" field, which in the default MultiplayerSettings.json is left as an empty string. Eventually I found that the only way to make things work was to put a zipfile there, and then to point 'StartGameCommand' at an executable inside that zip file (via the MountPath variable), which it duly launches by itself.
The documentation suggests that in this mode, MockVmAgent should just be a listener; that we'd need to run the server program ourself (perhaps through a debugger, which would be fab).. but MockVmAgent is launching the program itself, which.. doesn't seem like what the documentation suggests should be happening?
How can I actually put MockVmAgent into a passive listener mode so that I can actually run my server from a debugger and see it interact with the agent? Or am I completely misunderstanding how that is supposed to work?
Thanks for any advice/support!