Setting up local lobby and server

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 a local.cfg file and host it remotely for your client and server. An example local.cfg file can be found at http://alleg.egretfiles.com/Xynth/local.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 local.cfg files. A CfgFile string value set to the cfg file location (in my case "http://alleg.egretfiles.com/Xynth/local.cfg") needs to be added to the Microsoft Games\Allegiance\1.1 folder and an equivalent CfgFile value goes in Microsoft Games\Allegiance\1.1\Server. Additionally, create a ServerAddress string in Microsoft Games\Allegiance\1.1 folder that has a value of <LANIP>:2304 for example to match my local.cfg my key is 192.168.1.73:2304 .

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. Additionally, if you repeat the -regserver steps in the first paragraph on your objs10/FZRetail allsrv.exe and lobby.exe you can run those by simply executing them to give a less resource intensive server and lobby if you aren't debugging.