I dunno exactly when this started to happen, this week sometime probably. I don't play there really often so I don't know for sure.
So after about 5 minutes I get a 'warning: pb_security (1) must be equal to (0)' message and it boots me from the server.
I went back in and tried pb_security 0. Now the bizzare thing is I know all servers run pb_security 1 (and the reason it went back to 1 for me even if I changed it to 0). pb_security 1 is just a common command that every server uses. Why the hell am I getting kicked for not having it set to 0?
Probably because the Qu@ke n' W33d server admins have PunkBuster set to cvar check and boot you if you have pb_security set to 1. For what reason, I don't know.
To make it more convienent for youself, you can bind a key to togle pb_security on/off which you should be able to use while connecting or in-game:
set toggle_security vstr security_0
set security_0 "pb_security 0; set toggle_security vstr security_1"
set security_1 "pb_security 1; set toggle_security vstr security_0
bind x vstr toggle_security
It's server dependant. Every server has it at default (which is 1). If you change it in-game to say 0, it only looks like it's changed on your side, but if you do the sv_servercheck command (don't remember it quite fully) it will show you the real state of the cvar. If it's default at 1 on the server's side, you can't change it to 0 on the client side.
I used to have it at 0 in my autoexec.cfg But while in-game it would not parse it to 0. That's how I figured it can't be changed, unless maybe if the admin allows a 1/0 state. Or iz I wrong on this?
In any case, I don't know why the fuck I keep getting booted.
Eraser wrote:Forcing a pb_security setting sucks balls, because many computers completely freeze up in certain situations when pb_security is set to 1 or 0.
No, that's the pb_system setting you're refering to.
