[yzybb]

Hello, Silvers. Can it be prioritized to attack the first place? Doing so can slow down teammates in the front, and also allow teammates in the back to better keep up with the team. please.

[hefiwhfcds2]

Will a tank attack conflict with this plugin?它看起来具备些相似的功能
https://forums.alliedmods.net/showthread.php?t=334690

[Silvers]

Originally Posted by yzybb Hello, Silvers. Can it be prioritized to attack the first place? Doing so can slow down teammates in the front, and also allow teammates in the back to better keep up with the team. please.

Done.

Originally Posted by hefiwhfcds2 Will a tank attack conflict with this plugin?它看起来具备些相似的功能 https://forums.alliedmods.net/showthread.php?t=334690

Looks like they are compatible.

[moschinovac]

When setting like this

"tank"
	{
		"order"		"7,8" 
		"pinned"	"15"
		"incap"		"3"
		"voms"		"0"
		"voms2"		"0"
		"range"		"0.0"
		"wait"		"2.0"
		"last"		"1"
		"safe"		"1"
	}

The tank will always chase Lowest health survivors no matter how I attack him (even melee his back) but if set only order 7 without 8. Tank will priority Last Attacker as expected.

[knifeeeee]

PHP Code:

DirectorOptions <-
{
    SpecialInfectedAssault = 1
    cm_AggressiveSpecials = 1
} 


Does it affect plug-in performance or conflicts,I use this in coop.nut

At the same time, I found that sometimes monsters can be dazed, like Joceky

[Silvers]

Originally Posted by knifeeeee PHP Code: DirectorOptions <- {     SpecialInfectedAssault = 1     cm_AggressiveSpecials = 1 }  Does it affect plug-in performance or conflicts,I use this in coop.nut At the same time, I found that sometimes monsters can be dazed, like Joceky

No shouldn't be any conflict. Dazed would be unrelated to this plugin as this only does targeting.

2.18 (10-Aug-2022)
    - Added cvar "l4d_target_override_team" to specify which Survivor teams can be targeted.
    - Added option "dist" to the data config to set how close the Special Infected must be to a target to prevent changing target.
    - Added option "time" to the data config to set the duration of targeting the last attacker before being allowed to change target.
    - Fixed the wait time and last attacker interfering with selecting a new target. Thanks to "moschinovac" for reporting.

[axelnieves2012]

Hello Silvers, excellent work.
I have one question....
Is it possible add a new tag called "alreadyTargeted"?

It would be useful to prevent the Hunter steal Smoker's victims accidentally (sometimes it happens when both them attack the same survivor at the same time).
So if Smoker is already targeting someone, the Hunter will completelly ignore this survivor.

A new tag called "TanksRockTarget" would be nice too, because Tank's rock use to release survivors, because it takes some time throwing the rock, and he doesn't cancel his animation nor redirects his rock to another survivor.
So if somebody is being aimed by tank's rock, Smokers and Hunters will ignore them until Tank have thrown his rock.

[EDIT]
I also considered a new patch called "revivingSomeone" which will make Special Infected target a survivor that is helping another incapacitated one.

What do you think about this?

[Silvers]

2.19 (22-Sep-2022)
    - Added option "13" to "order" to target the Survivor furthest ahead in flow distance. Requested by "axelnieves2012".
    - Added option "targeted" to the data config to prevent targeting someone that's already targeted by another Special Infected. Requested by "axelnieves2012".

[Silvers]

2.20 (03-Oct-2022)
    - Added option "14" to target someone healing whose health is below "survivor_limp_health" cvar value. Added by "axelnieves2012".
    - Fixed order "12" and "13" being switched. Thanks to "axelnieves2012" for reporting.

[morzlee]

Is there any way to add the upper limit of survivors being selected as targeted on top of the targeted option, because the option will be harder to use if the server SI are more than 4.
If can, can you add a Native to other plugins to get whether the survivor has exceeded the targeted limit and a native to set targeted limit.
I already wrote my own plugin to implement it, but I don't know if there will be any conflict with target_override.
It would be better if can implement in same plugins.
SI_Target_limit