To use the lobby to connect to your server. When in lobby, open a console and type: sv_cheats 1 ms_force_dedicated_server <ip:port>
Once you "Start" in the lobby, it should connect to your server. If your lobby was in Versus, it will be Versus, if it was in Coop, it will be in Coop. It's the easiest way to play the mode type that you want on your server without having to worry about trying to force your server to Versus. It also appears that some achievements can only be gained if you come from a lobby and not from a direct connect. (Finishing a campaign on expert for example) -- Ravnox On Thu, 05 Mar 2009 11:28:55 -0600 Jay Deiman <[email protected]> wrote: > I'm wondering what the recommended setup is currently for setting up > a steam group server for L4D. I'm currently running 4 forks with 4 > separate config files. 2 of the instances are steam group servers > and 2 are public. > > The public servers seem perfectly fine, but the question is about the > steam group servers. They both "start up" as coop (as opposed to > versus) servers that you just join. If I want to play coop, it's not > a big deal since I can join and vote a different campaign, > difficulty, etc. Now, here are my questions. Is there a way that I > can make one of the steam group servers a versus only server? Can I > override the "+map" setting from the command line in my server.cfg > file as well as the mapcycle file? Second, is there a way to make it > so that I can just connect to the steam group servers via a normal > lobby? > > I've posted both my command-line startup and one of the server_##.cfg > files for the steam group server below for reference to what I'm > currently doing. > > Thanks in advance for any help, > > Jay _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
