[Dr. McKay]

This "fixes" the exploit that allows players to heal other players at any distance and also allows the heal target to retain unlimited ubercharge. This is the same exploit fixed in this plugin, but instead of blocking it, this plugin kicks/bans the medic so as to get rid of the troublemaker permanently. This plugin also does not rely on gamedata.

ConVars:

• infinite_uber_ban_length (def. 43200 [30 days]) - time in minutes to ban people who are caught abusing the exploit (0 = permanent, -1 = kick only)
• infinite_uber_message (def. "Healing exploit detected") - message to show when kicking/banning
• infinite_uber_num_detections (def. 30) - number of times the medic has to respawn within infinite_uber_spam_time seconds before triggering a kick/ban
• infinite_uber_spam_time (def. 2) - time in seconds between spawns in order to consider the client abusive (infinite_uber_num_detections spawns this close together are required to take action)

The defaults should be fine for pretty much everyone.

If you have SourceBans installed, it will use SourceBans. Otherwise the default ban method will be used.

[ddhoward]

I like yours better than mine. Does this prevent the ubercharge from staying once the medic is kicked/banned? I have had issues with perma-uber in the past when dealing with mediguns and disconnecting medics.

EDIT: Your plugin will, in fact, result in the healing target continuing to be healed and ubercharged when the medic disconnects. The uber will last until he dies/respawns, and the healing will last until he disconnects, even if he changes teams. Preventing this is the main reason that I opted to use the SDKCall & gamedata. Didn't even think about kicking/banning the people IN ADDITION TO stopping the healing lol. Wrote mine in a hurry, I was running late for work.

[Dr. McKay]

It will now slay the medic and wait a few seconds before kicking/banning them, allowing the uber time to fade.

[ddhoward]

The medic dying doesn't seem to actually be making the ubercharge fade, nor stop the perma-healing. :\ I have no idea why not.
EDIT: Never mind, I'm an idiot. Another plugin was conflicting with it.

It's still possible to begin the exploit again after the slay and before the kick (thus granting the healing target endless healing), but it would require some really fast action on the medic's part, especially if the server doesn't do instant respawns (and by instant, I mean that they are hooking player_death and calling TF2_RespawnPlayer). And he'd only get one shot at it... Perhaps checking the medigun's m_hHealingTarget the moment before the kick and doing ClientCommand retry on the target (if one exists) might be a good idea.

[Mitchell]

If this ever gets patch you could just remove the check for medic and this could be a fix on it's own for players that switch classes constantly spamming the events.

[ddhoward]

The game doesn't seem to allow you to switch classes that fast. I think the fastest is once per .75 seconds or something. This exploit involves changing loadout, not class.

But yes, it can still be irritating depending on what sort of plugins you have doing stuff on player_spawn.

[Dr. McKay]

Another update. Fixes this:

[Dr. Greg House]

Update: http://forums.steampowered.com/forum....php?t=3224059
Seems Valve has fixed this.

[ddhoward]

The Valve fix only works if the player was being ubered at the time. This does not stop the eternal healing if the exploiter didn't go for an uber.

Requesting un-un-approval for both of the plugins I guess.

[PolyQuad]

Does anyone think they are experiencing any false positives with this? I have seen a few bans with people who claim they have no idea what happened, but I am not sure if I believe them.