[yagura40977]

Originally Posted by Marttt He wants that the plugin displays common infected kills message in intervals (example: 5 in 5 minutes) And maybe in this interval print a summary from: *Total Special Infected Kill *Total Common Infected Kill *Friendly Fire Damage for each client and display it sorted by rank. This is what I understand.

yes


l4d2_kill_mvp.smx <=Calculated as the default kill

[axelnieves2012]

Originally Posted by Marttt He wants that the plugin displays common infected kills message in intervals (example: 5 in 5 minutes) And maybe in this interval print a summary from: *Total Special Infected Kill *Total Common Infected Kill *Friendly Fire Damage for each client and display it sorted by rank. This is what I understand.

Thanks for explanation. I will considerate it for next version.

[xy9860]

the Tank health is wrong in my server ,anybody can help me?

[axelnieves2012]

Originally Posted by xy9860 the Tank health is wrong in my server ,anybody can help me?

It is something I've got to fix. I think about two possible reasons:
1) Tank's health during burning.
2) Tank's incapacitation health.

When a Tank is dying, he loses health (set on z_tank_incapacitated_health "5000").

Could you please, set this value to 0 and tell me if something changed?

[strikeraot]

Can we remove damage from fire in this plugin? Just calculate Damages from weapon

[BloodyBlade]

This plugin does not compile on sm1.9?
I have this when compiling:
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0
exception thrown: abort("Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or (4) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0 "). Build with -s ASSERTIONS=1 for more info.

[Marttt]

Yes, it is compiling on 1.9

Are you trying to compile with spider?

I got the same error some days ago while using it to compile a plugin (is rare to occur, usually works),

As a workaround, I downloaded the SM 1.9 - build 6283

Then compile it with the spcomp.exe from the SM above.

[ReCreator]

L 02/01/2020 - 23:18:53: SourceMod error session started L 02/01/2020 - 23:18:53: Info (map "l4d_garage02_lots") (file "/home/server511/game/left4dead/addons/sourcemod/logs/errors_20200201.log") L 02/01/2020 - 23:18:53: [SM] MEMORY LEAK DETECTED IN PLUGIN (file "l4d_kills_manager.smx") L 02/01/2020 - 23:18:53: [SM] Unloading plugin to free 31557 handles. L 02/01/2020 - 23:18:53: [SM] Contact the author(s) of this plugin to correct this error. L 02/01/2020 - 23:18:53: -------------------------------------------------------------------------- L 02/01/2020 - 23:18:53: Type GameEvent | Count 31557 L 02/01/2020 - 23:18:53: -- Approximately 0 bytes of memory are in use by (31557) Handles. L 02/01/2020 - 23:18:53: [SM] Exception reported: Memory leak L 02/02/2020 - 00:00:45: Error log file session closed.

[axelnieves2012]

Originally Posted by strikeraot Can we remove damage from fire in this plugin? Just calculate Damages from weapon

I will do it. It was in my plans

[axelnieves2012]

Thanks for reporting. I've never seen this before