[aSmig]

This plugin stops Reliable Channel Overflows by kicking and optionally banning clients who flood the server with commands that generate a text response. A flood is defined here as more than 3 commands with less than a 5 second gap between each. This stops the annoying "Client X overflowed reliable channel" attack. When a client triggers this plugin, their name and SteamID are printed in the chat area for all to see. If you do not set any of the cvars, the default action is to permenantly ban attackers by SteamID. If you don't want to ban people, or would like to ban them for a short time, set the appropriate cvars in server.cfg as defined in the ConVars section below.

Based on block_crash by Viper2026 for EventScripts. If you use EventScripts on your server already, check out block_crash.

Commands:

• none

ConVars:

• stoprco_version
  • The current version of StopRCO. This is read-only and is provided for HLSW and other 3rd party applications.
• stoprco_ban (default 1)
  • Set to 1 if offenders should be banned.
• stoprco_bantime (default 0)
  • Set to the number of minutes to ban for (0 is forever)

Installation:

• From .smx
  • Download StopRCO.smx by using the "Get Plugin" link below. Place StopRCO.smx in your addons/sourcemod/plugins directory. Set cvars in server.cfg if you like.

Changelog:

• 0.1.0
  • Initial testing.
• 1.0.0
  • First release.
• 1.0.1
  • Fixed "Invalid timer handle" errors.
• 1.0.2
  • Fixed "Client index 0 is invalid" via rcon errors.
  • Added sm_timeleft, sm_nextmap, ping, and status.

Thanks to CShadowRun, Viper2026 and #sourcemod.

[KyleS]

This works great! Banned one moronic spammer from my server.

Andy50 - STEAM_0:1:23720677

[zeroibis]

Had an exploiter on the server last night, put this plugin on the server really fast and bam! There ass was banned

[bobbobagan]

You missed a few commands.

Like ff, sm_timeleft, sm_nextmap

Also, is there support for SourceBans?

[zeroibis]

My error logs are all filled with this:

L 08/24/2009 - 12:49:00: SourceMod error session started L 08/24/2009 - 12:49:00: Info (map "de_dust") (file "errors_20090824.log") L 08/24/2009 - 12:49:00: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 12:49:00: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 12:49:00: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 12:49:15: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 12:49:15: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 12:49:15: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 12:50:20: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 12:50:20: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 12:50:20: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 12:53:44: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 12:53:44: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 12:53:44: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:00:26: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:00:26: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:00:26: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:009: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:009: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:009: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:009: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:009: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:009: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:00:53: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:00:53: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:00:53: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:02:46: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:02:46: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:02:46: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:03:03: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:03:03: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:03:03: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:03:09: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:03:09: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:03:09: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:034: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:034: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:034: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:03:41: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:03:41: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:03:41: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:06:42: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:06:42: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:06:42: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:07:13: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:07:13: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:07:13: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:07:44: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:07:44: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:07:44: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: [SM] Native "KillTimer" reported: Invalid timer handle 0 (error 4) L 08/24/2009 - 13:08:24: [SM] Displaying call stack trace for plugin "StopRCO.smx": L 08/24/2009 - 13:08:24: [SM] [0] Line 37, /home/groups/alliedmodders/forums/files/4/3/7/9/3/43362.attach::OnClientDisconnect_Post() L 08/24/2009 - 13:08:24: Error log file session closed.

[Kigen]

Ya, you need more accurate checks on your handles.

Handles are fairly annoying and just to note KillTimers does not close the handle, it just stops the timer.

You need to change KillTimers to CloseHandle and also check if the handle has been defined and when the timer is executed empty it.

Handles are is a lot of fun. *sarcasm*

[aSmig]

Originally Posted by bobbobagan You missed a few commands. Like ff, sm_timeleft, sm_nextmap Also, is there support for SourceBans?

I'm only responding to console commands. The ones you listed are chat commands. You should have another plugin do spam control for chat stuff. As for SourceBans, I haven't added support for that but certainly could. It isn't something I have worked with before. Look for this in a future version.

In other news, the "Invalid timer handle" errors are now fixed. Thanks for the tips, Kigen.

[psychonic]

Originally Posted by Kigen You need to change KillTimers to CloseHandle and also check if the handle has been defined and when the timer is executed empty it.

Is the api documentation incorrect? For KillTimer(), it says "Use this instead of CloseHandle() if you need more options."

[Kigen]

Indeed, it says "Use this instead of CloseHandle() if you need more options." Which in your case I'm assuming you don't need more options since you are just planning to kill the timer and discard it, CloseHandle() will do all of that.

[Dragonshadow]

Originally Posted by aSmig I'm only responding to console commands. The ones you listed are chat commands. You should have another plugin do spam control for chat stuff. As for SourceBans, I haven't added support for that but certainly could. It isn't something I have worked with before. Look for this in a future version. In other news, the "Invalid timer handle" errors are now fixed. Thanks for the tips, Kigen.

sm_timeleft and sm_nextmap are console commands.