AlliedModders - [L4D2] Timed Button Distance Exploit Fix [v1.0.1

AlliedModders (https://forums.alliedmods.net/index.php)

- Plugins (https://forums.alliedmods.net/forumdisplay.php?f=108)

- - [L4D2] Timed Button Distance Exploit Fix [v1.0.1 | 15-January-2023] (https://forums.alliedmods.net/showthread.php?t=341119)

[L4D2] Timed Button Distance Exploit Fix [v1.0.1 | 15-January-2023]

L4D2 ONLY

In L4D1 this exploit doesn't work, so this plugin isn't necessary.

Description

Resets the button progress bar when the activator distance exceeds the maximum allowed. (96, defined by the player_use_radius cvar)

More useful for versus servers.

Exploit often done in the first chapter of L4D2 Sacrifice (c7m1_docks), which gives the activator some advantage as the survivor position is harder to be hit.

Steps to Reproduce

Spoiler

Cvars

A configuration file named "l4d2_timedbutton_dist_fix.cfg" will automatically be created for you upon the first run in the "\cfg\sourcemod\" folder.

PHP Code:


		
			
// Enable/Disable the plugin.

// 0 = Disable, 1 = Enable.

// -

// Default: "1"

// Minimum: "0.000000"

// Maximum: "1.000000"

l4d2_timedbutton_dist_fix_enable "1"

Related Game Cvars

player_use_radius => Maximum radius for a player to be able to trigger the "USE" functions. (default: 96)

Admin Commands

sm_print_cvars_l4d2_timedbutton_dist_fix => Print the plugin related cvars and their respective values to the console. (z flag required)

Change Log

Spoiler

Notes

The radius check still isn't 100% accurate according to the game core logic, because it does several checks, but is better than vanilla behavior. (search for: CBasePlayer::FindUseEntity())

Thank you!

Shao - for reporting a bug where the plugin wasn't working with non-solid buttons.

Related Plugins

[L4D2] Healing Distance Exploit Fix by Marttt

Post Reply

Any feedback, bug reports, fixes, improvements, translations or suggestions for the plugin are welcome.

Installation

Put the "l4d2_timedbutton_dist_fix.smx" file (click Get Plugin) in your "\addons\sourcemod\plugins\" folder.

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.0 | 01-January-2023]

Does it also apply when the survivor tries to heal teammate but distance exceeds the maximum allowed.
For example, being healed while climbing the ladder or being healed while tank punch.

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.0 | 01-January-2023]

Quote:

Originally Posted by HarryPotter (Post 2796381)

Does it also apply when the survivor tries to heal teammate but distance exceeds the maximum allowed.
For example, being healed while climbing the ladder or being healed while tank punch.

Released another plugin for that case as well.

[L4D1 & L4D2] Healing Distance Exploit Fix by Marttt

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.0 | 01-January-2023]

Quote:

Originally Posted by Marttt (Post 2796382)

Released another plugin for that case as well.

[L4D1 & L4D2] Healing Distance Exploit Fix by Marttt

Well done:)

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.0 | 01-January-2023]

This plugin interferes with https://forums.alliedmods.net/showthread.php?p=2780813 somehow. It causes survivors to t-pose and the progress bar to not appear.

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.1 | 15-January-2023]

Thanks for reporting @Shao.

Plugin updated (1.0.1)

Code:

1.0.1 (15-February-2023)

    - Fixed plugin not working with non-solid buttons. (thanks "Shao" for reporting)

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.1 | 15-January-2023]

Timed Button Distance Exploit Fix plugin is one of my favorite plugins. I like to use it because I can easily reset the button progress bar when the activator distance exceeds the maximum allowed. I found this plugin by mistake. Because I was actually searching for the https://www.torontomike.com/2022/11/...-plagiarizing/ website because I want to know how to summarize an article without plagiarizing. When I was looking for it on google search, I found your post link.

Re: [L4D2] Timed Button Distance Exploit Fix [v1.0.1 | 15-January-2023]

Seems like it conflicts with the barricade plugin, removing the plugin fixes the weird conflict.