I feel like an idiot, and I should. The problem was a UNIX/DOS text file issue. It was fixed by converting the line terminating characters to a UNIX format. This has never been something I've had to explicitly do before with the mapcycle file before, but apparently it was needed this time.
Sorry for wasting your time. On Wed, May 15, 2013 at 7:37 AM, Lucas Wagner <[email protected]> wrote: > I wrote this when it was late and I was tired. What I meant to say was on > the third server, the server boots to pl_badwater and the map cycle file is > set to > > pl_badwater > cp_gorge > pl_upward > > Regardless, it does not want to cycle, at all. Not according to the file > I've specified in the custom directory "custom/mapcycle/mapcycle.txt" which > is called out in the mapcyclefile cvar, nor according to the default > mapcycle.txt. > > Sorry for the confusion. > > > > On Wed, May 15, 2013 at 12:24 AM, Lucas Wagner <[email protected]> wrote: > >> I am running three servers, they are hosted. I am setting the >> mapcyclefile cvar to "custom/mapcycle/mapcycle.txt" >> >> On two of the three, the maps are cycling as I would expect. The server >> boots to pl_badwater, and the map cycle file is set to the following >> >> pl_badwater >> cp_gorge >> pl_upward >> >> I've verified the cvar is set correctly via console. Yet, when I execute >> "nextmap" from console, it comes back telling me that the next map is >> always pl_badwater. I've also confirmed that the server is constantly >> cycling through just Badwater, never visting Gorge or Upward. I've >> verified several times that everything is spelled correctly and this is not >> just a typo. >> >> Is this a known bug? >> >> Thank you, >> >> Lucas >> > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
