[olj]

Originally Posted by Skorpion1976 hm... I am tired... long day in office... I changed my post while you wrote your answer...so I have to ask again XDD (final question, believe me): A player as a hunter which is burning does extra damage to the victim, in versus, . Right or not ?

Yes, sir Burning hunter does damage to victim in versus.

[Skorpion1976]

*sigh with relief*
So the code line containing "...(HP-1) I can change to "HP-3" which means every time a damage takes place this 3 HP get subtracted extra from the current HP from the victim. Correct, too ?

[olj]

Redownload 1.3 version. I made a mistake there , forgot to return damage to 1, lolz.

[olj]

Yes you can edit this one, unless i add cvar damage. Im relly tired today. You need to change following:

line 108:

PHP Code:

if (HP>Your value Here) SetEntProp(victim, Prop_Send, "m_iHealth", (HP-Your value Here)); 


line 111:

PHP Code:

 if ((HP<=Your value Here) && (tempHP>Your value Here)) 


line:113

PHP Code:

 new Float:damagefloat = Your value Here (float type); 


[Skorpion1976]

Thanks!
I found this strange behaviour: I entered "(HP-20)" on line 108 and made a test:

I kicked all bots except 1.
Bot has 100 HP.
I was a hunter and on fire (no cheats on !!) and pounced the bot.
The bot did NOT go down in the moment of 0 HP but: all of a sudden the HP bar was full again and from now on the bot is invulnerable, no HP loss possible, not even from normal infected. Godbot! Same result with survivor upgrades on, where I activated the "hotmeal" (150 hp).
It seems there is a boundary for the value that can be subtracted from the HP ? Someone was writing about self-reviving bots which I also had in my games so far. Maybe it´s an ingame feature preventing the bot from getting incap due to rapid HP loss ? I dunno.

I tried "1", "3" and they work fine so it´s not a big issue at all. I wouldn´t go higher as I already have the hunter pounce damage set to 6 so it´s evil enough now.

[olj]

Anyway, grab last version, i added cvars to control damage, now its easier to use. Take a note, there are separate ones for temp hp and hard hp.

[Whosat]

L 08/22/2009 - 01:070: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:070: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:070: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:070: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:071: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:071: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:071: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:071: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:072: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:072: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:072: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:072: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:072: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:072: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:072: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:072: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:073: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:073: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:073: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:073: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:074: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:074: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:074: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:074: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:074: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:074: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:074: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:074: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:075: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:075: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:075: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:075: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:076: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:076: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:076: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:076: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:077: [SM] Native "GetEntDataFloat" reported: Entity 6 is invalid L 08/22/2009 - 01:077: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:077: [SM] [0] Line 156, l4d_brutal_hunter_mod 1.4 .sp::IsPlayerBurning() L 08/22/2009 - 01:077: [SM] [1] Line 117, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction()

I just checked server logs today, wasn't in the game so can't help much with what the entity was.
Oh and.... This was coming at like 5 errors per second.
Snippet:

L 08/22/2009 - 02:02:00: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:00: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:00: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:00: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:00: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:00: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:01: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:01: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:01: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:02: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:02: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:02: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:02: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:02: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:02: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:03: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:03: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:03: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:04: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:04: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:04: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:05: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:05: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:05: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 02:02:05: [SM] Native "KillTimer" reported: Invalid timer handle d51701b9 (error 3) L 08/22/2009 - 02:02:05: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 02:02:05: [SM] [0] Line 108, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction()

Started from

L 08/22/2009 - 01:575: [SM] Native "KillTimer" reported: Invalid timer handle d3270169 (error 3) L 08/22/2009 - 01:575: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:575: [SM] [0] Line 113, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction() L 08/22/2009 - 01:576: [SM] Native "KillTimer" reported: Invalid timer handle d3270169 (error 3) L 08/22/2009 - 01:576: [SM] Displaying call stack trace for plugin "l4d_brutal_hunter_mod 1.4 .smx": L 08/22/2009 - 01:576: [SM] [0] Line 113, l4d_brutal_hunter_mod 1.4 .sp::BonusDmgTimerFunction()

[olj]

Thanx. Try to fix this.

P.S. Retarded timers.

[olj]

Ok, grab new version. Hopefully fixed errors spamming, and added message how many bonus damage was done to victim. Works nice for me.

[Whosat]

Grabbed it. Gonna let it run for a while before I check for errors. Yesterday my server ran about 4 hours before the errors came.