[Encryption]

Ahh, looks like we need an update then

My ocd is killing me about it! =\

[Jamster]

Go right to the bottom of the code and remove the disconnect code. Compile, upload, done. Also, I think it's still a problem in older engines, though doing an engine check should be easy enough as to whether it should strip out the reason or not.

[Encryption]

Manually set it myself just edit the event from "" to "Disconnect by user."

[bobdole]

there may still be a vary small problem in older engines but they are mostly safe. the main reason CSS was so infected with the exploit use due to LSS allowing them to do it. However LSS no longer does it therefor only those knowledgeable in C++ is able to do it in old engines.

[dataviruset]

Originally Posted by Encryption Manually set it myself just edit the event from "" to "Disconnect by user."

Then there won't be any difference in messages, sometimes it's timeout, etc.
The best would be to check if the game engine is orange box and strip the disconnect message if it isn't.

[Jamster]

Here we go, I think this will work, I gather enough people are wanting this, hah. Feel free to use devicenull.

[Jamster]

Originally Posted by bobbobagan For anyone that doesn't know how... I removed that hidden character, saved it as UTF-8 as suggested by psychonic and applied that bug as mentioned by Nalidor above. See attached...

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

[SilentBr]

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

Jamster. Is this version OK with TF2? About that bug of respawn.

Thanks

[sinblaster]

jamster whats the difference in your addition?

[Sillium]

@SilentBr: Looking at the code I'd say: Yes

@sinblaster: If the engine is "new enough" the disconnect messages will be shown again