You fell vitcim to somthing called "admin slowhack".
It was previously made as a CS mod to thwart hackers, allowing the server admin to mess with their config files. Sadly, it generally only gets abused.
Make your config files read only to prevent this, or just simply play on VAC servers only. (2nd choice is far wiser.)
The idea of server admins running client scripts that alter your files literally, is in some legal eyes illegal. I for one, agree that it should be dis-allowed.
Found a nice little link for you:
http://home.covad.net/~k25125/Steamy...lowhacking.htm
Quote:
Here is the situation which I will summarize:
Players sometimes have their config.cfg settings slowhacked by server admins or sometimes accidentally change their own configuration. This is the file that contains all your keyboard settings and game controls.
Slowhacking is the process whereby Server Admins attempt to either punish misbehaving or cheating players or abusively mis-configure any player's keyboard and game control settings.
Normally to protect themselves, players should only have to mark their config.cfg file Read Only (R/O) (right-click, properties) and their settings should be safe. It is always a good idea to make a backup copy of your config.cfg file regardless.
Your config.cfg is located in your MOD directory, for example:
C:\Program Files\Steam\SteamApps\<email>\counter-strike\cstrike\config.cfg
C:\Valve\Steam\SteamApps\<email>\counter-strike\cstrike\config.cfg
However under certain conditions, config files that are marked R/O can still be modified by the player from the game console or by a slowhacking admin.
This is NOT an operating system specific problem and it is not a MOD specific problem and it is not a bug.
Instead this is an operational feature of the Half-Life Game itself which is enabled under certain circumstances.
Players with their config.cfg files marked R/O are reasonably safe as long as they do not enable > Developer Mode <.
Putting your client in developer mode automatically gives HL the ability to override the R/O attributes of your config.cfg file and will allow modifications to be written out.
This situation has been tested and verified in all MODs currently available through Steam
The safest procedure is:
1. Mark your config.cfg R/O.
2. copy your config.cfg to a backup file.
3. set developer 0
In addition, config.cfg automatically executes a second file called userconfig.cfg if it is present in the same directory.
You can put all you custom settings there if you prefer and that file is never written by HL and is not accessible by any server admin.
|