Hopefully the subject is enough to begin setting the stage. Up until tonight's update (9/14), we had a working fast download that would serve custom maps to connected/connecting players if they did not already have them, and they would be able to play.
We have a properly configured HTTP redirect. I've only been doing this for about the last 6 years so I don't need any well-meaning-but-presumptuous-and-contextually-irrelevant tutorials on sv_downloadurl, bzip2, etc. After the update, a server we allow custom maps to be voted in proceeded to basically fill up (36 public slots, or 37 total counting the reserved slot). However with the config we run, via manipulation of the mapcyclefile and mapgroup cvars based on player count, the server was running stock valve maps for most of the time as the player count built up. Eventually, a custom map (de_nuke_ve) got voted in. Once the server changed to de_nuke_ve, we saw many (connect-announce plugin based) connect announcements as players began reconnecting at map change, followed by disconnects. OF EVERY SINGLE PLAYER. My wife and I, on the local network, were the only 2 players on the server with the bot_quota of bots, despite the multitude of connect announcements from internet players. We lost everybody. A FULL SERVER OF HUMAN PLAYERS. Now, before somebody knee-jerks "you sure you have your custom maps set up properly in your pure server whitelist config?" -- know this: sv_pure is disabled. So is sv_consistency. It's not that I want either of them to be off, it's just the way CS:GO is right now. You couldn't run dedicated servers with either of them ON. (and the reason I say this is: I can vouch for my game config and my wife's -- we haven't modified ANYTHING - but our own servers would kick us for violations with pure or consistency enabled) So it's not an sv_pure or sv_consistency problem. I jumped into console for this server and checked, just be sure our "no config changes" update didn't finagle-force pure and consistency ON despite my explicit configuration to turn them off. They were both still OFF. Yet NOBODY - not ONE SINGLE PLAYER - including many who according to voice chat leading up to the map change were well familiar with de_nuke_ve, could connect/reconnect to our server once it changed to de_nuke_ve. But as soon as we changed the map back to a stock valve map, we started seeing players come back. Maybe if I write down Einstein's definition of insanity on a piece of paper, and lay it under my pillow, it will finally seep through. Tackdriver _______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
