I did some experimenting this morning. Linux, SM 1.3. About half the times I restarted the server, it would change to the lobby settings the first time I tried connecting. The other half, it stuck with the settings the server was already on. Even after my initial failure to get the lobby settings on the first connect, every subsequent connection resulted in the proper lobby settings being applied.
So, if it's SM, it doesn't seem to be version specific, but I'm starting to believe it's not SM. It COULD still be metamod, but without the server consistently not switching to the lobby settings on the first connection, it's hard to troubleshoot. The logs contain no information about any errors either. Can anyone offer any advice? Has anyone else seen similar behavior? Any server config settings that I can apply that might help? On Fri, Jan 29, 2010 at 2:36 PM, Andy C <[email protected]> wrote: > I recently switched from one provider that had Windows server to another > provider that has Linux servers. Now, I find that sometimes when I try > connecting to my server via the lobby, the server doesn't switch to the > lobby settings. For example, if me and my clanmates meet in a lobby, get a > VS game set up in the lobby, then connect, it might kick 4 players and put > us in a CoOp game on the default map and difficulty. > > This never happened with the Windows server. I copied the config file over > from the old servers to the new ones. The only mods installed are Metamod, > Sourcemod, Announcements, and L4D Stats. > > Sometimes if I join the server first through a coop lobby, then quit, the > next time I join it'll go to the right settings, but even that isn't > reliable. > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
