Addon Details

Watch - Add Favorite

Does this version work for you?

block_crash (for reliable channel overflowed exploit) - Version 1.2

posted on 2008-11-24 12:11:35
by Viper2026


Hack-ish workaround to prevent people from dropping clients on your server via the reliable channel overflow exploit. Please read the comments at the top of the file for important information regarding operating system and srcds plugin configurations!


******************************** (You should be able to simply extract the contents of this .zip archive into your cstrike directory, and the files will all go where they need to) ******************************** PLEASE NOTE: This code is python and is for use with eventscripts 2.0+, this is NOT an eventscripts classic script To use this script, make a folder in your \cstrike\addons\eventscripts directory called block_crash then inside of that new folder (\cstrike\addons\eventscripts\block_crash), move To use it, simply add "es_load block_crash" to your autoexec.cfg or whatever method you use to load scripts

Version Notes For 1.2

Updated on: 2009-03-06 01:23:29 EST by Viper2026 (View Zip Contents)
I've added a few more lines, specifically some es.regsaycmd's to cover additional vulnerable mani commands. People were getting clever and starting to use things like alias spam "say @timeleft; say @nextmap" but the main functionality is still the same. I also removed a few old comments, made some very minor code changes, and lowered the "tolerance threshold" from 5 to 3 before someone is kicked; it seems to catch people slightly more quickly this way and leads to less server lag and chat output spam. Additionally, it will now also print the name and steamid of people who are kicked by the script; not just the name as was the case before. I realize that it usually spams the hell out of the chat area when it kicks someone, but I honestly think it's a nice side effect so you don't need to go looking too hard to find out who's just been pwnd :) (This 2nd upload is just fixing an outdated web address in the comments)

( Previous Versions )