Don’t want to interfere in this nice discussion you 2 have going on 
But I just wanted to know how you relate the bug in v1.081 (which could be ANY kind of bug) to getting kicked for server incompatibility?
As far as I can tell you were getting kicked because of a bug in an older version, not because client and server had a different version.
@DG, I know, but he’s only kept this one going for 1 page, and all he can do is repeat himself. Disappointed tbh, not the IRON_MAN of old 
@SickBoy, he can’t, that’s the point, and that’s how you know he’s Trolling. He’s quoted that same snippet 5 times, on this page alone, even though no-one’s disputed it and despite the fact it has no relevance to this thread or the particular point in question. Hilarious! What’s even funnier, he keeps berating me for allegedly not reading it! ROFL, I haven’t had this much fun on the SD forums since the last time IRON_MAN was laughed out of town.
One of your problems, is that you are ignorant to all of those who have been getting kicked recently, so like a dork, you assume nobody is getting kicked.
Or to put it in your own kind of words : “One of my problems is, I get kicked from a server when it’s running this old bugged version and I am not, so like a dork, I assume it’s because we run different versions”
No. pb_security is a PunkBuster command, not an ET cvar. It cannot be set by using “set” or “seta”, so adding that line to your config file will do exactly nothing. Instead, the command should be entered in the console like so:
\pb_security 0
Or, you could bind it to a key with:
\bind x "pb_security 0"
In any case, the pb_security setting gets reset to “1” whenever you restart ET, so you’d have to set it to “0” manually every time you run ET and connect to a troublesome server.
Kendle, I hate to fuel our beloved forum troll, but your statement is not entirely correct. What you’re not taking into account is the PB security information (i.e the MD5 checksums of the PB server, client and anticheat files) that’s contained in the client’s pbcl.db file. If you’ve installed ET a long time ago and never deleted this file, it will contain the checksums of all the PB versions back to the first release. Whenever a new PB file is released, the PB master will offer the checksum information of the latest version to the clients, which poll the master every few minutes. If they’re not there already, the checksums get added to the pbcl.db file.
Now, whenever the PB client connects with a PB server, the server tells the client which client files to use. With a PB server that’s properly updated, this will normally be the latest client and anticheat versions. The client then checks its pbcl.db file to see if it has the security checksums for those versions. If it has, will activate them or it will download the files from the server if it doesn’t have the corresponding .htm files aready (and activates them after download). In this situation, your statement is correct.
IF, however, the client doesn’t have the security checksums in its pbcl.db file, then there is no way for the client to validate the validity of the PB files received from the server. This might happen you someone has reinstalled ET or has deleted the
“pb” directory. As a result of these missing checksums, the PB client will not activate those client and/or anticheat versions. On the server, you’ll get a “Client in distress” warning and the client status remains at “INIT”. Also, the “Warning: PB Server running old version…” warning now gets spammed by the client every few seconds, because it repeatedly gets a command from the server to switch to the older version, but it fails the checksum test every time. After a few minutes, the client gets kicked for failing to “update” (actually: downgrade) properly.
So, if the server is running an old version of the PB client or anticheat files and the client does not have the corresponding MD5 checksums in its pbcl.db file, the client will get kicked if he doesn’t use the “\pb_security 0” workaround.
Moral of the story: never, ever, delete your pbcl.db file. Make a backup copy if you need to reinstall ET.
I hope this clears things up.
Cheers.
Ok Lekdevil, thanks for that informative post. One question, does this pbcl.db file get replaced when you re-install ET?
The reason I ask, recently I was clearing out a load of .pk3 files from etmain and like an idiot I deleted one of the .pk3’s that come with ET, so ET wouldn’t run at all. So I re-installed ET (having also emptied the Recycle Bin before noticing) and the 1.02 patch, and then ran pbweb.exe in my /pb folder.
The last update to PB has occured since then, and, as always, I got the “Server running old version” message on my Clan’s server, which never auto-updates. However, I still didn’t get kicked, or get the message more than once, just as I’ve come to expect.
Would this be because the pbcl.db file in the /pb folder was still there from the previous ET installtion, and didn’t get replaced when I re-installed? Or maybe pbweb.exe updated it appropriately so that in effect it behaved as you describe even though I’d just re-installed ET?
Either way, I’m happy to stand corrected when the facts are presented. At least you’ve explained the situation rather than simply pointing to an out of date web page and then, ludicrously, refering to the date stamp on a complete separate web page as evidence of the 1st’s authenticity.
For future reference, the .pk3 files that come with ET are
pak0.pk3
pak1.pk3
mp_bin.pk3
I would guess that et install just doesn’t overwrite the pbcl.db
Note that IRON_TROLLs post, even to the extent is was correct, had nothing to do with pb admin requirement which was the topic of this thread. That ‘server is running old version’ thing crops up every time pb updates the server component.
Yeah, I know that now But one of them is very small, and I was clearing out all those pesky little .pk3’s that end up on your hard drive from visiting servers with custom Campaigns, etc.
No, it doesn’t, unless you delete it manually or delete the entire “pb” directory first. A reinstall of ET (or just the PB components) will only replace the pbsv.dll, pbcl.dll and pbag.dll files.
HTH.
So that’s why I’ve never had this problem then, and neither have my Clan-mates or other Clan players, we’ve all been playing ET for a long time our pbcl.db files contain all the appropriate information to allow us to play on servers running slightly out of date versions of PB. Thanks Lekdevil, always happy to be owned by someone who knows what they’re talking about! 