Posted November 21, 200321 yr I know this is the wrong place to post this but everyone seems to view GENERAL forums first so............... How can you keep the ADMINs from fucking your config.cfg shite up? I copied it and renamed it so that I could exec it if the ADMIN cocksucker decided he wanted to fuck with my shite. So far it works mint. But how can you keep the cocksuckin ADMIN out of your config.cfg?
November 21, 200321 yr right click, properties, read-only then it can't be changed by you OR admin, unless you reset properties :) they can still run other execclients on you, though..like +lookup, +back, +duck, or +right...but they have to run each individual command, and can't screw up purely config stuff...like volume, fps_max, rate, or whatnot.
November 21, 200321 yr Author right click, properties, read-only then it can't be changed by you OR admin, unless you reset properties :) they can still run other execclients on you, though..like +lookup, +back, +duck, or +right...but they have to run each individual command, and can't screw up purely config stuff...like volume, fps_max, rate, or whatnot. AH...READ only I should have known.....thanks Psycho.
November 21, 200321 yr np Butt :) BTW...advance warning...with read-only on, you can't change sensitivity in console...or anything else that alters the setings of your config.cfg file. I've found that it's easier to make alternate configs for common changes I make, protect them the same way, and include aliases to switch configs at the push of a button automatically, as a result. one example for legit playing in CS: I have a sniper config that is automatically executed when I hit the buyscript button from normal config for an AWP or scout...and the sniper config has a bind in the buy scripts for every other "main weapon" that switches back.... major differences in my "sniper.cfg" from normal config are pretty clear... mouse1 is bound "+attack;slot2" so as soon as I pop one off, it switches to pistol, until I hit "last weapon" again, and mouse3 ("special weapons function") has been modified..so when I click the mouse scroller, it automatically goes to max magnification scope, and toggles my sensitivity down to 1.337 when scoped, 4.9 when unscoped (increased accuracy)...basically, this was done by creating an alias for toggling sensitivity between two values, then doing <mouse3 bind "scopetoggle;senstoggler"> when scopetoggle s an alias alternating normla +attack2 command and "+attack2;pause;+attack2"
November 26, 200321 yr isnt there like a zoom_sensitivity_ratio command to fix sensitivity without aliasing? rifk awp script
December 10, 200321 yr just hit console when you know they changed your key, and bind it back. The admin will get pissed that his "neat tricks" arent working and keep on attempting to do it. Hit the up arrow in console and bind it back real quick and keep on attacking. He will use the same exact command usually like " bind "w" "exit" or w/e
December 10, 200321 yr also helps if you make a copy of config, called something only you will remember... then when admin unbinds you, just open console and type "exec <yourconfig>.cfg to repair..but I used to prevent guys doing this by unbinding console, or redefining "toggleconsole" as an alias that killed them
December 11, 200321 yr Doesn't OGC block all those commands? Alot of OGC clients had the block cmd removed.
December 11, 200321 yr just hit console when you know they changed your key, and bind it back. The admin will get pissed that his "neat tricks" arent working and keep on attempting to do it. Hit the up arrow in console and bind it back real quick and keep on attacking. He will use the same exact command usually like " bind "w" "exit" or w/e This doesn't work for shit if admin has half a brain...the first thing most admin who are going to play with execclient do is "unbindall", which USUALLY kills console access, and ALWAYS removes custom alias accesses
