Posted May 6, 200717 yr Protecting yourself against nasty Admins By oblivion11 Fed up of admins messing with your game? This thread will give you steps to take to prevent admins messing up your game... #1 - Protecting your config file (most important!!) You need to set your config.cfg file to 'Read-only' status. This file is located in the directory: C:\Program Files\Valve\Steam\SteamApps\STEAM-ACCOUNT\counter-strike source\cstrike\cfg\config.cfg (replace STEAM-ACCOUNT with your steam account) when you have found your config.cfg file Right-click > Properties > Tick Read-only box > Click Apply > Close the window Doing this will save your game unique game settings such as your name, video settings amongst other things. So with this on 'Read-only' status, your game settings will always return to their original state no matter what an admin does. Also, if you change your own settings they will also be reverted to their original state upon game restart. #2 - Having a none-changeable name Many admins like changing your name to silly things, or slightly changing your name to have it spelt wrong or make some kind of joke/comment. You can disable ANYONE changing your name, including yourself by doing this; Open your config.cfg file (refer to #1 if you don't know where this is) with notepad. Scroll to the bottom and add the following on a new line: alias "name" "say Name_Change_Disabled" Save the file (you'll need to 'UnRead-only' it to save). Now if you or an admin try and change your name Name_Change_Disabled will be disabled in chat To change your name, either delete the above line from your config.cfg and save it, or change where it says name "yournamehere" in your config.cfg file. #3 - Creating a config reset key Sometimes silly admins bind your keys to do silly things, a popular one is bind "mouse1" "kill" so every time you attack using your mouse you kill yourself, another is bind "mouse1" "say FIRE!!" so every time you try and shoot you say FIRE!! in chat. Indeed a real nuisance. Pressing your reset key will fix the problem. Open your config.cfg file (refer to #1 to where it is located) open it in notepad, scroll to the bottom and add a new line. Paste this in your new line: bind " KEY " "exec config.cfg" Replace KEY with the button you want to use as your reset key, I recommend using J, F11 or F12. For example if I wanted my reset key to be F11 my new line would look like: bind "F11" "exec config.cfg" So every time your game starts doing funny things when you press buttons, simply hit your reset key to fix the problem! #4 - Disabling +actions This is OPTIONAL so it's up to you if you decide to have it. It is an addition to your Reset Key, key. It will fix your actions in game so if an admin uses +attack which forces you to fire none-stop this will reverse the effects. Open your config.cfg file and paste all these at the bottom: -alt1 -attack -attack2 -back -break -camdistance -camin -cammousemove -camout -campitchdown -campitchup -camyawleft -camyawright -commandermousemove -duck -forward -graph -grenade1 -grenade2 -jlook -jump -klook -left -lookdown -lookup -mat_texture_list -movedown -moveleft -moveright -moveup -reload -right -score -showbudget -showbudget_texture -showbudget_texture_global -showscores -showvprof -speed -strafe -use -vgui_drawtree -voicerecord -walk -zoom Save the file. Now just hit your reset key if your player starts doing stuff without you touching anything. NOTE: This will also stop any scripts you may have running #5 - Harmful Commands to Disable (Advanced-Users Only) Some commands harm your game, to disable them from ever being changed/executed/used you need to open your config.cfg file (refer to #1) and add the alias to a new line. It must be a on a new line at the bottom! I've added comments using // to them. Only put these in your config.cfg if you know what you're doing and you understand the effects!! alias "fps_max" "say fps_max_DISABLED" // limits your maximum frames per second alias "quit" "say QUIT_GAME_DISABLED" // prevents you or admins closing your game, you must close your game using Task Manager alias "quit prompt" "say QUIT_GAME2_DISABLED" // must be used with the above for full effectiveness alias "cl_cmdrate" "say RATE_SET_DISABLED" // This will disable your rates being changed by most servers, some admins may kick for having low rates, and some servers auto-kick you because it can't change your rates. alias "kill" "say suicide_DISABLED" // prevents admins from killing you via kill command, may prevent slaying from some admin mods Notes & Things To Remember * Admins that do this are not 'hackers' they are simply using server side plugins which most servers have. * If your Reset Key doesn't work type exec config.cfg in console. * If an admin messes up your computer, you can't do anything lawful to get back at them, apart from never joining their server again and telling your personal CSS friends about the incident so they avoid the server in the future (people at Steam forums are not your CSS friends so don't come telling us about it!) * Posting in the Steam forums about so n' so admin messed up your game won't get the server admin in trouble. * There is nothing you can do to 100% protect yourself from server admins. * The admins are usually the owners or contributors, they can do anything they want, as it is their server. So arguing with them doesn't usually achieve much. * Not all admins are evil , they are there to help you, not look for reasons to ban you. * Constant chatting and insults and general stirring in servers provoke admins to punish you, so just behave. * Admins can't get you VAC banned even if you are obviously cheating/hacking, don't know if this is the case in CS1.6... * Admins running commands on your game is not illegal, so don't start calling your lawyers if they messed with your game. Thanks, oblivion11 sorry if I put this in the wrong section :happysad: Source http://www.csevolution.com/tuts10.php
May 6, 200717 yr * If an admin messes up your computer, you can't do anything lawful to get back at them, apart from never joining their server again and telling your personal CSS friends about the incident so they avoid the server in the future (people at Steam forums are not your CSS friends so don't come telling us about it!) Or you would just come back and ask then to turn on sv_cheats 1 just for a round or even 1 second :) Protecting yourself against nasty Admins That would be me :) I got even some special scripts to control players :D Open notepad then type in the following ma_cexec #t "+forward" wait;"wait;wait;wait;wait;wait;wait ma_cexec #t "-forward" Now save it as a .cfg file Bind it to a key, I prefer using the numpad keys :) So the 5 would be forward The 2 back the 3 right the 1 left The 4 Shoot The 6 reload Its to fun to keep playing when you are dead :) especialy teamkilling :D p.s use this on servers you got admin (I like the combination of rcon takeover in servers with sv_cheats 1 , then adding yourself as mani admin xD & using these scripts ) If you have some brains u can make ur own cool scripts to play with :) :lmfao:
May 6, 200717 yr Honestly, that guide it pretty horrible. Most of that stuff is pointless if you make your config Read Only. All you'd have to do if someone fucks with you is re-exec your config.cfg. Also, some of those "Notes & Things To Remember" are pretty autistic... Jesus. Also, AcidFox. Wouldn't you be able to do something like this? alias +e.forward "ma_cexec #t +forward" alias -e.forward "ma_cexec #t -forward" bind "key" +e.forward I'd test it but, yeah...
May 6, 200717 yr yes you could work with aliases but my config is read only and i just binded the cfg's to the keys :naughty: p.s (To get mani when u got rcon simply do the following) ma_client addClient "namehere" (I mostly use invisible name or if other admins got names like Client_1 , then i call myself Client_2 ) ma_client addSteam "name of client" "steamid" ma_client setaflag "name of client" "+client"
May 6, 200717 yr I know all that, just didn't feel like testing. Also, doesn't matter that your config is Read Only. The only difference it will make is the bind command won't stay if you restart Source (or re-exec your config.cfg). (Sorry for the common sense.)
May 16, 200717 yr Effort = FAIL. This shit is crap = just set your config to read me only. Problem solved.
