Ok... This is what I did:
I shut down HLDS Emptied banned.cfg Write protected it Started HLDS Wrote "writeid" in console Got message "cannot write to banned.cfg" Shutdown HLDS Took away "read only" Started HLDS Wrote "writeid" in console Checked banned.cfg and there were all the 188 Steam ID's again!
Pretty frustrating. :-(
The reason why I want this to work is that I cannot edit the banned.cfg file as I want. When I want to add a bunch of ID's they dissapear after writeid get send to console. Only those registrated by writeid are left in the banned.cfg file.
//DiS|Fox
From: "Mikee" <[EMAIL PROTECTED]>
Sorry, I didn't realize you were talking about CS which has the file called banned.cfg, but did you try uploading your correct banned.cfg after making it a read only file that cannot be overwritten, then issue the "writeid" command at console which cannot overwrite your temporary "read only" version, but may replace the cache version stored somewhere, then re-upload a replacement banned.cfg which has the same data, but is not read only protected after you resolve it?
_________________________________________________________________ L�ttare att hitta dr�mresan med MSN Resor http://www.msn.se/resor/
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
