Setting up CoD: World at War Custom Map and Mod Server
Monday, February 09 2009 @ 09:40 AM GMT

by Claire Claws
We already have an article on How To set up a Openwarfare Mod & Custom Map server when you rent a Call of Duty: World at War server from a Game Server Provider.
But for those who have an own, remote controlled, Call of Duty: World at War Windows server a different tutorial is handy to have. Especially now some things are 'named' different then in the previous versions of Call of Duty. For one... you now must use "fs_localAppData" in your command line.
Here an example of a CoD:WaW command line. Notice the CoD: WaW folder is not stored on C: but on a storage HD F:
F:(backslash)CoDWaW(backslash)CoDWaWmp.exe +set dedicated 2 +set net_ip xx.xxx.xxx.xx +set net_port 28960 +set fs_localAppData "F:CoDWaW" +set fs_game mods/openwarf +exec server.cfg +map_rotate
The above command line starts the .exe. Then it tells where the server can find mods and usermaps folders, what mod folder to use (openwarf) and to use the config file inside, here named server.cfg.
The use of fs_localAppData is new and has to be added because, just like Players Profile, a player now gets personal information and downloaded extras stored here; C:-Documents and Settings-name-Local Settings-Application Data-Activision-CoDWaW
So where do we put Mod and Map files/folders and how do we get the re-direct download to work ?












