Setting up local lobby and server

Warning! Article in work and currently inaccurate.

Setting up a local lobby and server running on your machine will allow you to test without using allsrvui.exe and allow for more straightforward debugging. To accomplish this, first locate objs10/FZDebug/lobby/lobby.exe and objs10/FZDebug/Fedsrv/allsrv.exe. Run both of these files once with the -regserver switch, i.e. create a shortcut to ...objs10/FZDebug/Fedsrv/allsrv.exe -regserver or navigate there using the command prompt and run allsrv.exe - regserver and lobby.exe -regserver.

The next step is to create .cfg files and host them remotely for your client and server. An example client .cfg file can be found at http://alleg.egretfiles.com/Xynth/FAZR6.cfg and a sample server .cfg file is at http://alleg.egretfiles.com/Xynth/temp.cfg These files will need to be edited to replace all instances of the local IP (192.168.1.73 in these files) with your local (inside the LAN) IP address found with ipconfig at the command prompt.

Finally, your registry needs to be edited to point to these remote cfg files. A CfgFile string value set to the cfg file location (in my case "http://alleg.egretfiles.com/Xynth/FAZR6.cfg") needs to be added to the Microsoft Games\Allegiance\1.1 folder and a similar CfgFile value pointing to your server cfg goes in Microsoft Games\Allegiance\1.1\Server.

Now to start a debugging session in Visual Studio, right click the appropriate projects and select Debug->Start new instance. Do this for the Lobby, Server, and Allegiance project in that order.