[retsam]

So, is that disconnect exploit fixed now? I havnt even been paying attention lately.

Also Jamster:

Originally Posted by Jamster DAMN, I forgot about this, applied also to my version. Sorry about that guys. ;-;

What all is changed in that version? Is that your own or something? I notice some things changed from the official one...For the disconnect part. You could improve that by just not even hooking the disconnect if the engine is "new". Not sure the point even doing the bool check, just dont hook it?

[psychonic]

Originally Posted by retsam So, is that disconnect exploit fixed now? I havnt even been paying attention lately.

Yes on some engines, no on others.

[Jamster]

Originally Posted by retsam So, is that disconnect exploit fixed now? I havnt even been paying attention lately. Also Jamster: What all is changed in that version? Is that your own or something? I notice some things changed from the official one...For the disconnect part. You could improve that by just not even hooking the disconnect if the engine is "new". Not sure the point even doing the bool check, just dont hook it?

Good point, lol. I'm dumb.

Ideally I'd do what KAC does and actually check the string to see if it needs blocking too. I guess it is resource light though.

[psychonic]

Originally Posted by Jamster Good point, lol. I'm dumb. Ideally I'd do what KAC does and actually check the string to see if it needs blocking too. I guess it is resource light though.

PHP Code:

if (GuessSDKVersion() < SOURCE_SDK_EPISODE2) 


That will only catch ep1.

It was only fixed in ep2v and with an optional ep1 update. That still leaves ep2, l4d, and l4d2.

Also, I don't think KAC's method fully stops it. Last I checked, KAC only checked the length of the message.

[Jamster]

Ah, thanks psychonic, I will update that, so essentially if it's not the ep2v engine I want to hook it, just in case since the ep1 fix is completely optional.

[retsam]

Hum ok. So I guess I need to update mine too.

[sinblaster]

Thanks for that answer sillium I appreciate it, but as the conversation has gone very technical I am lost, can someone please define If the engine is "new enough"

I suppose if I haven't got any problems at the moment I should just stay with the plug on the first post.

[dataviruset]

The plugin in the first post works, but it's a little bit pessimistic about the so called "disconnect messages".
Jamsters latest version is a bit better...

[Jamster]

The original still has the TF2 respawn bug too.

[Cerobug]

I have a rcon_lock.cfg in my addons/sourcemod/configs folder and its still recording every command to a log file.