update buged the rcbot Options

[Knight]

the new update buged the rcbot --'
when I enter the team fortress 2 and attempt to carry this message appears
Unable to load plugin "../bin/hpb_bot2"
So I ask you aconcertem the bug and the bug that when loading in the server name server bugs

[Doc Lithius]

Actually, here's the whole story:
In yesterday's first update, VALVe decided it would be a good idea to make it so only plugins they approve of and digitally sign would be able to be loaded into any VALVe Anti-Cheat (VAC) secure game ("Disabled clients loading server plug-ins unless the plug-ins are signed by Steam or the client is running in insecure mode."), be it dedicated or listen server. They did this (presumably) to stop certain people from using certain plugins which give them an actual edge over other players (no-wall hacks, idle server plugins, etc.), but as mentioned, this only applied to VAC secure servers.
The backlash? Perfectly innocent plugins such as RCBot2 and Mani Admin Plug-In were blocked from being used until they got the thumbs-up from the powers that be from VALVe. (As present time, VALVe is not giving a certification to Mani Admin Plug-in. Cheeseh will have to give word as to the fate of RCBot2.) Also, a number of game clients were no longer able to start Team Fortress 2. Even game clients which were fresh out-of-the-box installations were effected, apparently. So, later yesterday, VALVe disabled this security feature. ("Disabled signature checking to determine if it's the source of some reported launch issues")

As of right now, there's no word if this lockdown of unsigned plugins is going to be put back into place, but I'd like to point out that even if it is, this is not the end of RCBot2. As stated above, this and other plugins will still work on insecure, non-VAC servers. The problem is...I have no idea how to disable VAC on my listen server. I didn't get the chance to test if this lockdown affects LAN servers, either, so... But yeah, it's not as bad as you think, folks.