On Thursday 18 December 2003 05:45, Brian A. Stumm wrote: > On Wed, 17 Dec 2003, Alfred Reynolds wrote: > > This is a bug, it shouldn't change these files every time (note > > that it will occasionally when we need to add new functionality, > > but this shouldn't be often). We are looking into it. > > > > On a related note this release will not re-verify your install > > every time you run the "steam" command (it doesn't download the > > file, it just checks that it is up to date). So if you ever delete > > or corrupt a file just run the steam command to get things back in > > sync. > > No offense but this is unacceptible. Overwriting config files which > have the potential to be lenghty and complicated without at LEAST > performing a simple "mv autoexec.cfg autoexec.bat" prior to doing so > is just silly. The community is making blanket statements to set > permissions to read only on these files and meanwhile valve feels > they need the ability to overwrite. Combine the above actions and we > are asking for problems.
It would be at least marginally tolerable if the "updated" config files actually /did/ something. but when I discover that this "update" nuked ALL the dod_<mapname>.cfg files (containing all the class limits amongst other things) with files containing the following text: //Blank for now I get a little annoyed. I suppose we should be thankful that server.cfg wasn't on the list of targets. This issue has been raised before (when steam first rolled out iirc), please valve for the love of mike exclude cfg files (and liblist.gam) from any future updates. Nick _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
