[NoroHime]

update

v1.2 code clean thanks "Dragokas", add feature: 1. normalize the regular boomer to male model 2. normal boomer chance to l4d1 model 3. option to set leaker movement speed multiplier; 1-19-22 PHP Code: // if boomer is not leaker, normalize it to male boomer model leaker_normalize_model "1" // if normalize model, chance to set l4d1 boomer, 0: disable l4d1 model // Minimum: "0.000000" // Maximum: "100.000000" leaker_normalize_l4d1_chance "50" // leaker movement speed multiplier, -1: game default, 0: cant move, 2: double speed, etc.. leaker_speed "-1"

[NoroHime]

Originally Posted by HarryPotter Very good plugin, I really like leaker boomer. However I feel a little confusing, hard to tell this is boomer or leaker immediately. Maybe you can add the Flashlight or the hat attached to leaker boomer body, even simpler, make leaker boomer move faster or change the opacity of the leaker boomer to become closer to invisible. I suggest spit "leaker_chance" convar into two for people who don't like to play leaker boomer. PHP Code: //Real player leaker boomer chane "leaker_chance_real" //AI player leaker boomer chane "leaker_chance_AI"  and better reset convar OnPluginEnd() PHP Code: public void OnPluginEnd() //trigger when plugin unloads {     ResetConVar(FindConVar("boomer_leaker_chance")); }

yea, for model point, i have better solution normalize they model, for chance spawn, i wasnt idea to control.. just control by game convar, now can config speed

[NoroHime]

Originally Posted by Psyk0tik You misinterpreted what Dragokas meant. IsClientInGame() includes IsClientConnected(), so you need to remove IsClientConnected() and keep IsClientInGame() instead.

lol im writing then see you post, thanks you all, my english actually poop

[NoroHime]

update

v1.2.1 Leaker spawn reset after plugin unload, suggestion from "HarryPotter"; 1-21-22

[NoroHime]

Originally Posted by Dragokas I decided to overview a code a little bit. 1. Leaker_boomette - missing ConVar hook. 2. IsClientConnected is already include IsClientInGame, so the first one is redundant. Also, the last already guarantee that the client is valid, no IsValidEntity is required. 3. What is sense? Is that means double health decreasing (since the health already been decreased by that "damage" amount after hook finishes) ? In such case more "academic" would be damage *= 2.0 and return Plugin_Changed. 4. Also, executing AutoExecConfig after ConVar hook is set - is less effective, because in such case AutoExecConfig raise the hook and the hook callback potentially will be always called at least once if config contains modified value. 5. It is no reason to call a callback on OnConfigsExecuted, because you already hooked all ConVars. Putting ApplyCvars() inside end of OnPluginStart() is more efficient.

today my catched, when server hibernating, controled game cvar reset to 0 and not be hook, when hook applyCvars on OnConfigsExecuted then problem gone, i think this should require

[Dragokas]

Originally Posted by NoroHime today my catched, when server hibernating, controled game cvar reset to 0 and not be hook, when hook applyCvars on OnConfigsExecuted then problem gone, i think this should require

Well, in such case it's up to you.

It's a game bug. My personal opinion, I don't think devs should include the fix in each plugin. Instead, the central solution should be applied. For same reason I introduced "convar_anomaly_roundstart" ConVar in my ConVars Anomaly Fixer. For those who doesn't use it, you surely right to re-read ConVars on each map start (on OnConfigsExecuted).

[NoroHime]

update

v1.3 option to specify bot chance, thanks "HarryPotter", now "Left 4 DHooks Direct" is required; 1-25-22 PHP Code: // specify bot chance for boomer leaker, -1: not specify, 100: bot boomer certainly as leaker // Minimum: "0.000000" // Maximum: "100.000000" leaker_chance_bot "-1"

[HarryPotter]

PHP Code:

CreateTimer(0.0, PostBackChance); 


in this case, you can use RequestFrame instead, better then 0.0 timer.

Originally Posted by Silvers RequestFrame: Spoiler CreateTimer() has a minimum value of 0.1 seconds. For anything quicker (e.g. the next game frame) it's better to use RequestFrame().

PHP Code:

        if(leaker_chance_bot >= luck) {
            boomer_leaker_chance.SetInt(100);
            //CreateTimer(0.0, PostBackChance);
            RequestFrame(OnNextFrame, _);
        }

public void OnNextFrame(any data)
{
    boomer_leaker_chance.SetInt(leaker_chance); //back chance to global
} 


[NoroHime]

Originally Posted by HarryPotter PHP Code: CreateTimer(0.0, PostBackChance);  in this case, you can use RequestFrame instead, better then 0.0 timer. PHP Code:         if(leaker_chance_bot >= luck) {             boomer_leaker_chance.SetInt(100);             //CreateTimer(0.0, PostBackChance);             RequestFrame(OnNextFrame, _);         } public void OnNextFrame(any data) {     boomer_leaker_chance.SetInt(leaker_chance); //back chance to global }

yea thanks, in my past developing experience, instant timer use for async call

update

v1.3.1 improve better bot chance, thanks "HarryPotter"; 1-25-22

[NoroHime]

update

v1.3.2 1. fix issue 'some very rare cases when keep taking damage to dead leaker cause loop death', 2. fix issue 'wrong cvar bounds cause bot chance cant set -1', 3. fake event now support death position, 4. optional 'restrict only survivor can take damage to leaker'; 2-16-22 v1.3.3 now plugin can compile online, but bot chance specify feature still require 'Left 4 DHooks Direct'; 2-16-22 PHP Code: // restrict Leaker can survivor take damage only leaker_restrict_survivor "1"

seems event forwarding receive is safe to reference so plugin no needed attach .smx file, if your L4DD available then bot specifies work automatically